Actions
Bug #4735
closedsms.db is created in cwd, which from systemd's point of view is /
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
08/28/2020
Due date:
% Done:
100%
Resolution:
Spec Reference:
Description
On a Debian system, I noticed sms.db being created in the file system root.
- The -l flag exists to specify the database name, this could be added to the default service file that we ship with the package.
- We could use the vty to configure the database path.
We would prefer to move away from command line options. So therefore the db path should be added as a vty config option.
Another alternative from the systemd POV might be to use WorkingDriectory= but this might interfere with core dump files locations?
Related issues
Updated by keith over 3 years ago
NOTE: osmo-hlr uses the -l flag in the systemd.service file to specify the database location.
If we resolve this issue by moving the db location config to the vty/config file then the same should probably be done for the osmo-hlr.
Updated by keith over 3 years ago
Patch Merged to configure the database path from the vty/config
https://gerrit.osmocom.org/#/c/osmo-msc/+/19875/
Updated by keith over 3 years ago
- Status changed from Resolved to Closed
- % Done changed from 90 to 100
Updated by keith over 3 years ago
- Related to Bug #4821: Update working dir in systemd unit files added
Actions