Many packages seem to provide ENABLE/DISABLE variables in
/etc/default/foo, providing a confusing red herring for this
task --- a second method which does not work nearly as well,
as you pointed out
Though there are some situations where it is nessacery. Consider
vtund for example which has
Hi,
peter green wrote:
Though there are some situations where it is nessacery. Consider vtund for
example which has seperate enable/disable flags for running in server and
client modes (with the potential for multiple seperate client instances).
Thanks for this clarification. Luckily vtun's
tags 601455 - patch
retitle 601455 multiple, annoyingly different ways to disable an init script
quit
Hi Mathias,
Mathias Kub wrote:
When I try to stop a daemon after I disabled it in /etc/default/foo,
I get an error-message that I can not stop it, because it is
disabled.
Shouldn't I be
Package: general
Severity: minor
Tags: patch
When I try to stop a daemon after I disabled it in /etc/default/foo, I get an
error-message that I can not stop it, because it is disabled.
Shouldn't I be able to stop it even if I disabled it first?
This happens if you disabled a daemon but didn't
4 matches
Mail list logo
