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
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
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.
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.
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 ne
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 n
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
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 th
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%
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 t
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 tha
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 th
> 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
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
> 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,
> 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 O
> 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 w
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 xxM
> 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,
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
> 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
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
> > 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 fre
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
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
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 o
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 withou
> > 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 freebs
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
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
30 matches
Mail list logo
