1LFC‐GETACL(1)                        LFC       User      Commands
2LFC‐GETACL(1)
3
4
5
6[1mNAME[0m
7       lfc‐getacl ‐ get LFC directory/file access control lists
8
9[1mSYNOPSIS[0m
10       [1mlfc‐getacl [22m[[1m‐a[22m] [[1m‐d[22m] [4mpath[24m...
11
12[1mDESCRIPTION[0m
13       [1mlfc‐getacl  [22mgets  the  Access Control List  associ‐
14ated with a LFC direc‐
15       tory/file.  For each [4mpath[24m, it   displays  the  file
16name,  owner,  the
17       group, and the Access Control List (ACL) if present. If  a
18directory has
19       a default ACL, [1mlfc‐getacl [22malso displays the default
20ACL. Regular  files
21       cannot have default ACLs.
22
23       The output looks like:
24
25            # file: filename
26            # owner: username
27            # group: groupname
28            user::perm
29            user:uid:perm
30            group::perm
31            group:gid:perm
32            mask:perm
33            other:perm
34            default:user::perm
35            default:user:uid:perm
36            default:group::perm
37            default:group:gid:perm
38            default:mask:perm
39            default:other:perm
40
41       The  first  "user"  entry gives the permissions granted to
42the owner of
43       the  file.   The following "user" entries show the permis‐
44sions granted to
45       specific  users,  they are sorted in  ascending  order  of
46uid.  The first
47       "group"  entry  gives the permissions granted to the group
48owner  of  the
49       file.   The  following  "group" entries show  the  permis‐
50sions granted to
51       specific  groups,  they  are  sorted in ascending order of
52gid.  The "mask"
53       entry  is  the  maximum  permission  granted  to  specific
54users or groups.
55       It  does not affect the "owner" and  "other"  permissions.
56The  "mask"
57       entry  must be present if there  are  specific  "user"  or
58"group" entries.
59       "default" entries associated with a directory are inherit‐
60ed  as  access
61       ACL  by  the  files  or  sub‐directories created  in  that
62directory. The
63       [1mumask  [22mis  not  used.  Sub‐directories also inherit
64the  default  ACL  as
65       default  ACL.  As soon as there is one default ACL  entry,
66the 3 default
67       ACL  base  entries  (default  user, default group, default
68other)  must  be
69       present.
70
71       The entry processing conforms to the Posix  1003.1e  draft
72standard 17.
73
74       [4mpath[24m      specifies    the    LFC   pathname.    If
75[4mpath[24m does not start with [1m/[22m, it
76              is prefixed  by  the  content  of  the  [1mLFC_HOME
77[22menvironment variable.
78
79       [4muid[24m     is  displayed as the username if known else
80as the numeric id.
81
82       [4mgid[24m    is displayed as the groupname if known  else
83as the numeric id.
84
85       [4mperm[24m    is expressed as a combination of characters
86[1mrwx‐[0m
87
88[1mOPTIONS[0m
89       [1m‐a     [22monly display the access ACL.
90
91       [1m‐d     [22monly display the default ACL.
92
93[1mEXAMPLES[0m
94       lfc‐getacl /grid/atlas/test/file.log/d2
95
96       # file: /grid/atlas/test/file.log/d2
97       # owner: baud
98       # group: c3
99       user::rwx
100       group::r‐x              #effective:r‐x
101       other::r‐x
102       default:user::rwx
103       default:group::r‐x
104       default:other::r‐x
105
106[1mEXIT STATUS[0m
107       This program returns 0 if the operation was successful  or
108>0  if  the
109       operation failed.
110
111[1mSEE ALSO[0m
112       [1mCastor_limits(4)[22m,              [1mlfc_chmod(3)[22m,
113[1mlfc_chown(3)[0m
114
115[1mAUTHOR[0m
116       [1mLCG Grid Deployment [22mTeam
117
118
119
120LFC                         $Date:    2005/03/02    08:32:12    $
121LFC‐GETACL(1)
122
123
124
125
126
127
128
129
130
131
132
Impressum