Section 5: file formats
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 =…
pkcs15-profile – format of profile for pkcs15-init Synopsis Description The pkcs15-init utility for PKCS #15 smart card personalization is controlled via profiles. When starting, it will read two such profiles at the moment, a generic application profile, and a card specific profile. The generic profile must be specified on the command line, while the card-specific…
pkcs11.txt – NSS PKCS #11 module configuration file Description The pkcs11.txt file is used to configure initialization parameters for the nss security module and optionally other pkcs #11 modules. For full documentation visit m[blue]PKCS #11 Module Specsm[][1]. Files /etc/pki/nssdb/pkcs11.txt Authors The nss libraries were written and maintained by developers with Netscape, Red Hat, Sun, Oracle,…
pkcs11.txt – NSS PKCS #11 module configuration file Description The pkcs11.txt file is used to configure initialization parameters for the nss security module and optionally other pkcs #11 modules. For full documentation visit m[blue]PKCS #11 Module Specsm[][1]. Files /etc/pki/nssdb/pkcs11.txt Authors The nss libraries were written and maintained by developers with Netscape, Red Hat, Sun, Oracle,…
pkcs11.conf – Configuration files for PKCS#11 modules Description The pkcs11.conf configuration files are a standard way to configure PKCS#11 modules. File Format A complete configuration consists of several files. These files are text files. Since p11-kit is built to be used in all sorts of environments and at very low levels of the software stack,…
pipewire.conf – The PipeWire server configuration file Synopsis $XDG_CONFIG_HOME/pipewire/pipewire.conf /etc/pipewire/pipewire.conf /usr/share/pipewire/pipewire.conf /usr/share/pipewire/pipewire.conf.d/ /etc/pipewire/pipewire.conf.d/ $XDG_CONFIG_HOME/pipewire/pipewire.conf.d/ Description PipeWire is a service that facilitates sharing of multimedia content between devices and applications. On startup, the daemon reads a main configuration file to configure itself. It executes a series of commands listed in the config file. The config files…
pingd.conf – pingd configuration file Description The pingd configuration file configures the pingd daemon. The default configuration file loaded is /etc/pingd.conf. The configuration options that can be specified in the configuration file are listed below. Each configuration option must be listed on a separate line. Arguments for an option are separated by any amount of…
pgsql_table – Postfix PostgreSQL client configuration Synopsis postmap -q "string" pgsql:/etc/postfix/filename postmap -q – pgsql:/etc/postfix/filename <inputfile Description The Postfix mail system uses optional tables for address rewriting or mail routing. These tables are usually in dbm or db format. Alternatively, lookup tables can be specified as PostgreSQL databases. In order to use PostgreSQL lookups, define…
pgm – portable graymap file format Description The PGM format is a lowest common denominator grayscale file format. It is designed to be extremely easy to learn and write programs for. (It’s so simple that most people will simply reverse engineer it because it’s easier than reading this specification). A PGM image represents a grayscale…
PFM – PFM graphic image file format Description This document describes the PFM graphic image file format as understood by the Netpbm converters pamtopfm(1) and pfmtopam(1) There are multiple similar formats known as PFM in the world, none of them authoritatively documented. The format described here is one that Bryan Henderson deduced from a program…
perfevent.conf – the Performance Co-Pilot perfevent PMDA configuration file Synopsis $PCP_PMDAS_DIRS/perfevent/perfevent.conf Description The perfevent.conf configuration file defines which hardware performance counters are enabled by the perfevent PMDA. The configuration file contains a list of events that should be enabled for each PMU. The perfevent PMDA detects which PMUs present and programs the configured events. If…
pear.conf – configuration file for PEAR applications. Description The pear.conf is used by PEAR applications to store their configuration. This file should not be edited. The pear command provides the config-show, config-get and config-set sub-commands needed to change the configuration. Files /etc/pear.conf The system configuration file. $HOME/.pearrc The user configuration file. See Also pear(1) Copyright…
pcre_table – format of Postfix PCRE tables Synopsis postmap -q "string" pcre:/etc/postfix/filename postmap -q – pcre:/etc/postfix/filename <inputfile Description The Postfix mail system uses optional tables for address rewriting, mail routing, or access control. These tables are usually in dbm or db format. Alternatively, lookup tables can be specified in Perl Compatible Regular Expression form. In…
pcp.env – script to set Performance Co-Pilot run-time environment variables Synopsis /etc/pcp.env Description The pcp.env script is sourced by assorted Performance Co-Pilot (PCP) scripts and utilities to define the PCP operating environment variables. The conjugate for executable programs using the PCP libraries is the __pmGetConfig(3) function. Typical usage of pcp.env in a script is as…
pcp.conf – the Performance Co-Pilot configuration and environment file Synopsis /etc/pcp.conf Description When using Performance Co-Pilot (PCP) tools and utilities and when calling PCP library functions, a standard set of environment variables are defined in /etc/pcp.conf. These variables are generally used to specify the location of various PCP pieces in the file system and may…
atoprc – pcp-atop/pcp-atopsar related resource file Description This manual page documents the resource file of the pcp-atop and pcp-atopsar commands. These commands can be used to monitor the system and process load on a system. The pcp-atoprc file contains the default settings. These settings are read during startup, first from the system-wide rcfile /etc/atoprc and…
pcp-archive – Archive Files for Performance Co-Pilot Synopsis $PCP_LOG_DIR/pmlogger/*/*.{meta,index,0} $PCP_LOG_DIR/pmmgr/*/*.{meta,index,0} Description PCP log archives store volumes of historical values of arbitrary Performance Co-Pilot metrics recorded from a single host. Archives are self-contained in the sense that they contain all the important metadata that would be required for off-line or off-site analysis. The format is intended…