Prev: Flash click problem
Next: (no subject)
From: Dotan Cohen on 28 Mar 2010 12:20 Is there a good resource for learning to read log files such as the kernel log, messages, dmesg, and such? I have been googling but found nothing really comprehensive yet understandable for a newbie. Where should I start? Thanks! -- Dotan Cohen http://bido.com http://what-is-what.com -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/880dece01003280911p5718199fna6c24b90071ad685(a)mail.gmail.com
From: Jari Fredriksson on 28 Mar 2010 12:40 On 28.3.2010 19:11, Dotan Cohen wrote: > Is there a good resource for learning to read log files such as the > kernel log, messages, dmesg, and such? I have been googling but found > nothing really comprehensive yet understandable for a newbie. Where > should I start? > Install logwatch, it will email you the essentials of daily logs. -- http://www.iki.fi/jarif/ You may be recognized soon. Hide.
From: Dotan Cohen on 28 Mar 2010 14:20 > Install logwatch, it will email you the essentials of daily logs. > Thanks. Actually, my goal is to understand what I am reading in the logs, not just to have the error pointed out. But I will install logwatch for sure. Right now, I am fighting with a kernel panicking machine. Instead of googling each and every line of the messages log, I would love a reference that would explain what common lines mean, with an emphasis on error lines. But I can find no such resource! -- Dotan Cohen http://bido.com http://what-is-what.com Please CC me if you want to be sure that I read your message. I do not read all list mail. -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/880dece01003281116n5c96d758g3653e0955fcdf6be(a)mail.gmail.com
From: T o n g on 28 Mar 2010 14:20 On Sun, 28 Mar 2010 19:11:03 +0300, Dotan Cohen wrote: > Is there a good resource for learning to read log files such as the > kernel log, messages, dmesg, and such? I have been googling but found > nothing really comprehensive yet understandable for a newbie. Where > should I start? When I used RedHat, it has a nice logfile GUI viewer so as for you to view all system logs in a central place. I am yet to find such tools under Debian. So far, multitail is the closest that I can find: Description: view multiple logfiles windowed on console multitail lets you view one or multiple files like the original tail program. . The difference is that this program creates multiple windows on your console (with ncurses). It can also use colors while displaying the logfiles for faster recognizing which lines are important and which are not. . It is optimized for terminal-sessions through slow links. Tag: interface::text-mode, role::program, scope::utility, uitoolkit::ncurses, use::viewing, works-with::logfile Comments? -- Tong (remove underscore(s) to reply) http://xpt.sourceforge.net/techdocs/ http://xpt.sourceforge.net/tools/ -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/hoo66t$7dn$2(a)dough.gmane.org
From: Jari Fredriksson on 28 Mar 2010 14:30
On 28.3.2010 21:16, Dotan Cohen wrote: >> Install logwatch, it will email you the essentials of daily logs. >> > > Thanks. Actually, my goal is to understand what I am reading in the > logs, not just to have the error pointed out. But I will install > logwatch for sure. > > Right now, I am fighting with a kernel panicking machine. Instead of > googling each and every line of the messages log, I would love a > reference that would explain what common lines mean, with an emphasis > on error lines. But I can find no such resource! > I have no problem reading log files. But I have 25 years behind of reading those. Maybe you are not entitled to use a computer in the first place? -- http://www.iki.fi/jarif/ You're definitely on their list. The question to ask next is what list it is. |