HDTenEightyP/NetNews huggingface dataset:
From: geoff@tyger.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: Open a fixed securety-hole
Date: 28 Jan 1993 14:20:30 GMT
Organization: SunSelect
Distribution: world
Reply-To: geoff@tyger.East.Sun.COM
NNTP-Posting-Host: tyger.east.sun.com

In article 93Jan28124128@haegar2.uni-paderborn.de, kaz@uni-paderborn.de (Kay Mueller) writes:
##Hi out there,
##
##We are running the rpc.pcnfsd on a server with a restricted passwd.
##(only those users who are in /etc/netgroup on our nisserver are allowed to
##log in)
##The old deamon (PCNFS 3.5) did not care aboutthis, and every user could do
##his net name *
##But the new pcnfsd (pcnfsd.92.11.05) checks the local /etc/passwd and returns an
##"Authentication Failiure" to everyone not mentioned in /etc/netgroup.
##
##How can I open this securety hole?

pcnfsd doesn't check /etc/netgroup for anything. It calls getpwnam()
to find the passwd record for the user, but then it alsways has done.
The only new thing in the 92.11.05 daemon which might affect you is
the check for the presence of a valid user shell in the passwd record.
pcnfsd will use setusershell()/getusershell()/endusershell() if configured
to do so; otherwise it insists that the last two characters are "sh".
(A null shell field - equivalent to /bin/sh - is acceptable.)

If you are enforcing restricted logins via a custom shell, and you have 
defined USE_GETUSERSHELL, you will have to make sure that your custom
shell is included in /etc/shells. (See "man getusershell" for details.)
Otherwise, you can hack the code in pcnfsd_misc.c to cope with
your special setup.

---
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
--------------------------------------------------+-------------------
"What if they made the whole thing up?            | "The Great Lie" by
 Four guys, two thousand years ago, over wine..." |    The Tear Garden
From: mcollins@db (Marty Collins)
Newsgroups: comp.protocols.nfs
Subject: Re: TCP/IP, UDP, ICMP
Date: 21 Jan 93 18:55:27 GMT
Organization: Novell, Inc.
X-Newsreader: Tin 1.1 PL4

mxa11@po.CWRU.Edu (Madhavi Ahuja) writes:
: 
: Hi netters
: I am trying to understand computer protocols, the difference
: between the existing ones and so on... Could some one
: recommend any books/articles that mifght be able  to 
: explain all the above in plain terms (for a novice )
: Help and time greatly appreciated
: Thanks
: Madhavi
: (ma@acqdev.eeg.ccf.org)

For the TCPIP suite the best books I have come across are from Douglas Comer.
He has three volumes out, with help from others, that explain in great
detail the TCPIP suite of Protocols. Start with Volume one, Internetworking
with TCP/IP. 


--
	   A woman needs a man like a fish needs a bicycle.

   Marty Collins	       				U2 
   Product Support                                      Tryin to throw your
   NOVELL, INC.  San Jose, CA.				arms around the world.
   mcollins@novell.com   or
   Marty_Collins@SJF.Novell.COM
   1-800-NETWARE  
Newsgroups: comp.protocols.nfs
From: sjc@athena.mit.edu (Steven J Cariglia)
Subject: restarting rpc.statd
Organization: Massachusetts Institute of Technology
Date: Wed, 27 Jan 1993 19:07:33 GMT

What dangers (if any) are there in killing+restarting rpc.statd?

i.e. dangers to other processes on the same machine and/or local network
     and/or dangers to files/filesystems?

Thanks.
Xref: sparky comp.protocols.nfs:3214 comp.dcom.isdn:1235
From: johng@informix.com (John Galloway)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: Low cost ether/isdn brouters
Date: 26 Jan 93 01:17:30 GMT
Distribution: na
Organization: Galloway Research

