RE: Segfault in snmp_oid_compare ()

=?ks_c_5601-1987?B?sei8usij?= <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <00ac01c9ce20$ce2b7680$6a826380$@com>
Thanks for your replying. 
lsmCRDPTransactionID is Counter64 value
MIB definition is 


lsmCRDPTable OBJECT-TYPE
        SYNTAX        SEQUENCE OF LsmCRDPEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION   ""
        ::= { lsm 300 }

lsmCRDPEntry OBJECT-TYPE
        SYNTAX        LsmCRDPEntry
        MAX-ACCESS    not-accessible
        STATUS        current
        DESCRIPTION   ""
        INDEX         { lsmCRDPTransactionID, lsmCRDPFileName,
lsmCRDPServerID }
        ::= { lsmCRDPTable 1 }

LsmCRDPEntry ::=
        SEQUENCE {
				lsmCRDPTransactionID
						Counter64,
				lsmCRDPFileName
						OCTET STRING,
				lsmCRDPServerID
						Unsigned32,
				lsmCRDPFileSize
						Counter64,
				lsmCRDPLsmDirectory
						OCTET STRING,
				lsmCRDPVodServerIP
						IpAddress,
				lsmCRDPVodDirectory
						OCTET STRING,
				lsmCRDPProgressPercent
						Unsigned32,
				lsmCRDPState
						CRDPState
                }

However, I have some more questions.
it caused problem once or twice a day (My program 
updates lsmCRDPTable every 30seconds.) If using Counter64 value as index
to the table is invalid, why it work correctly in normal cases?

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave Shield
Sent: Wednesday, May 06, 2009 4:19 PM
To: ±è¼ºÈ£
Cc: [email protected]
Subject: Re: Segfault in snmp_oid_compare ()


2009/5/6 ±è¼ºÈ£ <[email protected]>:
> lsmCRDPTable_createEntry(netsnmp_tdata * table_data,
>                          U64 lsmCRDPTransactionID,

What is the syntax of the lsmCRDPTransactionID MIB object?
Is it Counter64 or what?


>     entry->lsmCRDPTransactionID = lsmCRDPTransactionID;
>     netsnmp_tdata_row_add_index(row, /*ASN_COUNTER64*/ASN_OPAQUE,
>                                 &(entry->lsmCRDPTransactionID),
>                                 sizeof(entry->lsmCRDPTransactionID));

Two problems here:
   Firstly, the Net-SNMP suite does not use simple 64-bit integer values
directly. It uses a structure counter64 to hold such values.

   Secondly, you can't use Counter64 (or Opaque) values as the
index to a table.    This is not valid in SNMP.

What is the definition of your MIB table?

Dave


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.