Re: [Nolug] time problems on RH 7.3

Mischa Krilov <subs@krilov.com> writes:

> Roetto Mike B CONT SSGC wrote:
>
>> I have a workaround that executes "rdate -s time.nist.gov" at startup, but
>> it's been bugging me.
>
> Whenever I've had to sync time, I've used ntp. It may be a better way
> for you to keep the clock in sync. Last time I played with it, we had
> one box ntp'ing to a server in the outside world, and all of other
> machines hit the internal ntp server.
>
> Link:
> http://www.ntp.org/

I'm going to second this post. If you need to sync time, you should
consider deploying NTP. You will need one box to sync to an ntp
server on the internet (or perhaps private to your navy.mil domain) or
via some sort of local GPS clock. you'll then need a couple of
internal servers to share syncing data as well.

>> Anyone have any ideas of things I could look at? Platform is RedHat 7.3 on a
>> Compaq Proliant 2500.
>
> For your specific problem, you may want to check and make sure that
> your BIOS clock is set the way you want it, including TZ (if possible)
> or if your system somehow thinks the clock is UTC time. If I were you,
> I'd set the time however you like, then use hwclock to sync the system
> time with the hardware clock.
>
> You can check to see if there's a discrepancy with:
>
> hwclock --show
>
> and sync the hardware clock to the system time as follows:
>
> hwclock --systohc
>
> Link:
> http://www.rt.com/man/hwclock.8.html
>
> Hope this helps.
>
> Mischa.
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>

-- 
Scott Harney<scotth@scottharney.com>
"...and one script to rule them all."
gpg key fingerprint=7125 0BD3 8EC4 08D7 321D CEE9 F024 7DA6 0BC7 94E5
___________________
Nolug mailing list
nolug@nolug.org