In which order relative to /etc/rc.d/ are entries in /etc/init/ started or killed?

leniviy · 04-16-2015, 04:08 AM

/etc/init/db2fmcd.conf :

Code:

...
start on stopped rc RUNLEVEL=[2345]
stop on starting rc RUNLEVEL=[016]
exec /opt/IBM/db2/V10.5/bin/db2fmcd
...

When I do: "init 1", what will happen first?

/etc/rc.d/rc1.d/K99* called
db2fmcd killed

MensaWater · 04-16-2015, 08:43 AM

Your conf file has "start on stopped rc RUNLEVEL=[2345]"

If you look in /etc/init you also have rc.conf. The above line says the triggering event is "stopped rc". (The .conf is not used when calling the name according to the man pages - see "man init" and others.

Since it says "stopped rc" that would suggest that it needs to have finished stopping all the init scripts controlled by rc such as your /etc/rc.d/rc1.d/K99*.

Given the foregoing I believe the order is:
/etc/rc.d/rc1.d/K99*
exec /opt/IBM/db2/V10.5/bin/db2fmcd

The sad thing is that until I saw your question I was blithely unaware of what /etc/init files did (as opposed to the more familiar /etc/init.d, /etc/rc.d stuff). The /etc/init were introduced for upstart and the others are from the original SysV init setup. On RHEL7 they've gone to systemd over SysV init and upstart so it doesn't have /etc/init. Therefore it appears this was only in RHEL6 (and other Linux distros such as Ubuntu).

michaelk · 04-16-2015, 08:57 AM

Scripts run in numerical order i.e. K01XXX-K99XXX then S01XXX -. Each init.d script contains its runlevel and start/stop value. when you run the chkconfig --add command a link with that value gets created in the rc0.d-rc6.d directories.

What version of Redhat are you running?