您好！
如果使用SNMPTRAP命令发送TRAP V1得数据呢，比如以下数据：
GT=6; ST=5; EID=.1.3.6.1.4.1.343.2.5.1.1;
.1.3.6.1.4.1.343.2.5.1.1.12.0=ULTRA-D0EE0DE1D;
.1.3.6.1.4.1.343.2.5.1.1.8.0=1236154078; .1.3.6.1.4.1.343.2.5.1.1.9.0=0;
.1.3.6.1.4.1.343.2.5.1.1.10.0=Intel Alert Management System II;
您好！
如果使用SNMPTRAP命令发送TRAP V1得数据呢，比如以下数据：
GT=6; ST=5; EID=.1.3.6.1.4.1.343.2.5.1.1;
.1.3.6.1.4.1.343.2.5.1.1.12.0=ULTRA-D0EE0DE1D;
.1.3.6.1.4.1.343.2.5.1.1.8.0=1236154078; .1.3.6.1.4.1.343.2.5.1.1.9.0=0;
.1.3.6.1.4.1.343.2.5.1.1.10.0=Intel Alert Management System II;
Hello,
Is there anyone who got NOTIFICATION-LOG-MIB support in snmptrapd
working on Win32 ? Even after having fixed a few compile time and
run-time errors, a MIB walk on OID 1.3.6.1.2.1.92 (notificationLogMIB)
still returns zero varbinds. Any advice is welcome.
The patch below fixes the
The code parsing cpuinfo strings could read past end of buffer.
Avoid this problem by using only part of the allocated size
and null terminating.
Add check for read error.
---
agent/mibgroup/hardware/cpu/cpu_linux.c | 33 +-
1 files changed, 23 insertions(+), 10
--
--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based
Valgrind can't figure out that speed will be set by SIOCETHTOOL,
so just initialize it.
---
.../mibgroup/if-mib/data_access/interface_linux.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
--- a/agent/mibgroup/if-mib/data_access/interface_linux.c 2009-03-16
16:44:07.608956089
Same proble as other proc scanning, need to terminate string
before calling strstr.
---
agent/mibgroup/hardware/memory/memory_linux.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
--- a/agent/mibgroup/hardware/memory/memory_linux.c 2009-03-16
16:44:16.512954764 -0700
+++
The code for reading /proc files guesses at an initial size buffer,
then has to retry if the buffer isn't big enough. This slows boot
since it has to repeat several time. It was a penny wise (save memory)
but pound foolish (cpu) choice in initial design. Instead choose size
that gets rounded up to
Hi Gabriele,
Thanks for reply!
On Mon, Mar 16, 2009 at 12:07:42PM +0100, Gabriele Messineo wrote:
the changes seem fine and the code really clean.
Thanks.
- I think too that VarList is an added complexity.
However, your implementation seems to me like a good tradeoff
