On Fri, 16 Jul 2004, Csillag[iso-8859-2] Tamás wrote:

> The only problem I came across, is a date logging issue.
> Let me explain: (I use socklog configuration created by socklog-conf)
> If I run
> # echo test | logger
> The following line appears in the logs
> user.notice: Jul 15 23:52:52 logger: test
> 
> But if I run the following perl script:
> 
> #!/usr/bin/perl
> 
> use Sys::Syslog qw(:DEFAULT setlogsock);
...
> The line is the following:
> mail.info: example.pl[3449]: test
> 
> The problem is that the latter lack's the time/date information.
> Most program works as expected but the perl based not.
> 
> I know that I can add a -t (or -tt) option to svlogd but it will add
> time information to *all* lines AFAIK.
> 
> I do not know if this is a perl bug and syslogd works around the
> problem, but it works right with it.

This is a problem with the syslog protocol. As you can see in
http://www.faqs.org/rfcs/rfc3164.html, the content of syslog messages is
ill-defined - essentially anything goes. Moreover, the recommended
TIMESTAMP format is in localtime, which as we've recently discussed here
is ambiguous. I'd recommend that you use -t or -tt in svlogd, and ignore
any timestamp which was supplied by the logging client. I guarantee you'll
be less confused taht way.

---
Charlie