* Fri 2007-11-30 Ian Jackson <[EMAIL PROTECTED]> INBOX > Peter Palfrader writes ("Re: Bug#412976 repoened - reassign tech-ctte > (mixmaster /etc/default/*)"): > >> Summary of current status: >> >> o The mixmaster package provides both the client and server functionality. >> o By default the server part (running a remailer) is not enabled. >> o To configure mixmaster to run as a remailer the admin has to set a dozen >> options in /etc/mixmaster/remailer.conf. Options like email address, >> which formats they will accept, whether to run as an exit or only as a >> middleman remailer, etc. >> o One of those options is the REMAIL setting, which enables or disables >> the remailing ("server") part of mixmaster. >> o The init script has code to only try starting the mixmaster daemon, which >> is only needed when it's being run as a remailer, when the REMAIL option >> is actually set to "y" in that config file. >> >> The submitter wants a new conffile, /etc/default/mixmaster, that is >> sourced by the init script to control whether the daemon is started. >> That would either be in addition or instead of the REMAIL setting in >> /etc/mixmaster/remailer.conf which is already used by the mixmaster >> software. > > Jari, do you agree with Peter Palfrader's summary above ? If not, in > what way is it not accurate, or which important facts does it leave > out ?
While I would have found it more beneficial to move towards separate stages: /etc/default/* Daemon boot control setup /etc/<daemon>/<configs> Daemon run time configuration I'm fine with the result. >From Admin's point of view dealing with symlinks is much more uncomfortable to control the initial start/stop status. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]