Are all the last_update values in status.dat always the same?

[Steven D. Morrey]

I've vetted through 2.7, 2.12 and 3.x in all cases it's the same 
		fprintf(fp,"\tlast_update=%lu\n",current_time);

Oddly enough I don't think this was a bug.  I think that this WAS a bug fix way back in the mists of time, the reason being is that the last_update time is NEVER set or updated except when it's read in from retention.dat

If we correct this code to the proper temp_host->last_update and temp_service->last_update, nagios will likely segfault as soon as it writes out status.dat
I vote for complete removal of this line and modification of extinfo.c to use the file update time, since it appears to be the only file that uses it.
Let me know what you think!

Sincerely,
Steve


________________________________________
From: Cary Petterborg [PetterborgCa at ldschurch.org]
Sent: Thursday, July 09, 2009 8:37 AM
To: Nagios Developers List
Subject: Re: [Nagios-devel] Are all the last_update values in status.dat always the same?

It is the same timestamp as "created" in the info record for all entries of last_update in the records (all 32,000 of them in the file).

I'll look at the code that we are using to see what it is using and compare it to the baseline 2.7 version. I don't think there will be any
difference in the code for that. Code changes for the nagios binary that we use are minimal.

Thanks

Cary

________________________________________
From: Andreas Ericsson [ae at op5.se]
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 always 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                   andreas.ericsson at op5.se
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
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-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 all copies of the original message.



------------------------------------------------------------------------------
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
Nagios-devel at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-devel

------------------------------------------------------------------------------
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