Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rice!sun-spots-request
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.sys.sun
Subject: Re: getwd() problems
Keywords: Networks
Message-ID: <4558@brazos.Rice.edu>
Date: 29 Jan 90 01:32:12 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 33
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n6
X-Sun-Spots-Digest: Volume 9, Issue 19, message 4 of 14

In article <4251@brazos.Rice.edu> ktibv!ml@relay.eu.net (Marinko Laban) writes:
>X-Sun-Spots-Digest: Volume 9, Issue 6, message 5 of 9
>
>We have two Sun's 4/110 (SunOS 4.0), both with a 325 Mb disk.  The two
>Sun's are called process1 and process2. 
>
> [stuff deleted]
>
>So you see that we have cross-mounted the file-systems of both
>computers. Now something weird happens ...
>
>Suppose a user logs in into process1, and goes to the directory
>/usr/kti/proj2. Note that this is physically a directory of process2. When
>he tries to do a 'pwd' he gets the message "pwd: getwd: can't open .."
>
>When the user logs in into process2, and does the same, no problem ...
>When the user logs in on process2 and goes to /usr/kti/proj1, still no
>problem...

I have seen the same type of thing. The problem was with the mount point
itself for the NFS file system.  Try this, unmount the filesystem in
question, NOW check the permissions and make sure they are what you want
(Owner, mode, group), then re-mount it.

When a filesystem is NFS mounted, the permissions of the mount point
should be completely overridden by the permissions of the mounted file
system. This does not appear to be the case.

Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110
(408)437-5254