pwd

[Patrick Place]

[]

/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2
/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir2/dir3

The above was the output of pwd, caused by the following sequence of events.
Note that the above should be all one line.

1) Create directories dir1, dir1/dir2, dir1/dir2/dir3

2) chmod o+r dir1 such that dir1 has permission rwx---r--

3) cd dir1/dir2/dir3

4) su to some id not in the owners group.

5) pwd.

Note that this is not the way I discovered this bug, simply a way
in which it can be demonstrated.  The bug appeared during my normal
use of Unix.

Note that if dir1 had permission rwx------, then pwd produced the
expected "cannot open .." message.

-- 
Patrick Place 		{inset, root44, mcvax, qtlon}!ist!pat
Imperial Software Technology, London England