[email protected] wrote:
The simplest way to achieve this is to:
a) Hack ntpd to "not notice" the leap-second announce bits 01 in
the packet header and pretend they're actually 00. This will
make it not insert a leap second.
Would a rude and crude way to do this be to shut down ntpd at say
11:55PM and restart it at 00:01?
What I am asking is when is the flag sent to the kernel. My reading of
the kernel code says that it will insert the second on the second roll
immeadiatly after the flag is set.
b) Run it with the -x flag so that it always slews the time.
The real solution would be to implement Markus Kuhn's UTS proposal
(http://www.cl.cam.ac.uk/~mgk25/uts.txt), which is about the most
reasonable meshing of the expectation that there are 86400
seconds per day with the fact that there are not.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger [email protected]
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |