tripathysagar/man_text huggingface dataset:
# vconsole.conf

## NAME



           vconsole.conf - Configuration file for the virtual console
    


## SYNOPSIS



           /etc/vconsole.conf
    


## DESCRIPTION



           The /etc/vconsole.conf file configures the virtual console, i.e.
           keyboard mapping and console font. It is applied at boot by udev
           using 90-vconsole.rules file. You can safely mask this file if you
           want to avoid this kind of initialization.
    
           The format of vconsole.conf is a newline-separated list of
           environment-like shell-compatible variable assignments, ignoring
           comments and empty lines. It is possible to source the
           configuration from shell scripts, however, beyond mere variable
           assignments no shell features are supported, allowing applications
           to read the file without implementing a shell compatible execution
           engine. See os-release(5) for a detailed description of the
           format.
    
           Note that the kernel command line options _vconsole.keymap=_ ,
           _vconsole.keymap_toggle=_ , _vconsole.font=_ , _vconsole.font_map=_ ,
           _vconsole.font_unimap=_ may be used to override the console settings
           at boot.
    
           Depending on the operating system other configuration files might
           be checked for configuration of the virtual console as well,
           however only as fallback.
    
           /etc/vconsole.conf is usually created and updated using
           systemd-localed.service(8).  localectl(1) may be used to instruct
           **systemd-localed.service** to query or update configuration.
    


## OPTIONS



           The following options are understood:
    
           _KEYMAP=_ , _KEYMAP_TOGGLE=_
               Configures the key mapping table for the keyboard.  _KEYMAP=_
               defaults to "us" if not set. Specially, if "@kernel" is
               specified, no keymap will be loaded, i.e. the kernel's default
               keymap is used. The _KEYMAP_TOGGLE=_ can be used to configure a
               second toggle keymap and is by default unset.
    
           _FONT=_ , _FONT_MAP=_ , _FONT_UNIMAP=_
               Configures the console font, the console map and the unicode
               font map.
    


## KERNEL COMMAND LINE



           A few configuration parameters from vconsole.conf may be
           overridden on the kernel command line:
    
           _vconsole.keymap=_ , _vconsole.keymap_toggle=_
               Overrides _KEYMAP=_ and _KEYMAP_TOGGLE=_.
    
               Added in version 232.
    
           _vconsole.font=_ , _vconsole.font_map=_ , _vconsole.font_unimap=_
               Overrides _FONT=_ , _FONT_MAP=_ , and _FONT_UNIMAP=_.
    
               Added in version 232.
    


## EXAMPLE



           **Example 1. German keyboard and console**
    
           /etc/vconsole.conf:
    
               KEYMAP=de-latin1
               FONT=eurlatgr
    


* * *
# auditd.cron

## NAME



           auditd.conf - time-based rotation of audit logs
    


## DESCRIPTION



           By default, the audit daemon (auditd) supports size-based log
           rotation, where logs are rotated once they reach a specified size,
           as configured in _/etc/audit/auditd.conf._  This manual describes an
           alternative method: time-based log rotation using **cron.** Using
           this approach, audit logs can be rotated at specified intervals
           (hourly, daily, weekly or on a custom date), regardless of their
           size.
    


## CONFIGURATION



           **1.Disable Size-Based Rotation:**
    
           To enable time-based log rotation, first disable **auditd's** built-in
           size-based rotation by setting the following parameter in
           _/etc/audit/auditd.conf:_
    
                  max_log_file_action = ignore
    
           **2. Configure Log Retention:**
    
           The **num_logs** parameter determines the number of rotated log files
           to keep. For daily rotation, setting
    
                  num_logs = 7
    
           ensures that logs from the last seven days are retained. However,
           on busy systems, audit logs may grow rapidly, potentially leading
           to a lack of disk space. To prevent this, ensure that the
           **space_left_action** parameter is configured to handle low-disk-space
           situations appropriately.
    
           **3. Apply Configuration Changes:**
    
           After modifying the main auditd configuration file, reload auditd
           to apply the changes:
    
                  auditctl --signal reload
    
           **4. Deploy the Rotation Script:**
    
           Copy the provided **auditd.cron** script to the appropriate cron
           directory ( _cron.daily_ or _cron.hourly_ or _cron.weekly_ , depending
           on your rotation preference). Then, ensure the file has the
           correct SELinux labels:
    
                  cp /usr/share/doc/audit/auditd.cron /etc/cron.daily
    


* * *
# gshadow

## NAME



           gshadow - shadowed group file
    


