From owner-freebsd-current Wed Oct 30 14:24: 2 2002 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 A844437B401 for ; Wed, 30 Oct 2002 14:24:00 -0800 (PST) Received: from clover.kientzle.com (user-112uh9a.biz.mindspring.com [66.47.69.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B5543E97 for ; Wed, 30 Oct 2002 14:23:56 -0800 (PST) (envelope-from kientzle@acm.org) Received: from acm.org (c43 [66.47.69.43]) by clover.kientzle.com (8.11.3/8.11.3) with ESMTP id g9UMNmE10040; Wed, 30 Oct 2002 14:23:48 -0800 (PST) (envelope-from kientzle@acm.org) Message-ID: <3DC05BF4.8050203@acm.org> Date: Wed, 30 Oct 2002 14:23:48 -0800 From: Tim Kientzle Reply-To: kientzle@acm.org User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.6) Gecko/20011206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gordon Tetlow Cc: current@freebsd.org Subject: Re: RCng Awkwardness References: <3DC03815.2050003@acm.org> <20021030200055.GA30253@roark.gnf.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Gordon Tetlow wrote: > On Wed, Oct 30, 2002 at 11:50:45AM -0800, Tim Kientzle wrote: > >>I find the standard arguments used by RCng quite >>awkward. In particular, ... "/etc/rc.d/nfsd stop" does >>not actually stop the nfsd process. ... > > ... I've found this behavior to be quite annoying. I'll > see if I can put something together. If you want to help me out and > put together the patches, I'd be more than happy to commit them. I have something partly sketched out, but it still needs some work. I can send you something in the next couple of days to look at. I see two awkward issues: * Is it necessary to distinguish 'stop' (unconditional stop) from 'shutdown' (stop only if enabled)?? Seems that at system shutdown you want everything to be taken down, regardless of whether it was brought up at boot or brought up manually post-boot. The unconditional 'stop' seems to be all that's needed. * Local rc scripts (in /usr/local/etc/rc.d) will still get run with a 'start' argument, while system scripts in /etc/rc.d will get a 'boot' argument. That's a bit awkward, but still reasonably consistent: 'start' is still an unconditional operation. I don't see any way around this without breaking existing systems after upgrade. Tim Kientzle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message