All, does anybody know exactly how 'respawn' entries work in the
/etc/inittab file ?
Running 4.0F with the capacity planning software installed (cpcunix), if the
process is killed or stopped for some other reason, the init process doesn't
seem to kick it off again. Running 'init q' launches the process ok. There
doesn't seem to be any problems with the inittab file itself. I'm wondering
if init only relaunches processes that were initially started on entry to
the relevant run level (via inittab) by monitoring the PID as opposed to
relaunching a 'manually' started process. I also tried adding an entry for
the line printer daemon (with respawn) which also starts ok with 'init q'
but does not respawn if the process is killed.
The inittab entries are thus :
# OSF/1 Release 1.0
is:3:initdefault:
ss:Ss:wait:/sbin/rc0 shutdown < /dev/console > /dev/console 2>&1
s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1
fs:23:wait:/sbin/bcheckrc < /dev/console > /dev/console 2>&1
kls:Ss:sysinit:/sbin/kloadsrv < /dev/console > /dev/console 2>&1
sysconfig:23:wait:/sbin/init.d/autosysconfig start < /dev/console >
/dev/console 2>&1
update:23:wait:/sbin/update > /dev/console 2>&1
it:23:wait:/sbin/it < /dev/console > /dev/console 2>&1
kmk:3:wait:/sbin/kmknod > /dev/console 2>&1
s2:23:wait:/sbin/rc2 < /dev/console > /dev/console 2>&1
cpc:3:respawn:/usr/bin/cpcunix -dump 300 -poll 10000 > /dev/console
2>&1
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
cons:1234:respawn:/usr/sbin/getty console console vt100
Thanks in advance
Paul Das
Received on Mon Nov 27 2000 - 09:58:55 NZDT