Bug#622970: Reassigned to insserv #622970

Jesse Smith jsmith at resonatingmedia.com
Fri Jul 19 00:08:28 BST 2019

On Sun, 17 Apr 2011 20:09:40 +0200 Thomas Hood wrote:
> I have just reassigned this report from resolvconf to
> insserv because I believe that the insserv maintainers
> will have more insight into the problem than I have.
> Here is a summary of what we have found out, as
> described earlier in the report's message log.
> Resolvconf was misbehaving on the submitter's two fresh
> squeeze machines. This was because resolvconf's initscript
> had been installed in rcS.d at the traditional sequence
> number S38 rather than at the appropriate sequence number
> for the submitter's systems, S13. This was because,
> although the submitter's systems had evidently been
> subjected to boot sequence reordering by (I presume)
> insserv, the /etc/init.d/.legacy-bootordering flag file was
> still present on his systems.
> This incongruous situation --- reordered boot sequence, but
> legacy flag file present --- may have resulted from the
> presence of initscripts on the system lacking LSB headers.
> --
> Thomas Hood

This is an interesting bug. Though I'm not sure if it is still a
problem. As far as I know, current versions of update-rc.d and insserv
do not check for the ".legacy-bootordering" file flag (or create or
remove it). I could be mistaken, but I think this was either resolved
quietly in the past, or is outside our scope. I tried running the latest
insserv with and without /etc/init.d/.legacy-bootordering in place and
didn't encounter differences in behaviour.

I think we can probably mark this one as closed unless someone comes up
with a way insserv is misbehaving in this situation.

- Jesse

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/attachments/20190718/370bb6a9/attachment.html>

More information about the Debian-init-diversity mailing list