LFC-MODIFYGRPMAP(1) LFC Administrator Commands LFC-MODIFYGRPMAP(1)NAME
lfc-modifygrpmap - modify group entry corresponding to a given virtual gid
SYNOPSIS
lfc-modifygrpmap --gid gid --group newname [ --status status ]
DESCRIPTION
lfc-modifygrpmap modifies the group entry corresponding to a given virtual gid.
This command requires ADMIN privilege.
OPTIONS --gid gid
specifies the Virtual Group Id.
--group newname
specifies the new group name. It must be at most 255 characters long.
--status status
status can be set to 0 or a combination of ARGUS_BAN and LOCAL_BAN. This can be either alphanumeric or the corresponding numeric
value.
EXIT STATUS
This program returns 0 if the operation was successful or >0 if the operation failed.
SEE ALSO lfc_modifygrpmap(3)LFC $Date: 2010-08-04 09:58:47 +0200 (Wed, 04 Aug 2010) $ LFC-MODIFYGRPMAP(1)
Check Out this Related Man Page
LFC-GETACL(1) LFC User Commands LFC-GETACL(1)NAME
lfc-getacl - get LFC directory/file access control lists
SYNOPSIS
lfc-getacl [-a] [-d] path...
DESCRIPTION
lfc-getacl gets the Access Control List associated with a LFC directory/file. For each path, it displays the file name, owner, the group,
and the Access Control List (ACL) if present. If a directory has a default ACL, lfc-getacl also displays the default ACL. Regular files
cannot have default ACLs.
The output looks like:
# file: filename
# owner: username
# group: groupname
user::perm
user:uid:perm
group::perm
group:gid:perm
mask:perm
other:perm
default:user::perm
default:user:uid:perm
default:group::perm
default:group:gid:perm
default:mask:perm
default:other:perm
The first "user" entry gives the permissions granted to the owner of the file. The following "user" entries show the permissions granted
to specific users, they are sorted in ascending order of uid. The first "group" entry gives the permissions granted to the group owner of
the file. The following "group" entries show the permissions granted to specific groups, they are sorted in ascending order of gid. The
"mask" entry is the maximum permission granted to specific users or groups. It does not affect the "owner" and "other" permissions. The
"mask" entry must be present if there are specific "user" or "group" entries. "default" entries associated with a directory are inherited
as access ACL by the files or sub-directories created in that directory. The umask is not used. Sub-directories also inherit the default
ACL as default ACL. As soon as there is one default ACL entry, the 3 default ACL base entries (default user, default group, default other)
must be present.
The entry processing conforms to the Posix 1003.1e draft standard 17.
path specifies the LFC pathname. If path does not start with /, it is prefixed by the content of the LFC_HOME environment variable.
uid is displayed as the username if known else as the numeric id.
gid is displayed as the groupname if known else as the numeric id.
perm is expressed as a combination of characters rwx-
OPTIONS -a only display the access ACL.
-d only display the default ACL.
EXAMPLES
lfc-getacl /grid/atlas/test/file.log/d2
# file: /grid/atlas/test/file.log/d2
# owner: baud
# group: c3
user::rwx
group::r-x #effective:r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x
EXIT STATUS
This program returns 0 if the operation was successful or >0 if the operation failed.
SEE ALSO Castor_limits(4), lfc_chmod(3), lfc_chown(3)AUTHOR
LCG Grid Deployment Team
LFC $Date: 2005/03/02 08:32:12 $ LFC-GETACL(1)