You are not logged in.
Pages: 1
Topic closed
Arch boots up after the Arch Linux 0.7 Wombat message and some processes FAIL. But the boot process is too fast, so that i can't see the details. Are these messages logged somewhere, because i can't find them in /var/log.
Till human voices wake us, and we drown. -Eliot
Offline
they're not logged, but you can remove the first character from /etc/issue (it's a c or something like that) so that it doesn't clear the screen
Offline
well, ok. But the system launches gdm at the end of the boot sequence, and also, even if i stop gdm from starting, what about the stuff that got scrolled off the screen? There must be a way to dump that stuff into a text file somehow, maybe with bootlogd? Unfortunately I have been unable to figure it out, yet.
Till human voices wake us, and we drown. -Eliot
Offline
if your talking about the messages that appear after the Arch Wombat message but before the daemons load try renaming /etc/rc.sysinit to /etc/rc.sysinit2 and create a new /etc/rc.sysinit file with the same permissions as the original. In this file put:
#!/bin/bash
/etc/rc.sysinit2 2>somefile
that will echo standard error into somefile. If that doesn't give you the errors replace the 2 with & and both standard out and standard error will be logged into that file.
Make sure that new file is executable.
Offline
I'm talking about all the messages from the Arch Wombat message until the login prompt, in essence evrything after the kernel messages (which are availabe using dmesg), i.e. the colorized messages about loading the modules, mounting the filesystems, loading the daemons. Some things don't just go from BUSY to DONE, but to FAIL instead. I can't know which ones because the whole things passes by too fast and I don't have bionic vision.
I'll try the solution you gave me and see if it works.
Till human voices wake us, and we drown. -Eliot
Offline
what I gave you will do everything up until the DAEMONS. For that go into /etc/rc.multi and change this line:
/etc/rc.d/$daemon start
to
/etc/rc.d/$daemon start 2>someotherdifferentfile
or alternately, you could add sleep 5 beneath the line and that will wait 5 seconds before proceding to the next daemon.
Offline
I tried both tricks but it didn't work because the filesystem is read-only during the beginning of rc.sysinit's execution and so the whole command flopped and i was thrown to the login prompt prematurely, long story short i remounted / rw and undid the evil i had done. I finaly saw the damn error by inserting a cat in my rc.local, stopped the whole thing cold, but the thing is, ctrl-c wouldn't kill cat, my system had been reduced to repeating everything i typed while trying to kill it.
My question remains, why not log all that stuff somewhere? I know now that all these errors are reported in various /var/log files, but wouldn't it be nice if it were logged and so would give you some heads up as to where to look in all those (huge) log files crammed in /var/log?
Till human voices wake us, and we drown. -Eliot
Offline
Isn't there a program (tee, I think) that will output to the screen and a file? If so, you could maybe pipe the daemon call to 'tee /var/log/daemon.log' and get both visual confirmation and logging?
v/r
Suds
Offline
You might be able to find the information you need in:
/var/log/everything
Jon
Offline
From another thread: http://wiki.archlinux.org/index.php/Dis … ow_control
Offline
Mr.Alex the last post in this thread was over five years ago, resurrecting it to post a link to the wiki is not going to help the OP
http://wiki.archlinux.org/index.php/For … Bumping.27
Closing
Offline
Pages: 1
Topic closed