Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

Re: How to tell a child what to do?

by Zaxo (Archbishop)
on Sep 21, 2005 at 09:33 UTC ( #493702=note: print w/replies, xml ) Need Help??

in reply to How to tell a child what to do?

On (4.), what is killing your children before their task is done?

There are lots of ways to talk to child processes. If there is a small fixed set of messages, signaling with kill is effective, with %SIG copy-on-write. If you need more extensive communication, pipes are my favorite, but sockets are also good. Each child will need to parse what you send it. See perlipc for details.

Another way is to only launch a child when it and the parent will know what it's supposed to do. That's best on systems, like Linux, where fork is cheap.

After Compline,

Replies are listed 'Best First'.
Re^2: How to tell a child what to do?
by Eyck (Priest) on Sep 21, 2005 at 09:55 UTC

    A: You (as a designer) don't know.

    Anyhoo, some tasks may take forever, thus you need to keep it running indefinitely.

    I don't know how launching a child only when task is ready is going to help, you still need to tell your newborn child what kind of tasks you prepared for them ( ie, pass some argument, I would go for $ARGV[], this seems simplest ).

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://493702]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (4)
As of 2021-01-19 14:51 GMT
Find Nodes?
    Voting Booth?