et
Sent: Tue, 18 Oct 2005 13:10:08 +0100
Subject: Re: Problems with tables in the same agent
> On Tue, 2005-10-18 at 08:30 -0300, Jordan Janeiro Lopes da Silva wrote:
> > why the agent calls the get_{first,next} of the result table if the
> > command snmptable was explicity for the c
On Tue, 2005-10-18 at 08:30 -0300, Jordan Janeiro Lopes da Silva wrote:
> why the agent calls the get_{first,next} of the result table if the
> command snmptable was explicity for the control table?
Remember that there's no such low-level SNMP request as "snmptable".
Fundamentally, the only reque
rdan Janeiro Lopes da Silva" <[EMAIL PROTECTED]>
Cc: [email protected]
Sent: Thu, 13 Oct 2005 18:29:30 -0400
Subject: Re: Problems with tables in the same agent
> On Thu, 13 Oct 2005 08:34:04 -0300 Jordan wrote:
> JJLDS> > The agent segfaults? What
On Thu, 13 Oct 2005 08:34:04 -0300 Jordan wrote:
JJLDS> > The agent segfaults? What happens if you do snmpgetnext with
JJLDS> > multiple varbinds?
JJLDS>
JJLDS> Yes. The same of snmptable, segmentation fault when the get_{first,
JJLDS> next}.
Can you get a stack trace?
--
NOTE: messages sen
> On Mon, 10 Oct 2005 10:59:59 -0300 Jordan wrote:
> JJLDS> I´ve developed a agent with 2 tables(control table and
> result table). JJLDS> When I query the agent with snmpget or snmpset
> everything goes fine. JJLDS> The problem is when I use snmptable. If
> the control table is empty, a JJLDS>
On Mon, 10 Oct 2005 10:59:59 -0300 Jordan wrote:
JJLDS> I´ve developed a agent with 2 tables(control table and result table).
JJLDS> When I query the agent with snmpget or snmpset everything goes fine.
JJLDS> The problem is when I use snmptable. If the control table is empty, a
JJLDS> segmentation
Hello guys, I´ve sent an e-mail last week but I´ve got no answers, so I´m
reporting my problem again.
I´ve developed a agent with 2 tables(control table and result table). When I
query the agent with snmpget or snmpset everything goes fine. The problem is
when I use snmptable. If the control tabl
