[Xymon] winpsclient: what about "clientbbwinmembug" setting?

[Mario DE CHENNO]

I was sure it was a legacy setting, and understand your point of view.
Anyway things are not totally clear for me....
I have a plain xymon 4.3.17 installation. Some memtests are presented as reported below.
As you can see, labels are different in bbwin and psclient reports. Furthermore, Swap value seems wrong for psclient on 2003.

Does still clientbbwinmembug default really matter? How are others dealing with that?

Mario

=======================================================
Windows server 2003 - BBwin

 Memory Used   Total  Pctg
 Physical:     825M   4095M   20%
 Virtual:       35M   2047M    1% [<- SWAP]
 Page:         576M   5976M    9%

Windows server 2003 - xymonclient.ps1  1.96 2015-01-21
clientbbwinmembug  : 1

 Memory              Used       Total  Percentage
 Physical           2641M       8191M         32%
 Actual                8M       8191M          0%
 Swap               2219M       9799M         22%

[where is SWAP? size is set to 2046-4092, it actually is 2046 MB]


Windows server 2012R2 - xymonclient.ps1  2.15 2016-02-03
clientbbwinmembug  : 0

 Memory              Used       Total  Percentage
 Physical           1052M       8191M         12%
 Actual              835M       8191M         10%
 Swap                  0M       4096M          0% [<- SWAP]


Windows server 2008 - xymonclient.ps1  2.02 2015-05-13
clientbbwinmembug : 1

 Memory              Used       Total  Percentage
 Physical           1810M       8192M         22%
 Actual                0M       8192M                 0%       [<- SWAP]
 Swap               1680M      16381M         10%
=======================================================0


Il giorno ven, 10/06/2016 alle 11.16 +0000, zak.beck at accenture.com ha scritto:
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20160610/2a02d51c/attachment.html>