From clamav-users-bounces@lists.clamav.net Wed Apr 11 16:17:44 2007 Return-Path: X-Original-To: list@tad.clamav.net Delivered-To: list@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKT6ODXG393r; Wed, 11 Apr 2007 16:17:44 +0200 (CEST) Received: from tad.clamav.net (localhost.localdomain [127.0.0.1]) by tad.clamav.net (Postfix) with ESMTP id BC9A441412B; Wed, 11 Apr 2007 16:17:32 +0200 (CEST) X-Original-To: clamav-users@tad.clamav.net Delivered-To: clamav-users@tad.clamav.net X-Virus-Scanned: Debian amavisd-new at tad.clamav.net Received: from tad.clamav.net ([127.0.0.1]) by localhost (tad.clamav.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LCK9vnaHhAVU for ; Wed, 11 Apr 2007 16:17:30 +0200 (CEST) Received: from mail3.lcrcomputer.net (mail3.lcrcomputer.net [209.172.152.5]) by tad.clamav.net (Postfix) with ESMTP id ACAC6414120 for ; Wed, 11 Apr 2007 16:17:29 +0200 (CEST) Received: from [192.168.250.166] (unverified [209.172.152.254]) by mail3.lcrcomputer.net (SurgeMail 3.8j) with ESMTP id 29855-1794114 for ; Wed, 11 Apr 2007 09:17:26 -0500 Message-ID: <461CEDEF.5010009@lcrcomputer.net> Date: Wed, 11 Apr 2007 09:17:19 -0500 From: Lyle Giese User-Agent: Thunderbird 1.5.0.8 (X11/20060911) MIME-Version: 1.0 To: clamav-users@lists.clamav.net X-Authenticated-User: lyle@lcrcomputer.net Subject: [Clamav-users] Clamdmon.sh X-BeenThere: clamav-users@lists.clamav.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: ClamAV users ML List-Id: ClamAV users ML List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: clamav-users-bounces@lists.clamav.net Errors-To: clamav-users-bounces@lists.clamav.net I am amazed at the number of people here that apparently not using SOMETHING to monitor clamd. Esp. when the developers include a nice script to check and restart clamd. I run three different mail servers and quickly found clamdmon and just a bit of PERL programming created a means of being notified of an issue. Yes, you have to have a means of being notified 'out of band'. But if you are serious about uptime, you need to know promptly when a mail server is not processing email and at that point you cann't depend on that email server to tell you it's broken. Lyle _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html