I just posted about this on the list last week. It seems there's a bug
or undocumented feature that keeps other drives from showing up right
now. If you lower the threshold so that the drive goes into the warning
state you will see that it actually is being monitored.
Vikas, is this the intended behaviour or a bug? If it's a bug could it be
related to the error some of us are seeing? i.e.
(libdebug) eventlog syswrite error:
I only see this on startup which could relate to writing info messages.
On Fri, Oct 23/98, Cedric MARSOT <Cedric.Marsot@intervalle.fr> wrote:
> Here is my config file for the file system:
>
> #DFspace_avail hosta|hostb 10 7 5 /$
> DFspace_avail * 5 4 3 /space$
> DFspace_%used * 80 90 100 /space$
> DFspace_avail * 5 4 3 /$
> #DFspace_%used * 80 90 100 /usr$
> #DFspace_%used * 80 90 97 /usr/local$
> #DFspace_%used * 80 90 97 /home$
> #DFspace_%used * 80 90 97 /var/spool$
> DFspace_%used * 90 95 101
> DFinodes_%used * 70 80 90
[snip]
>
> What I want to do is to see on the console DFinodes_%used, DFspace_%used and
> DFspace_avail for each file system: / and /space ...
>
--
Artificial Intelligence stands no chance against Natural Stupidity.
GAT d- -p+(--) c++++ l++ u++ t- m--- W--- !v
b+++ e* s-/+ n-(?) h++ f+g+ w+++ y*
|