From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Steudten Subject: Re: syslog does not start Date: Thu, 04 Mar 2004 22:58:47 +0100 Sender: linux-admin-owner@vger.kernel.org Message-ID: <4047A697.9030401@steudten.com> References: <200403041851.03011.fluca1978@virgilio.it> Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: terry white , linux-admin@vger.kernel.org No, this is ok. You don=B4t need an entry in inittab to redirect output= to=20 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=B4t it? If all your runscripts are ok - and I think they are - it looks like something isn=B4t 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 th= is, you=B4ve 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 g= oing > to hang at "mingetty's" target. --=20 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? - To unsubscribe from this list: send the line "unsubscribe linux-admin" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html