EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: IOCs under procServ as system services under systemd?
From: Andrew Johnson <[email protected]>
To: "Konrad, Martin" <[email protected]>, "[email protected]" <[email protected]>
Date: Mon, 27 Jun 2016 13:46:42 -0500
Hi Martin,

On 06/27/2016 12:48 PM, Konrad, Martin wrote:
>> Has anybody produced a systemd unit file for running the caRepeater?
> Nope. But something along the following lines should get you started:
>
> [Unit]
> Description=EPICS CA Repeater
> Requires=network.target
> After=network.target
> 
> [Service]
> ExecStart=/usr/bin/caRepeater
> Restart=always
> User=carepeater
> 
> [Install]
> WantedBy=multi-user.target

Thanks. Doesn't the "user=carepeater" parameter mean that there must be
a username called carepeater that is used just to run the repeater? I
would probably default to something like daemon instead.

>> It should be possible to extend the CA Repeater client with an option
>> to accept an open socket
> Are you suggesting to replace the caRepeater autostart functionality by
> systemd's socket activation in the long run?

Not replacing it (we will always need it to autostart for when an IOC is
running on an embedded system say), but adding the ability to use socket
activation when desired would make sense.

Its better if the repeater gets started automatically by the system so
the process doesn't run as a regular user or look like it's some random
CA client that hasn't been properly killed, thus for a long time Base
has built a sysv-init script S99caRepeater on Linux and Solaris. The
systemd unit file would provide an alternative to that; adding socket
activation seems like a sensible minor enhancement to avoid starting the
repeater unnecessarily.

Having a repeater that is started by socket activation automatically
exit when its last client disconnects would be an obviously-related
enhancement, but might take a bit more work.

- Andrew

-- 
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon

References:
IOCs under procServ as system services under systemd? Ralph Lange
Re: IOCs under procServ as system services under systemd? Niklas Claesson
Re: IOCs under procServ as system services under systemd? Konrad, Martin
Re: IOCs under procServ as system services under systemd? Konrad, Martin

Navigate by Date:
Prev: Re: IOCs under procServ as system services under systemd? Konrad, Martin
Next: Call to assert failed - EPICS Pedro Mantovani Antunes
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: IOCs under procServ as system services under systemd? Konrad, Martin
Next: Re: IOCs under procServ as system services under systemd? Konrad, Martin
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <20162017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 15 Jul 2016 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·