Daily and Weekly Periodic Scripts
luzar722 at gmail.com
Wed Feb 22 12:18:21 UTC 2017
Frank Leonhardt wrote:
> 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
Frank: Would you please share your scripts with the list?
More information about the freebsd-questions