Bug#1055205: closed by Vincent Blut (Re: Bug#1055205: chrony: SysV problems after upgrade)

2023-11-02 Thread Richard Lucassen
On Thu, 02 Nov 2023 12:27:05 +
"Debian Bug Tracking System"  wrote:

Hello Vincent,

Ok, thnx for your explanation! I changed it to disable (and
indeed there is only a K link) and I'll see at the next upgrade.

Richard.

> This is an automatic notification regarding your Bug report
> which was filed against the chrony package:
> 
> #1055205: chrony: SysV problems after upgrade
> 
> It has been closed by Vincent Blut .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Vincent Blut
>  by replying to this email.
> 
> 


-- 
___
It is better to remain silent and be thought a fool, than to speak
aloud and remove all doubt.

+--+
| Richard Lucassen, Utrecht|
+--+



Bug#1055205: chrony: SysV problems after upgrade

2023-11-02 Thread Paul Gevers

Hi Vincent,

On 02-11-2023 13:21, Vincent Blut wrote:

I'm closing this bug report as this is, to me, not something that should
handled on the packaging side.


Thank you for repairing my lack of looking these things up. I suspected 
as much (but failed to express that).


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1055205: chrony: SysV problems after upgrade

2023-11-02 Thread Vincent Blut
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


Processed: Re: Bug#1055205: chrony: SysV problems after upgrade

2023-11-02 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #1055205 [chrony] chrony: SysV problems after upgrade
Severity set to 'serious' from 'normal'

-- 
1055205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems