startup and shutdown sequence

[Franky Leeuwerck_1]

Hello Unix people,

We have an Ingres DBMS running on HP-UX 11.
The default run level is 3.

I added a start/stop script for starting or stopping the DBMS after/before the system startup/shutdown. The script is located in the /sbin/init.d directory.
In the /sbin/rc3.d I have a link to the script for starting up, in the /sbin/rc2.d there is a link for shutting it down.

Everything works.

My question is : if I let the DBMS startup in run level 3 (/sbin/rc3.d), why must I let it stop in run level 2.

I tried it with stopping it in run level 3 but that didn't work.

Regards,

Franky Leeuwerck

[Michael Tully · Accepted solution]

Hi,

Have a look at the man page for init (1m). This should explain everything.

$ man 1m init

HTH
Michael

[Donald Kok]

Hi Franky,

When you go up to a runlevel, say from 2 to 3, all S* will be run in alphabetic order. When you go down a runlevel (say from 5 to 3, or from 3 to 2) all K* scripts are run.

So you want to have a service run in level 3, you should kill it in level 2.

Greetzz
Donald

[Franky Leeuwerck_1]

Thanks for the quick replies.

Apparently the answer is very simple. It is the way HP-UX handles the run level transitions.

Best regards,
Franky

[Donald Kok]

Franky,
You seem to be one of the very few ingres admins around the forum. (Never met one before, all oracle). It is nice to be not alone anymore.

Maybe you like to see my start/stopscript, since CA does not deliver them.

Goodluck
Donald

[Yogeeraj_1]

hi,

Please allow me to shared this document with you.

This document explains the system startup and configuration models. Normally, Software developers construct rc files in a different manner, specifying run-level execution order and enabling control through configuration variables. System administrators control subsystem behavior, on a per-host basis, by modifying variables that control subsystem startup and shutdown.

regards
Yogeeraj

[Yogeeraj_1]

hi,

Please allow me to share this document with you.

This document explains the system startup and configuration models. Normally, Software developers construct rc files in a different manner, specifying run-level execution order and enabling control through configuration variables. System administrators control subsystem behavior, on a per-host basis, by modifying variables that control subsystem startup and shutdown.

The run-level paradigm and naming conventions are properly illustrated here. Has helped me a lot.

regards
Yogeeraj