Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid
 
PerlMonks  

Re^2: Implementing signals for Win32 Perl using named pipes

by Corion (Patriarch)
on Mar 11, 2008 at 13:19 UTC ( [id://673488]=note: print w/replies, xml ) Need Help??


in reply to Re: Implementing signals for Win32 Perl using named pipes
in thread Implementing signals for Win32 Perl using named pipes

I don't see that race condition as too critical because the same can happen everywhere where PIDs are recycled too soon. If we find out that PIDs get recycled far too quickly, we can think of a solution then. :)

A pipe cannot exist at process startup (by mechanism), because every process creates \\.\pipe\Perl\$$ and $$ is unique per process. The fork() emulation and signals between fork()ed children will be interesting to solve under this umbrella, but signals beween forked children could be handled by using shared memory anyway. I'm not sure how unique the fork-child-PIDs are across process boundaries, so maybe using $$ would still work, even with the fork emulation.

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (9)
As of 2024-04-23 17:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found