Bug#850703: systemd: incorrect LSB support with monit's init script
Michael Biebl
biebl at debian.org
Mon Jan 9 16:41:31 GMT 2017
Am 09.01.2017 um 17:30 schrieb Vincent Lefevre:
> Hi Martin,
>
> On 2017-01-09 16:41:20 +0100, Martin Pitt wrote:
>> Hello Vincent,
>>
>> Vincent Lefevre [2017-01-09 15:15 +0100]:
>>> The monit service (from the monit package) should be started last and
>>> stopped first. This is not the case with systemd.
>>>
>>> # Should-Start: $all
>>> # Should-Stop: $all
>>
>> Please note that the SysV concept of "$all" is notoriously broken
>> (what if another package uses $all too?),
>
> I suppose that both should fall in the same class, with no
> dependencies between them. Actually, this is how it is specified
> in <https://wiki.debian.org/LSBInitScripts>.
>
> $all facility supported by insserv to start a script after all
> the scripts not depending on $all, at the end of the boot
> ^^^^^^^^^^^^^^^^^^^^^
Well, what is "the end of the boot"? How is this defined?
That aside, if you've seen the list I posted in my other reply, what
happens if monit wants to monitor reniced?
> monit can monitor arbitrary services, so that I suppose that it
> doesn't know in advance. A solution would be to have a way to
> enumerate all the available services on the system, and add them there
> dynamically at system start up, but isn't this equivalent to $all?
An alternative idea: monit has a grace period, say 5 min, when it is
started. Within this grace period it does not warn about non-running
services.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170109/1c57cdeb/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list