Well, thanks for your comments, however...
hacker
Your 'tutorial' link is broken (fixed) points to the perlipc pod, which i mentioned i've already read.
I've seen the faq, and done what it said, read perlipc & ch 16 of the camel (which says pretty much the same thing), as well as ch16 of the perl cookbook.
I'm not trying to trap signals with eval (?!?), and my code already uses $SIG{ALRM} = sub{ die } ...
Zaxo
I fail to see the different moving waitpid() makes, apart from style. Mine is still executed by the parent (the code was tested before posting and works).
I'll need to create a signal handler of some sort, wont i? I tried changing the %SIG sub to { kill INT => $pid } but the child doesn't die...
I've read all i can get my hand's on (albiet not in depth), and have a general understanding of how everything works. All i'm after is how to, in effect, timeout system() and qx() calls safely, and capture output...
Update:
I urge you to reflect on why you asked the question.
Ok... <reflects> Because: i'm not sure 1) where/if/how to use kill, 2) wether or not i'm creating zombies, and 3) how to capture output.
The code was working, but you didn't know why.
No, i researched and wrote it myself, i'm just not sure about the zombie bit.
You reject advice on saving time and worry every time you need this kind of code.
Sorry, now you've lost me...
- ><iper
my JAPH:
print"Just another Perl hacker\n";
# ^ look, no space! pretty tricky hey?
-
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.
|
