Re: IOCs under procServ as system services under systemd?

["Konrad, Martin" <konrad@frib.msu.edu>]

Hi all,
Niklas and Stefani, thanks for sharing your systemd unit configuration.
It came just at the right time :-) I put together a similar one. Using
the foreground option (-f) of procServ is the recommended way with
systemd. My unit configuration [1] differs in some details:

> ConditionFileIsExecutable=/usr/bin/procServ 
> ConditionFileIsExecutable=/usr/local/ops/iocBoot/ioccontrol/st.cmd
This causes systemd to silently skip the service if one of these files
is not executable. Stefani, are you sure that's the behavior you want? I
would prefer it to fail with an error message instead (remove these two
lines).

I'm using "Restart=always" to make sure procServ is restarted
automatically even if it exited cleanly. I don't want users to find out
that they are not able to restart procServ after they shut it down by
pressing Ctrl-Q.

Note how systemd makes our life as developers easier: Daemons don't need to
- fork
- write PID files
- drop privileges by themselves
Systemd takes care of all these things for us :-)

Cheers,

Martin

[1]
https://stash.nscl.msu.edu/projects/DEPLOY/repos/puppet_module_epics_softioc/browse/templates/etc/systemd/system/ioc.service

-- 
Martin Konrad
Control System Engineer
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: konrad@frib.msu.edu