railcontrol for Debian
---------------------

Known limitation 1:
If you consider to start and stop railcontrol by a systemd service, there's an
issue with stdin being /dev/null inside a systemd service environment.

Workaround: Add the --daemonize option to railcontrol, this will stop it trying
to read from /dev/stdin.

[…]
[Service]
ExecStart=/usr/bin/railcontrol --daemonize […]
Type=forking
[…]

Known limitation 2:
Prepending paths to <file> in 'dbfilename = <file>' breaks the cleanup of option
'dbkeepbackups'.

Workaround: Do not prepand any path to 'dbfilename'. Set a working directory for
the process where the database file (and also log file) will be kept. Add the
WorkingDirectory= option to a systemd service file as one possible solution:

[…]
[Service]
WorkingDirectory=/home/myuser/railcontrol
ExecStart=/usr/bin/railcontrol --daemonize […]
Type=forking
[…]

Debian specific dynamic linking:
While the source package of railcontrol includes code copies of SQLite and zlib
(details are documented in README.source), the binary package does NOT include
those. The binary package is linked against the system libsqlite and system
zlib1g packages.

 -- Bruno Kleinert <fuddl@debian.org>  Fri, 31 May 2024 09:38:38 +0200
