Yeah - In client data, df doesn't even show it. At the command line, tho, a plain "df" *does* show it - as Filesystem "none." I am assuming Xymon is quietly, and normally quite correctly, ignoring any output that doesn't show an actual physical file system.
Has anyone tried monitoring any kind of RAMdisk before..?
-----Original Message----- From: Ryan Novosielski [mailto:novosirj at umdnj.edu] Sent: Wednesday, January 19, 2011 4:05 PM To: xymon at xymon.com Subject: Re: [xymon] Monitoring /tmp usage
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
It is possible that your problem stems from the fact that /tmp is type "none" and that a grep looking for /dev would fail. I'm not exactly sure what Xymon looks for, but I had to manually change some scripts associated with BB to look for even ZFS filesystems which do not have devices under / (or at least they don't appear to from df's POV).
On 01/19/2011 03:38 PM, Rob Munsch wrote:
Okay, so DISK is not impressed with me and just monitoring the physical disk. I am running a client on a remote VPS, and would like to keep an eye on its /tmp, but not sure how or where to define that. Or if? Any tips appreciated.
[df]
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hdv1 3768053780 1050316584 2717737196 28% /
[mount]
/dev/hdv1 on / type ufs (defaults)
none on /proc type proc (defaults)
none on /tmp type tmpfs (size=128m,mode=1777,nosuid,noexec,nodev)
**Rob Munsch**
IT Administrator
Philly**Car**Share
215-495-1040 x131
www.phillycarshare.org <http://www.phillycarshare.org>
Our Vision: A Philadelphia in which non-profit car sharing exceeds the convenience, flexibility, and affordability of car ownership.
- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Sr. Systems Programmer |$&| |__| | | |__/ | \| _| |novosirj at umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/CST-Academic Svcs. - ADMC 450, Newark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk03UeQACgkQmb+gadEcsb4aggCeLhcc9/QHS2EVOWQiThZibJXz KGEAnj8H+MJif0lHrYaakR8zI0JaUGlN =R3PO -----END PGP SIGNATURE-----