find command aborts when it shouldn't?

From: Harvey Rarback 312-702-9931 <RARBACK_at_cars3.uchicago.edu>
Date: Thu, 5 Sep 1996 15:33:29 -0500 (CDT)

    Folks,

I am a newbie Digital UNIX person, so please be gentle ;-)

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?
                                   --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."
Received on Thu Sep 05 1996 - 22:56:05 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:47 NZDT