## DESCRIPTION



           /etc/gshadow contains the shadowed information for group accounts.
    
           This file must not be readable by regular users if password
           security is to be maintained.
    
           Each line of this file contains the following colon-separated
           fields:
    
           **group name**
               It must be a valid group name, which exists on the system.
    
           **encrypted password**
               Refer to crypt(3) for details on how this string is
               interpreted.
    
               If the password field contains some string that is not a valid
               result of crypt(3), for instance ! or *, users will not be
               able to use a unix password to access the group (but group
               members do not need the password).
    
               The password is used when a user who is not a member of the
               group wants to gain the permissions of this group (see
               newgrp(1)).
    
               This field may be empty, in which case only the group members
               can gain the group permissions.
    
               A password field which starts with an exclamation mark means
               that the password is locked. The remaining characters on the
               line represent the password field before the password was
               locked.
    
               This password supersedes any password specified in /etc/group.
    
           **administrators**
               It must be a comma-separated list of user names.
    
               Administrators can change the password or the members of the
               group.
    
               Administrators also have the same permissions as the members
               (see below).
    
           **members**
               It must be a comma-separated list of user names.
    
               Members can access the group without being prompted for a
               password.
    
               You should use the same list of users as in /etc/group.
    


## FILES



           /etc/group
               Group account information.
    
           /etc/gshadow
               Secure group account information.
    


* * *
# proc_cmdline

## NAME



           /proc/cmdline - kernel boot arguments
    


## DESCRIPTION



           _/proc/cmdline_
                  Arguments passed to the Linux kernel at boot time.  Often
                  done via a boot manager such as **lilo**(8) or **grub**(8).  Any
                  arguments embedded in the kernel image or initramfs via
                  **CONFIG_BOOT_CONFIG** will also be displayed.
    


* * *
# proc_pid_statm

## NAME



           /proc/pid/statm - memory usage information
    


## DESCRIPTION



           _/proc/_ pid _/statm_
                  Provides information about memory usage, measured in pages.
                  The columns are:
    
                      size       (1) total program size
                                 (same as VmSize in _/proc/_ pid _/status_)
                      resident   (2) resident set size
                                 (inaccurate; same as VmRSS in _/proc/_ pid _/status_)
                      shared     (3) number of resident shared pages
                                 (i.e., backed by a file)
                                 (inaccurate; same as RssFile+RssShmem in
                                 _/proc/_ pid _/status_)
                      text       (4) text (code)
                      lib        (5) library (unused since Linux 2.6; always 0)
                      data       (6) data + stack
                      dt         (7) dirty pages (unused since Linux 2.6; always 0)
    
                  Some of these values are inaccurate because of a kernel-
                  internal scalability optimization.  If accurate values are
                  required, use _/proc/_ pid _/smaps_ or _/proc/_ pid _/smaps_rollup_
                  instead, which are much slower but provide accurate,
                  detailed information.
    


* * *
# proc_pid_root

## NAME



           /proc/pid/root/ - symbolic link to root directory
    


