Re: unbounded memory use in net-snmp (5.1.2 up to 5.4)

2007-03-03 Thread Thomas Anders
Mike Schmidt wrote: > I have net-snmp 5.4 running on > > - RH8 and CentOS 4.4 systems (compiled with no options to configure) > - Solaris 10. (compiled without embedded-perl because of perl issues) > > I also have some copies of 5.1.2 (the official CentOS version) installed > as binary from the C

Re: DisMan Event MIB Problem

2007-03-03 Thread Uday Sorte
Thanks Dave for all the hard work you have done. I think if I try compiling the subagent code as a part of master agent, using the "configure --with-mib-modules" this problem will not show up. I will try to explore more features down the line and will report you if I encounter any new problems.

Re: Net-snmp-users Digest, Vol 10, Issue 7

2007-03-03 Thread zaman L
On 3/2/07, [EMAIL PROTECTED] < [EMAIL PROTECTED]> wrote: Send Net-snmp-users mailing list submissions to net-snmp-users@lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/net-snmp-users or, via email, send

unbounded memory use in net-snmp (5.1.2 up to 5.4)

2007-03-03 Thread Mike Schmidt
Hi, I've searched the recent messages in the mailing list for memory leaks and other similar terms and found nothing helpful. Here's my situation: I have net-snmp 5.4 running on - RH8 and CentOS 4.4 systems (compiled with no options to configure) - Solaris 10. (compiled without embedded-perl

create-dataset api

2007-03-03 Thread Pilt
Hi everyone, when using dataset api initialize_table_() is used to populate the dataset. So for all following requests data will be extracted from this already formed structure. But what if I get some external data into the dataset, which can vary between requests? In old api I called the rout

Re: configuring net-snmp from source

2007-03-03 Thread zaman L
On 3/2/07, Dave Shield <[EMAIL PROTECTED]> wrote: On 02/03/07, zaman L <[EMAIL PROTECTED]> wrote: > ./snmpd -f -Lo -x udp:127.0.0.1:161 /tmp/snmp.skt No - that's wrong. The -x option is used to specify an *AgentX* socket. So the agent is now listening for AgentX connections on the standar