From: Joseph Parmelee <jparmele@wildbear.com>
To: linux-kernel@vger.kernel.org
Subject: Real Time Clock
Date: Fri, 26 Apr 2013 16:57:18 -0600 (CST) [thread overview]
Message-ID: <alpine.LNX.2.00.1304261607460.2465@bruno> (raw)
Regards to all:
I have been playing heavily with NTP recently and have encountered several
problems which prevent its complete usage. I am not sure at this time
whether this latest problem (which appears to have security implications) is
in the kernel or coming from user space via ntpd.
Please help me find this. Can someone list the conditions (if any) under
which the kernel changes the RTC under its own volition? (As opposed to a
specific instruction from user space, like an ioctl).
Best regards,
Joseph Parmelee
jpar m ele at wild b ear dot c o m.
Thanks very much.
reply other threads:[~2013-04-26 23:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LNX.2.00.1304261607460.2465@bruno \
--to=jparmele@wildbear.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®