[548] in netbsd-help mailing list archive
Re: Next problem
daemon@ATHENA.MIT.EDU (John Hawkinson)
Sun Dec 17 15:13:09 1995
Date: Sun, 17 Dec 95 15:12:56 -0500
To: jjnovak@MIT.EDU
Cc: ghudson@MIT.EDU, netbsd-help@MIT.EDU
From: John Hawkinson <jhawk@MIT.EDU>
> > Someone might want to fix the time settings for the computer that
> > hooks up with NetBSD. Every time I connect NetBSD, my computer's
> > clock is set ahead one hour (i.e. daylight savings time). And it's a
> > pain 'cuz techmail won't let you get kerberos when there's a one
> > hour skew between you and the server.
>
> I can't understand what you mean by this. Do you mean that when a
> machine boots NetBSD, and then is booted again under DOS, DOS's time
> is displaced one hour from what it was before? We can test this, but
> we've never heard of this problem before.
Yes we have!
Basically NetBSD thinks your time-of-day clock is in a different
timezone. I saw this once and fixed it by hand, but never propragated
the changes into our kernels, and I frankly don't remember the
right value, so you get to experiment. :-)
The kernel variable "tz" specfies the non-daylight-savings-time offset
of your machine's TOD clock in minutes to the left of GMT (a seperate
adjustment of 1 hour is made for EST vs. EDT). The default value is
"300", which is clearly not right for you, either because your TOD
clock & DOS are screwy, or whatever.
You can change the value with:
gdb -w /netbsd
print tz
set tz=360
quit
as root. I think 360 is what you want, but it might be 240. Anyway,
then you should reboot. Ensure that the time is set appropriately
under NetBSD, and then boot DOS and check it there. If it's off by two
hours, you went the wrong way. If it's still screwy, something's wrong
w/ my explanation so set tz to zero and compare the difference between
your DOS clock and it and then set it to the difference in minutes.
It might take you a few reboot cycles to get right, but I assume
that's OK w/ you.
Do let us know what the right number for you is; we rarely use DOS
on the machines we run NetBSD on so we don't tend to see this problem.
Thanks!
--jhawk
