check_disk

[Paul Clayton]

Found an interesting problem

Running check_disk on an HP server that uses long volume names such as
/dev/vgraid01/lvol1, causes nagios to report "Unable to read output:"
I discovered that the problem is because the output line of the df command
extends to two lines due to the long device name. Anybody got  awork around
on this one.
Regards

Unix like TeePee no windows, no gates, Apache inside.
 Paul Clayton
Global Unix Co-ordinator
Intec Telecom Systems
Ph +27 (0) 21 4309000
Fax +27 (0) 21 4309025
Mobile +27(0) 832853403




*******************************************************************************************
<http://www.intec-telecom-systems.com/>

This e-mail and any attachments are confidential and may also be privileged
and/or copyright material of Independent Technology Systems Limited
(or its affiliated companies). If you are not the intended or authorised recipient 
of this email or have received it in error, please delete it immediately and 
notify the sender by e-mail. In such a case reading, reproducing, printing or 
further dissemination of this e-mail is strictly prohibited and may be unlawful.

Independent Technology Systems Limited does not represent or warrant that 
an attachment hereto is free from computer viruses or other defects.

The opinions expressed in this e-mail and any of the attachments may 
be those of the author and are not necessarily those of Independent 
Technology Systems Limited.
******************************************************************************************



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
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