From owner-freebsd-hackers  Mon Aug 23  2:13:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from vax1.baker.ie (VAX1.baker.IE [194.125.50.91])
	by hub.freebsd.org (Postfix) with SMTP id A5F5714D3E
	for <hackers@freebsd.org>; Mon, 23 Aug 1999 02:13:48 -0700 (PDT)
	(envelope-from cillian@baker.ie)
Received: from baker.ie ([194.125.50.55]) by vax1.baker.ie with ESMTP
          for hackers@freebsd.org; Mon, 23 Aug 1999 10:18:43 +0100
Message-ID: <37C10D71.EAA5D819@baker.ie>
Date: Mon, 23 Aug 1999 09:59:29 +0100
From: Cillian Sharkey <cillian@baker.ie>
X-Mailer: Mozilla 4.6 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: proposed change for /etc/periodic/* scripts
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This would be useful in cutting down the size
of these emails esp. when you are receiving them from multiple
fbsd servers.. :P

example:

* if there are no passwd/group diffs found, don't print anything
  out (not even the header). Same for setuid etc.  diffs.

* For the 'df' status, only report filesystems that are over
  a certain capacity (95% or only xxMb left etc..)

and the same for all the other tests..basically if there's nothing
to report don't print anything (not even the header) otherwise
print the header and the results..

Ideas / Comments / Suggestions ?

- Cillian


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message