> the original process on a system fast enough to wrap the
> pid counter in < 1 sec?
on a recent, entry-level system (duron/600, 128M PC133)
I see ~13000 fork/child-exit/wait cycles per second.
clone is even worse (better): ~42K/second!
-
To unsubscribe from this list: send the line
Has everyone forgotten the old coda_fs-security discussion and
the question of how to be sure that you are still talking to
the original process on a system fast enough to wrap the
pid counter in < 1 sec?
(That question doesn't have to be solved with the pid, you can
use a wide cookie, but if
Has everyone forgotten the old coda_fs-security discussion and
the question of how to be sure that you are still talking to
the original process on a system fast enough to wrap the
pid counter in 1 sec?
(That question doesn't have to be solved with the pid, you can
use a wide cookie, but if
the original process on a system fast enough to wrap the
pid counter in 1 sec?
on a recent, entry-level system (duron/600, 128M PC133)
I see ~13000 fork/child-exit/wait cycles per second.
clone is even worse (better): ~42K/second!
-
To unsubscribe from this list: send the line "unsubscribe
4 matches
Mail list logo
