No, this is ok. You don´t need an entry in inittab to redirect output to
some ttys.
I have lost the focus to your problem. As I know you said
syslogd starts fine if started manually, but it fails to start
right after reboot, isn´t it?
If all your runscripts are ok - and I think they are - it looks
like something isn´t up right after reboot - like some modules aso.
Can you give the output from /var/log/dmesg or /var/log/boot*, if it
is a current RH dist.
If you have booted a new kernel, and the problem appears right after this,
you´ve changed something in the .config file or the kernel is bad.
if you don't have an entry in
'inittab' for the tenth vt, it seems to me that 'syslogd' output is going
to hang at "mingetty's" target.
--
Tom
LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?
-
: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
