Section 7: overview, conventions, and miscellany
po4a – framework to translate documentation and other materials Introduction The po4a (PO for anything) project goal is to ease translations (and more interestingly, the maintenance of translations) using gettext tools on areas where they were not expected like documentation. Table of content This document is organized as follow: 1 Why should I use po4a?…
po4a-runtime – po4a and runtime gettext translation without Autotools Introduction With po4a-build, po4a also includes support for adding translation of runtime script output messages using gettext but without requiring the package to adopt Autotools and the typical ./configure process. Using example Makefile snippets, packages can harness intltool with minimal effort. Layout Documentation translation should NOT…
po-debconf – introduction Description The goal of "debconf" was to make package configuration user-friendly. In order to achieve this, it is important to ensure that users will get the question in their own language. Translators need a framework to easily work on translations without having to track package development; "po-debconf" was designed to be able…
PMIx Constants Synopsis #include <pmix_common.h> Overview PMIx relies on the following types of constants: Maximum Sizes : In order to minimize malloc performance penalties, PMIx utilizes constant-sized arrays wherever possible. These constants provide the user with the maximum size of the various array types. Attributes : . Errors : PMIx uses negative error constants, with…
Process Management Interface – Exascale Synopsis #include <pmix.h> Overview The Process Management Interface (PMI) has been used for quite some time as a means of exchanging wireup information needed for interprocess communication. Two versions (PMI-1 and PMI-2) have been released as part of the MPICH effort. While PMI-2 demonstrates better scaling properties than its PMI-1…
pkeys – overview of Memory Protection Keys Description Memory Protection Keys (pkeys) are an extension to existing page-based memory permissions. Normal page permissions using page tables require expensive system calls and TLB invalidations when changing permissions. Memory Protection Keys provide a mechanism for changing protections without requiring modification of the page tables on every permission…
pipe – overview of pipes and FIFOs Description Pipes and FIFOs (also known as named pipes) provide a unidirectional interprocess communication channel. A pipe has a read end and a write end. Data written to the write end of a pipe can be read from the read end of the pipe. A pipe is created…
pilot-link – A suite of tools for communicating with Palm handhelds, such as those made by Palm, Handspring, Handera, TRGPro, Sony or other Palm Compatible Handheld PDA device. Section Pilot-link: Overview Description The pilot-link suite of tools contains a series of conduits, libraries, and language bindings for moving information to and from your Palm device…
pigeonhole – Overview of the Pigeonhole project’s Sieve support for the Dovecot secure IMAP and POP3 server Description The Pigeonhole project <http://pigeonhole.dovecot.org> adds support for the Sieve language (RFC 5228) and the ManageSieve protocol (RFC 5804) to the Dovecot Secure IMAP and POP3 Server (dovecot(1)). In the literal sense, a pigeonhole is a a hole…
pid_namespaces – overview of Linux PID namespaces Description For an overview of namespaces, see namespaces(7). PID namespaces isolate the process ID number space, meaning that processes in different PID namespaces can have the same PID. PID namespaces allow containers to provide functionality such as suspending/resuming the set of processes in the container and migrating the…
persistent-keyring – per-user persistent keyring Description The persistent keyring is a keyring used to anchor keys on behalf of a user. Each UID the kernel deals with has its own persistent keyring that is shared between all threads owned by that UID. The persistent keyring has a name (description) of the form _persistent.<UID> where <UID>…
pengine – Policy Engine Options Synopsis [no-quorum-policy=enum] [symmetric-cluster=boolean] [default-resource-stickiness=integer] [is-managed-default=boolean] [maintenance-mode=boolean] [start-failure-is-fatal=boolean] [enable-startup-probes=boolean] [stonith-enabled=boolean] [stonith-action=enum] [stonith-timeout=time] [have-watchdog=boolean] [concurrent-fencing=boolean] [startup-fencing=boolean] [cluster-delay=time] [batch-limit=integer] [migration-limit=integer] [default-action-timeout=time] [stop-all-resources=boolean] [stop-orphan-resources=boolean] [stop-orphan-actions=boolean] [remove-after-stop=boolean] [pe-error-series-max=integer] [pe-warn-series-max=integer] [pe-input-series-max=integer] [node-health-strategy=enum] [node-health-green=integer] [node-health-yellow=integer] [node-health-red=integer] [placement-strategy=enum] Description This is a fake resource that details the options that can be configured for the Policy Engine. Supported Parameters…
pcilib – a library for accessing PCI devices Description The PCI library (also known as pcilib and libpci) is a portable library for accessing PCI devices and their configuration space. Access Methods The library supports a variety of methods to access the configuration space on different operating systems. By default, the first matching method in…
pcap-tstamp – packet time stamps in libpcap Description When capturing traffic, each packet is given a time stamp representing, for incoming packets, the arrival time of the packet and, for outgoing packets, the transmission time of the packet. This time is an approximation of the arrival or transmission time. If it is supplied by the…
pcap-linktype – link-layer header types supported by libpcap Description For a live capture or “savefile”, libpcap supplies, as the return value of the pcap_datalink(3PCAP) routine, a value that indicates the type of link-layer header at the beginning of the packets it provides. This is not necessarily the type of link-layer header that the packets being…
pcap-filter – packet filter syntax Description pcap_compile() is used to compile a string into a filter program. The resulting filter program can then be applied to some stream of packets to determine which packets will be supplied to pcap_loop(3PCAP), pcap_dispatch(3PCAP), pcap_next(3PCAP), or pcap_next_ex(3PCAP). The filter expression consists of one or more primitives. Primitives usually consist…
pbs_server_attributes – pbs server attributes Description Server attributes can be read by any client; privilege is not required. Most server attributes are alterable by a privileged client, run by a user with administrator or operator privilege. Certain attributes require the user to have full administrator privilege. The following is a list of the server attributes….
pbs_resources_unicosmk2 – pbs resources under Unicos MK2 Description This page summarizes the resources and special features supported by PBS for Cray Research computers running Unicos MK version 2. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script. Resources cput Maximum…
pbs_resources_unicos – pbs resources under Unicos Description This page summarizes the resources and special features supported by PBS for Cray Research computers running Unicos versions 8 and 9. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script. Resources ncpus Maximum…
pbs_resources_sunos4 – pbs resources on SunOS 4 Description This page summarizes the resources supported by PBS for Sun workstations running SunOS 4.x. These resources are specified by including them in the -l option argument on the qsub or qalter command or in the PBS job script. Resources cput Maximum amount of CPU time used by…