Your message dated Mon, 08 Apr 2019 11:34:56 +0000
with message-id <[email protected]>
and subject line Bug#902026: fixed in systemd 241-3
has caused the Debian Bug report #902026,
regarding systemd: systemd-timesyncd should not run, when chronyd is running
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.)


-- 
902026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902026
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 238-5
Severity: normal

Dear systemd Debian package maintainers,
it seems I found out a regression of systemd-timesyncd.

It used to refuse to start, whenever other NTP clients (such as chrony)
were used.
If I read bug #805927 correctly, now this is accomplished with
other NTP clients shipping service files with an appropriate
"Conflicts=systemd-timesyncd.service" directive.
However, this does not seem to work as expected.

Please let me explain.

I have chrony running on my system, and its service file seems
to satisfy the above requirement:

  $ cat /lib/systemd/system/chrony.service
  [Unit]
  Description=chrony, an NTP client/server
  Documentation=man:chronyd(8) man:chronyc(1) man:chrony.conf(5)
  Conflicts=systemd-timesyncd.service openntpd.service ntp.service
  After=network.target
  ConditionCapability=CAP_SYS_TIME
  
  [Service]
  Type=forking
  PIDFile=/run/chronyd.pid
  EnvironmentFile=-/etc/default/chrony
  ExecStart=/usr/sbin/chronyd $DAEMON_OPTS
  ExecStartPost=-/usr/lib/chrony/chrony-helper update-daemon
  PrivateTmp=yes
  ProtectHome=yes
  ProtectSystem=full
  
  [Install]
  Alias=chronyd.service
  WantedBy=multi-user.target


But, as soon as I issue:

  # service systemd-timesyncd start

chrony dies and systemd-timesyncd starts.

I thought that systemd-timesyncd should refrain from starting and
leave chrony alone.

I think this misbehavior happens whenever all the services are
started (e.g.: at boot, when "systemctl daemon-reexec" is issued,
and so forth...).

This is very annoying.
My expectation is that the installation of chrony should automatically
disable systemd-timesyncd.
It used to work this way in the past, but it no longer seems to be the
case...

Could you please investigate and fix this issue?
Thanks for your time.

Bye!



-- Package-specific info:

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser          3.117
ii  libacl1          2.2.52-3+b1
ii  libapparmor1     2.12-4
ii  libaudit1        1:2.8.3-1
ii  libblkid1        2.32-0.1
ii  libc6            2.27-3
ii  libcap2          1:2.25-1.2
ii  libcryptsetup12  2:2.0.2-1
ii  libgcrypt20      1.8.3-1
ii  libgpg-error0    1.31-1
ii  libidn11         1.33-2.2
ii  libip4tc0        1.6.2-1
ii  libkmod2         25-1
ii  liblz4-1         1.8.2-1
ii  liblzma5         5.2.2-1.3
ii  libmount1        2.32-0.1
ii  libpam0g         1.1.8-3.7
ii  libseccomp2      2.3.3-2
ii  libselinux1      2.8-1
ii  libsystemd0      238-5
ii  mount            2.32-0.1
ii  procps           2:3.3.15-2
ii  util-linux       2.32-0.1

Versions of packages systemd recommends:
ii  dbus            1.12.8-3
ii  libpam-systemd  238-5

Versions of packages systemd suggests:
ii  policykit-1        0.105-20
pn  systemd-container  <none>

Versions of packages systemd is related to:
pn  dracut           <none>
ii  initramfs-tools  0.130
ii  udev             238-5

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 241-3

