[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#889640: marked as done (lintian: init.d-script-possible-missing-stop misfire on rcS scripts)



Your message dated Tue, 06 Feb 2018 02:18:21 +0530
with message-id <1517863701.2323293.1260456416.6148FD0C@webmail.messagingengine.com>
and subject line Re: Bug#889640: lintian: init.d-script-possible-missing-stop misfire on rcS scripts
has caused the Debian Bug report #889640,
regarding lintian: init.d-script-possible-missing-stop misfire on rcS scripts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
889640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889640
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.72
Severity: normal

And one more for today's trifecta :)

A SysV init script with:

 # Default-Start:     S
 # Default-Stop:      0 6

Will cause lintian to complain about it not being stopped in runlevel 1,
with a rationale that would be fine for services started in 2-5, but that
doesn't really apply for things which can be shut down in an orderly way
but shouldn't be just because you're switching to or entering runlevel 1.

  Cheers,
  Ron

--- End Message ---
--- Begin Message ---
Hey Ron!

> [..]

Well, thank you for such an informative followup! :)

>  - lintian is actually right.
[…]
>  - there was probably something else, but now I need a stiff drink and
>    a lie down

*grin*

> And unless I've really missed some other detail there, we can probably
> just close this one, leave lintian as is

Sure, will do :)  And no worries about the noise - indeed, it was
probably the very act of "rubber ducking" of the issue here that solved
it for you and, as I mentioned above, I learned quite a few things :)


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

--- End Message ---

Reply to: