Re: proposed change for /etc/periodic/* scripts
Ok, I'm going to start doing a bit of work on this so as to enable the periodic output to be customised I'll post my changes later for ppl that maybe interested (these changes will still be useful for myself anyway) I'll see if I can put all your suggestions in, thanks for the feedback. Cillian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
Ok, I'm going to start doing a bit of work on this so as to enable the periodic output to be customised I'll post my changes later for ppl that maybe interested (these changes will still be useful for myself anyway) I'll see if I can put all your suggestions in, thanks for the feedback. Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
Duncan Barclay wrote: > On 23-Aug-99 Cillian Sharkey wrote: > > > > yes perhaps an /etc/periodic.conf would be good, to control the level > > of verbosity and/or set options for each script ? > > I've hacked periodic here so that the scripts can be turned off with knobs in > a periodic.conf file. This would simplify customizing new installitions - one > no longer needs to add exit 0 to scripts. how about changing the output format; the top of the emailed report could contain a digest saying "everything's okay" for those who didn't want to read through the whole thing, then the rest of the report could have the usual verbose information. Then the digest could be made Even More concise, having brief lines like "disk free space changed" if it had, instead of the whole df output. then, if you wanted to know what had happened, you look to the rest of the email. if you want to ignore in certain notifications in the digest, you can. > Duncan -- Jon Povey - spamfil...@sullen.demon.co.uk "Doesn't all this crap just make you want to hurl?" - Netscape example app-defaults To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
Duncan Barclay wrote: > On 23-Aug-99 Cillian Sharkey wrote: > > > > yes perhaps an /etc/periodic.conf would be good, to control the level > > of verbosity and/or set options for each script ? > > I've hacked periodic here so that the scripts can be turned off with knobs in > a periodic.conf file. This would simplify customizing new installitions - one > no longer needs to add exit 0 to scripts. how about changing the output format; the top of the emailed report could contain a digest saying "everything's okay" for those who didn't want to read through the whole thing, then the rest of the report could have the usual verbose information. Then the digest could be made Even More concise, having brief lines like "disk free space changed" if it had, instead of the whole df output. then, if you wanted to know what had happened, you look to the rest of the email. if you want to ignore in certain notifications in the digest, you can. > Duncan -- Jon Povey - [EMAIL PROTECTED] "Doesn't all this crap just make you want to hurl?" - Netscape example app-defaults To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On 23-Aug-99 Cillian Sharkey wrote: > > yes perhaps an /etc/periodic.conf would be good, to control the level > of verbosity and/or set options for each script ? I've hacked periodic here so that the scripts can be turned off with knobs in a periodic.conf file. This would simplify customizing new installitions - one no longer needs to add exit 0 to scripts. Duncan --- Duncan Barclay | God smiles upon the little children, d...@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On 23-Aug-99 Cillian Sharkey wrote: > > yes perhaps an /etc/periodic.conf would be good, to control the level > of verbosity and/or set options for each script ? I've hacked periodic here so that the scripts can be turned off with knobs in a periodic.conf file. This would simplify customizing new installitions - one no longer needs to add exit 0 to scripts. Duncan --- Duncan Barclay | God smiles upon the little children, [EMAIL PROTECTED] | the alcoholics, and the permanently stoned. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
Garance A Drosihn wrote: > > I think this would need to be "knob-ized". I will ignore these > status reports for some time, and then some event comes up > where I am interested in reviewing all of them. If a partition > goes over 90%, for instance, I will want to know if it's been > growing 1% a week for months, or if all the growth happened last > night. Something inbetween might be nice. Nightly be able to display only "changed" items, but have full output on the weekly/monthly runs. Jim -- James E. HousleyPGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: page...@notepage.com 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
At 9:59 AM +0100 8/23/99, Cillian Sharkey wrote: * if there are no passwd/group diffs found, don't print anything out (not even the header). Same for setuid etc. diffs. I have one change to one of the scripts, the one checking for mail spool files. I changed it to recognize the spool file that the script itself is sending, and not keep warning me about something that it itself was doing. * For the 'df' status, only report filesystems that are over a certain capacity (95% or only xxMb left etc..) I think this would need to be "knob-ized". I will ignore these status reports for some time, and then some event comes up where I am interested in reviewing all of them. If a partition goes over 90%, for instance, I will want to know if it's been growing 1% a week for months, or if all the growth happened last night. --- Garance Alistair Drosehn = g...@eclipse.acs.rpi.edu Senior Systems Programmer or dro...@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
Garance A Drosihn wrote: > > I think this would need to be "knob-ized". I will ignore these > status reports for some time, and then some event comes up > where I am interested in reviewing all of them. If a partition > goes over 90%, for instance, I will want to know if it's been > growing 1% a week for months, or if all the growth happened last > night. Something inbetween might be nice. Nightly be able to display only "changed" items, but have full output on the weekly/monthly runs. Jim -- James E. HousleyPGP: 1024/03983B4D System Supply, Inc. 2C 3F 3A 0D A8 D8 C3 13 Pager: [EMAIL PROTECTED] 7C F0 B5 BF 27 8B 92 FE "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
At 9:59 AM +0100 8/23/99, Cillian Sharkey wrote: >* if there are no passwd/group diffs found, don't print anything > out (not even the header). Same for setuid etc. diffs. I have one change to one of the scripts, the one checking for mail spool files. I changed it to recognize the spool file that the script itself is sending, and not keep warning me about something that it itself was doing. >* For the 'df' status, only report filesystems that are over > a certain capacity (95% or only xxMb left etc..) I think this would need to be "knob-ized". I will ignore these status reports for some time, and then some event comes up where I am interested in reviewing all of them. If a partition goes over 90%, for instance, I will want to know if it's been growing 1% a week for months, or if all the growth happened last night. --- Garance Alistair Drosehn = [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Institute To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999, Cillian Sharkey wrote: > Keeping records would be handy alright..but cutting out all > the "everything is ok" msgs would reduce reading time..having > an option for full report OR just the important results should satisfy > everyone.. What I do run things through a filter that shows only things that I find interesting. It is only a few dozens of lines of shell. I don't actually do this for FreeBSD daily reports, because there isn't enough there to worry about, but for my application stuff it works a treat. David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999, Cillian Sharkey wrote: > Keeping records would be handy alright..but cutting out all > the "everything is ok" msgs would reduce reading time..having > an option for full report OR just the important results should satisfy > everyone.. What I do run things through a filter that shows only things that I find interesting. It is only a few dozens of lines of shell. I don't actually do this for FreeBSD daily reports, because there isn't enough there to worry about, but for my application stuff it works a treat. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> This may not be a good idea. I often check daily reports to see if > a disk has suddenly filled or had been gradually filling over a > long period of time - you wouldn't be able to get this info if you > print stuff selectively. in the case of df, one could set whether you want full df status OR just partial (ie ones over xx% or less that xxMB free) depending on your preference :) > For anyone who reads daily reports regurally it doesn't take long > to get used to the usual look of a report of moderate length > (<2screens?) and to notice if something is out of place. You don't > have to read every single word (and if you need to come back to it > all the info should be there). Keeping records would be handy alright..but cutting out all the "everything is ok" msgs would reduce reading time..having an option for full report OR just the important results should satisfy everyone.. Cillian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, Aug 23, 1999 at 09:59:29AM +0100, Cillian Sharkey wrote: > * 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..) This may not be a good idea. I often check daily reports to see if a disk has suddenly filled or had been gradually filling over a long period of time - you wouldn't be able to get this info if you print stuff selectively. For anyone who reads daily reports regurally it doesn't take long to get used to the usual look of a report of moderate length (<2screens?) and to notice if something is out of place. You don't have to read every single word (and if you need to come back to it all the info should be there). David. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> Make sure they always generate some output so that a message > does get mailed. On more than once occasion I noticed that one > of my boxes keeled over or the network broke when I didn't > get my expected daily output from that machine. My proposal would only *cut down* on all the white space, unnecessary lines etc. in the output, there would of course always be a report mailed out (with network interface status, uptime info etc..) As long as I get the reports and see no errors, i know all the various housekeeping chores the periodic scripts do have actually been done, if not I'll see an error msg in the report.. > You might want to make the df part an rc.conf (or maybe a new periodic.conf) > knob. I have couple of machines that basically do nothing all week long > and the disk space should always be pretty much constant. If I notice that > the disk space usage changed a lot, then I should go check that machine out, > because something went haywire. yes perhaps an /etc/periodic.conf would be good, to control the level of verbosity and/or set options for each script ? > I've had a bad experience with this in the past. One of our > adminstrators didn't like wading through all of the periodic > output and changed the scripts to do what you want. Sometime > down the line I figured out that he had broken something in > the script early on and 90% of it never got executed, and since > no output meant everything was fineyou get the point. Yes, that's always a danger.. :P to sum up : for scripts that do chores, if they ran successfully don't bother telling me. if they failed, tell me. for status reports (df, netstat, ruptime..) tell me for checks (passwd diff etc.) tell me IF there's something to report - Cillian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> This may not be a good idea. I often check daily reports to see if > a disk has suddenly filled or had been gradually filling over a > long period of time - you wouldn't be able to get this info if you > print stuff selectively. in the case of df, one could set whether you want full df status OR just partial (ie ones over xx% or less that xxMB free) depending on your preference :) > For anyone who reads daily reports regurally it doesn't take long > to get used to the usual look of a report of moderate length > (<2screens?) and to notice if something is out of place. You don't > have to read every single word (and if you need to come back to it > all the info should be there). Keeping records would be handy alright..but cutting out all the "everything is ok" msgs would reduce reading time..having an option for full report OR just the important results should satisfy everyone.. Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> 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 Make sure they always generate some output so that a message does get mailed. On more than once occasion I noticed that one of my boxes keeled over or the network broke when I didn't get my expected daily output from that machine. > 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..) You might want to make the df part an rc.conf (or maybe a new periodic.conf) knob. I have couple of machines that basically do nothing all week long and the disk space should always be pretty much constant. If I notice that the disk space usage changed a lot, then I should go check that machine out, because something went haywire. > 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.. I've had a bad experience with this in the past. One of our adminstrators didn't like wading through all of the periodic output and changed the scripts to do what you want. Sometime down the line I figured out that he had broken something in the script early on and 90% of it never got executed, and since no output meant everything was fineyou get the point. Again, maybe an rc.conf knob that tells the periodic scripts to be "quiet". I've got a couple of machines here that I would might use that on, but not on my main servers. -Mike -- Mike Pritchard m...@freebsd.org or m...@mpp.pro-ns.net To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, Aug 23, 1999 at 09:59:29AM +0100, Cillian Sharkey wrote: > * 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..) This may not be a good idea. I often check daily reports to see if a disk has suddenly filled or had been gradually filling over a long period of time - you wouldn't be able to get this info if you print stuff selectively. For anyone who reads daily reports regurally it doesn't take long to get used to the usual look of a report of moderate length (<2screens?) and to notice if something is out of place. You don't have to read every single word (and if you need to come back to it all the info should be there). David. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> Make sure they always generate some output so that a message > does get mailed. On more than once occasion I noticed that one > of my boxes keeled over or the network broke when I didn't > get my expected daily output from that machine. My proposal would only *cut down* on all the white space, unnecessary lines etc. in the output, there would of course always be a report mailed out (with network interface status, uptime info etc..) As long as I get the reports and see no errors, i know all the various housekeeping chores the periodic scripts do have actually been done, if not I'll see an error msg in the report.. > You might want to make the df part an rc.conf (or maybe a new periodic.conf) > knob. I have couple of machines that basically do nothing all week long > and the disk space should always be pretty much constant. If I notice that > the disk space usage changed a lot, then I should go check that machine out, > because something went haywire. yes perhaps an /etc/periodic.conf would be good, to control the level of verbosity and/or set options for each script ? > I've had a bad experience with this in the past. One of our > adminstrators didn't like wading through all of the periodic > output and changed the scripts to do what you want. Sometime > down the line I figured out that he had broken something in > the script early on and 90% of it never got executed, and since > no output meant everything was fineyou get the point. Yes, that's always a danger.. :P to sum up : for scripts that do chores, if they ran successfully don't bother telling me. if they failed, tell me. for status reports (df, netstat, ruptime..) tell me for checks (passwd diff etc.) tell me IF there's something to report - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon 1999-08-23 (09:59), Cillian Sharkey wrote: > 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 ? I have changes to this effect active on a box not here, I'll see if it is up-to-date enough to generate patches, and send them on to help you, if necessary. Neil -- Neil Blakey-Milner n...@rucus.ru.ac.za To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> 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 Make sure they always generate some output so that a message does get mailed. On more than once occasion I noticed that one of my boxes keeled over or the network broke when I didn't get my expected daily output from that machine. > 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..) You might want to make the df part an rc.conf (or maybe a new periodic.conf) knob. I have couple of machines that basically do nothing all week long and the disk space should always be pretty much constant. If I notice that the disk space usage changed a lot, then I should go check that machine out, because something went haywire. > 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.. I've had a bad experience with this in the past. One of our adminstrators didn't like wading through all of the periodic output and changed the scripts to do what you want. Sometime down the line I figured out that he had broken something in the script early on and 90% of it never got executed, and since no output meant everything was fineyou get the point. Again, maybe an rc.conf knob that tells the periodic scripts to be "quiet". I've got a couple of machines here that I would might use that on, but not on my main servers. -Mike -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999 10:18:40 +0100, Cillian Sharkey wrote: > I haven't actually done any work on this (yet) > but I might see what I can hack together.. > The reason I suggest that you provide diffs first is that it's difficult to comment on your proposal without seeing _how_ and to _what_ extent you want to change things. Diffs will remedy that. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> > Ideas / Comments / Suggestions ? ^ ^^^ Well ? > Diffs ? I haven't actually done any work on this (yet) but I might see what I can hack together.. ;) Cillian To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999 09:59:29 +0100, Cillian Sharkey wrote: > Ideas / Comments / Suggestions ? Diffs ? :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
proposed change for /etc/periodic/* scripts
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 majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon 1999-08-23 (09:59), Cillian Sharkey wrote: > 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 ? I have changes to this effect active on a box not here, I'll see if it is up-to-date enough to generate patches, and send them on to help you, if necessary. Neil -- Neil Blakey-Milner [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999 10:18:40 +0100, Cillian Sharkey wrote: > I haven't actually done any work on this (yet) > but I might see what I can hack together.. > The reason I suggest that you provide diffs first is that it's difficult to comment on your proposal without seeing _how_ and to _what_ extent you want to change things. Diffs will remedy that. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
> > Ideas / Comments / Suggestions ? ^ ^^^ Well ? > Diffs ? I haven't actually done any work on this (yet) but I might see what I can hack together.. ;) Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: proposed change for /etc/periodic/* scripts
On Mon, 23 Aug 1999 09:59:29 +0100, Cillian Sharkey wrote: > Ideas / Comments / Suggestions ? Diffs ? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
proposed change for /etc/periodic/* scripts
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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
