Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!amdcad!sun!pitstop!sundc!seismo!uunet!hi-csc!giebelhaus
From: giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus)
Newsgroups: comp.sys.apollo
Subject: Re: Problems with NFS & tcp_server
Keywords: mysterious deaths
Message-ID: <39c7b10c.1032a@hi-csc.UUCP>
Date: 20 Jan 88 04:43:00 GMT
References: <280@caldwr.caldwr.gov>
Reply-To: giebelhaus@hi-csc.UUCP (Timothy R. Giebelhaus)
Organization: csdd
Lines: 27

In article <280@caldwr.caldwr.gov> ack@caldwr.caldwr.gov (David Ackerman) writes:
>But all is not wine and roses. Since an initial period with no problems
>after bringing up NFS, we have begun to have problems with our
>tcp server dying.
> [...]
>Why didn't Apollo allow for multiple
>nfsd's the way some other companies (who shall remain nameless) do? It
>would take the load off of the lone nfsd.

I had some TCP problems, but since I installed the patch to TCP 3.0 life
has been wine and roses.  After installing the patch, I run routed with
the -r arguement to tcp_server instead of from a line in my etc.rc file.
I am not running 9.7 yet because I don't have TCP 3.1 yet.  I have not been
running nfsd much either since I have been waiting for the other unix boxes
to standardize on some set of uid's (almost done).  But, maybe news of the
3.0 patch may help anyway.

Apollo does allow for multiple nfsd's.  You can run it on as many nodes
as you like (presuming you have the license to do so).  In the Apollo NFS
manual (the best NFS manual by far which I have seen) it gives several
configuration suggestions including running multiple nfsd's for higher load
networks.
-- 
---------------------------------
UUCP: {uunet, ihnp4!umn-cs}!hi-csc!giebelhaus
ARPA: hi-csc!giebelhaus@umn-cs.arpa
Nobody I know admits to sharing my opinions.  I don't even have a pet.