From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Roskin Date: Mon, 15 Feb 2010 02:03:22 -0500 Subject: [ath9k-devel] AR5008 hanging computer In-Reply-To: <824572.10530.qm@web57904.mail.re3.yahoo.com> References: <824572.10530.qm@web57904.mail.re3.yahoo.com> Message-ID: <1266217402.28738.19.camel@mj> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Fri, 2010-02-12 at 15:42 -0800, hong zhang wrote: > > Getting kernel log from /var/log is not a good idea. > > I know /var/log/syslog can hold more kernel message than dmesg. Any other disadvantage? That's true. But syslogd can omit low-priority messages from the kernel. Irrelevant logs from other software can be present. The timestamps are rarely needed and take extra space. They also don't compress well. The is no convenient alternative to "dmesg -c" to clear the log and start over. I would not recommend clearing the system log like that, as it can contain important information from the userspace, such as break-in attempts etc. If the log buffer overflows, perhaps it's a good idea to disable irrelevant debug options or to stop debug output as soon as the error condition occurs. If case of hangs, serial console could help. -- Regards, Pavel Roskin