Dave Shield wrote:
>> There are [a couple of] areas where the code is non-trivially different:
>
>> - memTotalFree
>> - memSwapError{,Msg}
>
> I offer the attached patch for consideration w.r.t. these two areas.
I'm not sure I see the benefits of tweaking the MIB and the code to
replace "virtual memory" by "real+swap" for these objects.
> The second half is tweaking the code for these objects.
> In most cases, this doesn't actually affect the values returned at
> all - it just implements things in a somewhat clearer manner.
> (That's clearer as in more explicit, rather than necessarily simpler
> code. In particular, it avoids a reliance on implicit dependencies
> within the HAL memory module).
What's wrong with using "virtual memory" for these objects?
> This does slightly amend the behaviour on *BSD systems, where
> these objects have up to now been tracking free swap only (rather
> than swap+real). I recognise that any change of behaviour is
> unwelcome, but I suggest that the benefits of a clear and consistent
> approach outweigh any disadvantages.
Fine by me.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
