From owner-freebsd-isp@FreeBSD.ORG Mon Nov 17 13:17:41 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A9A816A4CF for ; Mon, 17 Nov 2003 13:17:41 -0800 (PST) Received: from k2.ma.krakow.pl (k2.ma.krakow.pl [195.205.243.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8CE943F85 for ; Mon, 17 Nov 2003 13:17:38 -0800 (PST) (envelope-from miki@ceti.pl) Received: from hermes.dom (host-ip194-227.crowley.pl [62.111.227.194]) by k2.ma.krakow.pl (8.12.10/8.12.10) with ESMTP id hAHLHV4Q028750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 17 Nov 2003 22:17:36 +0100 Received: from hermes.dom (localhost [127.0.0.1]) by hermes.dom (8.12.10/8.12.10) with ESMTP id hAHLHLWs000622 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 17 Nov 2003 22:17:23 +0100 Received: from localhost (miki@localhost) by hermes.dom (8.12.10/8.12.10/Submit) with ESMTP id hAHLHKGT000619 for ; Mon, 17 Nov 2003 22:17:20 +0100 X-Authentication-Warning: hermes.dom: miki owned process doing -bs Date: Mon, 17 Nov 2003 22:17:19 +0100 (CET) From: Mikolaj Rydzewski X-X-Sender: miki@hermes.dom To: isp@freebsd.org In-Reply-To: Message-ID: References: X-PGP-Fingerprint: 40 96 CB 86 5B 22 AF A3 A1 12 B5 11 24 12 05 E0 X-PGP-PublicKey: http://ceti.pl/~miki/pubkey.txt X-Phone: +48(502)502483 X-GG: 4185132 X-ICQ: 14597472 X-nic-hdl: MR5431-RIPE MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: Daily/weekly/monthly output aggregation X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2003 21:17:41 -0000 On Mon, 17 Nov 2003, Lapinski, Michael (Research) wrote: > The way I deal with it is by the size of the message, > day in day out the messages are usually +- a few bytes > different in size when things go normal. Maybe write > something that flags messages smaller or larger then > the daily average of the runs... Hello, Why don't you like the idea: no output means no errors? Just create your periodic scripts to produce no output when everything is fine. Cron will not mail you anything what has produced no results. Just to get the idea. I know, it isn't fool proof; there are more secure ways to do this, etc. But it works ;-) #!/bin/sh log=`mktemp /tmp/.log.XXXXXX` # ... perform your stuff, i.e. /usr/local/sbin/backup > $log 2>&1 if [ $? -ne 0 ]; then cat $log fi rm -f $log -- Mikolaj Rydzewski http://ceti.pl/~miki/ PGP KeyID: e17c4bd5 There are three kinds of people: men, women and unix.