From the following behavior, I don't no if it is a bug, but it seems a little bit strange. I have a text file with the following acl:

# file: Textdatei
# owner: test
# group: users
user::rwx
group::r-x
group:testgroup:-w-
mask::rwx
other::---

The user "timi", who is member of the groups "users" and "testgroup", is able to open and modify this text file. This is the behaviar I expect following the man page "acl" - when a user is not the owner and not a named user, and he is "member" of at least _one_ group class entry (owning group or named group), then his access rights are the union of all group class entries where he is "member" (eventually reduced by the mask). So "timi" gets read access because he is member of "users", the owning group. And he gets write access because he is member of "testgroup".

Now I do the same with a directory instead of a file.

# file: test
# owner: test
# group: users
user::rwx
group::r-x
group:testgroup:-w-
mask::rwx
other::---

But it isn't possible to create or delete files in this directory:

timi@rechner54:/home/test> cp ./Textdatei /home/test/test/thisdoesntwork
cp: no se puede crear el fichero regular «/home/test/test/thisdoesntwork»: Permiso denegado
timi@rechner54:/home/test>

When I change the persmissions to 

# file: test
# owner: test
# group: users
user::rwx
group::rwx
group:testgroup:---
mask::rwx
other::---

then the operation is possible. But when I add then write permission to group:testgroup (so I give _more_ permissions) then access I otherwise denied.

When I have two named groups, it is possible to distribute w and x to these two groups and than it works independently of the state of owning group.


Is this normal, that directories behave different then files?