Process execution daemon, monitoring execution.
There is at least one pem daemon on every host in the cluster: on Windows, there is one per host; on Linux, there is one pem daemon per host, plus one for every activity running on that host—the number varies with the number of activities running at any given time.
The pem daemon starts all activities and monitors the activity life cycle.
The pem daemon is started automatically by the lim daemon, and exits when lim exits.
Starts the daemon, reading from the EGO configuration file ego.conf in the specified directory, rather than from the directory set via the EGO_CONFDIR environment variable.
Starts the daemon in the background, with no associated control terminal. Outputs log messages into log file.
Starts the daemon in debug mode. When running in debug mode, the daemon runs in the foreground, displaying the log messages. Outputs log messages to stderr.
pem reads the configuration file ego.conf to retrieve the location of its configuration information. ego.conf is a generic configuration file shared by all daemons and clients. It contains configuration information and other information that dictates the behavior of the software.
pem reads ego.conf to retrieve the following information:
The temporary directory pem uses for persistent files. If not specified, uses your location set in the $TMPDIR or %TMPDIR% environment variable. If that is not set either, defaults to your operating systerm’s default temporary directory (for example, on Linux: /tmp).
If EGO_LOGDIR is not defined in ego.conf but EGO_TMPDIR is defined, then logs for pem and vemkd are logged here.
The log level used to determine the amount of detail logged.