Removing old Sys-V init-script on upgrade

Mark Hindley mark at hindley.org.uk
Tue May 12 19:24:14 BST 2026


On Tue, May 12, 2026 at 07:53:06PM +0200, Lorenzo wrote:
> Sven Hartge <sven at svenhartge.de> wrote:
> > The old Sys-V init-script does not really work for that anymore and I
> > would like to remove it on upgrade.
> 
> In principle I don't see any issue, you could have a multi instance
> systemd service and old single instance sysv script, debhelper will
> make sure that there are no conflicts (but I know nothing specific to
> radsecproxy): would you reconsider your decision if could get
> assistance on simplifying/ refreshing the script?
> If yes, the debian-init-diversity (in CC) list may be of help.

I agree, there should be no conflict between a systemd unit and an LSB
initscript, particularly now systemd in sid has dropped the sysv generator.

Removing the LSB initscript is an unhelpful disservice to non-systemd
users. Orphan-sysvinit-scripts is a suboptimal and second-best replacement.

There are many here who would give you help and advice to address any issues
with the LSB initscript.

So I urge you to keep it!

Thanks

Mark



More information about the Debian-init-diversity mailing list