Re: [Nagios-devel] Are all the last_update values in status.dat al=
Posted: Thu Jul 09, 2009 4:28 pm
Hi All,
After Andreas explained the correct default behavior I looked in base/xsdde=
fault.c
I found this on lines 443 & 499
fprintf(fp,"\tlast_update=3D%lu\n",current_time);
Now this is Nagios -2.7 the same one Cary is running. We should probably =
check 2.12 and 3.x to make sure this isn't the case there as well.
Sincerely,
Steve
________________________________________
From: Andreas Ericsson [[email protected]]
Sent: Thursday, July 09, 2009 1:23 AM
To: Nagios Developers List
Subject: Re: [Nagios-devel] Are all the last_update values in status.dat al=
ways the same?
Cary Petterborg wrote:
> The value for last_update in status.dat is the same for all records
> on our installation (30,000 services, 3300 hosts on 2.7- yes, I know
> it's old). Are there instances where this would not be the case? It
> seems that it would have been much more efficient to just put the
> last_update in the file once at the top if it is always the same for
> each record. Then things like diff and rsync of the status.dat file
> would be *significantly* better. Is there a possible use of the
> last_update field that I'm unaware of that would make a single
> last_update entry for the file be a bad idea?
>
They're tracked separately per status object. If the times are all
the same, that could mean you've found a bug, or Nagios does something
that doesn't quite make sense to me. This is from looking at the
data structures for hosts and services. I haven't examined the code
that prints it all out.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
---------------------------------------------------------------------------=
---
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Nagios-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/lis ... gios-devel
NOTICE: This email message is for the sole use of the intended recipient(s=
) and may contain confidential and privileged information. Any unauthorized=
review, use, disclosure or distribution is prohibited. If you are not the =
intended recipient, please contact the sender by reply email and destroy al=
l copies of the original message.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: ndreas Ericsson [[email protected]
After Andreas explained the correct default behavior I looked in base/xsdde=
fault.c
I found this on lines 443 & 499
fprintf(fp,"\tlast_update=3D%lu\n",current_time);
Now this is Nagios -2.7 the same one Cary is running. We should probably =
check 2.12 and 3.x to make sure this isn't the case there as well.
Sincerely,
Steve
________________________________________
From: Andreas Ericsson [[email protected]]
Sent: Thursday, July 09, 2009 1:23 AM
To: Nagios Developers List
Subject: Re: [Nagios-devel] Are all the last_update values in status.dat al=
ways the same?
Cary Petterborg wrote:
> The value for last_update in status.dat is the same for all records
> on our installation (30,000 services, 3300 hosts on 2.7- yes, I know
> it's old). Are there instances where this would not be the case? It
> seems that it would have been much more efficient to just put the
> last_update in the file once at the top if it is always the same for
> each record. Then things like diff and rsync of the status.dat file
> would be *significantly* better. Is there a possible use of the
> last_update field that I'm unaware of that would make a single
> last_update entry for the file be a bad idea?
>
They're tracked separately per status object. If the times are all
the same, that could mean you've found a bug, or Nagios does something
that doesn't quite make sense to me. This is from looking at the
data structures for hosts and services. I haven't examined the code
that prints it all out.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
---------------------------------------------------------------------------=
---
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Nagios-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/lis ... gios-devel
NOTICE: This email message is for the sole use of the intended recipient(s=
) and may contain confidential and privileged information. Any unauthorized=
review, use, disclosure or distribution is prohibited. If you are not the =
intended recipient, please contact the sender by reply email and destroy al=
l copies of the original message.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: ndreas Ericsson [[email protected]