"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
