On Sun, 2014-01-19 at 14:16 +0100, Carlos E. R. wrote:
On 2014-01-18 23:17, Linda Walsh wrote:
This type of script is what is missing in "systemd" -- that makes it hard to debug problems like these, BTW, so going back to an earlier suse version to pull out the start scripts is a good start-point for seeing what systemd "should" be doing.
But Linda, ntp is still started by an old style systemv init script, /etc/init.d/ntp.
Correct for Factory.. there seems some reluctance in porting ntp to a
native systemd service (which would have its merits by the way).
I myself am running my 'branched' package of ntp (see
home:dimstar:branches:network:time/ntp) which comes with a systemd
service and integrates fully into systemd, so that also timedatectl
(part of the system toolset) work as expected and know about the time
daemon.
I did submit that package in the past but after the SR was lingering for
too long I figured there was no interest on large scale... so I keep on
running it for myself (given: it does not do all the mess the sysV
script does.. I'd consider this startup script a very good example on
what not to do: either the daemon is smart of not.. working around a
dumb daemon with smart startup scripts sounds like investing in the
wrong corner).
Cheers,
Dominique
PS: If anybody want to test above ntp package, please go ahead..
--
Dimstar / Dominique Leuenberger