From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
Cc: supervision@list.skarnet.org
Subject: Re: Time discrepancy between svlog and application in log
Date: Fri, 2 Sep 2005 09:46:42 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.61.0509020944020.17206@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <78841E2C-AC3E-41EA-9A5C-346B1DBF68BD@nednieuws.com>
On Fri, 2 Sep 2005, Charles M. Gerungan wrote:
> Original line:
>
> @4000000043174ed71a26f434 2005-09-01 20:56:10: (log.c.73) server started
>
> Piped through tai64nlocal:
>
> 2005-09-01 20:56:13.438760500 2005-09-01 20:56:10: (log.c.73) server started
>
> Why is there a discrepancy between the two times: 20:56:13 vs. 20:56:10?
Delay somewhere in a possibly busy system. "application" looked at its
watch. Decided the time was 20:56:10, started building a string, then
(some time later) pushed that string into a socket. Some time later,
svlogd pulled the string from the socket, looked at its watch, started
building a string, then wrote the string into the file.
Such discrepancy is inevitable, but won't necessarily be noticeable.
prev parent reply other threads:[~2005-09-02 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 11:03 Charles M. Gerungan
2005-09-02 13:46 ` Charlie Brady [this message]
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.61.0509020944020.17206@e-smith.charlieb.ott.istop.com \
--to=charlieb-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).