| commit | ab04a9056788cf77f6b6c72605fc6027f21d9d7c | |
| author | Brandon Casey <drafnel@gmail.com> | |
| Mon, 15 Mar 2010 17:14:34 +0000 (15 12:14 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 17 Mar 2010 02:05:57 +0000 (16 19:05 -0700) | ||
| tree | de03a72d4c1499bfc827f757dce78e9b8bbf3206 | treesnapshot (tar.gz zip) |
| parent | db826571e4099066fe44233d95642591016c831b | commitdiff |
t/t1304: set the Default ACL base entries
According to the Linux setfacl man page, in order for an ACL to be valid,
the following rules must be satisfied:
* Whenever an ACL contains any Default ACL entries, the three Default
ACL base entries (default owner, default group, and default others)
must also exist.
* Whenever a Default ACL contains named user entries or named group
objects, it must also contain a default effective rights mask.
Some implementations of setfacl (Linux) do this automatically when
necessary, some (Solaris) do not. Solaris's setfacl croaks when trying to
create a default user ACL if the above rules are not satisfied. So, create
them before modifying the default user ACL's.
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
According to the Linux setfacl man page, in order for an ACL to be valid,
the following rules must be satisfied:
* Whenever an ACL contains any Default ACL entries, the three Default
ACL base entries (default owner, default group, and default others)
must also exist.
* Whenever a Default ACL contains named user entries or named group
objects, it must also contain a default effective rights mask.
Some implementations of setfacl (Linux) do this automatically when
necessary, some (Solaris) do not. Solaris's setfacl croaks when trying to
create a default user ACL if the above rules are not satisfied. So, create
them before modifying the default user ACL's.
Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t1304-default-acl.sh | diffblobblamehistory |