[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] cleaning up /etc/rc.d/rc3.d
- Subject: Re: [cobalt-users] cleaning up /etc/rc.d/rc3.d
- From: flash22@xxxxxxx
- Date: Sun Mar 18 10:00:18 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Sun, 18 Mar 2001, SM wrote:
> At 21:18 17-03-2001 -0800, you wrote:
> >The initial "K" indicates not only that they won't start when your
> >system runs in system level 3, but also that if they're already running
> >when you switch to system level 3, they'll stop.
> >
> >That's a linux convention (is it a BSD convention as well, anyone?).
>
> BSD does not use that convention.
It's more properly a 'System V' convention, other non-linux machines that
are based on system V unix use them also...BSD as usual does it's own
thing ;)
Unfortunatly , while 'standard' , there are a lot of annoying variations,
for example run level 5 is a normal runlevel for linux (X), but tells
solaris to turn the machine off ;)
(The K=kill, S=start is pretty standard afaik tho)
Linux has a strange tendency to use start scripts to stop things tho,
eg S40umountfs 'Starts unmounting the disks ;)
Incidently, the K(ill) scripts go in all the runlevels that are *not*
running that service, removing them from rc.x direcorties leaves the
action of that service *undefined* if there is still a (S)tart script at
some other run level...
Eg: when changing from runlevel 2 to 3, init doesn't execute the K scripts
in 2, rather, it runs the ones in 3 to kill off services that aren't
supposed to be running at run level 3...(that might have been started at
2)
gsh