|
|
On Sat, 09 Sep 2000 05:16:21 -0400, Matt Giwer wrote:
>Francois Dispot wrote:
>>
>> Matt Giwer wrote:
>> >
>> > I'm still learning linux. Its only been a bit over 8 months. Being up
>> > for essentially as long as you want it to be up is a problem in that the
>> > clock drifts. I know ... such problems to have.
>> >
>> > Create a file with this line and put it in your cron.hourly directory
>> > presuming full time network connect. Manual execution as root or
>> > whatever else. Of course make it +xxx.
>> >
>> > rtime -s tock.usno.navy.mil
>> >
>> > It corrects you to US Naval observatory time. It sets to half the
>> > transit time but you might want to pick a time source closer to home.
>>
>> ... or install and configure [x]ntpd.
>
> No man page for either on Redhat 6.2. rtime came with.
It's rdate not rtime. The full man page below:
RDATE(1) Red Hat RDATE(1)
NAME
rdate - get the time via the network
SYNOPSIS
rdate [-p] [-s] [host...]
DESCRIPTION
rdate connects to an RFC 868 time server over a TCP/IP network,
printing
the returned time and/or setting the system clock.
OPTIONS
-p Print the time returned by the remote machine.
-s Set the system time to the returned time.
HISTORY
2000-02-04 Elliot Lee <sop### [at] redhatcom>
Wrote it (previous incarnation had license problems, all
200
lines of it).
Utilities February 2000 1
--
Cheers
Steve email mailto:ste### [at] zeroppsuklinuxnet
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
4:40pm up 18 days, 20:53, 2 users, load average: 1.26, 1.12, 1.04
Post a reply to this message
|
|