From owner-freebsd-stable Mon Mar 15 1:30:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 3EE7314EA8 for ; Mon, 15 Mar 1999 01:30:18 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 15 Mar 99 09:29:59 +0000 (GMT) To: Nate Williams Cc: freebsd-stable@freebsd.org Subject: Re: OK, where did rc.local go? In-reply-to: Your message of "Sun, 14 Mar 1999 22:00:03 MST." <199903150500.WAA28622@mt.sri.com> X-Request-Do: Date: Mon, 15 Mar 1999 09:29:58 +0000 From: David Malone Message-ID: <9903150929.aa16138@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That "can't happen" as init make sure xdm can't fork too fast w/out > disabling itself. Unless it happened that the "xdm" binary had a bug in > it that caused 'nodaemon' to be ignored, which would cause the inferior > xdm process to fork un-beknownst to the original xdm process. I think it wasn't as straight forward as init spawning too many xdm's. I think it might have been xdm that was doing the forking, probably due to some difference in the environment in which it was invoked (sigmask maybe?). If someone is really interested I can try to reproduce it and get some more info - but I think it is just safest to start it from rc.local. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message