Hello,
First of all sorry for the crosspost with the bugtracker but I'm not sure the 
SF bugtracker is still used for the project?

So my problem: 
it's seems the OID UCD-SNMP-MIB::memShared.0 (OID .1.3.6.1.4.1.2021.4.13.0) no 
more longer exist since the version 5.4.3 included.
On the same server (debian 6, kernel 2.6.38.2)
- with version 5.4.1 (from deb package OR compiled from source) I ve got an 
answer:
# snmpget -v2c -c pub -On server 1.3.6.1.4.1.2021.4.13.0
.1.3.6.1.4.1.2021.4.13.0 = INTEGER: 0 kB

- with version 5.4.3 (from deb package OR compiled from source) and 5.6.1 
(compiled from source)
# snmpget -v2c -c pub -On server 1.3.6.1.4.1.2021.4.13.0
.1.3.6.1.4.1.2021.4.13.0 = No Such Object available on this agent at this OID

>From what I understood snmpd get this value from "Shmem" in /proc/meminfo. The 
>string is available in the file:

fkteqx-c37-15:net-snmp-5.6.1# cat /proc/meminfo
MemTotal: 24733492 kB
MemFree: 23446212 kB
Buffers: 87064 kB
Cached: 1028028 kB
SwapCached: 0 kB
Active: 496044 kB
Inactive: 635448 kB
Active(anon): 16416 kB
Inactive(anon): 144 kB
Active(file): 479628 kB
Inactive(file): 635304 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 24150012 kB
SwapFree: 24150012 kB
Dirty: 8 kB
Writeback: 0 kB
AnonPages: 15832 kB
Mapped: 5032 kB
Shmem: 152 kB
[... SNIP ...]

Maybe I have miss a patch or feature but I'm very surprised by this 
disappearing.

Thanks for your feedback/help

Regards
Emmanuel Vargas


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to