Description of problem:

If getfacl has an error getting acl information for a file, it prints an error
message that does not include the name of the file in question.  This makes the
output useless when multiple input files are selected.


Version-Release number of selected component (if applicable):

acl-2.2.3-1

How reproducible:

always

Steps to Reproduce:
1. create an empty directory
2. touch 1 3
3. getfacl 1 2 3 4
    
Actual results:

# file: 1
# owner: ejb
# group: ejb
user::rw-
group::rw-
other::r--

getfacl: No such file or directory
# file: 3
# owner: ejb
# group: ejb
user::rw-
group::rw-
other::r--

getfacl: No such file or directory


Expected results:

# file: 1
# owner: ejb
# group: ejb
user::rw-
group::rw-
other::r--

getfacl: 2: No such file or directory
# file: 3
# owner: ejb
# group: ejb
user::rw-
group::rw-
other::r--

getfacl: 4: No such file or directory


Additional info:

This is pretty serious.  If you use getfacl to dump acl information to a file
for all files in a directory and there are some dangling links (common for lock
files) or files for which you don't have permission to stat, getfacl will spit
out a bunch of error messages to stderr each without indicating which file has
the problem.  This makes diagnosis difficult.  This is a trivial fix.  I'm not
sure I found all the cases of where this type of lazy error message is issued,
but the one responsible for this error and an equivalent problem set setfacl are
fixed by the patch I've attached.