On 2017-03-07 09:02, Per Jessen wrote:

/usr/sbin/ntpd -g -q

Let's try. The effective call is: /usr/sbin/ntpd -g -q 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org The result is: minas-tirith:~ # /etc/cron.hourly/mine-clocksync 7 Mar 13:25:18 ntpd[4023]: ntpd 4.2.8p9@1.3265-o Mon Dec 19 17:18:26 UTC 2016 (1): Starting 7 Mar 13:25:18 ntpd[4023]: Command line: /usr/sbin/ntpd -g -q 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org 7 Mar 13:25:18 ntpd[4023]: proto: precision = 0.559 usec (-21) authreadkeys: full access list <NULL> 7 Mar 13:25:18 ntpd[4023]: switching logging to file /var/log/ntp 7 Mar 13:25:18 ntpd[4023]: Listen and drop on 0 v6wildcard [::]:123 7 Mar 13:25:18 ntpd[4023]: Listen and drop on 1 v4wildcard 0.0.0.0:123 7 Mar 13:25:18 ntpd[4023]: Listen normally on 2 lo 127.0.0.1:123 7 Mar 13:25:18 ntpd[4023]: Listen normally on 3 wlan0 192.168.1.129:123 7 Mar 13:25:18 ntpd[4023]: Listen normally on 4 lo [::1]:123 7 Mar 13:25:18 ntpd[4023]: Listen normally on 5 wlan0 [fe80::eee:e6ff:fed7:bb5f%3]:123 7 Mar 13:25:18 ntpd[4023]: Listening on routing socket on fd #22 for interface updates 7 Mar 13:25:18 ntpd[4023]: 0.0.0.0 c016 06 restart 7 Mar 13:25:18 ntpd[4023]: DNS 0.pool.ntp.org -> 193.145.15.15 7 Mar 13:25:18 ntpd[4023]: DNS 1.pool.ntp.org -> 158.227.98.15 7 Mar 13:25:18 ntpd[4023]: DNS 2.pool.ntp.org -> 81.19.96.148 7 Mar 13:25:18 ntpd[4023]: DNS 3.pool.ntp.org -> 213.251.52.234 7 Mar 13:25:18 ntpd[4023]: DNS 0.pool.ntp.org -> 158.227.98.15 7 Mar 13:25:18 ntpd[4023]: DNS 1.pool.ntp.org -> 193.145.15.15 7 Mar 13:25:18 ntpd[4023]: DNS 2.pool.ntp.org -> 158.227.98.15 7 Mar 13:25:18 ntpd[4023]: DNS 3.pool.ntp.org -> 81.19.96.148 7 Mar 13:25:19 ntpd[4023]: DNS 0.ch.pool.ntp.org -> 195.186.4.100 7 Mar 13:25:19 ntpd[4023]: DNS 1.ch.pool.ntp.org -> 212.51.144.44 7 Mar 13:25:19 ntpd[4023]: DNS 0.fr.pool.ntp.org -> 95.81.173.8 7 Mar 13:25:19 ntpd[4023]: DNS 0.uk.pool.ntp.org -> 80.87.131.131 7 Mar 13:25:19 ntpd[4023]: DNS 0.es.pool.ntp.org -> 81.19.96.148 7 Mar 13:25:19 ntpd[4023]: DNS Isengard.valinor -> 192.168.1.16 7 Mar 13:25:40 ntpd[4023]: ntpd: time set +15.161791 s ntpd: time set +15.161791s minas-tirith:~ # Instead of using the servers in the command line, it is using those in the ntp.conf file. Nod bad in itself, but unexpected. So I can instead not provide any server in the command line, I like that. My script is now, taking ideas from everybody that posted: #!/bin/sh LOGGER=/usr/bin/logger FACILIDAD=user.notice TAG=my_hourly_clocksync $LOGGER -t $TAG -p $FACILIDAD "Going to sync time now." #/usr/sbin/rcntp ntptimeset #Does not exist in Leap. /usr/sbin/ntpd -g -q ERR=$? # set hardware clock also in case of reboot if [ $ERR -eq 0 ] then /usr/sbin/hwclock -w echo echo "set hardware clock also in case of reboot" fi $LOGGER -t $TAG -p $FACILIDAD "Time should now be synced." -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

Carlos E. R. wrote:

There is no manual for ntpdate.

