Project

General

Profile

Actions

Bug #4821

closed

Update working dir in systemd unit files

Added by keith over 3 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
10/20/2020
Due date:
% Done:

100%

Spec Reference:

Description

For services running from systemd, we should add WorkingDirectory= directives

Some services may create files in CWD on startup.
This can be overridden by configuration directives, for example gtp state-dir in osmo-{sgsn|ggsn}

These directive should be deprecated/hidden in the future.


Related issues

Related to Cellular Network Infrastructure - Feature #4107: Start systemd services as non-root userStalledosmith07/15/2019

Actions
Related to OsmoSGSN - Bug #4820: gsn_restart is created in CWDResolvedkeith10/19/202010/20/2020

Actions
Related to OsmoMSC - Bug #4735: sms.db is created in cwd, which from systemd's point of view is /Closed08/28/2020

Actions
Related to OsmoMSC - Bug #5661: sms.db files not in proper directory / backtrace on old sms.dbResolvedmsuraev08/24/2022

Actions
Actions #1

Updated by keith over 3 years ago

  • Related to Feature #4107: Start systemd services as non-root user added
Actions #2

Updated by keith over 3 years ago

  • Related to Bug #4820: gsn_restart is created in CWD added
Actions #3

Updated by keith over 3 years ago

  • Related to Bug #4735: sms.db is created in cwd, which from systemd's point of view is / added
Actions #4

Updated by laforge about 3 years ago

  • Assignee changed from 513583 to osmith
Actions #5

Updated by fixeria over 1 year ago

  • Related to Bug #5661: sms.db files not in proper directory / backtrace on old sms.db added
Actions #6

Updated by laforge over 1 year ago

  • Assignee changed from osmith to msuraev
Actions #8

Updated by msuraev over 1 year ago

  • % Done changed from 0 to 60

To make sure no project is left behind let's summarize the current state

Repo Service Status
osmo-hlr osmo-hlr merged
osmo-ggsn osmo-ggsn merged
osmo-msc osmo-msc merged
osmo-gbproxy osmo-gbproxy merged
osmo-bsc osmo-bsc merged
osmo-mgw osmo-mgw merged
osmo-sgsn osmo-sgsn merged
osmo-sgsn osmo-gtphub merged
osmo-hnbgw osmo-hnbgw merged
osmo-hnodeb osmo-hnodeb merged
osmo-upf osmo-upf merged
osmo-cbc osmo-cbc merged
libosmo-sccp osmo-stp merged
osmo-bts *-mgr merged
osmo-bts osmo-bts-* merged
osmo-pcu osmo-pcu merged
osmo-trx osmo-trx-* merged
osmo-pcap osmo-pcap-* merged
osmo-smlc osmo-smlc merged
osmo-sip-connector osmo-sip-connector merged
osmo-python-tests osmo-ctrl2cgi WONTFIX
osmo-python-tests osmo-trap2cgi WONTFIX

Have I missed anything?

Actions #9

Updated by msuraev over 1 year ago

  • % Done changed from 60 to 90

Do I need to update osmo-*2cgi from osmo-python-tests as well? Are they still in use?

Actions #10

Updated by msuraev over 1 year ago

  • Status changed from In Progress to Stalled
Actions #11

Updated by laforge over 1 year ago

No need to update those cgi scripts, IMHO.

Actions #12

Updated by msuraev over 1 year ago

  • Status changed from Stalled to Resolved
  • % Done changed from 90 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)