reopen 412976 !
thanks
The bug title was:
Add /etc/default/mixmaster to control the daemon startup at boot
> The reason was explained before. You need to configure mixmaster
> anyway, so we use that file right there.
I cannot see how this is an explanation would address why mixmaster
deviates from the policy section that says to put "control of behavior"
into:
/etc/default/*
> This is not what is happening. Read it again and maybe you'll
> understand.
Quoting again the policy manual:
9.3.2. Writing the scripts
--------------------------
Often there are some variables in the `init.d' scripts whose values
control the behavior of the scripts, and which a system administrator
is likely to want to change.
....
they should be placed in a file in `/etc/default',
> This is not what is happening. Read it again and maybe you'll
> understand.
The system administrator wants to control the behavior of the daemon,
the startup at boot (enabled/disabled). Here is example from
/etc/default/bin9:
OPTIONS="-u bind"
# Set RESOLVCONF=no to not run resolvconf
RESOLVCONF=yes
ENABLE=no
In contrast to:
# /etc/init.d/mixmaster start
Not starting Mixmaster Daemon: remailer mode not enabled in
/etc/mixmaster/remailer.conf.
Repoening bug as the policy is not followed.
Jari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
