On 02/07/2018 03:25 AM, [email protected] wrote:
> From: Hinko Kocevar [mailto:[email protected]]
>> 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.
>
> Oh. That's unfriendly. There probably ought to be an option to fix that! I'd imagine it's an easy patch to procServ.
Not a bug!
While Hinko hasn't detailed what action he's trying to perform, I did
something like this one for temp file cleanup by fork()ing a child
process which then monitored it's parent. When the parent exits,
the client does it's thing and exits as well. This works even
for abnormal termination of the parent.
- Replies:
- Re: procServ under systemd service Hinko Kocevar
- 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
- Re: procServ under systemd service Hinko Kocevar
- RE: procServ under systemd service michael.abbott
- Navigate by Date:
- Prev:
Re: procServ under systemd service Ralph Lange
- Next:
Re: AreaDetector repository inconsistent Benjamin Franksen
- 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
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: procServ under systemd service michael.abbott
- Next:
Re: procServ under systemd service Hinko Kocevar
- 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
<2018>
2019
2020
2021
2022
2023
2024
|