Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #212456 > unrolled thread

Raspian ntp manual invocation?

Back to article view | Back to linux.debian.user

Contents

  Raspian ntp manual invocation? conover@rahul.net (John Conover) - 2019-08-08 20:20 +0200
    Re: Raspian ntp manual invocation? Gene Heskett <gheskett@shentel.net> - 2019-08-08 20:20 +0200
      Re: Raspian ntp manual invocation? Sven Joachim <svenjoac@gmx.de> - 2019-08-08 20:40 +0200
        Re: Raspian ntp manual invocation? conover@rahul.net (John Conover) - 2019-08-08 21:30 +0200
          Re: Raspian ntp manual invocation? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-08 21:40 +0200
        Re: Raspian ntp manual invocation? "Martin McCormick" <martin.m@suddenlink.net> - 2019-08-08 21:50 +0200

#212456 — Raspian ntp manual invocation?

Raspbian sets its system clock on power up.

Is it possible to manually make a 24/7 Raspbian set its clock
periodically?

    Thanks,

    John

-- 

John Conover, conover@rahul.net, http://www.johncon.com/

[toc] | [next] | [standalone]

#212457

On Thursday 08 August 2019 13:46:00 John Conover wrote:

> Raspbian sets its system clock on power up.
>
> Is it possible to manually make a 24/7 Raspbian set its clock
> periodically?
>
>     Thanks,
>
>     John

It can run ntp just fine. 

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>

[toc] | [prev] | [next] | [standalone]

#212458

On 2019-08-08 14:18 -0400, Gene Heskett wrote:

> On Thursday 08 August 2019 13:46:00 John Conover wrote:
>
>> Raspbian sets its system clock on power up.
>>
>> Is it possible to manually make a 24/7 Raspbian set its clock
>> periodically?
>>
>>     Thanks,
>>
>>     John
>
> It can run ntp just fine.

Or systemd-timesyncd, which is shipped with systemd since version 213
and enabled by default in Debian since version 219-1.

Cheers,
       Sven

[toc] | [prev] | [next] | [standalone]

#212460

Thanks Sven.

timedatectl(1) yields:

          Local time: Thu 2019-08-08 12:16:51 PDT
      Universal time: Thu 2019-08-08 19:16:51 UTC
            RTC time: n/a
           Time zone: America/Los_Angeles (PDT, -0700)
     Network time on: yes
    NTP synchronized: yes
     RTC in local TZ: no

Does this mean ntp(1) is running periodically?

    Thanks,

    John

BTW, the reason for the question is that the RPi documentation claims
ntp(1) is run ONLY AT BOOT to set the system time. I have a 3b+ that
has been running many weeks with less than a 100 mS system clock
error, implying that ntp(1) is run periodically. Hardly possible with
commodity timing components.

Sven Joachim writes:
> 
> Or systemd-timesyncd, which is shipped with systemd since version 213
> and enabled by default in Debian since version 219-1.
> 

-- 

John Conover, conover@rahul.net, http://www.johncon.com/

[toc] | [prev] | [next] | [standalone]

#212461

On Thu, Aug 08, 2019 at 12:28:32PM -0700, John Conover wrote:
> timedatectl(1) yields:
> 
>           Local time: Thu 2019-08-08 12:16:51 PDT
>       Universal time: Thu 2019-08-08 19:16:51 UTC
>             RTC time: n/a
>            Time zone: America/Los_Angeles (PDT, -0700)
>      Network time on: yes
>     NTP synchronized: yes
>      RTC in local TZ: no
> 
> Does this mean ntp(1) is running periodically?

More likely, it means systemd-timesyncd.service is running.

> BTW, the reason for the question is that the RPi documentation claims
> ntp(1) is run ONLY AT BOOT to set the system time.

... "the RPi documentation"?  As in hardware documentation?  How on earth
would the hardware documentation know what the operating system is going
to do?  Unless it's talking about something that happens in the firmware
before the OS is loaded.  In which case, it wouldn't be ntp(1).  The (1)
indicates a Unix command utility.  Not pieces of the firmware or whatever.

> I have a 3b+ that
> has been running many weeks with less than a 100 mS system clock
> error, implying that ntp(1) is run periodically. Hardly possible with
> commodity timing components.

ps is your friend.  Or systemctl status systemd-timesyncd.service.  Or
journalctl -u systemd-timesyncd.service.

[toc] | [prev] | [next] | [standalone]

#212462

Sven Joachim <svenjoac@gmx.de> writes:
> Or systemd-timesyncd, which is shipped with systemd since version 213
> and enabled by default in Debian since version 219-1.
> 
> Cheers,
>        Sven
> 
> 
	I have a Raspberry Pi 2 which was running jessie in 2016
and then I upgraded to stretch in 2018.  The Pi runs 24/7 and
I've not had a bit of trouble with ntp keeping it to within a
second which is about as good as it normally gets on any
unix-like system.

Martin McCormick

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web