[EMAIL PROTECTED] writes:

Well, Linux has no 1 second guarantees either.  At the suggestion of
Matthias, I now have a programm that recycles the same PID in much  less
than 1 second.
But you're not doing an exec() here. See how big of a penalty exec() imposes.

Here is the run of the program:

$  ./child
Collision after 0.14 secs! child:       32383   PID:    13145
About seven microseconds per vfork.

The hardware is an 1100MHz, 256M RAM Athlon box, running RH Linux 8.0.
Hopefully, an alternative will be available by the time 8 Ghz CPUs are commonplace.

Looks like using inodes instead of microseconds is going to be the final solution.



Reply via email to