[Mimedefang] [FOLLOWUP] Re: Restarting MIMEDefang

[Jan Pieter Cornet]

On Wed, Jun 22, 2005 at 09:36:22AM -0400, Dirk the Daring wrote:
>    As a followup, if I wanted to change one of the command-line options
> with which the multiplexor was invoked (for example, changing the "l"
> value, which periodically logs the slave status), could I stop and then
> restart just the multiplexor, or should I kill and restart both
> components?
> 
>    And what about MIMEDefang? If I wanted to change the invocation by,
> say, adding "-s" so it would filter on sender, can I stop/start that
> individual component without having to stop/start the multiplexor?

You can in principle restart each component separately. However, mimedefang
itself sometimes takes a while to exit, and as the last thing before
exiting it will unlink the mimedefang milter socket... so if you start
the new mimedefang before that, you end up short of a socket and sendmail
will complain.

I usually stop all sendmails and mimedefang processes, and then restart
everything again, when doing such maintenance (which you practically
never need once it's in production, so don't worry too much about it).

-- 
#!perl -wpl # mmfppfmpmmpp mmpffm <pmmppfmfpppppfmmmf at fpffmm4mmmpmfpmf.ppppmf>
$p=3-2*/[^\W\dmpf_]/i;s.[a-z]{$p}.vec($f=join('',$p-1?chr(sub{$_[0]*9+$_[1]*3+
$_[2]}->(map{/p|f/i+/f/i}split//,$&)+97):qw(m p f)[map{((ord$&)%32-1)/$_%3}(9,
3,1)]),5,1)='`'lt$&;$f.eig;                                # Jan-Pieter Cornet