From: Thomas Steudten <alpha@steudten.com>
To: terry white <twhite@aniota.com>, linux-admin@vger.kernel.org
Subject: Re: syslog does not start
Date: Thu, 04 Mar 2004 22:58:47 +0100 [thread overview]
Message-ID: <4047A697.9030401@steudten.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0403041212010.27023@yossarian.aniota.net>
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?
-
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
next prev parent reply other threads:[~2004-03-04 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.4.33.0403011827120.21790-200000@cupid.che.iitb.ac.in>
2004-03-04 17:51 ` syslog does not start Luca Ferrari
2004-03-04 20:29 ` terry white
2004-03-04 21:52 ` Glynn Clements
2004-03-04 21:58 ` Thomas Steudten [this message]
2004-03-14 11:23 ` Luca Ferrari
2004-03-17 19:41 ` Thomas Steudten
2004-03-01 12:58 Luca Ferrari
2004-03-01 17:09 ` terry white
2004-03-02 8:05 ` Luca Ferrari
2004-03-02 12:18 ` terry white
2004-03-02 23:14 ` Jay Goodman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4047A697.9030401@steudten.com \
--to=alpha@steudten.com \
--cc=linux-admin@vger.kernel.org \
--cc=twhite@aniota.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).