You are not logged in.
Pages: 1
Hi,
Today I noticed a failure in a startup script. Probably MySql, but I can't be sure: it's the last one in sequence, no time to pinpoint it visually . I tried logs, found nothing; certainly because I didn''t know how to use them.
So my question is a general one: how to deal with logs and failures like this one? How am I supposed to approach a problem like this?
Offline
1-switch off automatic login to GUI (if the case)
or
2-remove first line from /etc/issue if you don't see which daemon did not start (in text login)
then see what failed
Zygfryd Homonto
Offline
/etc/issue (a nice little file indeed ):
[H[2J
Arch Linux (Don't Panic) \r (\n) (\l)
You mean, the line before "Arch Linux (Don't Panic)..."?
Offline
yeap, it cleans the screen
Zygfryd Homonto
Offline
Another forum thread: link
I made it long
as I lacked the time to make it short...
Offline
Pages: 1