[Mimedefang] /etc/init.d/mimedefang

Jeff Rife mimedefang at nabs.net
Tue Feb 27 17:55:06 EST 2007


On 27 Feb 2007 at 16:41, Josh Kelley wrote:

> But if mimedefang crashes (rather than being stopped cleanly), the
> lock isn't removed, and if the init script checks for the presence of
> the lock before starting mimedefang, it will never start mimedefang
> until the lock is manually removed.  No other init script that I've
> checked does that.
> 
> The daemon function, which the init script calls, already checks for
> the existence of the service before trying to start it, so checking
> for the lock before attempting to start is redundant.

I agree it is redundant, but the checking that the "daemon" function 
does will also cause a service not to start until you manually delete a 
file (the /var/run/mimedefang.pid file)...at least until a reboot.

You could edit the line in /etc/rc.d/init.d/mimedefang to start
"daemon --force" if you really don't care about the state that things
might have been left in after a crash.

Although I have had the MIMEDefang filter process crash (SIGALRM with 
embedded perl), I have *never* seen the base mimedefang process (or 
mimedefang-multiplexor) crash, so I don't really see it as an issue 
with the init script the way it is now.


--
Jeff Rife |  
          | "Resistance...is *futile*" 
          |  
          |         -- Data, "Star Trek: First Contact" 





More information about the MIMEDefang mailing list