|Subject:||test "t/perms.t" is invalid; umask test broken w/ACLs|
t/perms.t sets umask to 027 writes a file and checks that file's mode is 0640. This is not guaranteed to be true on file systems with ACL's. It is best illustrated by setting a default ACL on the direct in which you are creating the test file. That sets the ACL on any newly created file. Give 'other' any access other than none (like 'r-x' instead of '---'). Then any file created will give "other" read access for non-executables. The defaults established by the file systems override process defaults like umask. Ishtar:> umask 027 Ishtar:> touch zzz Show quoted text
> ll zzz-rw-rw-r--+ 1 0 Jan 22 21:01 zzz ---why?--- Show quoted text
> lsacl zzz[u::rw-,u:law:rwx,g::rwx,g:lawgroup:rwx,m::rw-,o::r--] zzz (which it inherited from the directory) -- which specifies its own ACL and a default acl for created files.