Thomas Anders wrote:
> I'd suggest to rename init_mib() to netsnmp_init_mib() and only use this one
> throughout our code, so it'll always use the correct function. For backward
> compatibility reasons we'll still need an init_snmp wrapper, of course.
s/init_snmp/init_mib/
+Thomas
--
Thomas An
+1
>I'd suggest to rename init_mib() to netsnmp_init_mib() and only use this
one
throughout our code, so it'll always use the correct function. For backward
compatibility reasons we'll still need an init_snmp wrapper, of course.
>Dave has promised to post a provisional patch shortly. Assumed it w
-Coders,
Albert Chin has recently reported problems on HP-UX 11.11 (see the
net-snmp-users thread " Timeout errors on HP-UX 11.11" for details) and tracked
them down to the fact that his build used the init_mib() function provided by
libnm rather than ours. We link to libnm on HP-UX, because we're
Sorry, to forgot to cc.Hence forwarding again.Note: forwarded message attached.--- Begin Message ---
Dear DaveI will change the code back to the way it was. Assuming that the code is right,Can you please advice us with new ideas on how to fix the problem. As I mentioned in the mail, we have the man
Dear All,I am using Net-SNMP version 5.3.1 and have encountered a problem for a daemon configured to use pass-through persist (pass_persist token in the configuration file).Normally, the daemon re-reads it's configuration files when sent a HUP signal. However when using pass_persist, the daemon be
On 23/10/06, Venkata Guddeti <[EMAIL PROTECTED]> wrote:
> Dear Dave
> I will change the code back to the way it was. Assuming that the code is
> right, Can you please advice us with new ideas on how to fix the problem. As I
> mentioned in the mail, we have the manager running on the 32 bit machine.
Dear Dave,Thank you very much for the prompt reply from you and Robert.I have forgotten to mention that the manger machine is a 32 bit RHEL WS4 OS.Could that cause this kind of problem (getting two counter64 vars in one snmpget). Are there any rules that need to be followed when communicating betwe
On 23/10/06, Venkata Guddeti <[EMAIL PROTECTED]> wrote:
> case MODE_GET:
> struct counter64 counterVar;
> // Here I had low and high assigning as follows
> // counterVar.low = newStats->NumBCFileRead & 0x;
> // counterVar.high = newStats->NumBCFileRead >> 32;
> // After seeing
