[plug] inittab respawn

[Robert Andrews]

I run a tail on my /var/log/messages constantly when I am trying to find a
fault.
However The errors returned from init are not loged to the /var/log/messages
As I said before I understand that it is not possable to see boot up
messages on a terminal that does not exits
one would would have to be really dumb to think that this could be done
The error messages that I seen on the terminal was after the boot up was
complete and enters run level 3
Also issueing init q on my terminal does not display the errors messages
that are displayed on the "actual linux terminal'
I have also checked dmesg the errors are not displayed there iether
So my question still is "is it possable to display these errors on a
terminal"
"Not the actual boot messages"
I have just put my monitor back on my Linux box and issued init q from a
remote terminal all the errors are displayed on the linux terminal but not
the remote and I have checked all the logs that I know of and cannot find
the errors issued by init q


----- Original Message -----
From: "Brian Tombleson" <brian at paradigmit.com.au>
To: <plug at plug.linux.org.au>
Sent: Monday, January 29, 2001 8:34 PM
Subject: Re: [plug] inittab respawn


>
> ----- Original Message -----
> From: "Robert Andrews" <squirrel at emerge.net.au>
>
>
> > It was then that I could see all the error messages sent by init.
> > So my next question is why are these messages not sent to my terminal
> logged
> > on as root.
>
> Well, for starters, there is no terminal during most of your boot-up
> process.  The actual bootstrap messages are in /var/log/dmesg and
everything
> after the syslogd has bee started (early in the initialization after
> bootstrap but before your network/terminal is up) start going to
> /var/log/messages unless you have reconfigured the syslog daemon.
>
> It *really* helps to have a terminal on a machine when debugging
> system-level stuff.
>
> - Brian.
>
>
>