From owner-cvs-all Sun Jul 9 12:27:42 2000 Delivered-To: cvs-all@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 0AE8737BD98; Sun, 9 Jul 2000 12:27:39 -0700 (PDT) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id OAA15376; Sun, 9 Jul 2000 14:27:27 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from dial-81.max1.wa.cyberlynk.net(207.227.118.81) by peak.mountin.net via smap (V1.3) id sma015374; Sun Jul 9 14:27:03 2000 Message-Id: <4.3.2.20000709134256.00ab26b0@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Sun, 09 Jul 2000 14:26:17 -0500 To: Adam , "Andrey A. Chernov" From: "Jeffrey J. Mountin" Subject: Re: cvs commit: src/etc rc.shutdown Cc: cvs-all@FreeBSD.ORG In-Reply-To: References: <20000708220113.A81167@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:52 AM 7/9/00 -0400, Adam wrote: >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. Are there any ports out there that do shutdown properly with a -TERM from init? I saw little reason for adding functionality to rc.shutdown, but object even more to adding yet another gratuitous (IMO) knob in rc.conf. Would it not be simpler to assume a start if the rc.d scripts are invoked without an argument for the transition. Init already sends the -TERM, so I see start|stop functionality as a convenience for while the system is running. IOW, back out the rc.shutdown change *until* all ports with a rc.d script are ready. Was this even coordinated with the ports team? Certainly hope that an MFC is withheld until all issues are resolved. We are getting close to 4.1 and having ugly hacks to work around issues... The start|stop for rc.d script is good, but as pointed out by some may not work for their systems upon startup. If there is an ordering or additional work that should be done before stopping everything, then rc.shutdown should already be in use and/or the scripts modified (or the name changed as Peter Wemm pointed out). Speaking of ordering. Why not have ports that require an ordering have a numeric prefix. Otherwise it appears that there are a lot of things to change adding unnecessary complexity. The ports folks would then need to figure out what order# to assign, which is similar to the assignation of UID/GID. Perhaps there should be a listing for the ports needing this to avoid conflicts when new ports are added. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message