There’s a small bug in Nagios 2.0 where passive checks are marked as stale as soon as Nagios starts up. This will change it so that passive checks will be marked as stale when it exceeds the freshness_threshold after startup.

We’ve already sent this to the nagios-devel mailing list and Ethan has applied this to the Nagios 2.x branch in CVS, but we thought we’d add this here for completeness.

You can get the patch here.