Daniel, On Wed, Aug 14, 2024 at 07:32:58PM +0200, Daniel Gröber wrote: > > Can I ask why? Is it broken? Does it no longer work? > > Sure. I made the systemd service I introduced disabled by default. Since I > don't know how to do that in sysvinit land
Remove the runlevels from Default-Start: in the LSB header so that line is empty. See insserv(8). I can provide a patch for that in #1078674, if you want? > Frankly, I don't want to support two ways of doing things. Patches and > co-maintainers welcome. Of course users of non-systemd inits would be happy to provide patches and support to keep the LSB initscript within netperf working. > If orphan-sysvinit-scripts didn't exist this may have tipped in favor of > keeping it, but I decided placing it here (if you'll have it) and putting a > note in netperf NEWS is a reasonable compromise, since I'm already adding a > NEWS entry for the default disablement change. It is Matthew's call as to whether he wants to include netperf LSB initscript in orphan-sysvinit-scripts. However, orphan-sysvinit-scripts was not a solution of choice and is far from ideal. It was a last resort and sub-optimal compromise to deal with situations where maintainers refused to keep working LSB initscripts in their packages. Despite Matthew's considerable care an attention and without any criticism of his work, orphan-sysvinit-scripts has a number of unsolvable issues[1]. It also still requires coordination: if netperf was to change its behaviour in the future or require an alteration to an LSB script shipped by orphan-sysvinit-scripts, either you would need to notify/coordinate that, or users would have to wait until the breakage was noticed and then reported. With best wishes Mark [1] https://salsa.debian.org/matthew/orphan-sysvinit-scripts/-/blob/master/README.org
