monitor disk usage only for a specified fs type (NFS)?

[Babineau, Mike]

Short of using check_disk with a string of -X (--exclude-type) arguments
or writing a custom plugin, is there a way to monitor disk usage for
mounts of a specified fs type (in this case, NFS)?  The NFS mounts in
this case are rented, NAS'd-out SAN space, so I can't monitor the
source.  It seems like it may be possible with -p, but I haven't gotten
it to recognize any sort of wildcard.  Why does --exact-match exist if
-p won't accept partial paths/partitions or wildcards:

-E, --exact-match

For paths or partitions specified with -p, only check for exact paths

 

(I am using check_disk 1.79 packaged with nagios-plugins 1.4.5)

 

Any ideas?

 

Thanks,

---------------------------

Michael Babineau

Production Services

Pearson Curriculum Group

mike.babineau at pearson.com

 


**************************************************************************** 
This email may contain material confidential to
Pearson.  If you were not an intended recipient, 
please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070530/aa3f283e/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null