> > This is also a really bad idea, because with easily guessable pids you> > are opening yourself to /tmp races. This is actually a argument for> > random pids (or fixing the programs).> > Random pids just slow the process down. Its an argument for writing> decent code.

Clearly the security reasons are bogus, but weren't there efficiencyreasons for wanting random pids? Like the time it took to find an emptyslot in the process table for rapidly forking processes? I seem toremember a thread about this about a year back.

Sequential processes are nice for sysadmins, it makes it possible tofigure out execution order occassionally, estimate how quickly processesare forking, etc. Programs that rely on randomness of time() getpid() forany form of security are so naive that they likely have numerous otherexploitable problems and no simple concession by the kernel is going tohelp matters.

-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."

-To unsubscribe from this list: send the line "unsubscribe linux-kernel" inthe body of a message to majordomo@vger.rutgers.eduPlease read the FAQ at http://www.tux.org/lkml/