We believe that the bug you reported is fixed in the latest version of
systemd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <[email protected]> (supplier of updated systemd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 08 Apr 2019 12:59:32 +0200
Source: systemd
Architecture: source
Version: 241-3
Distribution: unstable
Urgency: high
Maintainer: Debian systemd Maintainers 
<[email protected]>
Changed-By: Michael Biebl <[email protected]>
Closes: 815582 902026 924406 924541 925190
Changes:
 systemd (241-3) unstable; urgency=high
 .
   [ Michael Biebl ]
   * Drop systemd-shim alternative from libpam-systemd.
     A fixed systemd-shim package which works with newer versions of systemd
     is unlikely to happen given that the systemd-shim package has been
     removed from the archive. Drop the alternative dependency from
     libpam-systemd accordingly.
   * Properly remove duplicate directories from systemd package.
     When removing duplicate directories from the systemd package, sort the
     list of directories in reverse order so we properly delete nested
     directories.
   * udev: Run programs in the specified order (Closes: #925190)
   * bash-completion: Use default completion for redirect operators
     (Closes: #924541)
   * networkd: Clarify that IPv6 RA uses our own stack, no the kernel's
     (Closes: #815582)
   * Revert "Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf"
     Apparently Conflicts= are not a reliable mechanism to ensure alternative
     NTP implementations take precedence over systemd-timesyncd.
     (Closes: #902026)
   * network: Fix routing policy rule issue.
     When multiple links request a routing policy, make sure they are all
     applied correctly. (Closes: #924406)
   * pam-systemd: Use secure_getenv() rather than getenv()
     Fixes a vulnerability in the systemd PAM module which insecurely uses
     the environment and lacks seat verification permitting spoofing an
     active session to PolicyKit. (CVE-2019-3842)
 .
   [ Martin Pitt ]
   * Enable udev autopkgtest in containers.
     This test doesn't actually need udev.service (which is disabled in
     containers) and works fine in LXC.
   * Enable boot-and-service autopkgtest in containers
     - Skip tests which can't work in containers.
     - Add missing rsyslog test dependency.
     - e2scrub_reap.service fails in containers, ignore (filed as #926138)
     - Relax pgrep pattern for gdm, as there's no wayland session in
       containers.
Checksums-Sha1:
 9f49e956d5d1761ba6beac51435cbec36fd5c757 4914 systemd_241-3.dsc
 becf2b7124ca7f189179c1bf95db173776571b87 152344 systemd_241-3.debian.tar.xz
 edb0acda4c43a257d45b537dfe4fd7f64e403697 9039 systemd_241-3_source.buildinfo
Checksums-Sha256:
 a993b25aaf8a46f2badb2e789ee1fbbdbcdfb313100c89e3d7287a5cea86027b 4914 
systemd_241-3.dsc
 2a7d599472081e3b38ef08ed677db519db1d2ef88390dca0799a791094b5b2f3 152344 
systemd_241-3.debian.tar.xz
 5f4fb7a55d55caded5549cc5fbff9fa4349f8c463d47ee08596956b6e05baf74 9039 
systemd_241-3_source.buildinfo
Files:
 d7d6cc24dbd5e5cd258b99ea29aa9068 4914 admin optional systemd_241-3.dsc
 a13953b14c90843c83647c232d4acc54 152344 admin optional 
systemd_241-3.debian.tar.xz
 54f3567fddd2fb83ecc0781dcda65a83 9039 admin optional 
systemd_241-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlyrL2kACgkQauHfDWCP
Ity/rBAAiZ0LsVsJ1WWN456tXrMKrlMvsUpD7jHKyryOQInt52Q58tGv29bzV9Di
Lmk4sfvYPQEj4fkZA26V0yypjCGU8htn0GDKONMcuoUhQMQQBKSp68PNL32X3G8b
RqAIZ+14OHK82grXMT6HQanorw6f9R/vzryOmypqIkN0TG5mrbjItzA8qTuY+Bma
WNA+PKv5F4JLvUlIFDHOk66SeWJA+Mft8NRVeki9e9YqueewBW/HNpEwzy/daAOC
EwLZzXG2AZ845HuA8Ovgi7UO1AOOq8OM0SbVSh1ODyz0qYuDvPxh5RwWyaDCCZm7
0L/cR6XK4ZdjRoL+W8XMUyf9YHvSpT2HuWq/wa/Ps+Yiudo0PtRVFuR+gmBDhjAh
DNF7AbOitHuFMEkxCm7G1GVq52euChpXUnOKCx1aJ2/uZkt/Xzb9KfGMtiqxdxo/
64KYdZRV3jXXmQYs6jlid998Xt+buw4Hiq0FgPewMcswfDSqRzzrhsZzjeqSF5z/
UsYk1Ixa71k+MjdcZwP/UyexoyGU1wPOg/GJZ67B2NZD0XYkepeITfR0p4yz9oJr
fvKj+J6xo+X2irHItG6JxWE15Qc4/JK25ZWbXsVTttImeHjpQHaUztd06Ytd23Cp
q4LOuSfayn4pTrTatGNcnsbJkqhjfJFD69fXBj4ak96WrJ3ywjI=
=jkxf
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to