Re: 12 and 24 hour clock timings -- arggh!
From: Jim Miller (jimspmcatcher_at_hotmail.com)
Date: 03/05/04
- Next message: Mark Hobley: "depmod and modinfo have hard coded paths"
- Previous message: Daniel Ganek: "Re: Recording ISOs"
- In reply to: P Gentry: "Re: 12 and 24 hour clock timings -- arggh!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Mar 2004 10:53:38 -0800
rdgentry1@cablelynx.com (P Gentry) wrote in message news:
> Not generally a good idea to use _different_ time sources when trying
> to maintain a _common_ and accurate time synch.
>
True enough. The machine is almost never in Windows; I just mentioned
this to be clear that, once upon a time, Windows had been able to play
with the clock.
> The differences you are seeing in the output are just differences in
> display format, I believe. The "good" machine is using default format
> (24 hrs) while "bad" has been set to use a custom format (12 hrs).
> Another variable to re-locate. KDE and Gnome store/use different
> settings for this and they/RH do not conform to what you would expect
> from reading the man pages.
I'll look for these. For what it's worth, the Gnome date/time panels
on the two machines are set identically (24 hour).
>
> Of more interest to me is why the backups are not working on the "bad"
> machine. Any time-base issues would be centered on the OS system time
> (always UTC in Linux) and yours seem to be reasonably close at ~ 25
> secs. I use Retrospect on my W98 partition and will re-visit its
> setup options -- my vote is that the "bad" machine is not set up
> correctly for what you want it to do. In what sense is yours not
> "working" on the bad machine?
If I do a full Retrospect backup on the "bad" client, and then
immediately follow up with a normal backup on the same client,
Retrospect believes that over half the disk needs to be backed up. If
I cancel out of that backup request and do it again, I get a different
estimate of what needs to be backed up -- plus or minus 10,000 files.
The "good" Linux client works fine, and my other backups (Mac and
Windows) are fine as well . I've got an open trouble ticket with
Dantz on this, but we have all been scratching our heads over it.
>
> BTW
> -- you may want to run your hw clock on UTC/GMT rather than local time
> when trying to keep systems in time synch (seems to be the "standard"
> practice)
> -- you may want to use a "better" or closer time server to lessen
> network/congestion effects. The 25 sec _difference_ is rather large
> for a local net.
That time difference reflects the time that I spent looking at the
results from one machine, switching to the ssh window opened on the
other machine, retyping the hwclock command, etc. If you look at the
running clock times on both machines, they're in quite good sync
(within 1 sec).
Thanks very much,
Jim
- Next message: Mark Hobley: "depmod and modinfo have hard coded paths"
- Previous message: Daniel Ganek: "Re: Recording ISOs"
- In reply to: P Gentry: "Re: 12 and 24 hour clock timings -- arggh!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
