On Mon, Jan 13, 2003 at 11:56:21AM -0800, Noah Garrett Wallach wrote: > > > timezone issue. > > all the documentation I have seen out there appears to be getting the > timezone set correctly. I have it set to PST. > > It is 2 hours off from the actual time. can somebody explain how to fix > this? I have NTPD running as well. > > Thanks in advance. > > - 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. ... 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 gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc
msg15343/pgp00000.pgp
Description: PGP signature
