From owner-freebsd-hackers  Mon Sep 25 08:48:55 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA14836
          for hackers-outgoing; Mon, 25 Sep 1995 08:48:55 -0700
Received: from phoenix.volant.org (root@phoenix.volant.org [205.179.79.1])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA14830
          for <hackers@FreeBSD.ORG>; Mon, 25 Sep 1995 08:48:49 -0700
From: patl@asimov.volant.org
Received: from asimov.volant.org (asimov.volant.org [205.179.79.65]) by phoenix.volant.org (8.6.11/8.6.9) with SMTP id IAA25402; Mon, 25 Sep 1995 08:47:33 -0700
Received: by asimov.volant.org (5.x/SMI-SVR4)
	id AA28921; Mon, 25 Sep 1995 08:53:10 -0700
Date: Mon, 25 Sep 1995 08:53:10 -0700
Message-Id: <9509251553.AA28921@asimov.volant.org>
To: jmb@kryten.atinc.com, terry@lambert.org, gryphon@healer.com
Subject: Re: ports startup scripts
Cc: hackers@FreeBSD.ORG, peter@taronga.com
X-Sun-Charset: US-ASCII
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

|>  > Consider:  A package which requires a daemon to be run needs to add a
|>  > startup and a shutdown script to the list of scripts to be executed.
|>  
|>  That's why I've been advocating a single master file. It adds the script
|>  to the startup script directory (we've been calling it "/etc/init/d") and
|>  makes a one line addition to "inittab".

Aaaccckkkk!!!!

One of the biggest wins of the SVr4/Solaris2/etc. system is that
packages -NEVER NEED TO EDIT STARTUP FILES-.  Automatic editting
of files is DANGEROUS and should be avoided.

(Please excuse me for shouting there, but this is important.)


|>  > It may also need to add a cron job to rotate the damons logs.
|>  
|>  No. With the new "daily" script handler (Jordan, have you told anyone
|>  else about this yet?) all it needs to do is add a line to the scheduled
|>  jobs config file (current name "sched.conf" like:
|>  
|>  	rotate_log	daily	/some/log/file

Could this be changed to 'add a file to the scheduled jobs directory',
to avoid the need to automatically edit a file?



|>  > Ordering guarantees within a single run level/state are hard to provide
|>  > with the single monolithic file model.
|>  
|>  Actually, a single file is the easiest to control ordering in.
|>  Last I checked, line 1 always came before line 2. :-)

Ah, but can you guarantee that the install script that inserts a
few new lines is putting them in the right place?




-Pat