lslpriacl Command
Purpose
Displays the access controls for the least-privilege (LP) Resource Initial ACL.
Syntax
- On the local node:
lslpriacl [ -l | -i | -t | -d | -D delimiter ] [-p] [-E] [-x] [-h] [-TV]
- On all nodes in a domain:
lslpriacl -a [ -l | -i | -t | -d | -D delimiter ] [-p] [-E] [-x] [-h] [-TV]
- On a subset of nodes in a domain:
lslpriacl { -n host1[,host2,… ] } [ -l | -i | -t | -d | -D delimiter ] [-p] [-E] [-x] [-h] [-TV]
Description
The lslpriacl command displays the access control list (ACL) that is associated with the least-privilege (LP) Resource Initial ACL. The accesses contained in the ACL entries are displayed. The Resource Initial ACL is used as the Initial ACL that gets copied to the Resource ACL when an LP resource is created. By default, this command displays information in table format (-t).
Field | Description |
---|---|
Identity | The network identity of the user. See lpacl Information for a description of the network identity. |
Permissions | The permissions allowed for Identity.
The valid values are:
|
NodeName | The location of the IBM.LPCommands resource class (for management domain scope or peer domain scope). |
PeerDomain | The name of the RSCT peer domain in which the IBM.LPCommands resource class is defined. This field is displayed when the -p flag is specified. |
This command runs on any node. If you want this command to run on all of the nodes in a domain, use the -a flag. If you want this command to run on a subset of nodes in a domain, use the -n flag. Otherwise, this command runs on the local node.
Flags
- -a
- Displays the Resource Initial ACLs on all nodes in the domain.
The CT_MANAGEMENT_SCOPE environment variable
setting determines the cluster scope. If CT_MANAGEMENT_SCOPE is
not set, the LP resource manager uses scope settings in this order:
- The management domain, if it exists
- The peer domain, if it exists
- Local scope
- -i
- Generates a template in a form that can be used, after appropriate editing, as file input to the chlpriacl command.
- -l
- Displays the information about separate lines (long format).
- -t
- Displays the information in separate columns (table format). This is the default.
- -d
- Displays the information using delimiters. The default delimiter is a pipe symbol (|). Use the -D flag if you want to change the default delimiter.
- -D delimiter
- Displays the information using the specified delimiter. Use this flag to specify a delimiter other than the default pipe symbol (|) when the information you want to display contains pipe symbols, for example. You can use this flag to specify a delimiter of one or more characters.
- -n host1[,host2,…]
- Specifies the node in the domain from which the Resource Initial ACL is displayed. By default, the Resource Initial ACL is displayed on the local node. This flag is valid only in a management domain or a peer domain. If CT_MANAGEMENT_SCOPE is not set, first the management domain scope is chosen if it exists, then the peer domain scope is chosen if it exists, and then local scope is chosen, until the scope is valid for the command. The command runs once for the first valid scope found.
- -p
- Displays the name of the RSCT peer domain in which the IBM.LPCommands resource class is defined.
- -E
- Displays read permission as elqv instead of r and write permission as cdos instead of w.
- -x
- Excludes the header (suppresses header printing).
- -h
- Writes the command usage statement to standard output.
- -T
- Writes the command trace messages to standard error.
- -V
- Writes the command verbose messages to standard output.
Environment variables
- CT_CONTACT
- Determines the system where the session with the resource monitoring and control (RMC) daemon occurs. When CT_CONTACT is set to a host name or IP address, the command contacts the RMC daemon on the specified host. If CT_CONTACT is not set, the command contacts the RMC daemon on the local system where the command is being run. The target of the RMC daemon session and the management scope determine the resource classes or resources that are processed.
- CT_IP_AUTHENT
- When the CT_IP_AUTHENT environment variable exists, the RMC daemon uses IP-based network authentication to contact the RMC daemon on the system that is specified by the IP address to which the CT_CONTACT environment variable is set. CT_IP_AUTHENT has meaning only if CT_CONTACT is set to an IP address; it does not rely on the domain name system (DNS) service.
- CT_MANAGEMENT_SCOPE
- Determines the management scope that is used for the session with
the RMC daemon in processing the resources of the least-privilege
(LP) resource manager. The management scope determines the set of
possible target nodes where resources can be processed. The valid
values are:
- 0
- Specifies local scope.
- 1
- Specifies local scope.
- 2
- Specifies peer domain scope.
- 3
- Specifies management domain scope.
Standard output
When the -h flag is specified, this command usage statement is written to standard output. When the -V flag is specified, this command verbose messages are written to standard output.
Standard error
All trace messages are written to standard error.
Exit status
- 0
- The command ran successfully.
- 1
- An error occurred with RMC.
- 2
- An error occurred with the command-line interface (CLI) script.
- 3
- An incorrect flag was specified on the command line.
- 4
- An incorrect parameter was specified on the command line.
- 5
- An error occurred with RMC that was based on incorrect command-line input.
- 6
- The resource was not found.
Security
To run the lslpriacl command, you need read permission in the Class ACL of the IBM.LPCommands resource class. Permissions are specified in the LP ACLs on the contacted system. See lpacl Information for general information about LP ACLs and the Administering RSCT guide for information about modifying them.
Implementation specifics
This command is part of the Reliable Scalable Cluster Technology (RSCT) fileset for the AIX® and Linux® operating systems.
Location
- /opt/rsct/bin/lslpriacl
Examples
- To list the Resource Initial ACLs on nodeA in
table format, run this command on nodeA:
The following output is displayed:lslpriacl
Resource Initial ACLs for LPRM Identity Permissions NodeName joe@LOCALHOST rx nodeA bill@0x374bdcbe384ed38a rwx nodeA jane@0x374bdcbe384ed38a rwax nodeA
- To list the Resource Initial ACLs on nodeA in
long format, run this command on nodeA:
The following output is displayed:lslpriacl -l
Resource Initial ACLs for LPRM NodeName c175n06.ppd.pok.ibm.com Identity = joe@LOCALHOST Permissions = rx Identity = bill@0x374bdcbe384ed38a Permission = rwx Identity = jane@0x374bdcbe384ed38a Permissions = rwax
- To list the Resource Initial ACLs on nodeA in
delimited format, run this command on nodeA:
The following output is displayed:lslpriacl -d
Resource Initial ACLs for LPRM Identity|Permissions|NodeName joe@LOCALHOST|rx|nodeA bill@0x374bdcbe384ed38a|rwx|nodeA jane@0x374bdcbe384ed38a|rwax|nodeA
- To list the Resource Initial ACLs in the active domain, run this
command:
The following output is displayed:lslpriacl -a
Resource Initial ACLs for LPRM Identity Permissions NodeName joe@LOCALHOST rx nodeA.pok.ibm.com bill@0x374bdcbe384ed38a rwx nodeA.pok.ibm.com jane@0x374bdcbe384ed38a rwax nodeA.pok.ibm.com joe@LOCALHOST rx nodeB.pok.ibm.com jane@0x374bdcbe384ed38a rwax nodeB.pok.ibm.com
- To list the Resource Initial ACLs in the active domain and list
the peer domain name, run this command:
The following output is displayed:lslpriacl -ap
Resource Initial ACLs for LPRM Identity Permissions NodeName PeerDomain joe@LOCALHOST rx nodeA.pok.ibm.com PD1 bill@0x374bdcbe384ed38a rwx nodeA.pok.ibm.com PD1 jane@0x374bdcbe384ed38a rwax nodeA.pok.ibm.com PD1 joe@LOCALHOST rx nodeB.pok.ibm.com PD1 jane@0x374bdcbe384ed38a rwax nodeB.pok.ibm.com PD1