You are not logged in.
Pages: 1
Hi,
In case of a startup script failure, what log to look into? What pattern to look for?
Offline
you should look the files over /var/log/
particularly, the dmesg log
there is the "dmesg" command, which reads the log.
to read the last lines of this log, just write
dmesg | tail
to read the 20th last lines,
dmesg | tail -n 20
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
Looks like dmesg.log ends with the kernel output (grey lines ). Init scripts follow... Unfortunately, they follow fast enough so I can't even spot which one failed. What am I supposed to do?
Offline
'Scroll Lock' key stops boot so you can read which failed
br0tat0chip in #archlinux and on freenode
Offline
You should run the command manually, the service script will hide the errors, just catch the return status.
So if the mpd service fails, instead of doing
# /etc/rc.d/mpd start
do
# mpd
That should usually shed more light on the issue.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
'Scroll Lock' key stops boot so you can read which failed
That would be great . It's just that the keyboard in question lacks the 'Scroll Lock' key (Toshiba laptop). What could be a possible substitute?
Last edited by Llama (2009-03-22 16:58:56)
Offline
*ignore that*
Last edited by shiinta (2009-03-23 02:05:01)
Offline
It's just that the keyboard in question lacks the 'Scroll Lock' key (Toshiba laptop). What could be a possible substitute?
Ctrl-S/Ctrl-Q
Offline
Pages: 1