Date: Tue, 21 Oct 1997 10:30:55 +0200 (SAT) From: Graham Wheeler <gram@cdsec.com> To: hackers@freebsd.org Subject: Re: Bug in 2.2.2 Message-ID: <199710210830.KAA12877@cdsec.com>
next in thread | raw e-mail | index | archive | help
> > I see the fork() in your code, but I don't see where it's doing a wait() t= > o = > > pick up the childs exit status. Am I missing something? No - I wrote the program very quickly. As I saved it I remembered I hadn't caught the SIGCHLDs to reap the zombies, but decided to run it anyway, and add the reap code afterwards. Which is why I said in my original message: > I hadn't bothered doing any signal catching here; this was quick 'n dirty. This doesn't change the point - which is that the program should not cause a panic. It should just cause the process table to fill up and for the fork()s to fail after a while. Admittedly this could cause problems with the O/S if it tries to fork something else, but the first message I saw was not a `cannot fork', but a `panic: vmstat...' (or something along those lines; I don't remember the exact message but I do remember that it was a VM related message). cheers gram -- Dr Graham Wheeler E-mail: gram@cdsec.com Citadel Data Security Phone: +27(21)23-6065/6/7 Internet/Intranet Network Specialists Mobile: +27(83)-253-9864 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data Security Products WWW: http://www.cdsec.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710210830.KAA12877>