Hi Mario
This setting existed before I started maintaining the script.
I believe it is there in case you have been using BBWin – all it does is swap the values reported for swap and virtual.
My guess is that BBWin reported these a certain way round, the actual correct way round is the opposite, but to maintain compatibility it does it like BBWin – unless you set clientbbwinmemdebug = 0.
If you're migrating from BBWin my guess is you'd want this on so that the client reports the same way. Otherwise, you may want it off.
The other problem with changing it is that I understand some admins have changed the text at the server end to be "correct" for them – so changing it here as well will cause more confusion!
I can add some documentation to the .doc file for what the parameter does.
Zak
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Mario DE CHENNO Sent: 10 June 2016 10:37 To: xymon at xymon.com Subject: [Xymon] winpsclient: what about "clientbbwinmembug" setting?
Hi all, Hi Zak.
I had to set in xymonclient_config.xml
<clientbbwinmembug>0</clientbbwinmembug>
to avoid bad detecting of swap memory in windows server 2008 and 2012
Is this (undocumented) parameter, and the relative snippet of code, still needed? And, if so, does make sense defaulting to 0 in the distributed config file?
Best regards and thanks for your work.
Mario De Chenno