From owner-freebsd-current Tue May 9 5: 9:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id C4E9037BE5B; Tue, 9 May 2000 05:08:37 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id OAA16944; Tue, 9 May 2000 14:08:27 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Tue, 9 May 2000 14:08:26 +0200 (EET) From: Narvi To: Will Andrews Cc: FreeBSD Ports , FreeBSD Current Subject: Re: rc.d startup scripts In-Reply-To: <20000506155749.K55274@argon.blackdawn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Errrmmm.... Really, did you check the archives for the issue? There used to be a real long thread on why/why not sysV style init scripts. It produced not one but several flamewars iirc 8-) In short - if we change from the present scheme, we want something better than just stop and restart entry points for the scripts. What happens if the restarting is not an atomic, independent act? On Sat, 6 May 2000, Will Andrews wrote: > Hello, > > I've noticed an inconsistency among our ports. It seems that not every port > that installs rc.d startup scripts includes methods to not only startup, > but also shutdown and/or restart, where appropriate. (Sent to -ports for > ports hackers' opinions.) > > Shouldn't this sort of thing be standardized? And maybe a similar method be > integrated into /etc/rc for restarting base system daemons? (Sent to > -current for src hackers' opinions.) > > Please continue specific discussion on either of these in their own list, > or if reply is general Cc both. > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message