Re,
Jonas Smedegaard <d...@jones.dk> writes:
>> I think the severity of this bug should be lowered to important since
>> there is no policy violation of needrestart at all.
>
> I think it is quite worrisome if simply installing (not actively using)
> needrestart inside a chroot spawns daemons - and that is not treated as
> serious (no matter framed by some geleral Debian Policy wording).
Needrestart was never written nor designed to run within a chroot. This
use case does not make any sense at all. Just don't do it (should be
added to the README ;-) .
>> I (upstream) or Patrick (maintainer) could add a patch to needrestart
>> to use invoke-rc.d instead of the service command. That would only be
>> a Debian specific workaround.
>
> Please do. That sounds like it would solve this issue.
ACK
>> Neighter do I. Another workaround could be to change needrestart to
>> list only mode within piupart using some local config snippet as they
>> do for policy-rc.d.
>
> If I understand you corretly, that you suggest to invent a mechanism
> essentially doing the same as policy-rc.d, then I see no need for that:
> Please respect the already existing policy-rc.d instead.
>
> I guess what you seek is a solution not specific to Debian - and find
> that wuite sensible. I suspect, however, that there is no XDG or
> similar more generic standard for respecting deployment-specific hooks -
> which is really what policy-rc.d is about (not only chroot support).
Yes, since I'm upstream it is required that needrestart focuses an
generic approach. A patch kept in Pattricks packaging VCS should keep
the balance.
HTH,
Thomas
--
:: WWW: https://fiasko-nw.net/~thomas/ ::
::: Jabber: xmpp:tho...@jabber.fiasko-nw.net :::
:: flickr: https://www.flickr.com/photos/laugufe/ ::
