home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!noiro.acs.uci.edu!714-725-3165.nts.uci.edu!cedman
- From: cedman@714-725-3165.nts.uci.edu (Carl Edman)
- Subject: Re: WANTED: clock setting software
- Nntp-Posting-Host: 714-725-3165.nts.uci.edu
- Message-ID: <2A6E24B1.18674@noiro.acs.uci.edu>
- Newsgroups: comp.sys.next.software
- Reply-To: Carl Edman <cedman@golem.ps.uci.edu>
- Organization: University of California, Irvine
- Lines: 27
- Date: 23 Jul 92 03:17:05 GMT
- References: <1992Jul16.173835.4248@fnbc.com> <Brpns5.7w@sounds.wa.com>
-
- In article <Brpns5.7w@sounds.wa.com> BrianW@SoundS.WA.com writes:
- >I would appreciate it if someone could send me a few pointers concerning setup
- >of NTP on the NeXT (I"m running System 2.2 on an isolated NeXTdimension with
- >SLIP and UUCP, but no ethernet connections).
- >
- >I have read the Man pages for ntp ntpd and ntpdc, but there is nothing in
- >NeXTadmin or NeXTanswers/92_spring about setting up NTP.
-
- Your problem is not NTP, but the interaction between NTP and SLIP and
- the lack of an ethernet. Early during the boot process the variable
- NETWORKUP is set according to whether there is an ethernet connection
- or not. Later on many network daemons are only started if NETWORKUP is
- set to -YES-. Among these network daemons is ntpd. You can either
- throw out that check in /etc/rc, or you can modify your SLIP startup
- script to set NETWORKUP to -YES- when the SLIP connection is
- established. That will also help other parts of the automatic system
- configuration, but remember to startup up SLIP early during the boot
- process to make certain that it is configured before the network
- daemons are started.
-
- >Is the solution as simple as adding a crontab.local entry for "/usr/etc/ntp -s
- >clock" as user root? If so, then why is there a need for the ntpd daemon? I
- >was able to run "/usr/etc/ntp clock" before the ntpd process was started.
-
- Not a good idea.
-
- Carl Edman
-