From clamav-users-bounces@lists.clamav.net Thu Apr 12 07:49:43 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 d7U9lSQJVeIt; Thu, 12 Apr 2007 07:49:43 +0200 (CEST) Received: from tad.clamav.net (localhost.localdomain [127.0.0.1]) by tad.clamav.net (Postfix) with ESMTP id C2B7916C156; Thu, 12 Apr 2007 07:49:34 +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 FIwDRgs15Qw3 for ; Thu, 12 Apr 2007 07:49:33 +0200 (CEST) Received: from inetnw.com (inetnw.com [65.101.150.185]) by tad.clamav.net (Postfix) with ESMTP id F084716C124 for ; Thu, 12 Apr 2007 07:49:32 +0200 (CEST) Received: from [192.168.0.10] (wireless.inetnw.com [192.168.1.2]) by inetnw.com (8.14.1/8.14.1) with ESMTP id l3C5nVFF013071 for ; Wed, 11 Apr 2007 22:49:31 -0700 (PDT) Message-ID: <461DC858.2020000@inetnw.com> Date: Wed, 11 Apr 2007 22:49:12 -0700 From: Dennis Peterson User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: ClamAV users ML References: In-Reply-To: X-Miltered: at omak with ID 461DC86B.000 by Joe's j-chkmail (http://inetnw.net/spam.php)! Subject: Re: [Clamav-users] error stops clamd 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 Luigi Iotti wrote: >> >> Notification is a part of the solution IMHO. If clamd recognizes that >> it's not able to load the new ones because the update process is still >> occurring, then it should continue running *AND* notify the sysadmin >> that it's running in what should be considered a degraded mode. The >> ease with which this is attained will vary by system. > > I agree. Only it's worth noticing that if I have a script that can inform me > via a pager that clamd is not running, than it's likely to be able to inform > me that an update did not go well, or that sigtool reports my virus > signatures to be 4 or 24 or NN hours old. I would be equally informed, but I > would have no denial of service. > > Just my opinion. The environment I support is a forest of gateway servers. If any/all lose the ability to scan viruses, the inside server forest, running a completely different tool suite, can pick up the load. My job is to bring full service back to my systems as quickly as possible. That happened - logs show no viruses were ingested, and this is a million message/week system. Fault tolerance, notification, redundancy. Oh - and expensive. Very expensive, in fact. Anyone know if this event caused Barracuda systems to fold up the tent? dp _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html