Quoting richard lucassen (mailinglists@???):

> I know, but for the moment it works and it might (temporarely) resolve
> his time problem. It's quite simple, simpler than running ntpd.

1. Doing '/usr/sbin/ntpd -g -q' is _exactly_ as simple.

2. An important point: executing '/usr/sbin/ntpd -g -q' is not 'running
ntpd' in the fashion you probably have in mind, i.e., doesn't launch any
daemonised process. This should have been clear from part of the
manpage I quoted, but, for clarity's sake I'll quote it again:

       -q     Exit the ntpd just after the first time the clock is set.  This
              behavior mimics that of the ntpdate program, which is to be
              retired.  The -g and -x options can be used with this option.
              Note:  The kernel time discipline is disabled with this option.

With the '-q' switch, ntpd does a one-shot adjustment of the time and
then terminates -- which is precisely the behaviour desired by people
who (still, in 2016) opt to run ntpdate.

Thus my strong recommendation: Remove package ntpdate, as it's
deprecated and its contents will soon cease to exist entirely.
Install package ntp. Run '/usr/sbin/ntpd -g -q' as a maintenance
script at startup time -- as an exact functional equivalent to ntpdate,
except maintained code that is not just in the middle of being end-of-lifed.

> And apart from that, that a good point of systemd, if ever there are
> network problems or whatsoever, the boot time may increase by minutes
> as ntpd cannot start.

This is an extremely illogical objection from someone urging running
/usr/sbin/ntpdate, as the same is true for it.

> BTW, I'm running ntpd. And I'll have a look into OpenNTP, as stated
> elswhere in this thread.

Er, that elsewhere would have been my post. You're welcome. ;->

-- 
Cheers,             Grossman's Law:  "In time of crisis, people do not rise to
Rick Moen           the occasion.  They fall to the level of their training."
rick@???          http://linuxmafia.com/~rick/lexicon.html#grossman
McQ! (4x80)