From owner-freebsd-questions Mon Jan 13 10:46:40 2003 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 137A837B401 for ; Mon, 13 Jan 2003 10:46:38 -0800 (PST) Received: from sub21-156.member.dsl-only.net (sub21-156.member.dsl-only.net [63.105.21.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C18943F5B for ; Mon, 13 Jan 2003 10:46:37 -0800 (PST) (envelope-from nkinkade@sub21-156.member.dsl-only.net) Received: from nkinkade by sub21-156.member.dsl-only.net with local (Exim 4.10) id 18Y9bY-000MJ6-00 for freebsd-questions@freebsd.org; Mon, 13 Jan 2003 10:46:36 -0800 Date: Mon, 13 Jan 2003 10:46:36 -0800 From: Nathan Kinkade To: freebsd-questions@freebsd.org Subject: Re: timezone issue Message-ID: <20030113184636.GS25529@sub21-156.member.dsl-only.net> Reply-To: nkinkade@dsl-only.net Mail-Followup-To: freebsd-questions@freebsd.org References: <20030113115439.B86410@typhoon.enabled.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="O3bhLwMadv7h6/J9" Content-Disposition: inline In-Reply-To: <20030113115439.B86410@typhoon.enabled.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --O3bhLwMadv7h6/J9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 13, 2003 at 11:56:21AM -0800, Noah Garrett Wallach wrote: >=20 >=20 > timezone issue. >=20 > all the documentation I have seen out there appears to be getting the > timezone set correctly. I have it set to PST. >=20 > It is 2 hours off from the actual time. can somebody explain how to fix > this? I have NTPD running as well. >=20 > Thanks in advance. >=20 > - Noah To what time is your CMOS clock set? PST might simply tell the system the offset from UTC - which itself is calculated by the utility `adjkerntz` based on your local time - found in your CMOS clock (assuming your CMOS clock is set to local time and not UTC). Also, if you just setup your system, ntpd might not choose to rapidly swing the system clock by 2 hours, as this could be confusing to the system. See the folling bits from the ntpd manpage: "In case there is no TOY chip or for some reason its time is more than 1000s from the server time, ntpd assumes something must be terribly wrong and the only reliable action is for the operator to intervene and set the clock by hand. This causes ntpd to exit with a panic message to the system log. The -g option overrides this check and the clock will be set to the server time regardless of the chip time. =20 =2E.. Under ordinary conditions, ntpd adjusts the clock in small steps so that the timescale is effectively continuous and without discontinuities." Basically, I'm guessing that your CMOS clock is off?? Hope this helps, Nathan -- GPG Public Key ID: 0x4250A04C=20 gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc --O3bhLwMadv7h6/J9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+IwmMWZYS9EJQoEwRAsFaAJ4hkrBoEvuXtJI66B/peQ5AhXGTfACfZErB 4oJcg5KduInpJAPGuCUKZT0= =v8tf -----END PGP SIGNATURE----- --O3bhLwMadv7h6/J9-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message