powerman.dev – PowerMan device specification files Description PowerMan device specifications are rather wierd. For this reason, we suggest that you leave the writing of these scripts to the PowerMan authors. However, if you insist, here is how they work. Note: the authors do not guarantee that the PowerMan specification language will not change, however we…
powerman.conf – configuration file for PowerMan Description The powerman.conf file typically includes one or more of the remote power controller (RPC) device files provided in the /etc/powerman directory; sets a few global options; instantiates RPC devices with unique names, hostnames, and ports; and maps node names to RPC’s and plug numbers. Network-attached RPC’s are instantiated…
postlogin – Common configuration file for PAMified services Synopsis /etc/pam.d/postlogin Description The purpose of this PAM configuration file is to provide a common place for all PAM modules which should be called after the stack configured in system-auth or the other common PAM configuration files. The postlogin configuration file is included from all individual service…
system-auth-ac, password-auth-ac, smartcard-auth-ac, fingerprint-auth-ac, postlogin-ac – Common configuration files for PAMified services written by authconfig(8) Synopsis /etc/pam.d/system-auth-ac Description The purpose of this configuration file is to provide common configuration file for all applications and service daemons calling PAM library. The system-auth configuration file is included from all individual service configuration files with the help of…
postfix-wrapper – Postfix multi-instance API Description Support for managing multiple Postfix instances is available as of version 2.6. Instances share executable files and documentation, but have their own directories for configuration, queue and data files. This document describes how the familiar "postfix start" etc. user interface can be used to manage one or multiple Postfix…
postconf – Postfix configuration parameters Synopsis postconf parameter … postconf -e "parameter=value" … Description The Postfix main.cf configuration file specifies parameters that control the operation of the Postfix mail system. Typically the file contains only a small subset of all parameters; parameters not specified are left at their default values. The general format of the…
poolset – persistent memory pool configuration file format Synopsis mypool.set Description Depending on the configuration of the system, the available non-volatile memory space may be divided into multiple memory devices. In such case, the maximum size of the transactional object store could be limited by the capacity of a single memory device. Therefore, libpmemobj(7), libpmemblk(7)…
po4a-build.conf – configuration file for building translated content Introduction po4a-build.conf describes how "po4a-build" should build translated and untranslated documentation from a set of untranslated source documents and corresponding PO files. All supported formats, in all supported combinations, can be handled in a single po4a-build.conf configuration file and in a single call to "po4a-build". However, you…
pnm – portable anymap file format Description The pnm programs operate on portable bitmaps, graymaps, and pixmaps, produced by the pbm, pgm, and ppm segments. There is no file format associated with pnm itself. See Also anytopnm(1), rasttopnm(1), tifftopnm(1), xwdtopnm(1), pnmtops(1), pnmtorast(1), pnmtotiff(1), pnmtoxwd(1), pnmarith(1), pnmcat(1), pnmconvol(1), pnmcrop(1), pnmcut(1), pnmdepth(1), pnmenlarge(1), pnmfile(1), pnmflip(1), pnmgamma(1), pnmindex(1),…
png – Portable Network Graphics (PNG) format Description PNG (Portable Network Graphics) is an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample…
png – Portable Network Graphics (PNG) format Description PNG (Portable Network Graphics) is an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample…
pmview – configuration file format for performance Description This man page describes version 2.1 of the pmview configuration file format. The configuration format supports metrics from multiple hosts or archives. A configuration file can specify metrics without a source, with different hosts and different archives. However, a configuration file that contains archives may only have…
pmrep.conf – pmrep configuration file Description pmrep is a customizable performance metrics reporting tool. Any available performance metric, live or archived, system and/or application, can be selected for reporting using one of the available output alternatives together with applicable formatting options. The metrics of interest are named in the metricspec argument(s) on the pmrep command…
pmns – the performance metrics name space Synopsis $PCP_VAR_DIR/pmns Description When using the Performance Metrics Programming Interface (PMAPI) of the Performance Co-Pilot (PCP), performance metrics are identified by an external name in a hierarchic Performance Metrics Name Space (PMNS), and an internal identifier, the Performance Metric Identifier (PMID). A PMNS specifies the association between a…
pmieconf – generalized pmie rules and customizations Description The pmieconf file formats are used by the pmieconf(1) tool as a way to generalize pmie(1) rule sets such that they can be easily configured for different systems and different environments. There are two completely different (although closely related) file formats discussed here, namely “pmieconf-rules” and “pmieconf-pmie”….
plowshare.conf – Configuration file for Plowshare Description Plowshare (plowdown, plowup, plowdel, plowlist or plowprobe) uses a configuration file called plowshare.conf for its initial setup. This configuration file is searched for in the following places when plowshare is started: ~/.config/plowshare/plowshare.conf /etc/plowshare.conf Note: Usage of configuration file can be disabled using –no-plowsharerc command-line option. There is also…
plotnetcfg – json output format Description Root object fields format (number) Currently 1. Will be increased if incompatible changes are introduced. A tool parsing the json output should refuse any format it’s not aware of. Note that adding of new fields is not considered to be an incompatible change. version (string) Plotnetcfg version. date (string)…
pki_default.cfg – Certificate Server instance default config file. Location /etc/pki/default.cfg Description This file contains the default settings for a Certificate Server instance created using pkispawn. This file should not be edited, as it can be modified when the Certificate Server packages are updated. Instead, when setting up a Certificate Server instance, a user should provide…
pki-server-logging – PKI Server Logging Configuration Location /etc/pki/<instance>/logging.properties, /var/lib/pki/<instance>/lib/log4j.properties, /etc/pki/<instance>/<subsystem>/CS.cfg Description PKI server logging can be configured using the following logging frameworks: – java.util.logging (JUL) (https://docs.oracle.com/javase/8/docs/api/java/util/logging/package-summary.html) – Log4j (http://logging.apache.org/log4j/1.2/) – Internal Logging java.util.logging (JUL) Tomcat uses JUL as the default logging framework. The configuration is described in http://tomcat.apache.org/tomcat-7.0-doc/logging.html and http://tomcat.apache.org/tomcat-8.0-doc/logging.html. The default configuration is located…
pki-logging – PKI Common Logging Configuration Location /usr/share/pki/etc/logging.properties, /etc/pki/logging.properties Description PKI clients and tools use java.util.logging (JUL) as the logging framework (see https://docs.oracle.com/javase/8/docs/api/java/util/logging/package-summary.html). The default logging configuration is located at /usr/share/pki/etc/logging.properties. By default only log messages with level WARNING or higher will be logged on the console. java.util.logging.ConsoleHandler.level = ALL java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter java.util.logging.SimpleFormatter.format =…