From owner-freebsd-questions@freebsd.org Wed Feb 22 09:33:10 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A011CE8542 for ; Wed, 22 Feb 2017 09:33:10 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 33FA519AA for ; Wed, 22 Feb 2017 09:33:09 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [192.168.1.208] (host81-134-87-65.range81-130.btcentralplus.com [81.134.87.65]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id v1M9WBlk061127 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO) for ; Wed, 22 Feb 2017 09:32:12 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <58AD5A9A.7070407@fjl.co.uk> Date: Wed, 22 Feb 2017 09:32:10 +0000 From: Frank Leonhardt Reply-To: frank2@fjl.co.uk Organization: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Daily and Weekly Periodic Scripts References: <18376E93-56AB-4D07-AC78-C66DE4ABFB11@lafn.org> In-Reply-To: <18376E93-56AB-4D07-AC78-C66DE4ABFB11@lafn.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 09:33:10 -0000 For what it's worth, in a similar situation I simply have a cron triggered script that greps certain files (or the output of certain utilities) and fires off an email if it finds/doesn't find certain things. Very simple and flexible, and it keeps nagging if I don't do anything about it. I keep thinking of doing something more gala, but over many years I've found this actually works for me. Regards, Frank. On 21/02/2017 22:02, Doug Hardie wrote: > I used to have a few servers and reading the daily and weekly periodic reports was a bit time consuming, but still viable. However, now I have a bunch of servers and am swamped with those reports daily. I have even less time available to read them and generally end up deleting them in mass. I have on occasion, although not in a few years, identified issues in those reports that need to be addressed. That part bothers me. > > I was wondering if anyone has done anything to create code to review those scripts and identify issues and only report those issues. For example, looking at the network counts, the collision rate should always be zero on ethernet. Finding a number there greater than zero is a problem that needs to be addressed. Likewise the error counts should also be zero. However, some systems do have a normal low level of errors so that rate would need to be configurable per system. > > — Doug > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"