Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!pa.dec.com!jrdzzz.jrd.dec.com!tkou02.enet.dec.com!jit345!diamond
From: diamond@jit345.swstokyo.dec.com (Norman Diamond)
Newsgroups: comp.unix.ultrix
Subject: Re: help needed with UCX
Keywords: UCX,VMS,NFS
Message-ID: <1991Apr19.054759.15885@tkou02.enet.dec.com>
Date: 19 Apr 91 05:47:59 GMT
References: <1991Apr17.210645.480@csc.canterbury.ac.nz>
Sender: usenet@tkou02.enet.dec.com (USENET News System)
Reply-To: diamond@jit345.enet@tkou02.enet.dec.com (Norman Diamond)
Organization: Digital Equipment Corporation Japan , Tokyo
Lines: 21

In article <1991Apr17.210645.480@csc.canterbury.ac.nz> lawrence@isams.dnet.nasa.gov writes:

>Thee error is something like:
>getwd: read error in .. -- can't start new shell

Since no one else has answered this, I will try to give a slight stab
with a very dull knife here.  The NFS system is often configured so
that a root client will have even fewer privileges than an ordinary
(unprivileged) user.  Partly this is to discourage clients from using
root, since they "should" use their actual userid, but it has side
effects.  For example, a root client might fail on a call to getwd()
because it can't follow the directory path back to the top (reading
the .. entry in each directory).

'Fraid I've never used UCX and don't know the correct answer to this
problem.  But if no one else can give an answer, then maybe putting
world read permission on some directories, or use of proxies in a
certain manner, might help.  As I said, just a stab with a dull knife.
--
Norman Diamond       diamond@tkov50.enet.dec.com
If this were the company's opinion, I wouldn't be allowed to post it.