From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 10:32:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F1EB16A41F for ; Mon, 5 Dec 2005 10:32:32 +0000 (GMT) (envelope-from pete@altadena.net) Received: from puffin.altadena.net (puffin.altadena.net [207.151.161.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8564143D6B for ; Mon, 5 Dec 2005 10:32:31 +0000 (GMT) (envelope-from pete@altadena.net) Received: from nat-gw.home.altadena.net ([66.127.158.99] helo=[192.168.169.21]) by puffin.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1EjDe2-0000cD-8f for current@freebsd.org; Mon, 05 Dec 2005 02:32:30 -0800 Message-ID: <4394173C.40606@altadena.net> Date: Mon, 05 Dec 2005 02:32:28 -0800 From: Peter Carah User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@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> In-Reply-To: <4393E915.8020302@FreeBSD.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 10:32:32 -0000 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