There used to be , e.g. in openSUSE 10.3 and 11.4. ntpdate is deprecated. -- Per Jessen, Zürich (4.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

On 2017-03-07 14:00, Mathias Homann wrote:

...

Am Dienstag, 7. März 2017, 03:45:40 CET schrieb Carlos E. R.:

...

No, running the ntpd daemon is not an option here.

...why? just wondering.

Because the laptop is not always connected to internet.

You can still run ntpd. It does not require a permanent connection. -- Per Jessen, Zürich (5.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 07/03/17 15:50, Carlos E. R. wrote:

...

You can still run ntpd. It does not require a permanent connection. I'm unsure of that. What does it do when the connection dies? What if the machine suspends or hibernates?

- perhaps "#systemctl status ntpd.service" shows ...... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

On 2017-03-07 14:43, Per Jessen wrote:

...

Carlos E. R. wrote:

...

On 2017-03-07 14:00, Mathias Homann wrote:

...

Am Dienstag, 7. März 2017, 03:45:40 CET schrieb Carlos E. R.:

...

No, running the ntpd daemon is not an option here.

...why? just wondering.

Because the laptop is not always connected to internet.

You can still run ntpd. It does not require a permanent connection.

I'm unsure of that. What does it do when the connection dies?

Typically it will be configured to use the local clock.

What if the machine suspends or hibernates?

Then it won't adjust any time :-)

Suppose there is network, it hibernates, and on restore there is no network, the more complex situation. During hibernate the disciplined clock does not run; instead it reads the clock from the cmos on awake, which can be off by several seconds. But there being no network, it can't. When it gets a time, it will try to slew, which can take hours at best: typically the machine will hibernate again before it syncs.

Is that a problem? I mean, it's a laptop without permanent connection, how accurate does it need to be?

I also think that on some of those situations it bails off.

I can't believe it would do a good job.

In my experience it does a very good job. I have 2-3 laptops (12.3 and leap422) - they spend hours suspended or hibernation or just powered off. I've never noticed any problems. -- Per Jessen, Zürich (6.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

...

In my experience it does a very good job. I have 2-3 laptops (12.3 and leap422) - they spend hours suspended or hibernation or just powered off. I've never noticed any problems.

No, you would have to compare the local time with an accurate clock.

Believe me, I do. Don't be silly, Carlos - of course I would notice if the time was suddenly out by a minute or so. Honestly, if you don't believe it'll work, don't do it. If you want advice - well, it works fine for me, just do it. -- Per Jessen, Zürich (3.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

On 2017-03-07 22:28, Per Jessen wrote:

...

Carlos E. R. wrote:

...

...

In my experience it does a very good job. I have 2-3 laptops (12.3 and leap422) - they spend hours suspended or hibernation or just powered off. I've never noticed any problems.

No, you would have to compare the local time with an accurate clock.

Believe me, I do. Don't be silly, Carlos - of course I would notice if the time was suddenly out by a minute or so.

Honestly, if you don't believe it'll work, don't do it. If you want advice - well, it works fine for me, just do it.

Please, don't be mad at me :-)

I tried years ago and it did not work for me. Maybe now it would work.

Sorry, I was a little frustrated last night, long day and such. Basically, I'm using ntpd on laptops for over 10 years. Sometimes they have a connection, sometimes they don't. Sometimes they're off/suspended/hibernated for days etc. I don't exactly watch over the clock to see that it is sync'ed, but if there was a problem I feel certain I would have noticed by now. This is a list of some 1500 restarts since July 2011 (from /var/log/ntp) on my main laptop: http://files.jessen.ch/toshiba1-clock-step -- Per Jessen, Zürich (6.8°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. wrote:

...

Basically, I'm using ntpd on laptops for over 10 years. Sometimes they have a connection, sometimes they don't. Sometimes they're off/suspended/hibernated for days etc. I don't exactly watch over the clock to see that it is sync'ed, but if there was a problem I feel certain I would have noticed by now.

This is a list of some 1500 restarts since July 2011 (from /var/log/ntp) on my main laptop:

http://files.jessen.ch/toshiba1-clock-step

Restarts? Is that reboots? Or just ntpd restart?

I think they happen on restart and resume and when interface are changed.

It doesn't seem to detect the hibernation, but the reappearance of the network interface.

Yes, the latter is the important bit. -- Per Jessen, Zürich (7.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org