From owner-freebsd-hackers@FreeBSD.ORG Fri Aug 31 17:10:17 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD61216A417 for ; Fri, 31 Aug 2007 17:10:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by mx1.freebsd.org (Postfix) with SMTP id 7DA6C13C48A for ; Fri, 31 Aug 2007 17:10:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 24133 invoked by uid 399); 31 Aug 2007 17:09:54 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 31 Aug 2007 17:09:54 -0000 X-Originating-IP: 127.0.0.1 Date: Fri, 31 Aug 2007 10:09:52 -0700 (PDT) From: Doug Barton To: Sean Bruno In-Reply-To: <46D84609.3080409@miralink.com> Message-ID: References: <46D84609.3080409@miralink.com> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=us-ascii Cc: freebsd-hackers@freebsd.org Subject: Re: rc functions don't allow processes to shutdown X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2007 17:10:17 -0000 On Fri, 31 Aug 2007, Sean Bruno wrote: > I noticed that if rc.conf has ntpd_enable="NO", an invocation of > /etc/rc.d/ntpd stop won't actually shut down ntpd. I checked a couple of > other processes(like net-snmp) and noted the same behavior. FYI, there is a list for discussing rc.d issues, freebsd-rc@. The current behavior is by design, and I don't think that changing it is a good idea this late in the game. Assuming that lack of an affirmative _enable variable is a constant, the only way that a service can be started is with either onestart or forcestart. The symmetry here would be to stop it the same way. > I would have expected that rc would be able to invoke the stop routines if a > utility is disabled, It can invoke them, in the same way that the start routines can be invoked if a service is not enabled, by prepending one or force to stop. Looking at this from the other direction, what would be the benefit to having plain stop act in the absence of an _enable variable for that service? Doug -- This .signature sanitized for your protection