From owner-freebsd-stable@FreeBSD.ORG Wed Nov 28 21:42:29 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 656D316A41A for ; Wed, 28 Nov 2007 21:42:29 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (outgoing01.lava.net [64.65.64.68]) by mx1.freebsd.org (Postfix) with ESMTP id 4325413C4E5 for ; Wed, 28 Nov 2007 21:42:29 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 800918334; Wed, 28 Nov 2007 11:42:28 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id CC1CA153882; Wed, 28 Nov 2007 11:42:27 -1000 (HST) Date: Wed, 28 Nov 2007 11:42:27 -1000 From: Clifton Royston To: Milan Obuch Message-ID: <20071128214227.GB15695@lava.net> Mail-Followup-To: Milan Obuch , freebsd-stable@freebsd.org References: <200711282116.53008.antik@bsd.ee> <200711282037.32490.freebsd-stable@dino.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711282037.32490.freebsd-stable@dino.sk> User-Agent: Mutt/1.4.2.2i Cc: freebsd-stable@freebsd.org Subject: Re: questionable feature- rcvar woes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Nov 2007 21:42:29 -0000 On Wed, Nov 28, 2007 at 08:37:30PM +0100, Milan Obuch wrote: ... > Agree - everything just fine. > > > Everything looks fine, but when I disable powerd in rc.conf then problem > > arise. > > > > 1) Disable powerd in rc.conf- comment it out. > > # enable_powerd="YES" > > 2) Stop powerd > > # /etc/rc.d/powerd stop > > ...silence- nothing in logs either. > > > > Stop for a moment - enable_powerd means actually 'enable action carried > by /etc/rc.d/powerd script', using this semantics actually explains all > details. Or you could treat it as a stack of a sort, reversing order to 2) 1) > just produces desired output. > > > What? Not even a warning message and powerd is actually running- why I have > > to reboot to disable it? I know that I can stop it by enabling it in > > rc.conf but what the point? Same problem when I want to start some service > > without appropriate line in rc.conf. I'd prefer to see somekind of warning > > about misconfigured rc.conf or at least information about what's going on > > in reality. > > > > I hope my explanation above suffices. I was hit by this too, but rc.d scripts > behavior is well designed and understandable. If, for some reason, you are > still hit with described behavior, there is a save rope - /etc/rc.d/powerd > forcestop will stop powerd even if there is no enable var in rc.conf. Agree, agree, agree. This is just something that any up-to-date admin should be aware of and in tune with. Yes, it's a bit different from how some-but-not-all start/stop scripts behaved in 4.x or older systems, but it's a very sensible behavior and it makes the /etc/rc.d and /usr/local/etc/rc.d scripts behave much more coherently and consistently. There are two different ways to get it to DWIM - either get in the habit of doing 2) then 1), or get in the habit of using forcestop. Given this, I don't see it as a problem. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services