From owner-freebsd-questions@freebsd.org Tue Feb 21 22:21:03 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 E1170CE89F1 for ; Tue, 21 Feb 2017 22:21:03 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id CDFC5101D for ; Tue, 21 Feb 2017 22:21:03 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.251] (sermon-archive.info [71.177.216.148]) by zoom.lafn.org (Postfix) with ESMTPSA id 0145834ADA1 for ; Tue, 21 Feb 2017 14:01:18 -0800 (PST) From: Doug Hardie Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Daily and Weekly Periodic Scripts Message-Id: <18376E93-56AB-4D07-AC78-C66DE4ABFB11@lafn.org> Date: Tue, 21 Feb 2017 14:02:16 -0800 To: "freebsd-questions@freebsd.org Questions" X-Mailer: Apple Mail (2.3259) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean 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: Tue, 21 Feb 2017 22:21:04 -0000 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. =E2=80=94 Doug