<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12"> <TITLE>RE: [Nagios-users] check_ntp and time-offset 0.000000 sec</TITLE> </HEAD> <BODY> I've done the same thing in our environment. An offset of '0' didn't happen very often, but it WAS frequent enough to get annoyed with notifications about it. --Ben -----Original Message----- From: ZIEGENBEIN, Kurt [<A HREF="mailto:kurt.ziegenbein@saarstahl.com">mailto:kurt.ziegenbein@saarstahl.com</A>] Sent: Tuesday, January 07, 2003 5:49 AM To: 'nagios-users@lists.sourceforge.net' Subject: [Nagios-users] check_ntp and time-offset 0.000000 sec Hi all! We had to comment out the following pice of code in the check_ntp plugin: # An offset of 0.000000 with an error is probably bogus. Actually, # it's probably always bogus, but let's be paranoid here. if ($offset == 0) { undef $offset;} We are using check_ntp to watch for the time difference on our server which are all NTP-Clients. Some times Nagios reported an error, because of a zero-offset. At the moment I can't overview why this check should be done. What do you think? ciao Kurt ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! <A HREF="http://www.vasoftware.com" TARGET="_blank">http://www.vasoftware.com</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users" TARGET="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> </BODY> </HTML>