In article <1993Jan25.142206.17177@gandalf.ca> dcarr@gandalf.ca (Dave Carr) writes:
>In <1993Jan22.002029.27149@informix.com> johng@informix.com (John Galloway) writes:
>
>Do you want the B-channels up permanently?  You probably want dial on
>demand, with some intelligence at both ends to establish the link only
>when required.  Given the choice between a standard bridge or router,
>the router wins.  But is a full router necessary in this case?
Likely 1 B channel up all the time with the other being added on demand.
The only way ISDN is affordable is via centrex, and intra-centrex calls
are fee so why not leave it up?
>
>I would argue that very little router code needs to be added to the 
>bridge to gain this functionality.  By adding static routing to our bridge
>I believe we have met your needs.
Agreed.  Just simple IP routing (as mentioned in a pervious post) would
be fine.  SNMP is nice, but cost is the dirving factor here so if not
having a full tcp/ip stack is easier/less-expensive, then it would be fine.
>
>Bonding makes one 128K channel by interleaving at the data stream bit level.
>It is necessary to account for the different delays between  the B channels.
>The alternative is to run LAPB multilink protocol.  But you are right.
>There is no standard yet on multilink. 
>
>With bonding you only have one channel.  With some software running on top
>of multilink, you can split the packet in pieces and load balance. 
>Fragmentation in this case is not done like a router, but similar to the
>more bit in X.25.

These two topcis are also realated.  If running completely seperate
B channels, then a user could leave one up all the time (and have a single
B chanles worth of resource on the host end dedicated to this user) but
only add the second on demand and thus have something like 1.25 B channels
for each user at the hub, and give 2 64K channels to most folks when
the need arises, but not have to have 2B channels dedicated to each user.
Digiboard claims they can do this with their IMAC with each B channel going
to a different user.  However this scheme would not allow the 2Bs to be bonded.
In part this comes down to the question: do apps like ftp want an
ack after every packet and hence not be able to make use of 2 64K channels
as opposed to one 128K channel?
	-jrg
-- 
internet    jrg@galloway.sj.ca.us  John R. Galloway, Jr  795 Beaver Creek Way
internet    johng@informix.com     CEO...receptionist    San Jose, CA   95133
applelink   D3413                  Galloway Research     (408) 259-2490
From: geoff@tyger.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS via TCP services
Date: 26 Jan 1993 01:03:02 GMT
Organization: SunSelect
Distribution: world
Reply-To: geoff@tyger.East.Sun.COM
NNTP-Posting-Host: tyger.east.sun.com

In article 930125171404@cream.ftp.com, jbvb@vax.ftp.com (James B. VanBokkelen) writes:
##In article <23JAN199311452594@uc780.umd.edu> cm305b@uc780.umd.edu (CMIS 305 SECTION 5011) writes:
##
##    I am interested in any work that is being done to have NFS use TCP
##    services.
##
##It isn't really at the level of papers anymore.  We've been shipping TCP
##client capability with our OS/2 product for almost a year, and we're adding
##it to our DOS product before the end of this quarter.  Sun's promised it
##for some version of Solaris (not 2.1, I think).  TGV and Process Software
##have it in their VMS TCP/IP packages.  Intercon demoed it for the Mac
##in 1991, I don't know if it is productized yet.

Plus it's available in BSD/386 and (I presume) 386bsd.

---
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)

Newsgroups: comp.protocols.nfs,comp.dcom.isdn
From: zbig@wariat.org (Zbigniew J. Tyrlik)
Subject: Re: Low cost ether/isdn brouters (was PC-NFS PPP Serial/ISDN driver wanted)
Followup-To: comp.protocols.nfs
Reply-To: zbig@wariat.org (Zbigniew J. Tyrlik)
Organization: Akademia Pana Kleksa, Public Access Uni* Site
Date: Fri, 22 Jan 1993 18:29:42 GMT

As quoted from <1jnj4tINN1io@nigel.msen.com> by emv@msen.com (Edward Vielmetti):

+---------------
> Talk to Sun or HP or NeXT or SGI (?) and build a box that will run as
> a hub for the ISDN they are building onto their motherboards.  Talk to
> Morning Star or their customers about what people are doing with PPP.
> Pick up some clues as to what is actually out there in the field today
> delivering Internet connections to people and build some gear that slides
> in nicely...aim at the equipment that's going to squash V.fast before it
> appears - 2B + NT1 in a single box, RS-232 or V.35, AT or V.25bis dialing,
> ship it list $999 day 1 quantity 1. - get there before someone like Adtran
> does...

I would love to have such a box, where I can feed it either from
Ethernet, and have it talk PPP/C|SL/IP to my internet provider. 

