From: Lloyd Zusman <ljz@asfast.com>
Subject: Incorrect leap seconds in runit's log timestamps
Date: Wed, 19 Jan 2005 14:07:43 -0500 [thread overview]
Message-ID: <von2c2xaqa.ln2@hippo.asfast.net> (raw)
I'm still using runit-1.0.3 (will upgrade soon).
I have just noticed that leap seconds are not properly being accounted for in the timestamps in the log/main/current files for each process that I'm managing. These timestamps seem to be 11 seconds off from UTC and 10 seconds off from TAI in the other direction.
I believe that TAI and UTC are 21 seconds apart these days, although a while ago, the discrepancy was only 11 seconds. This leads me to believe that the 11-second offset might have been hard coded into an early version of runit, and then never was changed.
Or am I missing something?
Also, when I upgrade to the latest version of runit, will this leap-second discrepancy change, by any chance?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
God bless you.
next reply other threads:[~2005-01-19 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 19:07 Lloyd Zusman [this message]
2005-01-19 20:37 ` Joël Riou
2005-01-19 23:56 ` Lloyd Zusman
2005-01-20 0:34 ` Never mind! (was: Incorrect leap seconds in runit's log timestamps) Lloyd Zusman
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=von2c2xaqa.ln2@hippo.asfast.net \
--to=ljz@asfast.com \
/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).