## DESCRIPTION



           _/proc/_ pid _/root/_
                  UNIX and Linux support the idea of a per-process root of
                  the filesystem, set by the chroot(2) system call.  This
                  file is a symbolic link that points to the process's root
                  directory, and behaves in the same way as _exe_ , and _fd/*_.
    
                  Note however that this file is not merely a symbolic link.
                  It provides the same view of the filesystem (including
                  namespaces and the set of per-process mounts) as the
                  process itself.  An example illustrates this point.  In one
                  terminal, we start a shell in new user and mount
                  namespaces, and in that shell we create some new mounts:
    
                      $ **PS1='sh1# ' unshare -Urnm** ;
                      sh1# **mount -t tmpfs tmpfs /etc** ;  # Mount empty tmpfs at /etc
                      sh1# **mount --bind /usr /dev** ;     # Mount /usr at /dev
                      sh1# **echo $$** ;
                      27123
    
                  In a second terminal window, in the initial mount
                  namespace, we look at the contents of the corresponding
                  mounts in the initial and new namespaces:
    
                      $ **PS1='sh2# ' sudo sh** ;
                      sh2# **ls /etc | wc -l** ;                  # In initial NS
                      309
                      sh2# **ls /proc/27123/root/etc | wc -l** ;  # /etc in other NS
                      0                                     # The empty tmpfs dir
                      sh2# **ls /dev | wc -l** ;                  # In initial NS
                      205
                      sh2# **ls /proc/27123/root/dev | wc -l** ;  # /dev in other NS
                      11                                    # Actually bind
                                                            # mounted to /usr
                      sh2# **ls /usr | wc -l** ;                  # /usr in initial NS
                      11
    
                  In a multithreaded process, the contents of the
                  _/proc/_ pid _/root_ symbolic link are not available if the main
                  thread has already terminated (typically by calling
                  pthread_exit(3)).
    
                  Permission to dereference or read (readlink(2)) this
                  symbolic link is governed by a ptrace access mode
                  **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    


* * *
# slapo-pbind

## NAME



           slapo-pbind - proxy bind overlay to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The **pbind** overlay to slapd(8) forwards Simple Binds on a local
           database to a remote LDAP server instead of processing them
           locally. The remote connection is managed using an instance of the
           ldap backend.
    
           The **pbind** overlay uses a subset of the _ldap_ backend's config
           directives. They are described in more detail in slapd-ldap(5).
    
           Note: this overlay is built into the _ldap_ backend; it is not a
           separate module.
    
           **overlay pbind**
                  This directive adds the proxy bind overlay to the current
                  backend.  The proxy bind overlay may be used with any
                  backend, but it is mainly intended for use with local
                  storage backends.
    
           **uri <ldapurl>**
                  LDAP server to use.
    
           **tls <TLS parameters>**
                  Specify the use of TLS.
    
           **network-timeout <time>**
                  Set the network timeout.
    
           **quarantine <quarantine parameters>**
                  Turns on quarantine of URIs that returned _LDAP_UNAVAILABLE_.
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


* * *
# service_seusers

## NAME



           service_seusers - The SELinux GNU/Linux user and service to
           SELinux user mapping configuration files
    


## DESCRIPTION



           These are optional files that allow services to define an SELinux
           user when authenticating via SELinux-aware login applications such
           as PAM(8).
    
           There is one file for each GNU/Linux user name that will be
           required to run a service with a specific SELinux user name.
    
           The path for each configuration file is formed by the path
           returned by selinux_policy_root(3) with _/logins/username_ appended
           (where _username_ is a file representing the GNU/Linux user name).
           The default services directory is located at:
                  _/etc/selinux/{SELINUXTYPE}/logins_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           **getseuser**(3) reads this file to map services to an SELinux user.
    


## FILE FORMAT



           Each line within the _username_ file is formatted as follows with
           each component separated by a colon:
                  _service_**:**_seuser_[**:**_range_]
    
           Where:
                  _service_
                         The service name used by the application.
                  _seuser_
                         The SELinux user name.
                  _range_
                         The range for MCS/MLS policies.
    


## EXAMPLES



           Example 1 - for the 'root' user:
                  # ./logins/root
                  ipa:user_u:s0
                  this_service:unconfined_u:s0
    
           Example 2 - for GNU/Linux user 'rch':
                  # ./logins/rch
                  ipa:unconfined_u:s0
                  that_service:unconfined_u:s0
    


* * *
# deb-origin

## NAME



           deb-origin - Vendor-specific information files
    


## SYNOPSIS



           **/usr/local/etc/dpkg/origins/**_filename_
    


## DESCRIPTION



           The files in **/usr/local/etc/dpkg/origins** can provide information
           about various vendors that are providing Debian packages.  These
           files are usually used both to determine the behavior of tools and
           resulting contents during package builds targeting a specific
           vendor, and to describe the provenance of packages.
    
           Packages can explicitly declare their vendor by including an
           **Origin** field, otherwise the vendor for a package without such
           field is assumed to be the one pointed to by the _default_ origin
           symbolic link.
    
           They contain a number of fields, or comments when the line starts
           with ‘**#** ’.  Each field begins with a tag, such as **Vendor** or **Parent** ,
           followed by a colon and the body of the field.  Fields are
           delimited only by field tags.  In other words, field text may be
           multiple lines in length, but the tools will join lines when
           processing the body of the field.
    
           The file should be named according to the vendor name.  The usual
           convention is to name the vendor file using the vendor name in all
           lowercase, but some variation is permitted.
    
           Namely (since dpkg 1.21.10), first, non-alphanumeric characters
           (‘**[^A-Za-z0-9]** ’) are mapped to dashes (‘**-** ’), then the resulting
           name will be tried in sequence by lower-casing it, keeping it as
           is, lower-casing then capitalizing it (that is upper-casing the
           first character), and only capitalizing it.
    


