Thread View: comp.sys.next.sysadmin
1 messages
1 total messages
Started by ns111310
Wed, 23 Dec 1992 22:13
SUMMARY: keeping good time with a remote machine
Author: ns111310
Date: Wed, 23 Dec 1992 22:13
Date: Wed, 23 Dec 1992 22:13
194 lines
7364 bytes
7364 bytes
I received several tips on how to keep my machine at home up to date
with a remote machine, which I assume has the correct time.
Here they are:
-----------------------------------------------------------
(Message inbox:318)
From jeffo@owens.slip.uiuc.edu Tue Dec 22 15:53:05 1992
Return-Path: <jeffo@owens.slip.uiuc.edu>
Received: from garcon.cso.uiuc.edu by longs.lance.colostate.edu
(5.65/lance.1.5)
id AA13068; Tue, 22 Dec 92 15:53:02 -0700
Received: from owens.slip.uiuc.edu by garcon.cso.uiuc.edu with SMTP id
AA16742
(5.67a8+/IDA-1.5 for <ns111310@longs.lance.colostate.edu>); Tue, 22 Dec
1992 1
6:52:57 -0600
Received: by owens.slip.uiuc.edu (NX5.67c/NX3.0S)
id AA01569; Tue, 22 Dec 92 16:52:54 -0600
Date: Tue, 22 Dec 92 16:52:54 -0600
From: J.B. Nicholson-Owens <jeffo@owens.slip.uiuc.edu>
Message-Id: <9212222252.AA01569@owens.slip.uiuc.edu>
Received: by NeXT.Mailer (1.87.1)
Received: by NeXT Mailer (1.87.1)
To: ns111310@longs.lance.colostate.edu
Subject: Re: question about ntp
Reply-To: jeffo@uiuc.edu
You wrote:
> I want to know if there is an easy way to add a line to the crontab
You don't want to do that. Suddenly jerking the clock back to what it
should
be is not a good way to keep other tasks up-to-date of what the correct
time
is. If you use ntp (the one that's already installed), it will keep a
process
running and slowly urge the clock toward the correct time (obtained from
another host).
Consult the ntp-related man page for details, but all you need is the ntp
(probably with ntp host) to be started in your /etc/rc.local (and perhaps
an
entry in NetInfo somewhere using the NetInfoMgr Tool [in the Auto Time
Management area]) and that's it.
--
-- Jeff (jeffo@uiuc.edu)
-- NeXTmail welcome
casco.lance.42 % next
(Message inbox:319)
From stuckey@mrcnext.cso.uiuc.edu Tue Dec 22 17:04:18 1992
Return-Path: <stuckey@mrcnext.cso.uiuc.edu>
Received: from garcon.cso.uiuc.edu by longs.lance.colostate.edu
(5.65/lance.1.5)
id AA13815; Tue, 22 Dec 92 17:04:17 -0700
Received: from mrcnext.cso.uiuc.edu by garcon.cso.uiuc.edu with SMTP id
AA18653
(5.67a8+/IDA-1.5 for <ns111310@longs.lance.colostate.edu>); Tue, 22 Dec
1992 1
8:04:14 -0600
Received: by mrcnext.cso.uiuc.edu (NeXT-1.0 (From Sendmail 5.52)/NeXT-1.0)
id AA02930; Tue, 22 Dec 92 18:03:11 CST
Date: Tue, 22 Dec 92 18:03:11 CST
From: stuckey@mrcnext.cso.uiuc.edu (Anthony J. Stuckey)
Message-Id: <9212230003.AA02930@mrcnext.cso.uiuc.edu>
To: ns111310@longs.lance.colostate.edu
Subject: Re: question about ntp
Newsgroups: comp.sys.next.sysadmin
References: <Dec22.220905.41998@yuma.ACNS.ColoState.EDU>
In comp.sys.next.sysadmin you write:
>I want to know if there is an easy way to add a line to the crontab
>file so that at (say) 2am every night, my machine (at home) slips into
>the local network, and resets the system clock... I want to do
>this because the clock slips badly here (I don't know about other places)
well -- you'll want to rsh across and run a script
or C program, or possibly even the "time" binary itself.
not hard at all. man crontab and off you go.
you could even do it with "at".
--
Anthony J. Stuckey stuckey@mrcnext.cso.uiuc.edu
"And if you frisbee-throw a universe where does it go?"
Turquoise, Steve Blunt.
casco.lance.43 % next
(Message inbox:320)
From sahayman@moose.cs.indiana.edu Tue Dec 22 21:34:15 1992
Return-Path: <sahayman@moose.cs.indiana.edu>
Received: from moose.cs.indiana.edu by longs.lance.colostate.edu
(5.65/lance.1.5
)
id AA15259; Tue, 22 Dec 92 21:34:13 -0700
Message-Id: <9212230434.AA15259@longs.lance.colostate.edu>
Received: by moose.cs.indiana.edu
(5.65c/9.4jsm) id AA08793; Tue, 22 Dec 1992 23:34:11 -0500
Date: Tue, 22 Dec 1992 23:34:11 -0500
From: "Steve Hayman" <sahayman@moose.cs.indiana.edu>
To: ns111310@longs.lance.colostate.edu
Subject: Re: question about ntp
Newsgroups: comp.sys.next.sysadmin
In-Reply-To: <Dec22.220905.41998@yuma.ACNS.ColoState.EDU>
Organization: NeXT Canada
Cc:
You'll find that "rdate" does what you want This simple program
synchronizes
your local clock with a remote machine. This may be easier than getting
the various time daemons going.
Something like this in your crontab should do it
00 0 * * * root /usr/ucb/rdate some-reliable-machine
casco.lance.44 % next
(Message inbox:321)
From thomas@Arnold.fkp.physik.th-darmstadt.de Tue Dec 22 23:47:22 1992
Return-Path: <thomas@Arnold.fkp.physik.th-darmstadt.de>
Received: from rs2.hrz.th-darmstadt.de by longs.lance.colostate.edu
(5.65/lance.
1.5)
id AA16035; Tue, 22 Dec 92 23:47:18 -0700
Received: from Arnold.fkp.physik.th-darmsta
(arnold.fkp.physik.th-darmstadt.de)
by rs2.hrz.th-darmstadt.de with SMTP id AA23866
(5.65c/IDA-1.4.4 for <ns111310@longs.lance.colostate.edu>); Wed, 23 Dec
1992 0
7:47:14 +0100
Received: by Arnold.fkp.physik.th-darmstadt.de (NeXT-1.0 (From Sendmail
5.52)/Cl
ient-1.5/HRZ-THD)
id AA03340; Wed, 23 Dec 92 07:47:13 GMT+0100
Date: Wed, 23 Dec 92 07:47:13 GMT+0100
From: Thomas Traexler <thomas@Arnold.fkp.physik.th-darmstadt.de>
Message-Id: <9212230647.AA03340@Arnold.fkp.physik.th-darmstadt.de>
Received: by NeXT Mailer (1.63)
To: ns111310@longs.lance.colostate.edu
Subject: Re: question about ntp
In comp.sys.next.sysadmin article
<Dec22.220905.41998@yuma.ACNS.ColoState.EDU> you wrote:
> I want to know if there is an easy way to add a line to the crontab
> file so that at (say) 2am every night, my machine (at home) slips
into
> the local network, and resets the system clock... I want to do
> this because the clock slips badly here (I don't know about other
places)
>
>
> thanks,
>
> -nate sammons
> ns111310@longs.lance.colostate.edu
You have to put a line like
/usr/etc/ntp -s -f <hostname> >/dev/null
in /private/adm/daily
--
Thomas Traexler Email:
TH-Darmstadt thomas@arnold.fkp.physik.th-darmstadt.de (NeXTmail)
Institut fuer dd3i@mvs.hrz.th-darmstadt.de (non NeXTmail)
Festkoerperphysik
-----------------------------------------------------
I have tried these:
/usr/etc/ntp -s -f <hostname> >/dev/null
and
/usr/ucb/rdate some-reliable-machine
my /etc/crontab file looks like this:
0 0 * * * root /usr/dialupip/bin/slipup
5 0 * * * root /usr/etc/ntp -s -f 129.82.104.36 > /dev/null
10 0 * * * root /usr/dialupip/bin/slipdown
I have to set up and take down the SLIP connection because I have the
timeout time set to some really large number...
well, there ya go, and thanks for all the help.
-nate sammons
ns111310@longs.lance.colostate.edu
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads