From: Karel Zak <kzak@redhat.com>
To: JWP <elseifthen@gmx.com>
Cc: util-linux@vger.kernel.org
Subject: Re: * RECALL * [PATCH 1/2] hwclock: hctosys drift compensation
Date: Tue, 16 Sep 2014 11:35:25 +0200 [thread overview]
Message-ID: <20140916093525.GG7867@x2.net.home> (raw)
In-Reply-To: <5416F1CC.2010007@gmx.com>
On Mon, Sep 15, 2014 at 10:03:56AM -0400, JWP wrote:
> So, also on my hwclock todo list is drift correcting --show.
> I believe that doing them together will yield a more eloquent
> patch, and streamline the code in general. Therefore, please
> disregard this patch for the time being. I apologize for
> submitting it prematurely.
OK, the idea to read adjtime file when we apply HW clock to
sys time makes sense.
> Of course, comments on the concepts or the code are welcome.
Something else:
See Documentation/TODO, the writable /etc/adjtime sucks, because in
many cases we want to keep /etc read-only. I see two possible ways:
1. move the file to /var/lib/hwclock/adjtime
This is already possible by "./configure ADJTIME_PATH=/var/lib/hwclock/adjtime"
(used for example by Linux-from-scratch project).
-- the problem is that the file (specially last UTC/LOCAL line)
may be expected by another tools
2. create another independent /var/lib/hwclock/drift file with
info about HW clock drift numbers and keep only zeros and
and UTC/LOCAL setting in /etc/adjtime.
This could be implemented backwardly compatible, if there is no
/var/lib/hwclock then always use /etc/adjtime for drift numbers.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-09-16 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-14 19:29 [PATCH 1/2] hwclock: hctosys drift compensation JWP
2014-09-14 19:46 ` [PATCH 2/2] hwclock: hctosys drift compensation man page JWP
2014-09-15 14:03 ` * RECALL * [PATCH 1/2] hwclock: hctosys drift compensation JWP
2014-09-16 9:35 ` Karel Zak [this message]
2014-09-16 13:08 ` JWP
2014-09-16 16:32 ` Bruce Dubbs
2014-09-16 23:08 ` JWP
2014-09-17 9:55 ` Karel Zak
2014-09-17 13:34 ` elseifthen
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=20140916093525.GG7867@x2.net.home \
--to=kzak@redhat.com \
--cc=elseifthen@gmx.com \
--cc=util-linux@vger.kernel.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).