From: John Haxby <john.haxby@oracle.com>
To: netfilter@vger.kernel.org
Cc: /dev/rob0 <rob0@gmx.co.uk>
Subject: Re: Iptables "-m time" option doesn't update when the clock changes
Date: Wed, 04 Apr 2012 14:52:42 +0100 [thread overview]
Message-ID: <4F7C522A.7060808@oracle.com> (raw)
In-Reply-To: <20120404131451.GI3502@harrier.slackbuilds.org>
On 04/04/12 14:14, /dev/rob0 wrote:
> The author posted that in early 2007, saying that most/all distros
> get this wrong. Is that still the case?
I don't know about "most distros" but anything that calls hwclock
--systz one way or another will get it right. That include RHEL6 and
its equivalents and current Fedora (I'm not sure how far back in Fedora,
but quite a way).
The critical udev rule is likely to be found in
/lib/udev/rules.d/88-clock.rules:
ACTION=="add", SUBSYSTEM=="rtc", ATTR{hctosys}=="1", RUN+="/sbin/hwclock
--systz --rtc=/dev/%k"
The "ATTR{hctosys}" refers to /sys/devices/*/*/rtc/rtc0/hctosys (or
similar). If it contains "1" then you have CONFIG_RTC_HCTOSYS=y in
the kernel config which means that rtc setting works nicely. I forget
the details, but it's described in the corresponding Kconfig file.
jch
prev parent reply other threads:[~2012-04-04 13:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 9:10 Iptables "-m time" option doesn't update when the clock changes Sebastian Arcus
2012-03-29 9:12 ` Jan Engelhardt
2012-03-29 9:30 ` Sebastian Arcus
2012-03-29 10:00 ` Jan Engelhardt
2012-03-29 10:21 ` Sebastian Arcus
2012-03-29 10:45 ` Jan Engelhardt
2012-03-29 13:45 ` /dev/rob0
2012-04-02 19:57 ` Sebastian Arcus
2012-04-02 22:07 ` /dev/rob0
2012-04-03 11:31 ` Sebastian Arcus
2012-04-04 9:35 ` John Haxby
2012-04-04 13:14 ` /dev/rob0
2012-04-04 13:52 ` John Haxby [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=4F7C522A.7060808@oracle.com \
--to=john.haxby@oracle.com \
--cc=netfilter@vger.kernel.org \
--cc=rob0@gmx.co.uk \
/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).