Date: Fri, 30 Apr 1999 09:51:28 -0700 (PDT) From: wpaul@FreeBSD.ORG To: sclawson@cs.utah.edu, wpaul@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/10970 Message-ID: <19990430165128.424E714D18@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
Synopsis: Children of ypserv don't necessarily go away. State-Changed-From-To: open->closed State-Changed-By: wpaul State-Changed-When: Fri Apr 30 09:45:27 PDT 1999 State-Changed-Why: Grrr. Okay, put another 'stupid' sticker next to my name. I dealt with this by having ypproc_all_2_svc() exit when it's done instead of return to the dispatcher. I left some of the sanity tests in though because I'm paranoid, and they shouldn't hurt. The test for 'forked' is removed. The test for 'am I the parent or a child' is not. If the condition shows up again, a warning message should be logged. Note that I tried to duplicate the failure condition myself many times, but no matter how hard I tried to hit the server it would never produce a bogus child process while I was looking at it. Instead it would always happen during the night, and not at any predictable interval. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990430165128.424E714D18>