They always did get wait()ed upon, just after the next connection, I believe. As a practical matter, that behavior doesn't cause any issues unless you're running on a system with 10K RAM...
John On 03/25/2012 10:53 PM, David Griffith wrote:
On Sun, 25 Mar 2012, Cameron Kaiser wrote:Does anyone here know why pygopherd constantly creates zombies? Does anyone know how to fix it?What OS? Sounds like it's not wait()ing on its children. Maybe try running it from (x)inetd?I'm running it on x86 and amd64. I just got a reply from John Goerzen who said that it has always done that. It just strikes me as something that really should be fixed instead of tolerating it.
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project