Set working directory in systemd service file

By default systemd will execute service with root directory (or home directory for user instance) which might result in
attempts to create files in unexpected place. Let's set it to 'osmocom' subdir of state directory (/var/lib for system instance) instead.

Related: OS#4821
Change-Id: I5117ab8d7b8542a161f69a9784a9667bda599473
1 file changed
tree: 28647580aa56a0dd6dd36613c2e00e22cab1f854
  1. contrib/
  2. debian/
  3. doc/
  4. include/
  5. m4/
  6. src/
  7. tests/
  8. .gitignore
  9. .gitreview
  10. .mailmap
  11. AUTHORS
  12. configure.ac
  13. COPYING
  14. git-version-gen
  15. Makefile.am
  16. osmoappdesc.py
  17. README.md
  18. README.vty-tests
  19. TODO-RELEASE
README.md

About osmo-gbproxy

osmo-gbproxy is a proxy for the Gb interface within the 3GPP GERAN (GPRS/EDGE RAN) architecture. It is part of the Osmocom Open Source Mobile Communications projects.

It allows you to aggregate many Gb links/connections into one. It also has the ability to convert between different Gb interface protocol stacking, such as from Gb-over-FrameRelay to Gb-over-IP.

Until 2021 it used to be part of the osmo-sgsn git repository, and before that (until 2017) part of openbsc.git

Homepage and Issue Tracker

Find the issue tracker and wiki online at https://osmocom.org/projects/osmo-gbproxy and https://osmocom.org/projects/osmo-gbproxy/wiki, respectively.

Documentation

You can find the user manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-usermanual.pdf and the VTY reference manual at https://ftp.osmocom.org/docs/latest/osmogbproxy-vty-reference.pdf.