* Re: [gentoo-proxy-maint] Checking before reinventing wheel: init script not waiting for child processes
@ 2016-06-02 7:02 99% ` Sam Jorna
0 siblings, 0 replies; 1+ results
From: Sam Jorna @ 2016-06-02 7:02 UTC (permalink / raw
To: gentoo-proxy-maint
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On Wed, Jun 01, 2016 at 04:02:12PM -0400, Philippe Chaintreuil wrote:
> Hello,
>
> I'm looking at a bug [1] that is complaining that an init script
> doesn't wait for the child processes of the daemon to exit before it
> returns.
>
> I just wanted to make sure that there's not a standard/existing
> methodology that does this before I start adding custom code.
> I guess I should also make sure that this isn't something the
> hive-mind thinks should be punted upstream. (I've looked at the source
> code, and the interrupt handler just loops through the child pids and
> exits, it doesn't wait on the pids.)
I haven't looked too closely at the code, but does spamd keep track of its own
children? As in, does the master process wait until the child processes are
terminated before terminating itself? If so, then perhaps you could force the
daemon into the foreground and have start-stop-daemon background it itself.
Cheers;
--
Sam Jorna
GnuPG Key: D6180C26
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2016-06-01 20:02 [gentoo-proxy-maint] Checking before reinventing wheel: init script not waiting for child processes Philippe Chaintreuil
2016-06-02 7:02 99% ` Sam Jorna
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox