Re: Time service for RS/6000

Article View: comp.sys.next.sysadmin

Article #726

Back to comp.sys.next.sysadmin Previous Next

#726

From: Louis A. Mamakos
Date: Thu, 13 Aug 1992 20:08

15 lines
1222 bytes

In article <1992Aug13.153801.27701@almserv.uucp> rmcghee@fnma.com writes:
>Can a NeXT time server service a RS/6000 as a time client?

Assuming that the RS/6000 has an working NTP implementation, then it
can syncronize its clock from a NeXT.  The NTP provided by NeXT
implements version 1 of the Network Time Protocol, so you need to make
sure that if you are using xntp or xntp3 that you specify "version 1"
in the configuration when when you reference the NeXT.

Alternatively, you can install xntp3 on the NeXT which works just
fine.  Currently, xntp3 doesn't look at the time service stuff in
netinfo for configuration; it reads the /etc/ntp.conf file.  This can
be considered a bug or a feature.

louie

Technical Details

Message-ID: <1992Aug13.200833.491@ni.umd.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!darwin.sura.net!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie

References: <1992Aug13.153801.27701@almserv.uucp>

Show Full Headers

Complete Article Headers

Newsgroups: comp.sys.next.sysadmin
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!darwin.sura.net!haven.umd.edu!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Subject: Re: Time service for RS/6000
Message-ID: <1992Aug13.200833.491@ni.umd.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Nntp-Posting-Host: sayshell.umd.edu
Organization: University of Maryland College Park
References: <1992Aug13.153801.27701@almserv.uucp>
Date: Thu, 13 Aug 1992 20:08:33 GMT
Lines: 17

Reply to Parent Message