From owner-cvs-all Sun Jul 9 0:52:39 2000 Delivered-To: cvs-all@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 711D237B54F; Sun, 9 Jul 2000 00:52:31 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id DAA25798; Sun, 9 Jul 2000 03:52:37 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 9 Jul 2000 03:52:37 -0400 (EDT) From: Adam To: "Andrey A. Chernov" Cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/etc rc.shutdown In-Reply-To: <20000708220113.A81167@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 8 Jul 2000, Andrey A. Chernov wrote: >On Sat, Jul 08, 2000 at 12:29:24PM -0700, Eugene M. Kim wrote: >> That sounds like a good idea, provided that it will be gone after a >> reasonable heads-up grace period. One scenario might be: >> >> * In FreeBSD 4.1: >> >> - Add a `# start|stop' line to every startup script in ports. > >I object such indirect magic as local hack hard to remember and not in Unix >style. Separate directories for sturtup/shutdown is much clearer solution. How about a rc.conf knob that controls whether rc.shutdown tells the rc.d scripts to "stop" and leave it up to the sysadmin to enable a new (helpful sometimes) feature which could be confusing or painful if turned on behind our backs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message