wait() on a PID that is not your child

Posted Oct 10, 2011 17:21 UTC (Mon) by mezcalero (subscriber, #45103)
In reply to: wait() on a PID that is not your child by HelloWorld
Parent article: A Plumber's Wish List for Linux

I wonder if this could be fixed by actually having 64bit PIDs. It's not that easy making things overrun 2^64.

to post comments

wait() on a PID that is not your child

Posted Oct 10, 2011 19:01 UTC (Mon) by HelloWorld (guest, #56129) [Link] (2 responses)

64 bit PIDs ought to be enough for anybody. If the system creates 10000
processes per second, the PIDs would overflow after 2^64/(60*60*24*365*10000) = 58494241 years.

wait() on a PID that is not your child

Posted Oct 12, 2011 22:15 UTC (Wed) by Baylink (guest, #755) [Link] (1 responses)

> should be enough for anybody.

You didn't *really* expect to get away with that, here, did you?

:-)

wait() on a PID that is not your child

Posted Oct 12, 2011 22:49 UTC (Wed) by HelloWorld (guest, #56129) [Link]

It was worth a try.

wait() on a PID that is not your child

Posted Oct 11, 2011 1:13 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]

They would look quite ugly, though.