Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!mimsy!prometheus!media!rmf
From: rmf@media.uucp (Roger Fujii)
Newsgroups: comp.sys.apollo
Subject: Re: NFS mount problem between Next <-> APOLLO
Message-ID: <1991Apr10.135826.26648@media.uucp>
Date: 10 Apr 91 13:58:26 GMT
References: <1991Apr9.015148.17946@leland.Stanford.EDU> <1991Apr9.072112.15858@alphalpha.com>
Organization: Media Cybernetics, Inc.
Lines: 27

nazgul@alphalpha.com (Kee Hinckley) writes:

>In article <1991Apr9.015148.17946@leland.Stanford.EDU> tonytran@portia.Stanford.EDU (Tony) writes:
>>I mounted a remote Apollo file system successfully, but I am only
>>able to access the Apollo if I were the root on the Next.

>Interesting.  I have a similar problem from a Sun to the Apollo.  I can access it, but
>df only works if I'm root.  I mounted //.  Anyone have any ideas?

Check to see what that port numbers are when you do an /etc/rpcinfo.
My recollection was that when one of the hosts allocated a port < 1024,
for a nfs daemon, the apollo would fail because its nfs daemon was
schitzoid (ran as the current user using it) and lost permission to
the connecting port (<1024 are priveliged ports).


>I've also seen other things.  The Sun hangs (^C breaks out of it) trying to
>run binaries stashed on the Apollo - or reading and writing large files. 
>The error on the Apollo was something to the affect that a value was
>non-numeric.

I seen this too.  The apollo must be screwing up the SunOS's shared text 
mechanism over nfs.  I wish apollo would implement the newer NFS protocol -
it would get rid of some of these headaches.
-- 
Roger Fujii - Media Cybernetics		Phone: (301)495-3305
Internet: rmf%media@uunet.uu.net 	UUCP: {uunet,hqda-ai}!media!rmf