Ok. That sounds reasonable. Thanks a lot! Hope you can can answer my
following questions:
1) What is the difference between snmp.conf and snmpd.conf files in
'/etc/snmp/' directory?
2) When I execl 'snmptrap' command from my program, which of the above
two *.conf files are actually used?
Thanks,
On Sat, 2011-10-01 at 19:44 +0530, Vivek Nagaraj wrote:
> All I did was added this line in 'snmpd.conf': "defTarget snmptrap udp
> :50162" and restarted the snmpd service using: 'service snmpd
> restart'.
>
> I used to get the first trap at the UDP port 50162. And I used to
> receive trap on my cl
All I did was added this line in 'snmpd.conf': "defTarget snmptrap udp
:50162" and restarted the snmpd service using: 'service snmpd
restart'.
I used to get the first trap at the UDP port 50162. And I used to
receive trap on my client Windows machine where the trap receiver was
running at the defa
On Wed, 2011-09-28 at 14:32 +0530, Vivek Nagaraj wrote:
> Thanks a lot!!! That worked like a charm on the first go! But the
> problem I faced was that the first time I got the trap at the right
> port (not 162), but subsequent traps were still sent to the default
> port i.e., 162.
>
> Can you plea
On Fri, 2011-09-30 at 12:15 -0400, Joe Lorenz wrote:
> I just ran into a segfault in netsnmp_swinst_arch_load() where if the
> pkg_directory name is set, but the dir can't be opened, it was still
> attempting
> to read the NULL descriptor.
>
> Symptom: snmpd segfault when walking the entire MIB
On Fri, 2011-09-30 at 08:33 -0400, Rodrigo Hjort wrote:
> Hello Magnus,
>
> Actually I'm using the Debian package libsnmp-dev (v5.4.2.1), and
> here's the requested instruction:
If that is the case then it isn't that but then I am quite confused as
it builds for me using libsnmp-dev 5.4.3~dfsg-2.