## FIELDS



           **Vendor:**_vendor-name_ (required)
               The value of this field determines the vendor name.
    
           **Vendor-URL:**_vendor-url_
               The value of this field determines the vendor URL.
    
           **Bugs:**_bug-url_
               The value of this field determines the type and address of the
               bug tracking system used by this vendor.  It can be a mailto
               URL or a debbugs URL (e.g., debbugs://bugs.debian.org/).
    
           **Parent:**_vendor-name_
               The value of this field determines the vendor name of the
               vendor that this vendor derives from.
    


## EXAMPLE



            Vendor: Debian
            Vendor-URL: https://www.debian.org/
            Bugs: debbugs://bugs.debian.org
    


* * *
# lxc.system.conf

## NAME



           lxc.system.conf - LXC system configuration file
    


## DESCRIPTION



           The system configuration is located at _/etc/lxc/lxc.conf_ or
           _~/.config/lxc/lxc.conf_ for unprivileged containers.
    
           This configuration file is used to set values such as default
           lookup paths and storage backend settings for LXC.
    
       **CONFIGURATION PATHS**
           **lxc.lxcpath**
                  The location in which all containers are stored.
    
           **lxc.default_config**
                  The path to the default container configuration.
    
       **CONTROL GROUPS**
           **lxc.cgroup.use**
                  Comma separated list of cgroup controllers to setup.  If
                  none is specified, all available controllers will be used.
    
           **lxc.cgroup.pattern**
                  Format string used to generate the cgroup path (e.g.
                  lxc/%n).
    
       **LVM**
           **lxc.bdev.lvm.vg**
                  Default LVM volume group name.
    
           **lxc.bdev.lvm.thin_pool**
                  Default LVM thin pool name.
    
       **ZFS**
           **lxc.bdev.zfs.root**
                  Default ZFS root name.
    
    **%%%SH%%%**
           **lxc**(1), lxc.container.conf(5), lxc.system.conf(5), lxc-usernet(5)
    


* * *
# ttytype

## NAME



           ttytype - terminal device to default terminal type mapping
    


## DESCRIPTION



           The _/etc/ttytype_ file associates termcap(5) and terminfo(5)
           terminal type names with tty lines.  Each line consists of a
           terminal type, followed by whitespace, followed by a tty name (a
           device name without the _/dev/_ prefix).
    
           This association is used by the program tset(1) to set the
           environment variable **TERM** to the default terminal name for the
           user's current tty.
    
           This facility was designed for a traditional time-sharing
           environment featuring character-cell terminals hardwired to a UNIX
           minicomputer.  It is little used on modern workstation and
           personal UNIX systems.
    


## FILES



           _/etc/ttytype_
                  the tty definitions file.
    


## EXAMPLES



           A typical _/etc/ttytype_ is:
    
               con80x25 tty1
               vt320 ttys0
    


* * *
# proc_pci

## NAME



           /proc/pci - PCI devices
    


## DESCRIPTION



           _/proc/pci_
                  This is a listing of all PCI devices found during kernel
                  initialization and their configuration.
    
                  This file has been deprecated in favor of a new _/proc_
                  interface for PCI (_/proc/bus/pci_).  It became optional in
                  Linux 2.2 (available with **CONFIG_PCI_OLD_PROC** set at kernel
                  compilation).  It became once more nonoptionally enabled in
                  Linux 2.4.  Next, it was deprecated in Linux 2.6 (still
                  available with **CONFIG_PCI_LEGACY_PROC** set), and finally
                  removed altogether since Linux 2.6.17.
    


* * *
# slapo-collect

## NAME



           slapo-collect - Collective attributes overlay to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The collect overlay is used to provide a relatively coarse
           implementation of RFC 3671 collective attributes.  In X.500, a
           collective attribute is "a user attribute whose values are the
           same for each member of an entry collection".
    
           Collective attributes are added to entries returned by a search
           operation when the entry is within the scope of the related
           ancestor.  Collective attributes can only be modified when the
           modification affects the related ancestor.
    


## CONFIGURATION



           This **slapd.conf** option applies to the collect overlay.  It should
           appear after the **overlay** directive.
    
           **collectinfo <DN> <attrlist>**
                  Specify the **DN** of the ancestor entry and the set of related
                  collective attributes, where **attrlist** is a comma-separated
                  list of attributes.  The **DN** should be within the naming
                  context of the database.
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


## ACKNOWLEDGEMENTS



           This module was written in 2003 by Howard Chu.  This man page was
           written in 2008 by Pierangelo Masarati.  **OpenLDAP Software** is
           developed and maintained by The OpenLDAP Project
           <http://www.openldap.org/>.  **OpenLDAP Software** is derived from the
           University of Michigan LDAP 3.3 Release.
    


* * *
# proc_kallsyms

## NAME



           /proc/kallsyms - kernel exported symbols
    


## DESCRIPTION



           _/proc/kallsyms_ (since Linux 2.5.71)
                  This holds the kernel exported symbol definitions used by
                  the **modules**(X) tools to dynamically link and bind loadable
                  modules.  In Linux 2.5.47 and earlier, a similar file with
                  slightly different syntax was named _ksyms_.
    


* * *
# dpkg.cfg

## NAME



           dpkg.cfg - dpkg configuration file
    


## DESCRIPTION



           This file contains default options for dpkg.  Each line contains a
           single option which is exactly the same as a normal command line
           option for dpkg except for the leading hyphens which are not used
           here.  Quotes surrounding option values are stripped.  Comments
           are allowed by starting a line with a hash sign (‘**#** ’).
    


## FILES



           _/usr/local/etc/dpkg/dpkg.cfg.d/[0-9a-zA-Z_-]*_
    
           _/usr/local/etc/dpkg/dpkg.cfg_
    
           _~/.dpkg.cfg_
    


* * *
# aliases

## NAME



           **aliases** — aliases file for smtpd
    


## DESCRIPTION



           This manual page describes the format of the **aliases** file, as used
           by _smtpd_(8).  An alias, in its simplest form, is used to assign an
           arbitrary name to an email address or a group of email addresses.
           This provides a convenient way to send mail.  For example an alias
           could refer to all users of a group: email to that alias would be
           sent to all members of the group.  Much more complex aliases can
           be defined however: an alias can refer to other aliases, be used
           to send mail to a file instead of another person, or to execute
           various commands.
    
           Within the file, ‘#’ is a comment delimiter; anything placed after
           it is discarded.  The file consists of key/value mappings of the
           form:
    
                 key: value1, value2, value3, ...
    
           _key_ is always folded to lowercase before alias lookups to ensure
           that there can be no ambiguity.  The key is expanded to the
           corresponding values, which consist of one or more of the
           following:
    
           _user_    A user on the host machine.  The user must have a valid
                   entry in the _passwd_(5) database file.
    
           _/path/to/file_
                   Append messages to _file_ , specified by its absolute
                   pathname.
    
           |_command_
                   Pipe the message to _command_ on its standard input.  The
                   command is run under the privileges of the daemon's
                   unprivileged account.
    
           :_include_ :_/path/to/file_
                   Include any definitions in _file_ as alias entries.  The
                   format of the file is identical to this one.
    
           _user-part@domain-part_
                   An email address in RFC 5322 format.  If an address
                   extension is appended to the user-part, it is first
                   compared for an exact match.  It is then stripped so that
                   an address such as user+ext@example.com will only use the
                   part that precedes ‘+’ as a _key_.
    
           _error_ :_code message_
                   A status code and message to return.  The code must be 3
                   digits, starting 4XX (TempFail) or 5XX (PermFail).  The
                   message must be present and can be freely chosen.
    


## FILES



           _/etc/mail/aliases_     Default **aliases** file.
    


* * *
# repertoiremap

## NAME



           repertoiremap - map symbolic character names to Unicode code
           points
    


## DESCRIPTION



           A repertoire map defines mappings between symbolic character names
           (mnemonics) and Unicode code points when compiling a locale with
           localedef(1).  Using a repertoire map is optional, it is needed
           only when symbolic names are used instead of now preferred Unicode
           code points.
    
       **Syntax**
           The repertoiremap file starts with a header that may consist of
           the following keywords:
    
           _comment_char_
                  is followed by a character that will be used as the comment
                  character for the rest of the file.  It defaults to the
                  number sign (#).
    
           _escape_char_
                  is followed by a character that should be used as the
                  escape character for the rest of the file to mark
                  characters that should be interpreted in a special way.  It
                  defaults to the backslash (\).
    
           The mapping section starts with the keyword _CHARIDS_ in the first
           column.
    
           The mapping lines have the following form:
    
           _< symbolic-name> <code-point> comment_
                  This defines exactly one mapping, _comment_ being optional.
    
           The mapping section ends with the string _END CHARIDS_.
    


## FILES



           _/usr/share/i18n/repertoiremaps_
                  Usual default repertoire map path.
    


## STANDARDS



           POSIX.2.
    


## NOTES



           Repertoire maps are deprecated in favor of Unicode code points.
    


## EXAMPLES



           A mnemonic for the Euro sign can be defined as follows:
    
           <Eu> <U20AC> EURO SIGN
    


* * *
# erofs

## NAME



           erofs - the Enhanced Read-Only File System
    


## DESCRIPTION



           **erofs** is a create-once read-only filesystem, with support for
           compression and a multi-device backing store.
    
           There are two inode formats:
    
           •  32-byte compact with 16-bit UID/GID, 32-bit file size, and no
              file times
           •  64-byte extended with 32-bit UID/GID, 64-bit file size, and a
              modification time (_st_mtim_).
    
       **Mount options**
           **user_xattr**
           **nouser_xattr**
                  Controls whether _user_ extended attributes are exposed.
                  Defaults to yes.
    
           **acl**
           **noacl** Controls whether POSIX acl(5)s are exposed.  Defaults to
                  yes.
    
           **cache_strategy** =**disabled** |**readahead** |**readaround**
                  Cache allocation for compressed files: never, if reading
                  from start of file, regardless of position.  Defaults to
                  **readaround**.
    
           **dax**
           **dax** =**always** |**never**
                  Direct Access control.  If **always** and the source device
                  supports DAX, uncompressed non-inlined files will be read
                  directly, without going through the page cache.  **dax** is a
                  synonym for **always**.  Defaults to unset, which is equivalent
                  to **never**.
    
           **device** =_blobdev_
                  Add extra device holding some of the data.  Must be given
                  as many times and in the same order as **--blobdev** was to
                  **mkfs.erofs**(1).
    
           **domain_id** =_did_
           **fsid** =_id_
                  Control CacheFiles on-demand read support.  To be
                  documented.
    


## VERSIONS



           **erofs** images are versioned through the use of feature flags; these
           are listed in the **-E** section of **mkfs.erofs**(1),
    


## CONFIGURATION



           Linux must be configured with the **CONFIG_EROFS_FS** option to mount
           EROFS filesystems.  There are sub-configuration items that
           restrict the availability of some of the parameters above.
    


* * *
# classes.conf

## NAME



           classes.conf - class configuration file for cups
    


## DESCRIPTION



           The **classes.conf** file defines the local printer classes that are
           available.  It is normally located in the _/etc/cups_ directory and
           is maintained by the cupsd(8) program.  This file is not intended
           to be edited or managed manually.
    


## NOTES



           The name, location, and format of this file are an implementation
           detail that will change in future releases of CUPS.
    


* * *
# proc_pid_oom_score

## NAME



           /proc/pid/oom_score - OOM-killer score
    


## DESCRIPTION



           _/proc/_ pid _/oom_score_ (since Linux 2.6.11)
                  This file displays the current score that the kernel gives
                  to this process for the purpose of selecting a process for
                  the OOM-killer.  A higher score means that the process is
                  more likely to be selected by the OOM-killer.  The basis
                  for this score is the amount of memory used by the process,
                  with increases (+) or decreases (-) for factors including:
    
                  •  whether the process is privileged (-).
    
                  Before Linux 2.6.36 the following factors were also used in
                  the calculation of oom_score:
    
                  •  whether the process creates a lot of children using
                     fork(2) (+);
    
                  •  whether the process has been running a long time, or has
                     used a lot of CPU time (-);
    
                  •  whether the process has a low nice value (i.e., > 0)
                     (+); and
    
                  •  whether the process is making direct hardware access
                     (-).
    
                  The _oom_score_ also reflects the adjustment specified by the
                  _oom_score_adj_ or _oom_adj_ setting for the process.
    


* * *
# proc_kpagecgroup

## NAME



           /proc/kpagecgroup - memory cgroups
    


## DESCRIPTION



           _/proc/kpagecgroup_ (since Linux 4.3)
                  This file contains a 64-bit inode number of the memory
                  cgroup each page is charged to, indexed by page frame
                  number (see the discussion of _/proc/_ pid _/pagemap_).
    
                  The _/proc/kpagecgroup_ file is present only if the
                  **CONFIG_MEMCG** kernel configuration option is enabled.
    


* * *
# mime.convs

## NAME



           mime.convs - mime type conversion file for cups (deprecated)
    


## DESCRIPTION



           The **mime.convs** file defines the filters that are available for
           converting files from one format to another.  The standard filters
           support text, PDF, PostScript, and many types of image files.
    
           Additional filters are specified in files with the extension
           _.convs_ in the CUPS configuration directory.
    
           Each line in the **mime.convs** file is a comment, blank, or filter
           line.  Comment lines start with the # character.  Filter lines
           specify the source and destination MIME types along with a
           relative cost associated with the filter and the filter to run:
    
               source/type destination/type cost filter
    
           The _source/type_ field specifies the source MIME media type that is
           consumed by the filter.
    
           The _destination/type_ field specifies the destination MIME media
           type that is produced by the filter.
    
           The _cost_ field specifies the relative cost for running the filter.
           A value of 100 means that the filter uses a large amount of
           resources while a value of 0 means that the filter uses very few
           resources.
    
           The _filter_ field specifies the filter program filename.  Filenames
           are relative to the CUPS filter directory.
    


## FILES



           _/etc/cups_ - Typical CUPS configuration directory.
           _/usr/lib/cups/filter_ - Typical CUPS filter directory.
           _/usr/libexec/cups/filter_ - CUPS filter directory on macOS.
    


## EXAMPLES



           Define a filter that converts PostScript documents to CUPS Raster
           format:
    
               application/vnd.cups-postscript application/vnd.cups-raster 50 pstoraster
    


## NOTES



           CUPS filters are deprecated and will no longer be supported in a
           future feature release of CUPS.  Printers that do not support IPP
           can be supported using applications such as ippeveprinter(1).
    


* * *
# pwhistory.conf

## NAME



           pwhistory.conf - pam_pwhistory configuration file
    


## DESCRIPTION



           **pwhistory.conf** provides a way to configure the default settings
           for saving the last passwords for each user. This file is read by
           the _pam_pwhistory_ module and is the preferred method over
           configuring _pam_pwhistory_ directly.
    
           The file has a very simple _name = value_ format with possible
           comments starting with _#_ character. The whitespace at the
           beginning of line, end of line, and around the _=_ sign is ignored.
    


## OPTIONS



           **debug**
               Turns on debugging via syslog(3).
    
           **enforce_for_root**
               If this option is set, the check is enforced for root, too.
    
           **remember=**_N_
               The last _N_ passwords for each user are saved. The default is
               _10_. Value of _0_ makes the module to keep the existing contents
               of the opasswd file unchanged.
    
           **retry=**_N_
               Prompt user at most _N_ times before returning with error. The
               default is 1.
    
           **file=**_/path/filename_
               Store password history in file _/path/filename_ rather than the
               default location. The default location is
               /etc/security/opasswd.
    


## EXAMPLES



           /etc/security/pwhistory.conf file example:
    
               debug
               remember=5
               file=/tmp/opasswd
    


## FILES



           /etc/security/pwhistory.conf
               the config file for custom options
    


* * *
# proc_scsi

## NAME



           /proc/scsi/ - SCSI
    


## DESCRIPTION



           _/proc/scsi/_
                  A directory with the _scsi_ mid-level pseudo-file and various
                  SCSI low-level driver directories, which contain a file for
                  each SCSI host in this system, all of which give the status
                  of some part of the SCSI IO subsystem.  These files contain
                  ASCII structures and are, therefore, readable with cat(1).
    
                  You can also write to some of the files to reconfigure the
                  subsystem or switch certain features on or off.
    
           _/proc/scsi/scsi_
                  This is a listing of all SCSI devices known to the kernel.
                  The listing is similar to the one seen during bootup.  scsi
                  currently supports only the _add-single-device_ command which
                  allows root to add a hotplugged device to the list of known
                  devices.
    
                  The command
    
                      echo 'scsi add-single-device 1 0 5 0' > /proc/scsi/scsi
    
                  will cause host scsi1 to scan on SCSI channel 0 for a
                  device on ID 5 LUN 0.  If there is already a device known
                  on this address or the address is invalid, an error will be
                  returned.
    
           _/proc/scsi/_ drivername _/_
                  _drivername_ can currently be NCR53c7xx, aha152x, aha1542,
                  aha1740, aic7xxx, buslogic, eata_dma, eata_pio, fdomain,
                  in2000, pas16, qlogic, scsi_debug, seagate, t128, u15-24f,
                  ultrastore, or wd7000.  These directories show up for all
                  drivers that registered at least one SCSI HBA.  Every
                  directory contains one file per registered host.  Every
                  host-file is named after the number the host was assigned
                  during initialization.
    
                  Reading these files will usually show driver and host
                  configuration, statistics, and so on.
    
                  Writing to these files allows different things on different
                  hosts.  For example, with the _latency_ and _nolatency_
                  commands, root can switch on and off command latency
                  measurement code in the eata_dma driver.  With the _lockup_
                  and _unlock_ commands, root can control bus lockups simulated
                  by the scsi_debug driver.
    


* * *
# flatpak-installation

## NAME



           flatpak-installation - Configuration for an installation location
    


## DESCRIPTION



           flatpak can operate in system-wide or per-user mode. The
           system-wide data is located in $prefix/var/lib/flatpak/, and the
           per-user data is in $HOME/.local/share/flatpak/.
    
           In addition to the default installation locations, more
           system-wide installations can be defined via configuration files
           /etc/flatpak/installations.d/, which must have the .conf extension
           and follow the format described below.
    


## FILE FORMAT



           The installation config file format is using the same .ini file
           format that is used for systemd unit files or application .desktop
           files.
    
       **[Installation ...]**
           All the configuration for the the installation location with name
           NAME is contained in the [Installation "NAME"] group.
    
           The following keys are recognized:
    
           **Path**(string)
               The path for this installation. This key is mandatory.
    
           **DisplayName**(string)
               The name to use when showing this installation in the UI.
    
           **Priority**(integer)
               A priority for this installation.
    
           **StorageType**(string)
               The type of storage used for this installation. Possible
               values include: network, mmc, sdcard, harddisk.
    


## EXAMPLES



               [Installation "extra"]
               Path=/location/of/sdcard
               DisplayName=Extra Installation
               StorageType=sdcard
    


* * *
# motd

## NAME



           motd - message of the day
    


## DESCRIPTION



           The contents of _/etc/motd_ are displayed by login(1) after a
           successful login but just before it executes the login shell.
    
           The abbreviation "motd" stands for "message of the day", and this
           file has been traditionally used for exactly that (it requires
           much less disk space than mail to all users).
    


## FILES



           _/etc/motd_
    


* * *
# proc_pid_mem

## NAME



           /proc/pid/mem - memory
    


## DESCRIPTION



           _/proc/_ pid _/mem_
                  This file can be used to access the pages of a process's
                  memory through open(2), read(2), and lseek(2).
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_ATTACH_FSCREDS** check; see
                  ptrace(2).
    


* * *
# default_contexts

## NAME



           default_contexts - The SELinux default contexts configuration file
    


## DESCRIPTION



           The default contexts configuration file _default_contexts_ contains
           entries that allow SELinux-aware login applications such as PAM(8)
    
           SELinux-aware login applications generally use one or more of the
           following libselinux functions that read these files from the
           active policy path:
                  get_default_context(3)
                  get_ordered_context_list(3)
                  get_ordered_context_list_with_level(3)
                  get_default_context_with_level(3)
                  get_default_context_with_role(3)
                  get_default_context_with_rolelevel(3)
                  query_user_context(3)
                  manual_user_enter_context(3)
    
           The default context configuration file path for the active policy
           is returned by **selinux_default_contexts_path**(3). The default,
           default contexts file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/default_contexts_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    


## FILE FORMAT



           Each line in the default configuration file consists of the
           following:
                  _login_process user_login_process [user_login_process] ..._
    
           Where:
                  _login_process_
                         This consists of a _role_**:**_type_[**:**_range_] entry that
                         represents the login process context that are
                         defined in the policy.
                  _user_login_process_
                         This consists of one or more _role_**:**_type_[**:**_range_]
                         entries that represent the user login process
                         context defined in the policy.
    


## EXAMPLE



           # ./contexts/default_contexts
           system_r:crond_t:s0            system_r:system_crond_t:s0
           system_r:local_login_t:s0      user_r:user_t:s0 staff_r:staff_t:s0
           system_r:remote_login_t:s0     user_r:user_t:s0
           system_r:sshd_t:s0             user_r:user_t:s0
           system_r:sulogin_t:s0          sysadm_r:sysadm_t:s0
           system_r:xdm_t:s0              user_r:user_t:s0
    


* * *
# slapo-deref

## NAME



           slapo-deref - Dereference Control overlay to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    
           ETCDIR/slapd.d
    


## DESCRIPTION



           This overlay implements the draft Dereference control. The overlay
           can be used with any backend or globally for all backends.
    


## EXAMPLES



             database mdb
             ...
             overlay deref
    
           Given these entries:
             dn: cn=Howard Chu,ou=people,dc=example,dc=org
             objectClass: inetOrgPerson
             cn: Howard Chu
             sn: Chu
             uid: hyc
    
             dn: cn=Pierangelo Masarati,ou=people,dc=example,dc=org
             objectClass: inetOrgPerson
             cn: Pierangelo Masarati
             sn: Masarati
             uid: ando
    
             dn: cn=Test Group,ou=groups,dc=example,dc=org
             objectClass: groupOfNames
             cn: Test Group
             member: cn=Howard Chu,ou=people,dc=example,dc=org
             member: cn=Pierangelo Masarati,ou=people,dc=example,dc=org
    
           A search could be performed with a Dereference request control
           value specified as
    
             { member, uid }
    
           I.e.,
             ldapsearch -x -b dc=example,dc=org -E 'deref=member:uid'
    
           and the "cn=Test Group" entry would be returned with the response
           control value
             { { member, cn=Howard Chu,ou=people,dc=example,dc=org,
                 { { uid, [hyc] } } },
               { member, cn=Pierangelo Masarati,ou=people,dc=example,dc=org,
                 { { uid, [ando] } } } }
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    
           ETCDIR/slapd.d
                  default slapd configuration directory
    


* * *
# proc_pid_timerslack_ns

## NAME



           /proc/pid/timerslack_ns - timer slack in nanoseconds
    


## DESCRIPTION



           _/proc/_ pid _/timerslack_ns_ (since Linux 4.6)
                  This file exposes the process's "current" timer slack
                  value, expressed in nanoseconds.  The file is writable,
                  allowing the process's timer slack value to be changed.
                  Writing 0 to this file resets the "current" timer slack to
                  the "default" timer slack value.  For further details, see
                  the discussion of **PR_SET_TIMERSLACK** in prctl(2).
    
                  Initially, permission to access this file was governed by a
                  ptrace access mode **PTRACE_MODE_ATTACH_FSCREDS** check (see
                  ptrace(2)).  However, this was subsequently deemed too
                  strict a requirement (and had the side effect that
                  requiring a process to have the **CAP_SYS_PTRACE** capability
                  would also allow it to view and change any process's
                  memory).  Therefore, since Linux 4.9, only the (weaker)
                  **CAP_SYS_NICE** capability is required to access this file.
    


* * *