Folks,
Last week I asked the question quoted below and got two replies. The replies
concerned how to make the find command not return errors, but that is not my
question. The error listed causes the find command to abort instead of just
returning the error and continuing down the directory tree. Thus I don't know
if it didn't return a file because it wasn't there or it aborted before
reaching the file. Is this a bug in Digital UNIX 4.0?
--Harvey
----
Harvey Rarback phone: (312)702-9931
CARS fax: (312)702-5454
University of Chicago Internet: rarback_at_cars3.uchicago.edu
5640 South Ellis Avenue "Make no little plans. They have no magic to
Chicago, IL 60637 stir men's souls."
---------------------------------------------------------------------------
> I am seeing the following behavior of the find command executed as root when
> it tries to read an NFS mounted file to which it does not have read access:
>
> # ls -d /people
> /people
> # find / -name people -print
> # find: bad directory </tmp_mnt/net/cars1/home/claude>
> #
>
> The command seems to abort and I get the prompt back. This behavior does not
> occur when executed from a non-root account or if cars1:/home is exported with
> root access to my machine. I am running DU 4.0
>
> The reference page doesn't indicate that this should be the expected behavior.
> Is it?
Received on Tue Sep 10 1996 - 00:43:09 NZST