| Title: | DEC TCP/IP Services for OpenVMS |
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
| Created: | Thu Nov 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5568 |
| Total number of notes: | 21492 |
I have a user with a strange problem. She's mounting a VMS file system
onto a UNIX machine. She can cd to her directory, list and type out
her files, but when she enters the "pwd" command, she gets "permission
denied". She's the owner of the directory and all of her files, and
the VMS file protections are normal.
The VAX is running UCX V4.1, VMS V7.0.
I've got another user who is mounting the same disk from the same UNIX
system, and he's not having the problem. He and the person with the
problem have the same GID. The only difference with their accounts is
that he's using ksh, she's using csh (although I can't see where that
would make a difference).
I searched the file on pwd, didn't come up with anything useful.
Thanks-
Lisa
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5495.1 | ksh works! | TLE::MICHAUD | Lisa Michaud, DTN 381-0879 | Fri May 09 1997 11:21 | 10 |
an update- I had the user switch to ksh, and she could use the pwd
command without a problem!
any idea what's going on here? both ksh and csh ARE in the /etc/shells
file, and she is using them from the directories specified in
/etc/shells.
just curious at this point...
Lisa
| |||||
| 5495.2 | UTRTSC::KNOPPERS | Oswald Knoppers | Mon May 12 1997 02:41 | 3 | |
Has she got a file called 'pwd' in that directory with no 'x' access? Oswald | |||||
| 5495.3 | nope | TLE::MICHAUD | Lisa Michaud, DTN 381-0879 | Tue May 13 1997 14:55 | 4 |
I see what you're thinking, but no, she doesn't have a file called
'pwd' in that directory...
Lisa
| |||||
| 5495.4 | Make that, CSH DOESN'T CACHE IT ... | UCXAXP::GEMIGNANI | Thu May 15 1997 16:35 | 20 | |
It is possible that `pwd' under one shell caches the name of the
directory. I know that csh does it ... it gets the inode number of
the current directory then uses an algorithm to search its way back up
the path by reading the parent directory and matching the inode number
of the member file with its name.
The problem (often) is that the top level directory does not provide
read access (it allows search, but then, if you knew the name you
wouldn't be trying to translate it now, would you?).
Usually, the problem is that the system manager exports the whole disk
to the users and, usually, 000000.DIR is W:E. This leads to the
problem which you described which I detailed above.
To get around it, export the person's actual directory to them. For
example, I would export /userdisk1/gemignani to my workstation, where I
mount it under that name. I always have both read and search access to
my own directory.
Try this; I believe it's what you are looking for.
| |||||