From: "Csillag Tamás" <cstamas@digitus.itk.ppke.hu>
Cc: supervision@list.skarnet.org
Subject: Re: syslog from perl but no date (svlogd)
Date: Sat, 17 Jul 2004 00:43:52 +0200 [thread overview]
Message-ID: <20040716224352.GI7203@digitus> (raw)
In-Reply-To: <Pine.LNX.4.44.0407151856290.3069-100000@e-smith.charlieb.ott.istop.com>
On 07/15, Charlie Brady wrote:
>
> On Fri, 16 Jul 2004, Csillag[iso-8859-2] Tamás wrote:
>
> > The only problem I came across, is a date logging issue.
...
> > user.notice: Jul 15 23:52:52 logger: test
> >
> > But if I run the following perl script:
> ...
> > The line is the following:
> > mail.info: example.pl[3449]: test
> >
> > 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 read them before posting. (I agree)
> 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.
Yes but in this case I would like to omit 'Jul 15 23:52:52' part to only have
2004-07-16_22:35:35.00431 at the beginning of each line.
I will look to the code if it can be imlemented without messing up the
code.
Do you know what could be a prefered way?
Hmm, maybe some kind of processor can do the hard work for me.
Maybe a perl script?
I will mail it here if I have a working solution.
--
cstamas
next prev parent reply other threads:[~2004-07-16 22:43 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
2004-07-16 22:43 ` Csillag Tamás [this message]
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=20040716224352.GI7203@digitus \
--to=cstamas@digitus.itk.ppke.hu \
--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).