Re^8: perl file status and sudo

[Anonymous Monk]

I think he means situations where he is denied read access to a directory:

$ echo $EUID
1000

$ ls -ld /var/log/apache2
drwxr-x--- 2 root adm 12288 Mar 18 06:25 /var/log/apache2
$ ls -l /var/log/apache2
ls: cannot open directory /var/log/apache2: Permission denied
$ perl -E 'say ((-e q-/var/log/apache2/access.log-) ? "exists" : "not 
+exists: $!")'
not exists: Permission denied

# echo $EUID
0
# perl -E 'say ((-e q-/var/log/apache2/access.log-) ? "exists" : "not 
+exists: $!")'
exists

He probably just should examine $!

[JavaFan]

I cannot think of a situation where you have "read access to anything", but don't have read access to a directory. Anyway, if he needs read access to a directory, ACLs can be used. As I pointed out in my first reply.

[aaron_baugher]

Viewing a directory listing requires read permission on the directory, but entering the directory and viewing the files inside it requires execute permission on the directory. He could be talking about something like that, where he has read permission for everything but can't see some files because he doesn't have execute permission on all directories. That's not real security, and it wouldn't make a lot of sense, but not much about this situation seems to.

[JavaFan]

Let's not try to guess what might be the case. Let's see whether the OP can describe what his actual problem, in a what that he can be helped. (But, if it is the case you're describing, it's again ACLs that will come to the rescue).