Bug#538304: insserv: start and stop in same runlevel

[Dmitry Bogatov]

control: tags -1 +fixed-upstream

[2019-04-11 17:50] Jesse Smith <jsmith at resonatingmedia.com>
>
> part       text/plain                1086
> On 4/11/19 7:43 AM, Dmitry Bogatov wrote:
> > [2019-01-24 19:42] Jesse Smith <jsmith at resonatingmedia.com>
> >> I'm looking into this bug in insserv and want to make sure I'm
> >> understanding the issue correctly. As I read it, the problem is that if
> >> the user specifies the same runlevel in both the Default-Start and
> >> Default-Stop fields, insserv will set up the "Stop" symbolic link, but
> >> will not complain about it?
> >>
> >> Ideally, insserv should probably still use this behaviour, but print a
> >> warning that the same runlevels should not be listed in both the
> >> Default-Start and Default-Stop fields. Is this a correct summary of the
> >> above request?
> > Yes, seems so.
>
> I have addressed this upstream. The next version of insserv will print a
> warning when an init.d script has the same runlevel specified in the
> Default-Start and Default-Stop fields. The output looks like this:
>
>    insserv: Script bluetooth has overlapping Default-Start and
> Default-Stop runlevels (2 3 4 5) and (0 1 3 6). This should be fixed.
>
> Apart from the warning, insserv functions as before.

Thank you.
-- 
        Note, that I send and fetch email in batch, once every 24 hours.
                 If matter is urgent, try https://t.me/kaction
                                                                             --