Gentoo Archives: gentoo-proxy-maint

From: Sam Jorna <wraeth@g.o>
To: gentoo-proxy-maint@l.g.o
Subject: Re: [gentoo-proxy-maint] Checking before reinventing wheel: init script not waiting for child processes
Date: Thu, 02 Jun 2016 07:02:46
Message-Id: 20160602070236.GA2898@cerberus.civica.com.au
In Reply to: [gentoo-proxy-maint] Checking before reinventing wheel: init script not waiting for child processes by Philippe Chaintreuil
1 On Wed, Jun 01, 2016 at 04:02:12PM -0400, Philippe Chaintreuil wrote:
2 > Hello,
3 >
4 > I'm looking at a bug [1] that is complaining that an init script
5 > doesn't wait for the child processes of the daemon to exit before it
6 > returns.
7 >
8 > I just wanted to make sure that there's not a standard/existing
9 > methodology that does this before I start adding custom code.
10 > I guess I should also make sure that this isn't something the
11 > hive-mind thinks should be punted upstream. (I've looked at the source
12 > code, and the interrupt handler just loops through the child pids and
13 > exits, it doesn't wait on the pids.)
14
15 I haven't looked too closely at the code, but does spamd keep track of its own
16 children? As in, does the master process wait until the child processes are
17 terminated before terminating itself? If so, then perhaps you could force the
18 daemon into the foreground and have start-stop-daemon background it itself.
19
20 Cheers;
21 --
22 Sam Jorna
23 GnuPG Key: D6180C26

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-proxy-maint] Checking before reinventing wheel: init script not waiting for child processes Philippe Chaintreuil <gentoo_bugs_peep@×××××××××××××.com>