Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Nov 1998 17:00:00 -0500 (EST)
From:      ADRIAN Filipi-Martin <adrian@ubergeeks.com>
To:        Greg Lehey <grog@lemis.com>
Cc:        dyson@iquest.net, wes@softweyr.com, tlambert@primenet.com, hackers@FreeBSD.ORG
Subject:   Re: System V init (was: Linux to be deployed in Mexican schools; Where was FreeBSD?)
Message-ID:  <Pine.BSF.3.96.981129164342.867C-100000@lorax.ubergeeks.com>
In-Reply-To: <19981130080037.A423@freebie.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Nov 1998, Greg Lehey wrote:

> [moved to -hackers]
> 
> On Sunday, 29 November 1998 at  9:29:58 -0500, John S. Dyson wrote:
> > Greg Lehey said:
> >>
> >> OK.  The *idea* of run modes seems to make sense, and I wouldn't
> >> change the System V method on a system which had it, but how useful is
> >> it really?  Consider:
> >>
> >> Run state	Meaning		BSD init
> >> 0		halt		halt
> >> 1		single user	shutdown
> >> 2		multi user,	Whaat??
> >> 		no network
> >> 3		multiuser	(multiuser; stop single user)
> >> 4		undefined
> >> 		(most systems)	can't see any equivalent on PCs
> >> 5		PROM monitor
> >> 6		reboot		reboot

	Nooooo....  If we must have start/stop scripts, we don't need run
levels.  I believe run-levels encourage a lesser form of "reboot whenever
there is a problem".  People reach for the shot gun and try dropping to
say level 2 and then returning to level 3.  Along the way many innocent
processes are stopped (work/effort/connections are lost) and restarted.
Even worse, the problem may not be resolved.  In my experience, it is
typically one process that is having/causing problems.  A HUP or a TERM
with some other diagnostics is usually sufficient.

	This lack of fine control is my biggest grip with standard sysv
start/stop scripts.  If we had individual start/stop scripts for
everything and then perhaps "grouped" start/stop scripts for say all of
the NFS server daemons, it would help and be better than just bringing
over the model lock, stock and barrel. 

	I still don't understand why this has become an issue again.
There is /usr/local/etc/rc.d.  The scrtips are called with "start" and
using rc.shutdown, you can make sure they are called with "stop".  What
more does a third party software vendor need?  They certainly cannot care
about how basic system functions are managed. 
	
	Adrian
--
[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981129164342.867C-100000>