From owner-freebsd-questions@FreeBSD.ORG Sat Apr 26 10:32:19 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DCDD37B404 for ; Sat, 26 Apr 2003 10:32:19 -0700 (PDT) Received: from dhumketu.homeunix.net (dialpool-210-214-66-130.maa.sify.net [210.214.66.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF95443FA3 for ; Sat, 26 Apr 2003 10:32:14 -0700 (PDT) (envelope-from shantanoo+fbsd@ieee.org) Received: by dhumketu.homeunix.net (Postfix, from userid 1001) id DCB574555; Sat, 26 Apr 2003 21:39:32 +0530 (IST) Date: Sat, 26 Apr 2003 21:39:32 +0530 From: Shantanu Mahajan To: David Kelly Message-ID: <20030426160932.GA670@dhumketu.homeunix.net> Mail-Followup-To: David Kelly , freebsd-questions@freebsd.org References: <20030425211506.GA47060@grumpy.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <20030425211506.GA47060@grumpy.dyndns.org> User-Agent: Mutt/1.4i Organization: Hmmm... I dunno X-OS: FreeBSD 5.0-RELEASE i386 cc: freebsd-questions@freebsd.org Subject: Re: Time Problem in 5.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Apr 2003 17:32:19 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable +++ David Kelly [freebsd] [25-04-03 16:15 -0500]: | On Sat, Apr 26, 2003 at 12:18:13AM +0530, Shantanu Mahajan wrote: | > |=20 | > | You really haven't provided anywhere near enough information for us to | > | diagnose a failure with ntpdate. | >=20 | > > sudo ntpdate 216.244.192.3 | > 26 Apr 00:14:08 ntpdate[717]: no server suitable for synchronization fo= und |=20 | So what is your problem with ntpdate? Clearly the problem is that | 216.244.192.3 did not respond with an answer. Is your network actually | up? Is 216.244.192.3 reachable? Is port 123 blocked in your firewall? Network is up. can ping 216.244.193.3. No firewall. All ports are open. | Scrolling up thru this thread I see where Shantanu says he tried ntpdate | in single user mode. Duh. Networking isn't brought up until the system | goes multi. No network, no network time. Altho being up to process 717 | in single user is unusual. I tried the following command in single mode # date;sleep 1;date |=20 | As for the output of sleep(1), his date(1) is rounded down to 1 second | in display so if the first date is at 16.9 seconds and a 1 second sleep | later might very well be at 18.0 and appear to be 2 seconds later. |=20 | Sleep is only an approximate in any case. I remember documentation on | other Unix systems stating a "sleep 1" might return immediately. So it | was common to use a "sleep 2" if you wanted to hope for at least a 1 | second delay. for sleep 1, I am getting 2 sec delay. |=20 | --=20 | David Kelly N4HHE, dkelly@hiwaay.net | =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D | The human mind ordinarily operates at only ten percent of its | capacity -- the rest is overhead for the operating system. |=20 | ------------------------------ Regards, Shantanu --=20 An age is called Dark not because the light fails to shine, but because people refuse to see it. =20 --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+qq868NTC7RN6/Z4RApVUAJ9ibZTqaX3zX+/9Ur0PEAQln4g92QCff8z9 BBTHuNJoSocskmRTv5IFdbU= =GMSu -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--