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  2016  2017  <20182019  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  2016  2017  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: procServ under systemd service
From: Hinko Kocevar <[email protected]>
To: [email protected]
Cc: EPICS Tech Talk <[email protected]>
Date: Wed, 7 Feb 2018 12:11:09 +0100
On Wed, Feb 7, 2018 at 11:44 AM,  <[email protected]> wrote:
> Doesn't the --noautorestart flag do what you need?

Not really because procServ just hangs after client died.. I would
still need to send the ^Q to exit the procServ process and then
systemd service can take over.

/Hinko

>
>> -----Original Message-----
>> From: [email protected] [mailto:tech-talk-
>> [email protected]] On Behalf Of Hinko Kocevar
>> Sent: 07 February 2018 10:40
>> To: Ralph Lange
>> Cc: EPICS Tech Talk
>> Subject: Re: procServ under systemd service
>>
>> I understand that ^Q will make procServ to exit, but I do not want to
>> know when I need to send it. IOW, what I'm after is, if an IOC dies,
>> procServ needs to exit by itself without user intervention and let the
>> systemd take over and restart the service (procServ).
>> If I understand the 'ExecStop=' correctly it is executed when the
>> service is being stopped, i.e. when user does:
>>
>> $ sudo systemctl stop [email protected]
>>
>> Again, for my case, procServ would need to exit on the behalf of
>> clients death, and not as a consequence of users actions (sending ^Q
>> or issuing systemctl stop).
>>
>> I must be missing something, because I fail to recognize the suggested
>> approaches as viable solution for me.
>>
>> Thanks,
>> Hinko
>>
>> On Wed, Feb 7, 2018 at 11:07 AM, Ralph Lange <[email protected]> wrote:
>> > On Wed, Feb 7, 2018 at 10:04 AM, Hinko Kocevar <[email protected]>
>> wrote:
>> >>
>> >>
>> >> Actually I was looking for a way for procServ to exit once the client
>> >> has died.
>> >
>> >
>> > Isn't that what Tomas suggested?
>> > Sending ^Q after the child died will tell the procServ server to exit.
>> >
>> > Cheers,
>> > ~Ralph
>> >
>>
>>
>>
>> --
>> .. the more I see the less I believe.., AE AoR
>
> --
> This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
> Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom



-- 
.. the more I see the less I believe.., AE AoR

Replies:
RE: procServ under systemd service michael.abbott
References:
procServ under systemd service Hinko Kocevar
RE: procServ under systemd service Mazanec Tomáš
Re: procServ under systemd service Hinko Kocevar
Re: procServ under systemd service Ralph Lange
Re: procServ under systemd service Hinko Kocevar
RE: procServ under systemd service michael.abbott

Navigate by Date:
Prev: RE: procServ under systemd service michael.abbott
Next: RE: procServ under systemd service michael.abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: procServ under systemd service michael.abbott
Next: RE: procServ under systemd service michael.abbott
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  2020  2021  2022  2023  2024 
ANJ, 07 Feb 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·