On Wed, 9 Mar 2005, Eric Jahn wrote:
> On Wed, 2005-03-09 at 09:22 -0500, Kwan Lowe wrote:
> > The troubleshooting approach can depend on your distro. You have the right
> > idea in hunting down a bad or missing library. On an RPM distro you could do
> > something like:
> >
> > 1) rpm -qif /sbin/getty
>
> Thanks for your help Kwan. I don't think getty is the culprit here.
> Init says it can't start getty, but only because getty can't start
> (disabled because respawning too fast) because it waiting on another
> broken library. So how do I see what library that is? If I could see
> the full boot message that scrolls past super quickly (not dmesg, and
> not /var/log/messages) I think it might name the problem library. -Eric
You could edit /etc/inittab and replace a failing call to "/sbin/getty
getty_args" with "/usr/bin/strace /sbin/getty getty_args 2&> some_file".
Might want to include the date in the filename (or make the call not exit)
since init will call it over and over. Try calling getty manually from the
command line (pointed at e.g. tty8).
-- -eben ebQenW1@EtaRmpTabYayU.rIr.OcoPm home.tampabay.rr.com/hactarTwo atoms are walking along. Suddenly, one stops. The other says, "What's wrong?" "I've lost an electron." "Are you sure?" "I'm positive!"
----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:25:31 EDT