Syntax
pmcheckperms> [-f] [-v]
pmcheckperms> -z on|off[:<pid>]
Description
The pmcheckperms utility can be used to check the ownership and permissions of Privilege Manager files on the system. It may be run on a plugin host, an agent, or a policy server.
The following directory hierarchies are validated by pmcheckperms:
-
/etc/opt/quest/qpm4u/policy
-
/var/opt/quest/qpm4u/evcache
-
/var/opt/quest/qpm4u/iolog
-
/var/opt/quest/qpm4u/pmclient
-
/var/opt/quest/qpm4u/pmevents.db
-
/var/opt/quest/qpm4u/pmpolicy
-
/var/opt/quest/qpm4u/.qpm4u/.perfdata
-
/var/opt/quest/qpm4u/.qpm4u/.repository
Options
pmcheckperms has the following options.
Table 52: Options: pmcheckperms
|
-f |
Fixes detected permission issues.
If pmcheckperms finds an ownership or permission problem, it sets the correct value for the affected file or directory. |
|
-v |
Enables verbose output.
The command prints the name of each checked file and directory in the standard output. |
|
-z |
Enables or disables debug tracing, and optionally sends SIGHUP to the running process.
Before using this option, see Enabling program-level tracing. |
Settings
pmcheckperms uses the following entries in the /etc/opt/quest/qpm4u/pm.settings file.
Table 53: Settings: pmcheckperms
|
eventLogQueue <pathname> |
Specifies the location of the event log queue, where event data is temporarily queued before being written to the event log database. |
Syntax
pmclientd [-v]i|[-z on|off[:<pid>]]
Description
The pmclientd daemon runs on an agent and allows the agent to respond to remote requests sent by a policy server as a result of calling a remote function from the policy file. It is not required on a policy server, as the pmmasterd daemon can serve these requests, if received from another policy server. pmclientd listens on the configured policy server port and responds to a remote request received from any valid policy server or any host listed in the clients setting in pm.settings.
Options
pmclientd has the following options.
Table 54: Options: pmclientd
|
-v |
Displays the version number of Privilege Manager for Unix and exits. |
|
-z |
Enables or disables debug tracing, and optionally sends SIGHUP to running process.
Before using this option, see Enabling program-level tracing. |
Syntax
pmclientinfo -v | [-z on|off[:<pid>]]] | -c [-h <host>]
Description
The pmclientinfo utility displays configuration information about a client host. This utility provides some information about the policy server group and the license features supported by the policy server group. You can specify a host on the command line to retrieve the details from a specific policy server host. Otherwise, the utility checks each policy server listed in the pm.settings file in turn until it finds one in a policy server group. Any user can run pmclientinfo.
Options
pmclientinfo has the following options.
Table 55: Options: pmclientinfo
|
-c |
Displays CSV, rather than human-readable output. |
|
-h <host> |
Specifies policy server host name to interrogate for policy group information. |
|
-v |
Displays the version number of Privilege Manager for Unix and exits. |
|
-z |
Enables or disables debug tracing.
Before using this option, see Enabling program-level tracing. |
Examples
Any user on the host can run this utility. It displays the following information, in human readable or CSV format:
- Joined to a policy group : YES
- Policy group name configured for this policy server group : adminGroup1
- Primary policy server hostname : adminhost1
Human Readable output from a client:
- Joined to a policy group : YES
- Name of policy group : adminGroup1
- Hostname of primary policy server : adminhost1.example.com
CSV output from a client:
PMCLIENTINFO.JOINED,Joined to a policy group,YES
PMCLIENTINFO.POLICYGROUPNAME,Name of policy group,adminGroup1
PMCLIENTINFO.PRIMARYPOLICYSERVER,Hostname of primary policy server,adminhost1.example.com
Syntax
pmcp [-v]|[-z on|off[:<pid>]] [-m <masterhost>] file1 rhost:file2
Description
Use pmcp to copy a file from one host to another. The pmcp command allows you to select the policy server host to contact, bypassing the usual selection methods. The specified host must be present in the masters setting in the pm.settings file. This functionality is the same as using pmrun [-m masterhost].
You can use the following policy variables with pmcp:
Table 56: Policy variables: pmcp
|
filesize |
Specifies the size of the source file. |
|
filename |
Specifies the name of the source file, including the full path. |
|
filedest |
Specifies the name of the target file, including the full path. |
|
fileuser |
Specifies the user name associated with the source file UID. |
|
filegroup |
Specifies the group name associated with the source file GID. |
|
filedate |
Specifies the date that the source file was last modified. This returns a string in the form: YYYY/MM/DD. |
Options
pmcp has the following options.
Table 57: Options: pmcp
|
-m <masterhost> |
Selects a policy server host to contact. |
|
-v |
Displays product version information. |
|
-z |
Enables or disables debug tracing, and optionally sends SIGHUP to running process.
Before using this option, see Enabling program-level tracing. |
