-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi all,
I've got a silly question regarding systemd.
I'm currently writing a data collection software package which pulls
data from various sources and provides a real-time and historical data
interface for trending and analysis. Basically the data-gathering
guts of a SCADA system.
The system is built on the Unix philosophy, so each communications
driver and service runs as a separate process, communicating over
AMQP. So far so good.
I've used the OpenVPN init script as a template for creating my init
scripts, which allows me to not only start and stop all drivers, but
also start or stop an individual driver. e.g.
/etc/init.d/driver-service start foo
... much the same way you can start and stop individual OpenVPN
tunnels this way.
That works fine on Debian Wheezy, which uses sysvinit. Not so great
with Jessie on systemd. It seems the arguments after 'start' get
discarded somewhere. My only workaround has been to set
_SYSTEMCTL_SKIP_REDIRECT=1 in my environment (a big thank-you to the
people on this list who pointed this out to me), which then bypasses
systemd and permits the bash script to handle it.
Is there some way for the init script to tell systemd what subservices
are valid or do I have to maintain specialised scripts for systemd?
Regards,
- --
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iJ4EARMKAAYFAlXWSxQACgkQoCQEvFhlDPnTcAIAqOI7cMPhlQ8bpFp8mCcFQ/He
b6WTUJ8gw7sBzayQQgYyEA0NNJ+F7Qjwh0OweT4c+xSjrE6MlK1KMzUczW/hSwIA
jEpB8ysaO4JBofpk2zJG7LoVMis1PQoMgQpUv1/r+tdVXyWwKjARgxGHKWSLAmjV
iqWOxjfBbTNLYS9a9nEL4Q==
=+YjC
-----END PGP SIGNATURE-----
