Date: Mon, 15 Mar 1999 09:30:33 -0700 From: Nate Williams <nate@mt.sri.com> To: David Malone <dwmalone@maths.tcd.ie> Cc: Nate Williams <nate@mt.sri.com>, freebsd-stable@freebsd.org Subject: Re: OK, where did rc.local go? Message-ID: <199903151630.JAA00496@mt.sri.com> In-Reply-To: <9903150929.aa16138@salmon.maths.tcd.ie> References: <199903150500.WAA28622@mt.sri.com> <9903150929.aa16138@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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?). It shouldn't be forking at all with the '-nodaemon' parameter. > 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. Then it won't get re-started if xdm dies. :( Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903151630.JAA00496>