Re: [Nagios-devel] Bug report: downtimes beyond 2038 cause event

Engage with the community of users including those using the open source solutions.
Includes Nagios Core, Plugins, and NCPA

Re: [Nagios-devel] Bug report: downtimes beyond 2038 cause event

Postby Guest » Mon Apr 08, 2013 5:34 am

--14dae9cdcad74c34ae04d9d3852c
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 5, 2013 at 4:55 PM, Andreas Ericsson wrote:

> On 04/05/2013 09:41 AM, Anton L=F6fgren wrote:
>
>> For the record, the following patch identically triggers the faults on m=
y
>> x86_64 Arch installation (where time_t normally is a quad word).
>>
>>
> Well, yes. You're explicitly casting it to a 32-bit value but it can't
> hold that much so it gets truncated.

Right. The point I was trying to make was merely that it indeed seems like
an integer overflow is causing the issue Ton Voon's experiencing. I'm sorry
for the noise if that had already established as fact.


> But CentOS 5 really shouldn't have
> 32-bit time_t, and especially not on 64-bit archs, so I don't know
> where it's getting its cast from.
>
Indeed - it'd be great to have some more information on what structs are
actually being used on his system. Along, possibly, with whichever build
flags were used to build his CentOS Nagios installation

--14dae9cdcad74c34ae04d9d3852c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On F=
ri, Apr 5, 2013 at 4:55 PM, Andreas Ericsson <=3D"mailto:ae@op5.se" target=3D"_blank">ae@op5.se> wrote:
=
x #ccc solid;padding-left:1ex">
On 04/05/2013 09:41 AM, Anton L=F6fgren wrote:

x #ccc solid;padding-left:1ex">
For the record, the following patch identically triggers the faults on myr>
x86_64 Arch installation (where time_t normally is a quad word).






Well, yes. You're explicitly casting it to a 32-bit value but it can=
9;t

hold that much so it gets truncated.
Right. The point I w=
as trying to make was merely that it indeed seems like an integer overflow =
is causing the issue Ton Voon's experiencing. I'm sorry for the noi=
se if that had already established as fact.

=A0
r-left:1px #ccc solid;padding-left:1ex">But CentOS 5 really shouldn't h=
ave

32-bit time_t, and especially not on 64-bit archs, so I don't know

where it's getting its cast from.
Indeed - it'=
d be great to have some more information on what structs are actually being=
used on his system. Along, possibly, with whichever build flags were used =
to build his CentOS Nagios installation



--14dae9cdcad74c34ae04d9d3852c--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: alofgren@op5.com
Guest
 

Return to Community Support

Who is online

Users browsing this forum: Eric05 and 45 guests