And I need 56/64 bandwidth to get some more breathing space. Going
with leased 56k line, and all addtional hardware is not my may of
spending money. but if I have to invest more that grand in such
gear, I will rather rig nice KA9Q and will run it as router, pop
server, etc...  



> 
>   Edward Vielmetti, vice president for research, Msen Inc. emv@Msen.com
>         Msen Inc., 628 Brooks, Ann Arbor MI  48103 +1 313 998 GLOB
> 

_zjt
-- 
********************************************************************
Zbigniew J. Tyrlik       DoD# 0759   VF700C '84      zbig@wariat.org
IBM PC SIG Sysop - Cleveland Free-Net    aa609@cleveland.freenet.edu
APK	       Public Access UNI* Cleveland,          (216)-481-9436
Feeds, shell, FTP & telnet access        Uniboard distribution point 
********************************************************************
Newsgroups: comp.protocols.nfs
From: ricardo@ing.puc.cl (Ricardo Schmutzer von Oldershausen)
Subject: Re: PC-NFS with ULTRIX in ENHANCED security mode
Organization: Universidad Catolica de Chile
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 27 Jan 1993 21:34:22 GMT

Ralf Hirning (ralf@wilma.physik.uni-stuttgart.de) wrote:
: The ncnfsd - daemon compares the given password with the entry in
: /etc/passwd, but in enhanced security mode the is only a '*' there.

: Is there a patch for pcnfsd to run properly with ULTRIX?
The pcnfsd.c source of SUN has a #define to enable the use of shadow
password files.  The source should be with your PC-NFS distribution
disks.  But I do not know if it works under Ultrix.

Ricardo.
--
+-----------------------+--------------------------------+--------------+
| Ricardo A. Schmutzer | Internet: ricardo@ing.puc.cl    | Conectividad |
| PUC, Santiago, Chile |           ricardo@lascar.puc.cl | Distr. Comp. |
+----------------------+---------------------------------+--------------+
Newsgroups: comp.protocols.nfs,bit.listserv.vm-util,bit.listserv.ibm-main
From: westes@netcom.com (Will Estes)
Subject: NFS Client for VM/CMS going to UNIX server?
Organization: Mail Group
Date: Thu, 28 Jan 1993 09:38:03 GMT

I need help understanding to what extent I can map a UNIX file
system to a VM/CMS system using NFS.

I have an application where I need to map the UNIX news hierarchy,
starting at /usr/spool/news, to a VM/CMS minidisk.  The problem is
that VM/CMS has a flat file system that doesn't understand
subdirectories.

Two questions:  1) does the standard IBM TCP product for VM include
an NFS client?  2) can anyone think of an effective workaround for
the problem I am describing?  I suppose we could read in the news
system's active file, and then proceed to mount each news
subdirectory sequentially for processing.  Since there are hundreds
of subdirectories involved, it seems like this would be a slow
process.  Are there other concerns with this approach, or are there
better solutions?
 
-- 
Will Estes		Internet: westes@netcom.com
Xref: sparky comp.protocols.nfs:3169 comp.dcom.isdn:1188
From: marc@aria.Ascend.COM (Marco S Hyman)
Newsgroups: comp.protocols.nfs,comp.dcom.isdn
Subject: Re: Low cost ether/isdn brouters
Date: 26 Jan 93 16:15:17 GMT
Followup-To: comp.dcom.isdn
Distribution: na
Organization: Ascend Communications, Alameda, CA

Note: nothing to do with comp.protocols.nfs -- followup-to comp.dcom.isdn.

In article <1993Jan26.011730.185@informix.com> johng@informix.com (John Galloway) writes:
 > These two topcis are also realated.  If running completely seperate
 > B channels, then a user could leave one up all the time (and have a single
 > B chanles worth of resource on the host end dedicated to this user) but
 > only add the second on demand and thus have something like 1.25 B channels
 > for each user at the hub, and give 2 64K channels to most folks when
 > the need arises, but not have to have 2B channels dedicated to each user.

This can also be done using an Inverse Mux as the interface between your
router and wide area network.  Ours, for example, has a mode where a minimum
bandwidth, maximim bandwidth, increment amount, and decrement amount are are
specified.  The box looks at the ratio between flags/non-flags (or
mark/non-mark) to determine link utilization.  When the utilizaztion goes
above a target bandwidth is added, when below the target bandwidth is
reduced.  Experience shows its best to add channels in big chunks (4-6 at a
time) and remove them in little chunks (1-2 at a time).

