Date: Mon, 05 Dec 2005 02:32:28 -0800 From: Peter Carah <pete@altadena.net> To: current@freebsd.org Subject: Re: [rc update] sshd no longer starts at boot Message-ID: <4394173C.40606@altadena.net> In-Reply-To: <4393E915.8020302@FreeBSD.org> References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <7.0.0.16.2.20051204102647.037622d8@pozo.com> <43933CFB.8060908@FreeBSD.org> <4393E915.8020302@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton wrote: > Thanks to debugging help from Manfred and Scott, I've decided to give up > on trying to figure out what's wrong with the ports scripts. :) > Seriously though, Brooks and I have had a conversation about whether the > *.sh scripts generally need to be sourced into the shell at all, or can > they be run like "regular" rc.d scripts. The problems with the fairly > simple stuff that Scott and Manfred had installed (i.e., completely > non-obvious, and no good reason for it to fail) convinced me that we > need to go this route, at least in the short term. > > Doug > All this from cvsup about 2 or 3 pm pst: My problem is more related to the earlier ones; I hadn't noticed cron (which now looking didn't start), but moused doesn't start, nor sshd. These are *not* in the ports... (and yes, I refreshed all of /etc/rc* and removed old scripts from rc.d...) The problem with cups.sh dropped me into single user, from which if I just ^D all the missing stuff started, including cupsd. Strange... Actually does sound like a script is leaving state around that affects others. -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4394173C.40606>