There are several disadvantages to installing a SIGCHLD handler
- Signals aren't reliable so you may not get one for every child expiry. Using waitpid in a loop will help
here.
- You can get SIGCHLDs from your children when they haven't died
(eg your child gets sent a SIGSTOP - the parent will get a SIGCHLD)
- You can get SIGCHLDs from perl operations like open "|.." and backticks if you are unlucky which can confuse things.
- Unreliable signals are evil!
Some of the examples in The Perl Cookbook have the correct
waitpid in a loop in the SIGCHLD handler, but some don't (for instance the section on
a preforking daemon).
Personally I would ignore SIGCHLD and make the parent wait()
for the children to die. It will be nicely blocked (ie not using any
excess CPU) until it needs to do something (ie make more children).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
