Re: turn on timestamps in kernel log messages?

On Mon, Aug 29, 2022 at 01:04:27AM +0100, void wrote:
> On Mon, Aug 29, 2022 at 12:46:45AM +0100, void wrote:
> > On Sun, Aug 28, 2022 at 06:00:34PM -0400, Dan Langille wrote:
> > > Did it work?
> > 
> > Not sure yet
> > 
> > This is with it set to 1:
> > 
> > kernel log messages:
> > +[2526502] tap3: link state changed to DOWN
> > +[2526886] tap3: link state changed to UP
> > +[2527114] tap3: link state changed to DOWN
> > +[2527124] tap3: link state changed to UP
> > +[2527231] tap3: link state changed to DOWN
> > +[2527242] tap3: link state changed to UP
> 
> # sysctl kern.msgbuf_show_timestamp=2
> 
> [2544779] tap12: link state changed to DOWN
> [2544789] tap12: link state changed to UP
> [2545295] tap12: link state changed to DOWN
> [2545306] tap12: link state changed to UP
> 
> so, unfortunately it doesn't give a useful timestamp.
> 
> What I'm looking for is something like 2022-08-29.01:02.05 BST
> or even just 2022-08-29.01:02

might be worth adjusting your syslog.conf to capture all kern.*
messages, then they'll land in /var/log/messages or somewhere similar
and have human readable timestamps.  here's an example from my
/var/log/messages file:

Aug 26 15:50:30 topanga kernel: tun0: link state changed to Up


hope this helps,
-pete

-- 
Pete Wright
pete@nomadlogic.org