From: elseifthen <elseifthen@gmx.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: * RECALL * [PATCH 1/2] hwclock: hctosys drift compensation
Date: Wed, 17 Sep 2014 09:34:25 -0400 [thread overview]
Message-ID: <54198DE1.8040008@gmx.com> (raw)
In-Reply-To: <20140917095528.GJ7867@x2.net.home>
On 09/17/2014 05:55 AM, Karel Zak wrote:
>> My initial thought when I read u-l's todo list was that adjtimex [ -c | -a ]
>> depend upon /etc/adjtime *drift* data. Do we care about breaking that?
>
> I'm not sure, but I guess adjtimex reads /etc/adjtime to get info
> about UTC/LOCAL only. Well, it seems we need to check adjtimex code.
man 8 adjtimex
-c[count], --compare[=count]
... CMOS clock readings are adjusted
for systematic drift using using the correction in /etc/adjtime
-- see hwclock(8)...
> Note that we have hwclock --compare to provide adjtimex -c functionality
> with in hwclock.
I have not had a chance to examine it closely yet, but it appears to be quite
rudimentary at this point when compared to adjtimex -c. I'm not sure I understand
the purpose of trying to build adjtimex into hwclock anyway. Why not just use
adjtimex to do adjtimex things?
>> I have often thought that hwclock should have a separate 'configuration' file,
>> for example, to allow specific init behavior customization without requiring
>> system admins to modify the init scripts.
>
> The old RHEL/Fedora has /etc/sysconfig/hwclock where is possible
> to specify hwclock command line, so no one is forced to modify init
> scripts. All you need is to read the file from your init scripts.
But that is distro specific. Rather than having everyone baking their own
solution it seems more practical for hwclock to have its own config file.
This todo item seems like a good opportunity to do so.
> (but yes, we (upstream) still support the original hwclock(8) use-cases
> and non-systemd installations)
I'm glad you included this comment. I wouldn't wasting my time trying to
improve hwclock otherwise. I have no interest in dragging the systemd war
into this conversation, but my distro of choice is pushing back against it.
Also with IoT putting Linux into everything from automobiles to light bulbs,
and some of them interested in keeping good date-time, I think hwclock's init
capabilities could remain relevant for some time to come. Linux is about more
then just distros, yes?
Will
prev parent reply other threads:[~2014-09-17 13:34 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
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 [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=54198DE1.8040008@gmx.com \
--to=elseifthen@gmx.com \
--cc=kzak@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.