sbradley@mipos3.intel.com (Seth Bradley ~) (02/06/89)
We are using rn patchlevel 39. When one invokes rn from an NFS'ed
home directory, it immediately dies with a "getwd: read error in ..".
Is there any patch to fix this? In case it matters, we are running
ULTRIX 2.3. Thanks in advance!
--
UUCP: {dalek|decwrl|hplabs|oliveb|pur-ee|amdcad}!intelca!mipos3!sbradley
Phone: (408) 765-4147dik@uva.UUCP (Casper H.S. Dik) (02/06/89)
In article <3545@mipos3.intel.com> sbradley@mipos3.UUCP (Seth Bradley ~) writes: > >We are using rn patchlevel 39. When one invokes rn from an NFS'ed >home directory, it immediately dies with a "getwd: read error in ..". >Is there any patch to fix this? In case it matters, we are running >ULTRIX 2.3. Thanks in advance! > This is not a bug in rn.Some programs try to get the current working directory if this fails they exit. Getwd determines the working directory by recursively opening directory .. and find the directory entry corresponding to the current directory. This fails, leaving you in the wrong dir, if you don't have read and execute permission in all directories in the path to the current directory. If those permissions seem ok, check out the mount points. In some versions of *nix there's a bug that preserves the permissions of the mount point when trying to access .. in the root of a mounted filesytem. Example # ls -ld /mnt drwxr-x--x root wheel .... # mount host:/filesys /mnt # su nobody % cd /mnt % /bin/pwd getwd: .. Permission denied. % ls -ld drwxr-xr-x root wheel .... Fix: chmod a+x /mnt (before mounting, needless to say) I was bitten by this one very badly on one of our Sun-3's. It was with an NFS filesystem, but i don't know whether the problem is more common than that. >-- >UUCP: {dalek|decwrl|hplabs|oliveb|pur-ee|amdcad}!intelca!mipos3!sbradley >Phone: (408) 765-4147 --cd ____________________________________________________________________________ Casper H.S. Dik University of Amsterdam | dik@uva.uucp The Netherlands | ...!uunet!mcvax!uva!dik