RE: sysUpTime jumps from 24 to 472 on Linux

"Mike Ayers" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <83E753BE7B6A324ABB336245BAF1DAAC073BB1D4@mailserver.metatv-ds.metatv.com>
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of arul vadivel
> Sent: Tuesday, October 09, 2007 2:17 AM


> I just want to fix this in my application using ucd-snmp 
> 4.2.3 (without migrating to latest version).
> When I do diff between latest version and the old version 
> agent/mibgroups/util_func.c and .h file,
> I can see they modified the return type for sysUptime to 
> u_long from int as given below:

<SNIP/>

> I modified the same in the src file and did make install to 
> compile/install the changes.
> But, still it is not reflected in my application. 
> 
> Could  someone please shed some light on this?
> It would be very much approciated.

	Yes.  Quite simply, there were more changes than the one file needed to fix the problem.  In fact 4->5 was quite the rewrite, so it appears this problem was never fixed in version 4.

	If you want to continue using version 4, and do not have a workaround for this issue, then you will need to fix this bug yourself, as it is most likely that there is noone left doing active development on that branch.

	Your magical clue is that 2^31 ms = 24.8551 d, and 2^32 ticks - 2^31 ms = 472.2476 days!


	Enjoy!

Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.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.