NetSaint and Y2K


Is NetSaint Y2K Compliant?

As far as I can tell, NetSaint is Year 2000 compliant. That being said, I can't be held responsible for any problems NetSaint may encounter or cause when the new millenium rolls around. You've been warned. Besides, you've got the source code so you can check things out for yourself!

How Does NetSaint Determine the Current Date and Time?

NetSaint uses the time() function to obtain the current system time from the underlying operating system. As long as NetSaint is able to get the proper date and time from the operating system, it should continue to function properly. Your mileage may vary if the underlying OS or hardware you are using is not Y2K compliant.

Where Does NetSaint Use Timestamps?

  1. In the service check scheduling queue
  2. As a timestamp at the beggining of each line in the log file
  3. As a timestamp at the beggining of each line in the status log
  4. In the $DATETIME$ macro

NetSaint's Scheduling Queue

The scheduling queue within NetSaint is what makes everything work. It controls when service checks are performed. Service checks are queued based on the time returned by the time() function. If your system clock rolls back to 1900 and the result from the time() function reflects this, the following things will probably occur:

  1. NetSaint will wait for approximately 100 years before performing the next service check
  2. Notifications for failed services and hosts will be delayed until the corresponding check is run (at least 100 years)

This would an annoyance at worst, but you're going to make sure that your hardware and OS are Y2K compliant, right?

Plugins and External Programs

Plugins and external programs that NetSaint calls in order to do service checks and notifications may or may not be Y2K compliant. If in doubt, check the source code.