Ho Folks, yet another puzzle for you.
fork(2) can fail and report EAGAIN if a. run out of a resource other than memory b. too many processes on the system c. too many processes per uid d. too many child processes per process for each of the above, on linux, how the heck do you 1. obtain current usage 2. obtain limit afaics getrusage(2) is no help (d)(2) can be done by getrlimit(RLIMIT_NPROC) or sysconf(_SC_CHILD_MAX) except that both man pages are pretty vague as to whether they are (c) or (d). It would be great if libexplain could distinguish between the 4 cases. suggestions? Regards Peter Miller <[EMAIL PROTECTED]> /\/\* http://miller.emu.id.au/pmiller/ PGP public key ID: 1024D/D0EDB64D fingerprint = AD0A C5DF C426 4F03 5D53 2BDB 18D8 A4E2 D0ED B64D See http://www.keyserver.net or any PGP keyserver for public key. "If you break your leg, don't come running to me!"
signature.asc
Description: This is a digitally signed message part
_______________________________________________ coders mailing list coders@slug.org.au http://lists.slug.org.au/listinfo/coders
