From: Charlie Brady <charlieb-smarden-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: syslog from perl but no date (svlogd)
Date: Thu, 15 Jul 2004 19:06:17 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0407151856290.3069-100000@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <20040715222109.GE7203@digitus>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1304 bytes --]
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
next prev parent reply other threads:[~2004-07-15 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 22:21 Csillag Tamás
2004-07-15 23:06 ` Charlie Brady [this message]
2004-07-16 22:43 ` Csillag Tamás
2004-07-17 10:27 ` Csillag Tamás
2004-07-17 10:59 ` Clemens Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0407151856290.3069-100000@e-smith.charlieb.ott.istop.com \
--to=charlieb-smarden-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).