The solution is a expensive (need router + IMUX), but available off the
shelf today.

// marc
-- 
// work: marc@ascend.com          uunet!aria!marc
// home: marc@dumbcat.sf.ca.us    pacbell!dumbcat!marc
From: bigenwal@sun-valley.amcc.rochester.edu (Chris J. Bigenwald)
Newsgroups: comp.protocols.nfs
Subject: Why should I worry about RTM.EXE
Date: 28 Jan 93 20:31:15 GMT
Organization: University of Rochester (Rochester, NY)

Sorry about my previously poor post....  My question is why should I be worried (or not worried) about loading RTM.EXE before running Windows?  This little network that I am watching seems to be running OK without it.

- Chris
Newsgroups: comp.protocols.nfs
From: fr@eagle.mumath (Farid Rahmi)
Subject: Re : Beeing nobody sometimes
Reply-To: fr@eagle.mumath
Organization: BIM sa nv
Date: Wed, 27 Jan 93 17:35:41 GMT


Jorn,


>when looking at the user information in the "network" part of the control
>panel the user name will be "nobody", the domain will be nothing (not
>"none" but plainly no entry, and UID and GID will be -1! (should be -2
>or shouldn't it?). The error occurs intermittently, sometimes 4 times a day.
>There is no known way to provoke it. Some PCs has never failed.

Looks like something (PC appl?) is wildly poking in your memory here, corrupting
UID and GID data,NIS domain name,etc... or are you using emm386 with the WD cards 
and have you forgotten to use the -x switch or something ?

Farid.
From: eichin@athena.mit.edu (Mark Eichin)
Newsgroups: comp.protocols.time.ntp
Subject: Re: Solaris 2.1
Date: 28 Jan 1993 00:44:48 GMT
Organization: Massachusetts Institute of Technology
Distribution: inet
NNTP-Posting-Host: tweedledumb.cygnus.com
In-reply-to: jones@HERMES.CHPC.UTEXAS.EDU's message of 27 Jan 93 02:14:53 GMT

>> I don't know what to use for tick.  Does anyone have any ideas.
	usec_per_tick, I think... it works for me, anyhow.
>> I am fairly close to having a working version of xntpd for Solaris 2.1.
	I got one to run -- but it wouldn't talk to anything! I could
query it with ntpq or xntpdc from the local host, but it wouldn't talk
to any other server on my local net, even though it resolved the
addresses. (This is under Solaris 2.0; I'll have 2.1 before the week
is out, and see if that makes a difference.)
>> Would anyone like to try it out before I send Mills the patches?
	If you get it to actually talk to something else, I'd like to
try it. 
					_Mark_ <eichin@cygnus.com>
					Cygnus Support
From: ajudge@maths.tcd.ie (Alan Judge)
Newsgroups: comp.protocols.time.ntp
Subject: Re: XNTP3/MIPS RISCos 5.01 solved (ish)
Date: 25 Jan 93 11:54:31 GMT
Distribution: inet
Organization: The Internet


Lars> from your log it looks like the system time jumped one second backward
Lars> in the minute after 05:56:26. Perhaps the SETTIMEOFDAY_DAMAGED patch
Lars> does not always guess correctly to which side RISC/os 5 is going to
Lars> jump?
The SETTIME code only gets called if we are stepping, so I don't see
how it could cause the problem.  In any case, it actually uses
gettimeofday to see where we actually stepped to, so I don't think it
could "guess" incorrectly.
--
Alan
From: pml@marsh.cacs.usl.edu (Patrick M. Landry)
Newsgroups: comp.protocols.time.ntp
Subject: Terminology question from a layman
Date: 26 Jan 93 16:53:30 GMT
Article-I.D.: usl.1993Jan26.165330.14136
Distribution: usa
Organization: The Center for Advanced Computer Studies

Can someone tell me (a layman) what the terms "delay" "offset" and "disp"
mean in and XNTP context. A pointer into the appropriate docs would be 
fine. Just a general idea so I can tell if my clock is behaving.
--
patrick
Newsgroups: comp.protocols.time.ntp
From: A9000005@tscc.macarthur.uws.edu.au
Subject: ntp 3.4-AIX 3.1, SunOS 4.1.2-xntpd and timezones?
Organization: University of Western Sydney, Macarthur
Date: Thu, 28 Jan 1993 13:52:37 GMT

Hi,
  I have just installed ntp 3.4 on a RS6000 with AIX 3.1.5.  This is just
to keep my own time, I am not serving to anyone.  I have setup my ntp.conf
with 2 "server" lines: one local and one on another campus.  Both are
running xntpd (not sure of the version) on SunOS 4.1.2.
 
I start ntpd and watch the log, all works fine.  There is one problem though:
the time on my RS6000 is 1 hour behind that of the Sun's.  Here is the
output of the "date" command on the RS6000:
 
Thu Jan 28 07:59:04 EET 1993
 
Here is the output of "date" on the local Sun:
 
Thu Jan 28 08:59:04 EST 1993
 
I am in a daylight saving zone.  If I use "setclock" to get the time from
the Sun, it also gives me the wrong time. (Same as ntpd)  "Setclock" worked
fine before daylight saving started!
 
Any suggestions as to who has the timezone problem?  Me?  The Sun? Both?
 
Thanks,
 
---
  Brian Watson
  Programmer, Computing Centre
  University of Western Sydney, Macarthur
  Internet: b.watson@uws.edu.au
Newsgroups: comp.protocols.time.ntp
From: dor@acl.lanl.gov (David O. Rich)
Subject: xntp v3: Previous time adjustment didn't complete
Reply-To: dor@acl.lanl.gov
Organization: Advanced Computing Lab, LANL, NM
Distribution: comp
Date: Sat, 23 Jan 1993 00:46:11 GMT

After grabbing, building and installing the latest version of XNTP
(Version 3), I've noticed that my Sun SPARC machines regularly emit
the following warning/message.

Jan 22 16:25:00 koala xntpd[27079]: Previous time adjustment didn't complete

By regularly I'm talking every couple of minutes or so.  Can someone
tell me what this means and what I might to do fix the problem?

Thanks!
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.time.ntp
Subject: Re:  XNTP3/MIPS RISCos 5.01 solved (ish)
Date: 23 Jan 93 17:45:15 GMT
Distribution: inet
Organization: The Internet

Alan,

Would you like to update the xntp3 distribution with either/both README
and patches? If so, please send to me and I will energize files.

Dave
From: km@mathcs.emory.edu (Ken Mandelberg)
Newsgroups: comp.protocols.time.ntp
Subject: XNTP on Solaris 2?
Date: 24 Jan 1993 18:19:59 GMT
Organization: Emory University, Dept of Math and CS
Distribution: world
Reply-To: km@mathcs.emory.edu
NNTP-Posting-Host: km-sl.cc.emory.edu

Has anyone gotten xntp3 to run on Solaris 2.1? 


---
Ken Mandelberg      | km@mathcs.emory.edu          PREFERRED
Emory University    | {rutgers,gatech}!emory!km    UUCP 
Dept of Math and CS | km@emory.bitnet              NON-DOMAIN BITNET  
Atlanta, GA 30322   | Phone: Voice (404) 727-7963, FAX 727-5611
Newsgroups: comp.protocols.time.ntp
Subject: Service in UK
From: whiskerp@logica.co.uk (Peter Whisker)
Date: Mon, 25 Jan 1993 12:18:57 GMT
Organization: Logica DCG Ltd., Cobham, Surrey, UK

I looked at a copy of the December 1992 clock.txt.

It seems that the UK has no NTP servers - the nearest (and the only GMT/BST 
time zone one) is Trinity College Dublin.

Is this true ? I don't mind using TCD as I studied Engineering there but it 
does seem odd that there are none listed for the UK.

Peter Whisker
_______________________________________
Peter Whisker   (whiskerp@logica.co.uk)
Logica DCG Ltd.
Cobham, Surrey KT11 1HY, UK
Newsgroups: comp.protocols.time.ntp
From: fsset@bach.lerc.nasa.gov (Scott Townsend)
Subject: Total novice question regarding xntpd & RS6000's
Organization: NASA Lewis Research Center [Cleveland, Ohio]
Distribution: na
Date: Wed, 27 Jan 1993 19:23:25 GMT

I'm a new, non-administartor type user of AIX & xntpd on a cluster of 32
RS6000's.  This system is used for lots of compute-bound things, some running
in parallel over Ethernet.

Anyway, the nodes don't seem to be keeping very good time:

	lace01 13:58:18
	lace02 13:58:21 +3
	lace03 13:58:20 -1
	lace04 13:58:21 +1
	lace05 13:58:23 +2
	lace06 13:58:24	+1
	lace07 13:58:35 +11
	lace08 13:58:26 -9
	lace09 13:58:29 +3
	lace10 13:58:28 -1
	lace11 13:58:29 +1
	lace12 13:58:32 +3
	lace13 13:58:37 +5
	lace14 13:58:31 -6
	lace15 13:58:34 +3
	lace16 13:58:34
	lace17 13:58:35 +1
	lace18 13:58:32 -3
	lace19 13:58:39 +7
	lace20 13:58:39
	lace21 13:58:41 +2
	lace22 13:58:39 -2
	lace23 13:58:42 +3
	lace24 13:58:40 -2
	lace25 13:58:46 +6
	lace26 13:58:47 +1
	lace27 13:58:43 -4
	lace28 13:58:46 +3
	lace29 13:58:44 -2
	lace30 13:58:47 +3
	lace31 13:58:53 +6
	lace32 13:58:47 -6

The above output is from a trivial rsh script run from lace07, the elapsed time
was 29 seconds.

My question is, are the above time descrepancies reasonable?  For instance,
there's a 9 second reverse jump between lace08 and lace07.  From listening
to this group for a little while it sounds like things should be better.
On the other hand, with bursty network traffic and often compute-bound CPUs
I could imagine xntpd going a bit 'unstable' attempting to track the clock
drifts while seeing varying network delays.

I'd appreciate any comments you may have.  I`m not an administrator for this
system but if the net wisdom can suggest some things to try, either I can
try it or if I don't have the required permissions I think I can find someone
who does.



-- 
Scott Townsend,  Sverdrup Technology Inc.  NASA Lewis Research Center Group
fsset@bach.lerc.nasa.gov
From: ajudge@maths.tcd.ie (Alan Judge)
Newsgroups: comp.protocols.time.ntp
Subject: XNTP3/MIPS RISCos 5.01 solved (ish)
Date: 21 Jan 93 12:24:06 GMT
Distribution: inet
Organization: The Internet

Thanks to several net people, I have now sorted out my problem with
NTP on a MIPS Magnum 4000 with RISC/os 5.01.  (At least, I think so.)

Philip Gladstone provided a patch (SETTIMEOFDAY_DAMAGED) which worked
around the problem where settimeofday ignores the sub-second part.

However, the primary problem turned out to be the MIPS kernel.  All
MIPS workstations have time of day chips, and it seems that the kernel
intermittently checks this clock and adjusts the CPU clock accordingly
(both by using an internal adjtime(), and by changing the basic speed
of the CPU clock causing the "Adjust CLOCK Hz" messages in syslog).
Obviously, this has bad interactions with the correct operation of
NTP, which is doing something similar based on NTP clocks outside.
Each time the kernel does this, NTP has a fit.

It seems from the code that this has always been done, even on R3000
machines and in RISCos 4.51, so NTP has always been a bit funny
(despite us running it for more than a year).  On the R4000, however,
the CPU clock (and maybe the TOD clock) is much further out to start
with and this explains the problems that I had getting NTP to
stabilise.

There is no MIPS-provided way to turn this off (like Sun's
dosynctodr).  However, MIPS do provide source code for all their
drivers with RISCos, so it is a fairly simple patch on most MIPS boxes
to turn this off.  They inadvertently omitted the R4000 TODC source
though, so I had to patch the binary.

I have put in a request for an easier way to disable the clock syncing.


A WARNING: at least on the R4000, the basic CPU clock speed is WAY
out, drifting over a second a minute unless you change the tick rate.
I am have now been running ntp3 for a few days with the tick set to
9808 (is this a record?), and have a freq of around 100ppm, so maybe
9809 would be better.  I'm hoping that the CPU clock is at least
stable even if it is way off, but I won't know for a few weeks and
reboots.

I haven't upgraded the R3000 boxes yet, so I don't know how bad they
are.  So, be careful if you switch off the clock syncing.
--
Alan
Newsgroups: comp.protocols.time.ntp