Matt:

Hmmm... Matt, this is exactly what init is designed to do, it will respawn any daemon that stops running, and reruns it automatically. Some people use something called daemon tools, or something called supervisor, all which work just fine. I think init does a great job of this also assuming the daemon is well behaved.

# CLAMD
cl:2345:respawn:/usr/local/sbin/clamd
               ^^^^^^^  The magic is the respawn keyword.

A demostration is in order:

[EMAIL PROTECTED] 11250]# ps -aef |grep clam
root      2626     1  0 Feb07 ?        00:00:04 /usr/local/sbin/clamd
         ^^^^ note this number

[EMAIL PROTECTED] 11250]# kill -9 2626
[EMAIL PROTECTED] 11250]# ps -aef |grep clam
root     11248     1  2 14:15 ?        00:00:00 /usr/local/sbin/clamd
        ^^^^^ woo hoo!

QED.

HFC


Matt Kettler wrote:

Henry F. Camacho Jr wrote:
Don:

Another way to do this is to do it during init.

Yes, but that doesn't solve his problem. It's also probably what Don is
doing right now.

Dons problem is spamd crashing and dying.

He's looking for a mechanism to ensure it gets restarted even if it
crashes. init won't do that, it will just ensure that spamd starts as
the system boots.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to