Your message dated Tue, 24 Nov 2015 16:11:58 +0100
with message-id <[email protected]>
and subject line Re: Bug#805742: systemd: add ntpdate to the list of another 
NTP daemon installed
has caused the Debian Bug report #805742,
regarding systemd: add ntpdate to the list of another NTP daemon installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
805742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 227-2
Severity: normal

Dear Maintainer,

please add the binaries from ntpdate package to the "list of another NTP daemon 
installed"
in the systemd-timesyncd.service.d/disable-with-time-daemon.conf configuration 
file

Best
Denis


-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.113+nmu3
ii  libacl1         2.2.52-2
ii  libapparmor1    2.10-2+b1
ii  libaudit1       1:2.4.4-4
ii  libblkid1       2.27.1-1
ii  libc6           2.19-22
ii  libcap2         1:2.24-12
ii  libcap2-bin     1:2.24-12
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.4-3
ii  libkmod2        21-1
ii  liblzma5        5.1.1alpha+20120614-2.1
ii  libmount1       2.27.1-1
ii  libpam0g        1.1.8-3.1
ii  libseccomp2     2.2.3-2
ii  libselinux1     2.3-2+b1
ii  libsystemd0     227-2
ii  mount           2.27.1-1
ii  sysv-rc         2.88dsf-59.2
ii  udev            227-2
ii  util-linux      2.27.1-1

Versions of packages systemd recommends:
ii  dbus            1.10.2-1
ii  libpam-systemd  227-2

Versions of packages systemd suggests:
pn  systemd-container  <none>
ii  systemd-ui         3-4

-- Configuration Files:
/etc/systemd/logind.conf changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Denis

Am 22.11.2015 um 00:59 schrieb Michael Biebl:
> Am 22.11.2015 um 00:31 schrieb Denis Danilov:
>> Dear Michael
>>
>> during the boot I see that both timesyncd and ntpdate do the sync almost at 
>> the same time, like
>>
>> Nov 21 22:39:40 debian systemd-timesyncd[599]: Synchronized to time server 
>> 82.197.188.130:123 (3.debian.pool.ntp.org).
>> Nov 21 22:39:42 debian ntpdate[1678]: adjust time server 192.33.96.102 
>> offset -0.342289 sec
>>
>> one of them will be enough, or?
> 
> Well, as I said, ntpdate does it only once, during boot. timesyncd, like
> ntp, keeps your clock continuously updated.
> They serve different purposes.

ntpdate is not really an alternative to timesyncd, it only provides a
subset of the functionality and there is no real reason to have ntpdate
installed/running when timesyncd is active.
And since ntpdate is not real replacement for timesyncd, having it
installed should not disable timesyncd.

What you really want is to either uninstall ntpdate (since it's not
really necessary anymore) or have ntpdate do nothing if timesyncd is active.
For the latter, feel free to file a bug report against the ntpdate package.

Given the above, I'm going to close this bug report.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---

Reply via email to