• Bug#680293: update-rc.d manual: `update-rc.d remove name` works when `/

    From Andrew Bower@21:1/5 to Dmitry Bogatov on Fri May 16 00:30:01 2025
    On Fri, Jan 11, 2019 at 12:37:07PM +0000, Dmitry Bogatov wrote:
    [2012-07-04 22:17] Paul Menzel <pm.debian@googlemail.com>
    I guess the bug has been present for a longer time, so please update the version information accordingly.

    Dear maintainers of init-system-helpers, please consider following
    patch, that adjust behaviour of update-rc.d to match manpage.

    If this bug is ever fixed, please make sure that '-f' still allows the
    symlinks to be removed.

    Currently the only way to restore the symlinks to the defaults specified
    by the initscript are 'remove' followed by 'defaults' because the
    'defaults' operation, inexplicably to me, won't set the defaults unless
    there are no symlinks at all.

    #339460 is marked as WONTFIX and #731905 doesn't seem to think this
    situtation ('defaults' not doing anything useful for an
    already-installed script) is a problem so presumably the behaviour of 'defaults' isn't ever going to change, so let's at least make sure
    'remove -f' remains to let users and maintscripts do a forcible revert
    to defaults when required.

    Thanks!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Josh Triplett@21:1/5 to andrew@bower.uk on Fri May 16 14:50:01 2025
    On Thu, 15 May 2025 23:22:43 +0100 Andrew Bower <andrew@bower.uk> wrote:
    If this bug is ever fixed, please make sure that '-f' still allows the symlinks to be removed.

    Currently the only way to restore the symlinks to the defaults specified
    by the initscript are 'remove' followed by 'defaults' because the
    'defaults' operation, inexplicably to me, won't set the defaults unless
    there are no symlinks at all.

    As I understand it, the reason for this is that maintainer scripts do `update-rc.d scriptname defaults`, and that should preserve sysadmin
    removals of symlinks (because the syadmin doesn't want something to
    run).

    The *current* convention (which bends the rules about preserving
    sysadmin changes but in a way that kinda works for people) is that if
    you remove just `S` symlinks but leave the `K` symlinks you can prevent something from starting, but if you remove *all* the symlinks then
    `defaults` will reinstall them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)