pmserviced [-d] [-n] [-s] [-v] [-z on|off[:<pid>]]
The Privilege Manager service daemon, (pmserviced) is a persistent process that spawns the configured Privilege Manager services on demand. The pmserviced daemon is responsible for listening on the configured ports for incoming connections for the Privilege Manager for Unix daemons. It is capable of running the pmmasterd, pmlocald, pmclientd, and pmtunneld services.
Only one of pmmasterd and pmclientd may be enabled as they use the same TCP/IP port. See the individual topics in PM settings variables for more information about these daemon settings.
pmserviced has the following options.
Table 79: Options: pmserviced
||Logs debugging information such as connection received, signal receipt and service execution.
By default, pmserviced only logs errors.
||Does not run in the background or create a pid file. By default, pmserviced forks and runs as a background daemon, storing its pid in /var/opt/quest/qpm4u/pmserviced.pid. When you specify the -n option, it stays in the foreground. If you also specify the -d option, error and debug messages are logged to the standard error in addition to the log file or syslog. |
||Connects to the running pmserviced and displays the status of the services, then exits. |
||Displays the version number of Privilege Manager and exits.|
Enables or disables tracing for pmserviced.
Refer to Enabling program-level tracing before using this option.
pmserviced uses the following options in /etc/opt/quest/qpm4u/pm.settings to determine the daemons to run, the ports to use, and the command line options to use for each daemon.
Table 80: Options: pmserviced
Table 81: Settings: pmserviced
|pmservicedLog pathname | syslog
||Fully qualified path to the pmserviced log file or syslog.|
|pmmasterdEnabled YES | NO
||When set to YES, pmserviced runs pmmasterd on demand.|
The TCP/IP port pmmasterd or pmclientd uses to listen.
||Any command line options passed to pmmasterd.|
|pmlocaldEnabled YES | NO
||When set to YES, pmserviced runs pmlocald on demand.|
||The TCP/IP port pmlocald uses to listen.|
||Command line options passed to pmmasterd.|
|pmclientdEnabled YES | NO
||When set to YES, pmserviced runs pmclientd on demand.|
||Any command line options passed to pmclientd.|
|pmtunneldEnabled YES | NO
||When set to YES, pmserviced runs pmtunneld on demand.|
||The TCP/IP port pmtunneld uses to listen.|
|Any command line options passed to pmtunneld.|
- settings file: /etc/opt/quest/qpm4u/pm.settings
- pid file: /var/opt/quest/qpm4u/pmserviced.pid
pmsh -a|-b|-c <file>|-e|-f|-i|-m|-n|-o <option>|-s|-u|-v|-x|-C|-E|-I|-B|-V
The Privilege Manager Bourne Shell (pmsh) command is a fully featured version of sh, that provides transparent authorization and auditing for all commands submitted during the shell session. pmsh supports the standard options for sh.
Using the appropriate policy file variables, you can configure each command entered during a shell session, to be:
- forbidden by the shell without further authorization to the policy server
- allowed by the shell without further authorization to the policy server
- presented to the policy server for authorization
Once allowed by the shell, or authorized by the policy server, all commands run locally as the user running the shell program.
pmsh has the following options.
Table 82: Options: pmsh
|Flags variables for export when assignments are made to them.|
|Enables asynchronous notification of background job completion. (UNIMPLEMENTED) .|
|Allows the shell to run in the background.|
|Reads commands from a file instead of from standard input.|
|Does not overwrite existing files with `>'.|
|Exits immediately if any untested command fails in non-interactive mode. The exit status of a command is considered to be explic- itly tested if the command is part of the list used to control an if, elif, while, or until; if the command is the left hand oper- and of an ``&&'' or ``||'' operator; or if the command is a pipe- line preceded by the ! operator. If a shell function runs and its exit status is explicitly tested, all commands of the function are considered to be tested as well.|
|Enables the built-in emacs(1) command line editor (disables the -V option if it has been set; set automatically when interactive on terminals).|
|Disables pathname expansion..|
|A do-nothing option for POSIX compliance.|
|Forces the shell to behave interactively.|
|Ignores EOF's from input when in interactive mode.|
|Turns on job control (set automatically when interactive).|
|If not interactive, reads commands but do not run them. This is useful for checking the syntax of shell scripts.|
|Sets the specified shell option. A list of shell options can be displayed using the set -o builtin command.|
|Reads commands from standard input (set automatically if no file arguments are present). This option has no effect when set after the shell has already started running (i.e., when set with the set command).|
|Writes a message to standard error when attempting to expand a variable, a positional parameter or the special parameter ! that is not set, and if the shell is not interactive, exit immediately.|
|The shell writes its input to standard error as it is read. Useful for debugging.|
|Enables the built-in vi command-line editor (disables -E if it has been set). |
|Writes each command (preceded by the value of the PS4 variable subjected to parameter expansion and arithmetic expansion) to standard error before it is run. Useful for debugging.|
pmsh supports the following builtin commands:
., :, [, alias, bg, break, cd, chdir, command, continue, echo, eval, exec, exit, export, false, fg, getopts, hash, jobs, kill, local, printf, pwd, read, readonly, return, set, shift, test, times, trap, true, type, ulimit, umask, unalias, unset, wait
Use the pmshellwrapper program as a wrapper for any valid login shell on a host. It provides full keystroke logging for any normal shell, but does not provide authorization of the commands run from the shell.
To use pmshellwrapper, you must create a link for the real shell you want to use. For example:
ln –s /opt/quest/libexec/pmshellwrapper
When the user runs pmshell_bash, it transparently converts this to pmrun bash.
pmsrvcheck --csv [ --verbose ] | --help | --pmpolicy | --primary | --secondary
Use pmsrvcheck to verify that a policy server is setup properly. It produces output in either human-readable or CSV format similar to that produced by the preflight program.
The pmsrvcheck command checks:
- that the host is configured as a primary policy server and has a valid repository
- has a valid, up-to-date, checked-out copy of the repository
- has access to update the repository
- has a current valid Privilege Manager license
- pmmasterd is correctly configured
- pmmasterd can accept connections
pmsrvcheck produces output in either human-readable or CSV format similar to the pre-flight output.
pmsrvcheck has the following options.
Table 83: Options: pmsrvcheck
||Displays csv, rather than human-readable output.|
||Displays usage information.|
||Verifies that Privilege Manager policy is in use by the policy servers. |
||Verifies a primary policy server. |
||Verifies a secondary policy server. |
||Displays verbose output while checking the host.|
|Displays the Privilege Manager version number and exits.|
- Settings file: /etc/opt/quest/qpm4u/pm.settings