Chat now with support
Chat with Support

Safeguard for Sudo 6.1 Common Documents - Administration Guide

One Identity Privileged Access Suite for Unix Introducing Privilege Manager for Sudo Planning Deployment Installation and Configuration Upgrade Privilege Manager for Sudo System Administration Managing Security Policy Administering Log and Keystroke Files Troubleshooting Privilege Manager Variables Privilege Manager programs Installation Packages Unsupported Sudo Options Privilege Manager for Sudo Policy Evaluation


pmlogxfer -h | -v

Transfers event logs and I/O logs after an off-line policy evaluation has occurred. pmlogxfer is initiated by pmloadcheck when there are log files queued for transfer from a Sudo Plugin host to the server.

NOTE: pmlogxfer is not intended to be run directly, it is normally invoked by pmpluginloadcheck at a regular interval (every 30 minutes by default).


pmlogxfer has the following options.

Table 27: Options: pmlogxfer
Option Description
-h Displays usage information.
-v Displays the version number of Privilege Manager and exits.

Directory for offline log files:

Related Topics



pmmasterd [ -v ]| [ [ -ars ] [ -e <logfile> ] ]

The Privilege Manager master daemon (pmmasterd) is the policy server decision-maker. pmmasterd receives requests from pmrun or the Sudo Plugin and evaluates them according to the security policy. If the request is accepted, pmmasterd asks pmlocald or the Sudo Plugin to run the request in a controlled account such as root.

A connection is maintained between pmmasterd and the Sudo Plugin for the duration of the session. This also occurs between pmmasterd and pmlocald, if keystroke logging is enabled. When the pmmasterd connection is maintained throughout the session, keystroke and event log data is forwarded on this connection.

If keystroke logging is not enabled, pmlocald reconnects to pmmasterd at the end of the session to write the event log record showing the final completion code for the command run by pmlocald. If pmlocald is unable to reconnect, it writes instead to a holding file, pm.eventhold.hostname. It then attempts to write the pmevents.db record to the host the next time pmmasterd connects to pmlocald. Multiple files can accrue and they will all be delivered to the proper host when the connection is restored.

The policy server master daemon typically resides on a secure machine. You can have more than one policy server master daemon on different hosts for redundancy or to serve multiple networks.

pmmasterd logs all errors in a log file if you specify the -e filename option.


pmmasterd has the following options.

Table 28: Options: pmmasterd
Option Description
-a Sends job acceptance messages to syslog.
-e <filename> Logs any policy server master daemon errors in the file specified.
-r Sends job rejection messages to syslog.
-s Sends any policy server master daemon errors to syslog.
-v Displays the version number of pmmasterd and exits.

  • Privilege Manager policy file (sudo type): /etc/opt/quest/qpm4u/policy/sudoers


pmplugininfo -v | -c [-h <host>]

Run the pmplugininfo command on a Sudo Plugin host to display information about the policy server group that the host has joined.


pmplugininfo has the following options.

Table 29: Options: pmplugininfo
Option Description

Displays output in CSV, rather than human-readable format.

-h <hostname>

Specifies the hostname to interrogate for policy group information.


Displays product version and exits.


The following is an example of the human-readable output:

Joined to a policy group             : YES 
Name of policy group                 : adminGroup1 
Hostname of primary policy server    : adminhost1



pmpluginloadcheck -v  
                     -s|-p|-i [-e <interval>][-t <sec>] 
                    [-c|-f][-b][ -h <master>][-t <sec>] [-a][-r]


The pmpluginloadcheck daemon runs on each Sudo Plugin host and controls load balancing and failover for connections made from the host to the configured policy servers. It runs as a daemon, and is started as needed to verify the status of the configured policy servers.

Information is gathered from a policy server each time a normal sudo session connects to the policy server. This information is used to determine which policy server to use the next time a session is requested. If a host cannot establish a connection to a policy server because, for example, the policy server is offline, then this policy server is marked as offline and no more connections are submitted to this policy server until it is available again. For each policy server that is marked as offline, the pmpluginloadcheck daemon checks at intervals, and attempts to establish a connection with the policy server to determine its current status. If pmpluginloadcheck successfully establishes a session with the policy server, it is marked as online and is made available for normal sudo sessions.

To check the current status of all configured policy servers and display a brief summary of their status, run pmpluginloadcheck with no options. Add the –f option to show full details of each policy server status.


pmpluginloadcheck has the following options.

Table 30: Options: pmpluginloadcheck
Option Description


Verifies the connection as if certificates are configured.


Runs in batch mode.


Reports full details of selected servers in CSV, rather than human-readable format.

-e <interval>

Sets the refresh interval (in minutes).

The default is 60 minutes.

The minimum value is 2 minutes.


Reports full details of data for each policy server (or selected policy server, when using the –h option).

-h <master>

Selects a policy server to verify.


Starts up the pmpluginloadcheck daemon, if it is not already running.


Pause (send SIGUSR1) to a running daemon.


Sends SIGHUP to a running daemon.


Reports last cached data for selected servers instead of connecting.


Stops the pmloadcheck daemon, if it is running.

-t <sec>

Specifies a timeout (in seconds) to use for each connection.


Displays the version string and exits.

Related Documents