re: kern/46488: Feature suggestion for "dmesg" output

[matthew green <mrg%eterna.com.au@localhost>]

The following reply was made to PR kern/46488; it has been noted by GNATS.

From: matthew green <mrg%eterna.com.au@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
    netbsd-bugs%netbsd.org@localhost, 
randolf+netbsd.org%inter-corporate.com@localhost
Subject: re: kern/46488: Feature suggestion for "dmesg" output
Date: Wed, 30 May 2012 17:43:51 +1000

 >  >  Aren't they logged (with timestamp) by syslogd in /var/log/messages (at
 >  >  least in the default configuration) as well?
 >  >  
 >  >  If log rotation gets in the way, you can configure it to a kernel only
 >  >  log and rotate that slower (or never).
 >  
 >      The problem with /var/log/messages is that a lot of things get 
 >  logged there and after months the old entries that are needed to 
 >  determine time/date of events are no longer available (due to the log 
 >  files being cycled out eventually) on high-volume systems.
 >  
 >      Setting up a kernel-only log seems like a great solution (although 
 >  timestamps in dmesg output for errors that occur after the boot 
 >  process is complete would still be nice).  Which "man" page should I 
 >  read to find out more about configuring this?
 
 see /usr/share/examples/syslogd/all.debug.
 
 i wish we used this as a default, i love having each level have its
 own file etc.  also, i think in 2012 it's time to increase the
 default sizes.
 
 
 .mrg.
 
 ps: also see all.newsyslog.conf.