Not much point in doing memory monitoring on a Solaris sparse zone. Might as well put a check in the client script to not collect memory info for a sparse zone with capped memory. See here for more info. http://www.xymon.com/archive/2010/02/msg00213.html
Regards Vernon
On Wed, Dec 15, 2010 at 6:11 AM, Tim McCloskey <tm at freedom.com> wrote:
Henrik,
Thanks for the speedy answer. I had seen this in fun in hobbitd/client/$clients.c. You must enjoy porting that part of the project each time some OS makes a change :)
Trivia: On Solaris 10 zones prtconf can get the installed "Memory size:" But anything further (like prtdiag) will fail.
System Configuration: Sun Microsystems i86pc Memory size: 32768 Megabytes System Peripherals (Software Nodes):
prtconf: devinfo facility not available
Regards,
Tim
From: Henrik Størner [henrik at hswn.dk] Sent: Tuesday, December 14, 2010 1:50 PM To: xymon at xymon.com Subject: Re: SV: [xymon] Xymon reports excessive memory usage on 1 SLES 11 host
On Tue, 14 Dec 2010 13:42:21 -0800, Tim McCloskey wrote:
What does the Solaris client use to get this data? vmstat? (free is not a native solaris tool).
Each OS has their own way of reporting memory utilisation - it is completely non-standard, and the one part of the Xymon client that requires the most code for each new OS!
Specifically for Solaris, Xymon uses prtconf to determine how much memory is installed, and vmstat to determine how much is being used. "swap -s" was used for determining how much swap was being used, but earlier today I committed an update so we will now use "swap -l" instead.
Regards, Henrik
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com
To unsubscribe from the xymon list, send an e-mail to xymon-unsubscribe at xymon.com