🚀 go-pugleaf

Lewis Burgess (burgess@quickturn.com) wrote:

... snip
:
:    Now that I'm working on it, I've begun to realize I'm not really sure
:    _when_ named should be started and stopped (which rc directories to put
:    it in, and wether it should be an S or a K) and where in the whole
:    startup and shutdown they should go up and down.

:    Any ideas?

: You didn't mention what OS you're using.  Your comment about the S and K leads
: me to believe that you're using a System V machine.  

... snip

I suspect Lewis is right in his assumption, so:

On our Digital Unix (formerly OSF/1) system which inits in the style of 
System V, the following are symbolic links to /sbin/init.d/named:

in /sbin/rc0.d:
	K40named

in /sbin/rc2.d:
	K45named

in /sbin/rc3.d:
	S15named

in rc3.d the following start before named: inet, quota, uucp, settime, 
syslog, gateway, route, and rwho.  I.e., they have a lower number 
following the inital S.

in rc0.d, the following are killed before named: inetd, snmpd, xntpd, 
timed, cron, sendmail, nfsmount. nfs, and nis.  As you might imagine, 
none are started at 0 level.

in rc2.d, the kill order is the same as in /sbin/rc3.d, while, of course, 
none of the interenet services are started at this level.


Hope this helps

Bruce
--
----------------
bbp@nic.com