Section 5: file formats
pam.conf, pam.d – PAM configuration files Description When a PAM aware privilege granting application is started, it activates its attachment to the PAM-API. This activation performs a number of tasks, the most important being the reading of the configuration file(s): /etc/pam.conf. Alternatively, this may be the contents of the /etc/pam.d/ directory. The presence of this…
pam.conf, pam.d – PAM configuration files Description When a PAM aware privilege granting application is started, it activates its attachment to the PAM-API. This activation performs a number of tasks, the most important being the reading of the configuration file(s): /etc/pam.conf. Alternatively, this may be the contents of the /etc/pam.d/ directory. The presence of this…
package.json — Specifics of npm’s package.json handling Description This document is all you need to know about what’s required in your package.json file. It must be actual JSON, not just a JavaScript object literal. A lot of the behavior described in this document is affected by the config npm help settings described in npm-config. Default…
package-locks – An explanation of npm lockfiles Description Conceptually, the "input" to npm help install is a npm help package.json, while its "output" is a fully-formed node_modules tree: a representation of the dependencies you declared. In an ideal world, npm would work like a pure function: the same package.json should produce the exact same node_modules…
package-lock.json – A manifestation of the manifest Description package-lock.json is automatically generated for any operations where npm modifies either the node_modules tree, or package.json. It describes the exact tree that was generated, such that subsequent installs are able to generate identical trees, regardless of intermediate dependency updates. This file is intended to be committed into…
package.json – Specifics of npm’s package.json handling Description This document is all you need to know about what’s required in your package.json file. It must be actual JSON, not just a JavaScript object literal. A lot of the behavior described in this document is affected by the config settings described in npm help 7 npm-config….
ovs-vswitchd46conf46db – Open_vSwitch database schema A database with this schema holds the configuration for one Open vSwitch daemon46 The top-level configuration for the daemon is the Open_vSwitch table, which must have exactly one record46 Records in other tables are significant only when they can be reached directly or indirectly from the Open_vSwitch table46 Records that…
logwatch.conf, ignore.conf, override.conf – logwatch configuration files Description logwatch.conf – ( /etc/logwatch/conf/logwatch.conf ) – can contain the local configuration options. The list of valid settings and their default values are in /usr/share/logwatch/default.conf/logwatch.conf. ignore.conf – ( /etc/logwatch/conf/ignore.conf ) is the list of regular expressions. The set of logs decribed by this set is ignored by logwatch….
ovdb – Overview storage method for INN Description Ovdb is a storage method that uses the Berkeley DB library to store overview data. It requires version 4.4 or later of the Berkeley DB library (4.7+ is recommended because older versions suffer from various issues). Ovdb makes use of the full transaction/logging/locking functionality of the Berkeley DB environment. Berkeley DB…
outlook.pst – format of MS Outlook .pst file Synopsis outlook.pst Overview Low level or primitive items in a .pst file are identified by an I_ID value. Higher level or composite items in a .pst file are identified by a D_ID value. There are two separate b-trees indexed by these I_ID and D_ID values. Starting with…
outlook.pst – format of MS Outlook .pst file Synopsis outlook.pst Overview Low level or primitive items in a .pst file are identified by an I_ID value. Higher level or composite items in a .pst file are identified by a D_ID value. There are two separate b-trees indexed by these I_ID and D_ID values. Starting with…
os-release, initrd-release – Operating system identification Synopsis /etc/os-release /usr/lib/os-release /etc/initrd-release Description The /etc/os-release and /usr/lib/os-release files contain operating system identification data. The basic file format of os-release is a newline-separated list of environment-like shell-compatible variable assignments. It is possible to source the configuration from shell scripts, however, beyond mere variable assignments, no shell features are…
org.freedesktop.timedate1 – The D-Bus interface of systemd-timedated Introduction systemd-timedated.service(8) is a system service that can be used to control the system time and related settings. This page describes the D-Bus interface. The D-Bus Api The service exposes the following interfaces on the bus: node /org/freedesktop/timedate1 { interface org.freedesktop.timedate1 { methods: SetTime(in x usec_utc, in b…
org.freedesktop.systemd1 – The D-Bus interface of systemd Introduction systemd(1) and its auxiliary daemons expose a number of APIs over D-Bus. This page only describes the various APIs exposed by the system and service manager itself. It does not cover the auxiliary daemons. The service manager exposes a number of objects on the bus: one Manager…
org.freedesktop.resolve1 – The D-Bus interface of systemd-resolved Introduction systemd-resolved.service(8) is a system service that provides hostname resolution and caching using DNS, LLMNR, and mDNS. It also does DNSSEC validation. This page describes the resolve semantics and the D-Bus interface. This page contains an API reference only. If you are looking for a longer explanation how…
org.freedesktop.portable1 – The D-Bus interface of systemd-portabled Introduction systemd-portabled.service(8) is a system service that may be used to attach, detach and inspect portable services. This page describes the D-Bus interface. The Manager Object The service exposes the following interfaces on the Manager object on the bus: node /org/freedesktop/portable1 { interface org.freedesktop.portable1.Manager { methods: GetImage(in s…
org.freedesktop.machine1 – The D-Bus interface of systemd-machined Introduction systemd-machined.service(8) is a system service that keeps track of locally running virtual machines and containers. This page describes the D-Bus interface. The Manager Object The service exposes the following interfaces on the Manager object on the bus: node /org/freedesktop/machine1 { interface org.freedesktop.machine1.Manager { methods: GetMachine(in s name,…
org.freedesktop.login1 – The D-Bus interface of systemd-logind Introduction systemd-logind.service(8) is a system service that keeps track of user logins and seats. The daemon provides both a C library interface as well as a D-Bus interface. The library interface may be used to introspect and watch the state of user logins and seats. The bus interface…
org.freedesktop.locale1 – The D-Bus interface of systemd-localed Introduction systemd-localed.service(8) is a system service that can be used to control the system locale and keyboard mapping from user programs. This page describes the D-Bus interface. The D-Bus Api The service exposes the following interfaces on the bus: node /org/freedesktop/locale1 { interface org.freedesktop.locale1 { methods: SetLocale(in as…
org.freedesktop.import1 – The D-Bus interface of systemd-importd Introduction systemd-importd.service(8) is a system service which may be used to import, export and download additional system images. These images can be used by tools such as systemd-nspawn(1) to run local containers. The service is used as the backend for machinectl pull-raw, machinectl pull-tar and related commands. This…