Empathy List Archives

HM

Hal Murray

Sun, Jan 1, 2017 1:05 PM

No NTP was running.

What software told the kernel that there was going to be a leap second at the
end of the day?

--
These are my opinions. I hate spam.

ghane0@gmail.com said: > No NTP was running. What software told the kernel that there was going to be a leap second at the end of the day? -- These are my opinions. I hate spam.

DM

David Malone

Sun, Jan 1, 2017 2:44 PM

On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote:

ghane0@gmail.com said:

No NTP was running.

What software told the kernel that there was going to be a leap second at the
end of the day?

I guess it was part of systemd?

https://wiki.archlinux.org/index.php/systemd-timesyncd

David.

On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote: > ghane0@gmail.com said: > > No NTP was running. > What software told the kernel that there was going to be a leap second at the > end of the day? I guess it was part of systemd? https://wiki.archlinux.org/index.php/systemd-timesyncd David.

P

Paul

Sun, Jan 1, 2017 3:36 PM

On Sun, Jan 1, 2017 at 9:44 AM, David Malone dwmalone@maths.tcd.ie wrote:

On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote:

ghane0@gmail.com said:

No NTP was running.

What software told the kernel that there was going to be a leap second

at the

end of the day?

I guess it was part of systemd?

Unless you explicitly install ntp, systemd runs an SNTP-like client to keep
the time increasing (say across reboots) and notify the kernel of pending
leap seconds. In that circumstance one would expect to see ...59:59 twice.

https://www.freedesktop.org/software/systemd/man/systemd-timesyncd.service.html

On Sun, Jan 1, 2017 at 9:44 AM, David Malone <dwmalone@maths.tcd.ie> wrote: > On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote: > > ghane0@gmail.com said: > > > No NTP was running. > > > What software told the kernel that there was going to be a leap second > at the > > end of the day? > > I guess it was part of systemd? > Unless you explicitly install ntp, systemd runs an SNTP-like client to keep the time increasing (say across reboots) and notify the kernel of pending leap seconds. In that circumstance one would expect to see ...59:59 twice. https://www.freedesktop.org/software/systemd/man/systemd-timesyncd.service.html

SG

Sanjeev Gupta

Mon, Jan 2, 2017 3:38 AM

On Sun, Jan 1, 2017 at 10:44 PM, David Malone dwmalone@maths.tcd.ie wrote:

On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote:

ghane0@gmail.com said:

No NTP was running.

What software told the kernel that there was going to be a leap second

at the

end of the day?

I guess it was part of systemd?

     https://wiki.archlinux.org/index.php/systemd-timesyncd

Yes, please.

--
Sanjeev Gupta
+65 98551208 http://www.linkedin.com/in/ghane

On Sun, Jan 1, 2017 at 10:44 PM, David Malone <dwmalone@maths.tcd.ie> wrote: > On Sun, Jan 01, 2017 at 05:05:45AM -0800, Hal Murray wrote: > > ghane0@gmail.com said: > > > No NTP was running. > > > What software told the kernel that there was going to be a leap second > at the > > end of the day? > > I guess it was part of systemd? > > https://wiki.archlinux.org/index.php/systemd-timesyncd Yes, please. -- Sanjeev Gupta +65 98551208 http://www.linkedin.com/in/ghane

time-nuts@lists.febo.com

Re: [time-nuts] Leap-second capture on laptop