From owner-freebsd-ports  Wed Sep 20 05:44:34 1995
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id FAA01267
          for ports-outgoing; Wed, 20 Sep 1995 05:44:34 -0700
Received: from critter.tfs.com ([140.145.230.252])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA01261
          for <ports@freebsd.org>; Wed, 20 Sep 1995 05:44:28 -0700
Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id FAA01004 for <ports@freebsd.org>; Wed, 20 Sep 1995 05:43:57 -0700
X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol
To: ports@freebsd.org
Subject: Re: ports startup scripts 
In-reply-to: Your message of "Wed, 20 Sep 1995 04:59:24 PDT."
             <199509201159.EAA04965@silvia.HIP.Berkeley.EDU> 
Date: Wed, 20 Sep 1995 05:43:56 -0700
Message-ID: <1002.811601036@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-ports@freebsd.org
Precedence: bulk


Here is my view on this matter:

I belive the scripts should support three arguments:
	start
	stop
	restart

I belive we need to scan multiple directories, and support the following
semi-hardcoded paths:

	/etc/rc.d
		for the root's own hacks and for major startup tasks
		("sh /etc/rc.d/nfs restart" would be a wonderful thing....)

	/etc/pkg/rc.d
		for installed packages startup tasks

	/etc/X11/rc.d
		for X11 related startup tasks.

It should all be under /etc because the security goes south if we are not
very careful.

And that's all folks...
--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@ref.tfs.com       TRW Financial Systems, Inc.
Just that: dried leaves in boiling water ?