[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Rrd not updating
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Rrd not updating
- From: Henrik Stoerner <henrik (at) hswn.dk>
- Date: Tue, 25 Mar 2008 22:36:35 +0100
- References: <20080114211748.GD4153 (at) hswn.dk> <BAC1D28A5AB852439A6914CA7AB4E63F05409057 (at) permls05.wde.woodside.com.au> <20080115103417.GA2840 (at) cgoyard1.exp75.cvf> <20080325131242.GB5529 (at) cgoyard1.exp75.cvf> <20080325135443.GA16781 (at) hswn.dk> <47E92AEC.3000702 (at) tmsusa.com>
- User-agent: Mutt/1.5.15+20070412 (2007-04-11)
On Tue, Mar 25, 2008 at 09:40:12AM -0700, Sloan wrote:
> Henrik Stoerner wrote:
>> On Tue, Mar 25, 2008 at 02:12:42PM +0100, Charles Goyard wrote:
>>
>>> On our setup, the problem comes from a counter overflow in uptime
>>> handling on some SCO : after 248 days of uptime, the uptime is reported
>>> negative, and the rrd handler misses the expression (no "up:").
>>>
>>
>> Ahh - the old 31-bit timer tick issue. Linux has the same problem
>> because a timer ticks at 100 Hz using a signed 32-bit integer; so
>> 2^31 / (24*60*60*100) = 248 days and a bit.
>>
>
> That's news to me -
Sorry, I should have written "Linux HAD the same problem" (past tense).
This was fixed somewhere in the early 2.4.x kernels. That's why I wrote
it was the "old" problem.
Henrik