I should have given a bit more detail in my initial e-mail (it was
contained in a followup):
with the configuration as described below, both "date" and "date -u"
return the current local time.
I completely gave up trying to get time to work correctly with respect
to Samba. I didn't look deeply into exactly what time is getting
served, etc., but I know that if I edit a file on the Linux box using a
program running on the Win98 box, the timestamp on the final (edited)
file on the Linux box is returned on the Linux box as being several
hours in the future. (So "make" then proceeds to give lots of nasty
warnings after I've been editing source code, because it realises that
the time stamps are hosed.)
The exact situation under those circumstances (I just tested this) is
that if I use the Win98 editor to edit a Linux file, the timestamp
associated with the file after I have finished editing is reported
correctly by Windows explorer, but the time reported by Linux lies six
hours in the future (I am actually six hours behind GMT).
Your configuration sounds closer to "correct" than mine, so I'd be
interested in knowing exactly what you have for your /etc/localtime and
clock files.
>From what I have read, it should be possible to have everything (except
possibly Samba) working correctly with the BIOS time running on local
time, but I'm beginning to suspect that in fact the only way to get it
all right (again, except for Samba) is to have the BIOS running on GMT.
Doc Evans
PS One is tempted to wonder why something so basic hasn't been reduced
to a simple configuration dialog for idiots. At this point, I feel like
I would qualify.
On 24 May 01, at 21:01, David Rankin wrote:
> "D. R. Evans" wrote:
>
> > Where can I find something that definitively and correctly tells me how
> > to get my Linux 7.2 system to return the correct results when I try the
> > following commands:
> >
> > 1. date
> > 2. date -u
> >
> > The BIOS clock is running on local time (US Mountain time).
> >
> > According to the documentation I have read, the correct configuration
> > is to have /etc/localtime be set to /usr/share/zoneinfo/US/Mountain
> > and to have the following contents of /etc/sysconfig/clock:
> > ARC=false
> > UTC=false
> > Zone=America/Denver
> >
> > This causes "date" to respond correctly, and the clock on the screen to
> > display the correct time, but "date -u" gives the wrong time.
> >
> > I've fiddled around with these files, but nothing I've tried has been
> > the magic combination.
> >
> > Doc Evans
> >
>
> Doc, I don't know what type of problem you're having, but I have had an
> ongoing nightmare with Linux system time and the time Samba as a timeserver
> reports to the WinXX clients. The problem I experience occurs when system
> time is set to GMT, localtime to America/Chicago (or anything else). Linux
> shows the correct time, but the time that gets served to the Samba clients
> is shifted in the opposite direction be the appropriate GMT offset for the
> CST timezone. Say GMT is 1800 zulu, CST (in the real world is 1200), Samba
> serves WinXX clients 0000. I am still chasing this one.
>
> With the system clock set to CST, I get the right time served and I don't
> have any problems with functioning of the clock. The downside is I can't
> use xntpd to sync my system clock to the atomic clock because the realworld
> of timekeeping functions in GMT. Let me know your symptoms and I will see
> if I can't prepare a differential diagnosis upon which further diagnostics
> can be done to eliminate the invalid points and arrive at a final
> diagnosis.
>
>
> --
> David Rankin
> Nacogdoches, Texas
>
--------------------------------------------------------------
Phone: +1 303 494 0394
Mobile: +1 720 839 8462
Fax: +1 781 240 0527
--------------------------------------------------------------
