Your message dated Thu, 2 Nov 2023 13:21:58 +0100
with message-id <ZUOUcWkNUGMrxfIh@lamella>
and subject line Re: Bug#1055205: chrony: SysV problems after upgrade
has caused the Debian Bug report #1055205,
regarding chrony: SysV problems after upgrade
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 ow...@bugs.debian.org
immediately.)
--
1055205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chrony
Version: 4.4-3
Severity: normal
I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/
(update-rc.d chrony remove).
But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and
starts chronyd, even though chronyd is SysV disabled.
Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these and
do not start chronyd. Maybe it's a good idea to just display a warning in that
case.
Richard.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages chrony depends on:
ii adduser 3.137
ii init-system-helpers 1.65.2
ii iproute2 6.5.0-4
ii libc6 2.37-12
ii libcap2 1:2.66-4
ii libedit2 3.1-20230828-1
ii libgnutls30 3.8.1-4+b1
ii libnettle8 3.9.1-2
ii libseccomp2 2.5.4-1+b3
ii tzdata-legacy 2023c-10
ii ucf 3.0043+nmu1
chrony recommends no packages.
Versions of packages chrony suggests:
ii bind9-dnsutils [dnsutils] 1:9.19.17-1
ii dnsutils 1:9.19.17-1
pn networkd-dispatcher <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Richard,
Le 2023-11-02 09:01, Richard Lucassen a écrit :
> Package: chrony
> Version: 4.4-3
> Severity: normal
>
> I run chronyd supervised. Therefore I removed symlinks in /etc/rc2.d/
> (update-rc.d chrony remove).
> But after an upgrade the deb package installs new symlinks in /etc/rc2.d/ and
> starts chronyd, even though chronyd is SysV disabled.
>
> Please check if /etc/rc2.d/*chrony symlinks exist, if not, don't add these
> and do not start chronyd. Maybe it's a good idea to just display a warning in
> that case.
>
I'm closing this bug report as this is, to me, not something that should
handled on the packaging side. From update-rc.d(8):
A common system administration error is to delete the links with the
thought that this will
"disable" the service, i.e., that this will prevent the service from
being started. However,
if all links have been deleted then the next time the package is
upgraded, the package's
postinst script will run update-rc.d again and this will reinstall links
at their factory de-
fault locations. The correct way to disable services is to configure the
service as stopped in
all runlevels in which it is started by default. In the System V init
system this means renam-
ing the service's symbolic links from S to K. .P The script .BI
/etc/init.d/ name must exist
before update-rc.d is run to create the links.
Running 'update-rc.d chrony disable' as root should work too.
> Richard.
Have a good day,
Vincent
signature.asc
Description: PGP signature
--- End Message ---
