In message <[email protected]>,
Risto Vaarandi writes:
>in the most recent version, I've also included new commandline options
>--childterm and --nochildterm which define if child processes will get
>the SIGTERM signal when sec terminates. Up to the last version, SIGTERM
>was always issued which was useful for taking down long running
>processes not receiving data from sec over a pipe.
>I was wondering if it would be wise to make --nochildterm the default?
>On one hand, it differs from the current default (always deliver the
>signal), but on the other hand, it might not be necessary in many cases.
>Any opinions on that?
I think I would leave the default at --childterm. I can't think of any
time I would want a process started from SEC to stay alive when the
parent SEC goes away. I don't like leaving orphaned processes
around. If somebody wants to leave the child process running after SEC
terminates they can catch the TERM signal and ignore it.
Sending a TERM to a process that already exited is a no-op so there is
no down side to sending the signal.
--
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Simple-evcorr-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
