From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 1 05:44: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 AD2A616A421 for ; Sat, 1 Sep 2007 05:44: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 340D113C480 for ; Sat, 1 Sep 2007 05:44:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 10283 invoked by uid 399); 1 Sep 2007 05:43:59 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 1 Sep 2007 05:43:59 -0000 X-Originating-IP: 127.0.0.1 Date: Fri, 31 Aug 2007 22:43:57 -0700 (PDT) From: Doug Barton To: Erik Trulsson In-Reply-To: <20070831191429.GA63829@owl.midgard.homeip.net> Message-ID: References: <46D84609.3080409@miralink.com> <20070831191429.GA63829@owl.midgard.homeip.net> 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; charset=US-ASCII; format=flowed Cc: Sean Bruno , 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: Sat, 01 Sep 2007 05:44:17 -0000 On Fri, 31 Aug 2007, Erik Trulsson wrote: > The times I have noticed that stop does not work without an _enable variable > has been when I wished to stop running some service. First I edited rc.conf > to remove the _enable line (to make sure the service did not start the next > time I restarted the computer) and then I tried to stop the service using > the normal 'stop' invocation. This of course did not work which was very > annoying. (The above is IMO the proper order to do this - if it worked.) With all due respect, I think that if you've done the same wrong thing the same wrong way multiple times, and haven't learned not to keep doing it wrong, changing the code to meet your expectations is the least of our worries. That said, you of course have the code to modify in any way you see fit. I do not believe however that what you're suggesting is in the interests of the majority of FreeBSD users. Doug -- This .signature sanitized for your protection