search for: leapsecond

sorry, i didnt watch src/main/datetime.c ... Index: leap_second/src/main/datetime.c =================================================================== --- leap_second/src/main/datetime.c (????? 68608) +++ leap_second/src/main/datetime.c (?????) @@ -303,14 +303,15 @@ } #ifndef HAVE_POSIX_LEAPSECONDS -/* There have been 25 leapseconds: see .leap.seconds in R +/* There have been many leapseconds: see .leap.seconds in R + * (as.Date(.leap.seconds)-as.Date("1970-01-01"))*86400 */ -static int n_leapseconds = 25; static const time_t leapseconds[] = { 78796800, 94694400,126230400,1577...

hi, Index: leap_second/src/library/base/R/zdatetime.R =================================================================== --- leap_second/src/library/base/R/zdatetime.R (revision 68608) +++ leap_second/src/library/base/R/zdatetime.R (working copy) @@ -24,7 +24,8 @@ "1979-12-31", "1981-6-30", "1982-6-30", "1983-6-30",

...y code > before and happy with it), but having to reboot frequently is not > ideal either, particularly on machines where scheduling downtime is a > fairly involved process. I'm looking for the compromise with the > least pain involved. > Hi Les, https://access.redhat.com/labs/leapsecond/leap_vulnerability.sh If you don't have a subscription then the key bits from the script are: # RHEL 4 needs to be after -89 # RHEL 5 needs to be after -164 # RHEL 6 Affected Versions # 6 GA: All Versions # 6.1: Versions before -131.30.2 # 6.2: Versions before -220.25.1 # 6.3: Versions before -...

...o build it, like from the Fedora package) to set the leap flag. Then just watch your system through the leap second. - If you also need to "prove" NTP, you'll have to set up a second system to be your NTP server. Set it to local mode with no outside servers, add the current leapseconds file, and set it's clock to a little before the leap second. Sync your test server to that clock, then wait for the leap second. The issue (from IIRC 2009?) I ran into with a leap second only happened when the kernel was under load (race condition on console lock when printing the "...

On Tue, 24 Mar 2015 12:56:27 -0500 Les Mikesell wrote: > Doesn't anyone have a list of the oldest > kernel version for each Centos version you could be running and still > avoid known problems? The best answer to your question is "the latest version", since previous versions all have known issues of one kind or another. It's not a great idea to run outdated Centos

I glanced at the .leap.seconds object and noticed that it has not been updated for the most recent leap second that occurred 2005 December 31, 23h 59m 60s. See the IERS bulletin here: http://hpiers.obspm.fr/iers/bul/bulc/bulletinc.dat Moreover, after a more careful glance at the .leap.seconds object, I noticed that there are two incorrect entries. First, there was not a leap second on 1986 June

On Tue, Jan 20, 2015 at 3:27 PM, Michael Hennebry <hennebry at web.cs.ndsu.nodak.edu> wrote: > Unix and ntp handle leap seconds a bit differently. > Unix time increases during the leap second and drops back a second after. > Ntp freezes time during the leap second. > OS kernels may do either or neither. Does anyone have a succinct summary of how to prove to management-types that

On Fri, Mar 6, 2015 at 2:04 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 03/06/2015 01:41 PM, Les Mikesell wrote: >> >> I just want the package revisions for at least the kernel and tzdata* >> files and anything else where previously-found bugs related to the >> leap second have been fixed. > > > https://access.redhat.com/articles/15145 In

So, I have a server at home that has four VMs running inside it. All are managed via puppet. The physical host runs puppetmasterd. I don''t recall noticing this before, but puppetmasterd has decided to be kind of crazy. Here''s the physical host with no puppetmasterd running: top - 11:36:15 up 271 days, 15:16, 1 user, load average: 5.68, 5.50, 6.45 Tasks: 129 total, 1

...LAGS where there is not. #---------------------------------------------------------------------- #2 const char ... vs char #---------------------------------------------------------------------- had to compile with -qinitauto=00 to get the program to run the program to check for POSIX handling of leapseconds. Without it, the program hangs! #---------------------------------------------------------------------- # There needs to be some way to set an AR_FLAGS variable, ... #---------------------------------------------------------------------- I've tried setting environement variables, running con...

From: David Vrabel <david.vrabel@citrix.com> The high resolution timer code gets notified of step changes to the system time with clock_was_set() or clock_was_set_delayed() calls. If other parts of the kernel require similar notification there is no clear place to hook into. Add a clock_was_set atomic notifier chain (clock_was_set_notifier_list) and call this in place of clock_was_set().