From owner-freebsd-current Sat Aug 2 15:03:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA16993 for current-outgoing; Sat, 2 Aug 1997 15:03:19 -0700 (PDT) Received: from unique.usn.blaze.net.au (root@unique.usn.blaze.net.au [203.17.53.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA16971; Sat, 2 Aug 1997 15:03:08 -0700 (PDT) Received: from unique.usn.blaze.net.au (davidn@local [127.0.0.1]) by unique.usn.blaze.net.au (8.8.6/8.8.5) with ESMTP id IAA14912; Sun, 3 Aug 1997 08:02:11 +1000 (EST) Message-Id: <199708022202.IAA14912@unique.usn.blaze.net.au> To: Paul Traina cc: committers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: rc.shutdown In-reply-to: Your message of "Sat, 02 Aug 1997 12:07:08 MST." <199708021907.MAA06706@precipice.shockwave.com> X-Face: (W@z~5kg?"+5?!2kHP)+l369.~a@oTl^8l87|/s8"EH?Uk~P#N+Ec~Z&@;'LL!;3?y Date: Sun, 03 Aug 1997 08:02:11 +1000 From: David Nugent Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This warning is bogus, rc.shutdown is not required for proper > operation, so why complain? The complaint is generic; it doesn't come from init itself, but from from /bin/sh. I think special-casing its non-existance is probably the way to go, in which case, the attempt to run it will simply be skipped. Any objections? This should also make it easy to integrate into 2.2. I can't see any reason not do do so, can you? It is a minor addition, a "new feature", sure, but there are no costs involved provided the warning is removed and the benefits for news servers in particular are there. The sysctl used is already in 2.2-stable. The only element missing is sysctlbyname(3) in 2.2's libc. [Peter Wemm - did you get my request to add it a couple of weeks ago? :-) If you have, I missed the commit message]. Regards, David David Nugent - Unique Computing Pty Ltd - Melbourne, Australia davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/