Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 (Denver Mods 4/2/84) 6/24/83; site drutx.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxl!ihnp4!drutx!opus
From: opus@drutx.UUCP (ShanklandJA)
Newsgroups: net.bugs,net.unix-wizards
Subject: Re: UNIX error message set wrong on open "file1/file2"
Message-ID: <573@drutx.UUCP>
Date: Fri, 6-Jul-84 18:00:33 EDT
Article-I.D.: drutx.573
Posted: Fri Jul  6 18:00:33 1984
Date-Received: Sat, 7-Jul-84 02:11:58 EDT
References: <4778@utcsrgv.UUCP>
Organization: AT&T Information Systems Laboratories, Denver
Lines: 12
Keywords: perror, ENOENT, EACCES, open


    > Any reason why open("file/file") should return EACCES [rather
    > than ENOENT if the first file exists, but is not a directory]?

Yeah (or at least, sort of).  If the first file didn't have execute
permission set, it wouldn't be "searchable" as a directory.  Granted,
it would probably be clearer if the kernel checked whether 'file1'
was a directory BEFORE checking the permission bits to see if it could
be searched, rather than after; but I'll be willing to bet that's exactly
what's happening.

Jim Shankland
..!ihnp4!druxy!opus