Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

Re: child and parent process communication

by jbert (Priest)
on Sep 03, 2008 at 11:59 UTC ( #708730=note: print w/replies, xml ) Need Help??

in reply to child and parent process communication

Your SIGUSR1 idea is OK, but doesn't scale nicely and you'll get a thundering herd of processes all waking up and checking the shared mem area. It'll be N^2 with your number of connections (since you have N procs and presumably O(N) signals).

IMHO, you should open a pipe before the fork and have the child write the userid back to the parent (and then close off the pipes). With a single one-way message, you'll avoid any difficult deadlock situations.

The parent just needs to add it's end of the pipe to your existing select/poll loop and do a read+close (or you'll leak fds) when it gets the info it needs.

  • Comment on Re: child and parent process communication

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (4)
As of 2021-04-23 08:04 GMT
Find Nodes?
    Voting Booth?

    No recent polls found