On Wed, 2009-10-07 at 17:16 +0530, Saurabh Kadekodi wrote: > Hi All, > Scheduling for restart. > process '/sbin/syslogd -n -m 0' (pid 253) exited. Scheduling for restart. > process '/usr/bin/tail -f /var/log/messages' (pid 254) exited. > Scheduling for restart. > process '/sbin/syslogd -n -m 0' (pid 259) exited. Scheduling for restart. > process '/usr/bin/tail -f /var/log/messages' (pid 260) exited. > Scheduling for restart. > process '/sbin/syslogd -n -m 0' (pid 265) exited. Scheduling for restart. > process '/usr/bin/tail -f /var/log/messages' (pid 266) exited. > Scheduling for restart. > > This latter part then keeps on recurring indefinately.
In /etc/inittab of the target filesystem you find that syslogd is launched in respawn mode. # Logging junk null::sysinit:/bin/touch /var/log/messages #null::respawn:/sbin/syslogd -n -m 0 null::respawn:/sbin/klogd -n Comment this line and launch syslogd later from command line to see why it exits. Using NFS to boot the target root eases debugging a lot, but your Kernel needs to enable NFS boot first. Cheers, Marco -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
