topic Re: rc3.d in Operating System - HP-UX

rc3.d

lastgreatone — Wed, 26 Sep 2001 01:11:42 GMT

Shouldn't the KILL script be in the rc2.d, which is one directory below the run level? My peers decided the Start and Kill scripts for Oracle should be in rc3.d. (They originally had it in rc1.d). BTW the NFS kill is in rc2.d.

TIA

Re: rc3.d

A. Clay Stephenson — Wed, 26 Sep 2001 01:37:21 GMT

Hi Frankie:

You are correct. The rule is that the kill script goes in one run-level below that of the start script. e.g If your start script is
/sbin/rc3.d/S910oracle then your kill script should be /sbin/rc2.d/K090oracle. The other convention (though not a requirement) is that the 3 digits of both scripts should add to 1000. This almost always brings them up and down in the intended order. I have also implemented Oracle to start in rc4.d and stop in rc3.d assuming the default run-level is 4.

Regards, Clay

Re: rc3.d

Victor_5 — Wed, 26 Sep 2001 01:38:34 GMT

Hi Frankie:

In order to meet dependency requirements, services are generally killed in the reverse order from which they are started.

For example, assume there are four services, W, X, Y, and Z. The S/K script names for these
services would likely be:

/sbin/rc3.d: /sbin/rc2.d:
------------ ------------
S200W K800W
S300X K700X
S400Y K600Y
S500Z K500Z

Regarding NFS, the startup scripts are in:

NFS core /sbin/rc2.d
NFS client /sbin/rc2.d
NFS server /sbin/rc3.d

Shawn

Re: rc3.d

Animesh Chakraborty — Wed, 26 Sep 2001 01:43:43 GMT

hi,
See the link below:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x6c02a24d9abcd4118fef0090279cd0f9,00.html

Regards
Animesh

Re: rc3.d

Animesh Chakraborty — Wed, 26 Sep 2001 01:51:15 GMT

Hi,
http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0xdfb779bffde7d4118fef0090279cd0f9,00.html

A must read before you start
http://docs.hp.com/hpux/onlinedocs/os/startup.html

Thanks
Animesh

Re: rc3.d

A. Clay Stephenson — Wed, 26 Sep 2001 01:52:31 GMT

Hi Frankie:

One other point, if both the start and kill scripts trigger at the same run-level and that level is the default run-level as set by the initdefault entry in /etc/inittab, the kill script will not even be triggered. That is why you always kill at run-level - 1.

Regards, Clay

Re: rc3.d

Scott Van Kalken — Wed, 26 Sep 2001 04:07:24 GMT

General rule of thumb also is that the start and kill script numbers should add up to 1000 (it's a neatness thing)

Re: rc3.d

James R. Ferguson — Wed, 26 Sep 2001 10:54:15 GMT

Hi Frankie:

'Kill' scripts should execute at one run-level lower than their 'start' counterpart, for the reason that Clay clearly states in his second post.

In addition the "1000-rule", when followed, means not only that processes will be killed in in the *reverse* order that they were started, but that processes will *not* be killed until a potentially dependent process is first killed.

Consider processes A, B and C started at run-level-3 as S100A, S400B and S900C. Assume further that S400B is dependent upon some service provided by S100A. The proper kill scripts would be at run-level-2 and respectively be K100C, K600B and K900A. Thus, "B" would be gracefully terminated before "A"'s service is killed.

Regards!

...JRF...

Re: rc3.d

Darrell Allen — Wed, 26 Sep 2001 12:07:32 GMT

Hi Frankie,

Aside from being a good convention, the kill script MUST be in a lower level from the start script or it will not be executed (see /sbin/rc). It is only executed when changing run-level to it's level or a lower level. For example, changing from run-level 3 to 1 executes Kill scripts in rc2.d and rc1.d.

Darrell