[systemd-devel] systemd-logger and external syslog daemon

Rainer Gerhards rgerhards at hq.adiscon.com
Fri Mar 11 00:51:47 PST 2011


> -----Original Message-----
> From: Michael Biebl [mailto:mbiebl at gmail.com]
> Sent: Friday, March 11, 2011 8:45 AM
> To: Rainer Gerhards
> Cc: systemd-devel at lists.freedesktop.org
> Subject: Re: [systemd-devel] systemd-logger and external syslog daemon
> 
> 2011/3/11 Rainer Gerhards <rgerhards at hq.adiscon.com>:
> >
> > So isn't that already a solution?
> >
> 
> The problem with PRINTK_TIME afaics is that it needs to be turned on
> explicitly whereas I'd expect SO_TIMESTAMP will be available always
> (if the kernel is recent enough)?
> 
> In any case you'd need to interpret that data on the rsyslog side, to
> compute a correct time stamp and then (optionally) strip off the [
> 5913.491848] markers.

I am not opposed to doing that -- I'd really like to have as good a timestamp
as possible. But the issue is that usually there is none. I've also seen that
the SO_TIMESTAMP fix is not present in currently frequently distributed
kernels

So question now: how to proceed?

Rainer


More information about the systemd-devel mailing list