Jonathan Nieder <jrnie...@gmail.com> writes: > Russ Allbery wrote:
>> This probably should already be a Policy violation, saying that they >> should use invoke-rc.d instead. Is there any drawback to them using >> invoke-rc.d? > Yes, I think there is a drawback. Forgetting about upstart and systemd > for the moment, if I use "/etc/init.d/<service> start" or "service > <service> start" directly, I get a guarantee that the service has been > started. If I use "invoke-rc.d <service> start", then the policy hook > can intercept my request and cause the daemon not to be started but > report success. > I'm not sure what the right thing to do in that case is. That seems like a feature, not a bug, in the case of configuration installed by Debian packages such as what's cited in this part of the thread. If I have a policy rule that says not to run that init script, I mean it, and I don't want ifup running it anyway. > Another downside is that invoke-rc.d is Debian-specific. So are the network hooks under discussion. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/873998gtk7....@windlord.stanford.edu
