tripathysagar/man_text huggingface dataset:
# proc_profile

## NAME



           /proc/profile - kernel profiling
    


## DESCRIPTION



           _/proc/profile_ (since Linux 2.4)
                  This file is present only if the kernel was booted with the
                  _profile=1_ command-line option.  It exposes kernel profiling
                  information in a binary format for use by **readprofile**(1).
                  Writing (e.g., an empty string) to this file resets the
                  profiling counters; on some architectures, writing a binary
                  integer "profiling multiplier" of size _sizeof(int)_ sets the
                  profiling interrupt frequency.
    


* * *
# slapd-dnssrv

## NAME



           slapd-dnssrv - DNS SRV referral backend to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The DNSSRV backend to slapd(8) serves up referrals based upon SRV
           resource records held in the Domain Name System.
    
           This backend is experimental.
    


## CONFIGURATION



           The DNSSRV backend has no backend nor database specific options.
           It is configured simply by "database dnssrv" followed a suffix
           directive, e.g. suffix "".
    


## ACCESS CONTROL



           The **dnssrv** backend does not honor all ACL semantics as described
           in slapd.access(5).  In fact, this backend only implements the
           **search** operation when the **manageDSAit** control (RFC 3296) is used,
           otherwise for every operation a referral, whenever appropriate, or
           an error is returned.  Currently, there is no means to condition
           the returning of the referral by means of ACLs; no access control
           is implemented, except for **read (=r)** access to the returned
           entries, which is actually provided by the frontend.  Note,
           however, that the information returned by this backend is
           collected through the DNS, so it is public by definition.
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


* * *
# proc_pid_cgroup

## NAME



           /proc/pid/cgroup - control group
    


## DESCRIPTION



           _/proc/_ pid _/cgroup_ (since Linux 2.6.24)
                  See cgroups(7).
    


* * *
# proc_kpagecount

## NAME



           /proc/kpagecount - count of mappings of physical pages
    


## DESCRIPTION



           _/proc/kpagecount_ (since Linux 2.6.25)
                  This file contains a 64-bit count of the number of times
                  each physical page frame is mapped, indexed by page frame
                  number (see the discussion of _/proc/_ pid _/pagemap_).
    
                  The _/proc/kpagecount_ file is present only if the
                  **CONFIG_PROC_PAGE_MONITOR** kernel configuration option is
                  enabled.
    


* * *
# gdbinit

## NAME



           gdbinit - GDB initialization scripts
    


## SYNOPSIS



           ~/.config/gdb/gdbinit
    
           ~/.gdbinit
    
           ./.gdbinit
    


## DESCRIPTION



           These files contain GDB commands to automatically execute during
           GDB startup.  The lines of contents are canned sequences of
           commands, described in the GDB manual in node "Sequences" -- shell
           command "info -f gdb -n Sequences".
    
           Please read more in the GDB manual in node "Startup" -- shell
           command "info -f gdb -n Startup".
    
           **(not enabled with "--with-system-gdbinit" during compilation)**
               System-wide initialization file.  It is executed unless user
               specified GDB option "-nx" or "-n".  See more in the GDB
               manual in node "System-wide configuration" -- shell command
               "info -f gdb -n 'System-wide configuration'".
    
           **(not enabled with "--with-system-gdbinit-dir" during compilation)**
               System-wide initialization directory.  All files in this
               directory are executed on startup unless user specified GDB
               option "-nx" or "-n", as long as they have a recognized file
               extension.  See more in the GDB manual in node "System-wide
               configuration" -- shell command "info -f gdb -n 'System-wide
               configuration'".
    
           [1m~/.config/gdb/gdbinit[24m or _~/.gdbinit_
               User initialization file.  It is executed unless user
               specified GDB options "-nx", "-n" or "-nh".
    
           **.gdbinit**
               Initialization file for current directory.  It may need to be
               enabled with GDB security command "set auto-load
               local-gdbinit".  See more in the GDB manual in node "Init File
               in the Current Directory" -- shell command "info -f gdb -n
               'Init File in the Current Directory'".
    


## OPTIONS



    


## ENVIRONMENT



    


* * *
# proc_pid_setgroups

## NAME



           /proc/pid/setgroups - allow or deny setting groups
    


## DESCRIPTION



           _/proc/_ pid _/setgroups_ (since Linux 3.19)
                  See user_namespaces(7).
    


* * *
# zos-remote.conf

## NAME



           zos-remote.conf - the audisp-racf plugin configuration file
    


## DESCRIPTION



           **zos-remote.conf** controls the configuration for the
           audispd-zos-remote(8) Audit dispatcher plugin. The default
           location for this file is _/etc/audit/zos-remote.conf_ , however, a
           different file can be specified as the first argument to the
           **audispd-zos-remote** plugin. See audispd-zos-remote(8) and
           auditd(8).  The options available are as follows:
    
           _server_ This is the IBM z/OS ITDS server hostname or IP address
    
           _port_   The port number where ITDS is running on the z/OS server.
                  Default is 389 (ldap port)
    
           _user_   The z/OS RACF user ID which the audispd-zos-remote plugin
                  will use to perform Remote Audit requests. This user needs
                  READ access to FACILITY Class resource
                  IRR.LDAP.REMOTE.AUDIT (See audispd-zos-remote(8)).
    
           _password_
                  The password associated the the z/OS user ID configured
                  above.
    
           _timeout_
                  The number in seconds that **audispd-zos-remote** plugin will
                  wait before giving up in connection attempts and event
                  submissions. The default value is 15
    
           _q_depth_
                  The **audispd-zos-remote** plugin will queue inputted events to
                  the maximum of _q_depth_ events while trying to submit those
                  remotely. This can handle burst of events or in case of a
                  slow network connection. However, the **audispd-zos-remote**
                  plugin will drop events in case the queue is full. The
                  default queue depth is 64 - Increase this value in case you
                  are experiencing event drop due to full queue
                  (**audispd-zos-remote** will log this to syslog).
    


* * *
# quotatab

## NAME



           quotatab - Descriptions of devices with disk quotas
    


## SYNOPSIS



           **/etc/quotatab**
    


## DESCRIPTION



           The **quotatab** file lists human descriptions of devices for the
           purpose of warnquota(8) notifications.
    
           Each line consists of a device path name followed by a colon and a
           description. White space, apostrophe, and double quote characters
           surrounding the names and descriptions will be stripped. The
           description field can encode a new-line as a pipe character.
    
           Empty lines or lines starting with a hash sign or a semicolon are
           ignored.
    


## EXAMPLE



           # comment
           /dev/sda2: Home directories.|This becomes the second line.
    


## FILES



           **/etc/quotatab**
                  list of device descriptions
    


* * *
# proc_pid_clear_refs

## NAME



           /proc/pid/clear_refs - reset the PG_Referenced and ACCESSED/YOUNG
           bits
    


## DESCRIPTION



           _/proc/_ pid _/clear_refs_ (since Linux 2.6.22)
    
                  This is a write-only file, writable only by owner of the
                  process.
    
                  The following values may be written to the file:
    
                  1 (since Linux 2.6.22)
                         Reset the PG_Referenced and ACCESSED/YOUNG bits for
                         all the pages associated with the process.  (Before
                         Linux 2.6.32, writing any nonzero value to this file
                         had this effect.)
    
                  2 (since Linux 2.6.32)
                         Reset the PG_Referenced and ACCESSED/YOUNG bits for
                         all anonymous pages associated with the process.
    
                  3 (since Linux 2.6.32)
                         Reset the PG_Referenced and ACCESSED/YOUNG bits for
                         all file-mapped pages associated with the process.
    
                  Clearing the PG_Referenced and ACCESSED/YOUNG bits provides
                  a method to measure approximately how much memory a process
                  is using.  One first inspects the values in the
                  "Referenced" fields for the VMAs shown in _/proc/_ pid _/smaps_
                  to get an idea of the memory footprint of the process.  One
                  then clears the PG_Referenced and ACCESSED/YOUNG bits and,
                  after some measured time interval, once again inspects the
                  values in the "Referenced" fields to get an idea of the
                  change in memory footprint of the process during the
                  measured interval.  If one is interested only in inspecting
                  the selected mapping types, then the value 2 or 3 can be
                  used instead of 1.
    
                  Further values can be written to affect different
                  properties:
    
                  4 (since Linux 3.11)
                         Clear the soft-dirty bit for all the pages
                         associated with the process.  This is used (in
                         conjunction with _/proc/_ pid _/pagemap_) by the check-
                         point restore system to discover which pages of a
                         process have been dirtied since the file
                         _/proc/_ pid _/clear_refs_ was written to.
    
                  5 (since Linux 4.0)
                         Reset the peak resident set size ("high water mark")
                         to the process's current resident set size value.
    
                  Writing any value to _/proc/_ pid _/clear_refs_ other than those
                  listed above has no effect.
    
                  The _/proc/_ pid _/clear_refs_ file is present only if the
                  **CONFIG_PROC_PAGE_MONITOR** kernel configuration option is
                  enabled.
    


* * *
# labels.conf

## NAME



           **labels.conf** - Performance Co-Pilot labels configuration
    


## SYNOPSIS



           _/etc/pcp/labels.conf_
    


## DESCRIPTION



           Several Performance Co-Pilot (PCP) tools and utilities support the
           use of metric labels.  This functionality applied a hierarchical
           set of labels to each instance of every metric, as described in
           pmLookupLabels(3).
    
           The pmcd(1) and pmproxy(1) daemons are particularly important to
           the labels system, respectively providing the labels in real-time
           and then discovering recorded (archive) labels and indexing these
           for pmseries(1) queries using a distributed key-value service such
           as **https://valkey.io/ **.
    
           The _/etc/pcp/labels.conf_ file is a single point of configuration
           for behaviour affecting all labels exported by **pmcd** or through
           tools using PMAPI local context services.  It uses the common
           ``ini'' file format and any variable it specifies that is not in
           an explicit square-bracket enclosed section is considered a
           [global] variable.
    
           The available configuration variables are as follows :
    
           **machineid_hash** =_none_ |_sha256_
                When specified in the [global] section, controls the manner
                in which the local machine-id(5) is exported as a label.  The
                default setting (none) exports a "machineid" context label
                with value reflecting the contents of the _/etc/machine-id_
                file, on any platforms that provide this file.  The
                alternative (sha256) exports a "machineid_sha256" label,
                instead, and the value is the SHA256 (one-way) hash of the
                file.
    


* * *
# proc_pid_comm

## NAME



           /proc/pid/comm - command name
    


## DESCRIPTION



           _/proc/_ pid _/comm_ (since Linux 2.6.33)
                  This file exposes the process's _comm_ value—that is, the
                  command name associated with the process.  Different
                  threads in the same process may have different _comm_ values,
                  accessible via _/proc/_ pid _/task/_ tid _/comm_.  A thread may
                  modify its _comm_ value, or that of any of other thread in
                  the same thread group (see the discussion of **CLONE_THREAD**
                  in clone(2)), by writing to the file
                  _/proc/self/task/_ tid _/comm_.  Strings longer than
                  **TASK_COMM_LEN**(16) characters (including the terminating
                  null byte) are silently truncated.
    
                  This file provides a superset of the prctl(2) **PR_SET_NAME**
                  and **PR_GET_NAME** operations, and is employed by
                  pthread_setname_np(3) when used to rename threads other
                  than the caller.  The value in this file is used for the _%e_
                  specifier in _/proc/sys/kernel/core_pattern_ ; see core(5).
    


* * *
# proc_dma

## NAME



           /proc/dma - ISA DMA channels
    


## DESCRIPTION



           _/proc/dma_
                  This is a list of the registered _ISA_ DMA (direct memory
                  access) channels in use.
    


* * *
# proc_pid_task

## NAME



           /proc/pid/task/, /proc/tid/, /proc/thread-self/ - thread
           information
    


## DESCRIPTION



           _/proc/_ pid _/task/_ (since Linux 2.6.0)
                  This is a directory that contains one subdirectory for each
                  thread in the process.  The name of each subdirectory is
                  the numerical thread ID (_tid_) of the thread (see
                  gettid(2)).
    
                  Within each of these subdirectories, there is a set of
                  files with the same names and contents as under the
                  _/proc/_ pid directories.  For attributes that are shared by
                  all threads, the contents for each of the files under the
                  _task/_ tid subdirectories will be the same as in the
                  corresponding file in the parent _/proc/_ pid directory (e.g.,
                  in a multithreaded process, all of the _task/_ tid _/cwd_ files
                  will have the same value as the _/proc/_ pid _/cwd_ file in the
                  parent directory, since all of the threads in a process
                  share a working directory).  For attributes that are
                  distinct for each thread, the corresponding files under
                  _task/_ tid may have different values (e.g., various fields in
                  each of the _task/_ tid _/status_ files may be different for each
                  thread), or they might not exist in _/proc/_ pid at all.
    
                  In a multithreaded process, the contents of the
                  _/proc/_ pid _/task_ directory are not available if the main
                  thread has already terminated (typically by calling
                  pthread_exit(3)).
    
           _/proc/_ tid _/_
                  There  is a numerical subdirectory for each running thread
                  that is not a thread group leader (i.e., a thread whose
                  thread ID is not the same as its process ID); the
                  subdirectory is named by the thread ID.  Each one of these
                  subdirectories contains files and subdirectories exposing
                  information about the thread with the thread ID _tid_.  The
                  contents of these directories are the same as the
                  corresponding _/proc/_ pid _/task/_ tid directories.
    
                  The _/proc/_ tid subdirectories are _not_ visible when iterating
                  through _/proc_ with getdents(2) (and thus are _not_ visible
                  when one uses ls(1) to view the contents of _/proc_).
                  However, the pathnames of these directories are visible to
                  (i.e., usable as arguments in) system calls that operate on
                  pathnames.
    
           _/proc/thread-self/_ (since Linux 3.17)
                  This directory refers to the thread accessing the _/proc_
                  filesystem, and is identical to the _/proc/self/task/_ tid
                  directory named by the process thread ID (_tid_) of the same
                  thread.
    


* * *
# proc_iomem

## NAME



           /proc/iomem - I/O memory map
    


## DESCRIPTION



           _/proc/iomem_
                  I/O memory map in Linux 2.4.
    


* * *
# proc_apm

## NAME



           /proc/apm - advanced power management
    


## DESCRIPTION



           _/proc/apm_
                  Advanced power management version and battery information
                  when **CONFIG_APM** is defined at kernel compilation time.
    


* * *
# forward

## NAME



           **forward** — email forwarding information file
    


## DESCRIPTION



           Users may put a **.forward** file in their home directory.  If this
           file exists, _smtpd_(8) forwards email to the destinations specified
           therein.
    
           A **.forward** file contains a list of expansion values, as described
           in _aliases_(5).  Each expansion value should be on a line by
           itself.  Expansion is performed under the user ID of the **.forward**
           file owner.
    
           Permissions on the **.forward** file are very strict and expansion is
           rejected if the file is group or world-writable; if the home
           directory is group writeable; or if the file is not owned by the
           user.
    
           Users should avoid editing the **.forward** file directly, to prevent
           delivery failures from occurring if a message arrives while the
           file is not fully written.  The best option is to use a temporary
           file and use the _mv_(1) command to atomically overwrite the former
           **.forward**.  Alternatively, setting the _sticky_(8) bit on the home
           directory will cause the **.forward** lookup to return a temporary
           failure, causing mails to be deferred.
    


## FILES



           _~/.forward_     Email forwarding information.
    


## EXAMPLES



           The following file forwards mail to “user@example.com”, and pipes
           the same mail to “examplemda”.
    
                 # empty lines are ignored
    
                 user@example.com        # anything after # is ignored
                 "|/path/to/examplemda"
    


## CAVEATS



           The pipe ‘|’ and :include: mechanisms are not allowed for the root
           user.
    


* * *
# removable_context

## NAME



           removable_context - The SELinux removable devices context
           configuration file
    


## DESCRIPTION



           This file contains the default label that should be used for
           removable devices.
    
           selinux_removable_context_path(3) will return the active policy
           path to this file. The default removable context file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/removable_context_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    


## FILE FORMAT



           The file consists of a single line entry as follows:
                  _user_**:**_role_**:**_type_[**:**_range_]
    
           Where:
                  _user role type range_
                         A user, role, type and optional range (for MCS/MLS)
                         separated by colons (:) that will be applied to
                         removable devices.
    


## EXAMPLE



           # ./contexts/removable_contexts
           system_u:object_r:removable_t:s0
    


* * *
# sestatus.conf

## NAME



           sestatus.conf - The sestatus(8) configuration file.
    


## DESCRIPTION



           The _sestatus.conf_ file is used by the sestatus(8) command with the
           **-v** option to determine what file and process security contexts
           should be displayed.
    
           The fully qualified path name of the configuration file is:
                  _/etc/sestatus.conf_
    
           The file consists of two optional sections as described in the
           **FILE FORMAT** section. Whether these exist or not, the following
           will always be displayed:
                  The current process context
                  The init process context
                  The controlling terminal file context
    


## FILE FORMAT



           The format consists of two optional sections as follows:
                  **[files]**
                  _file_name_
                  _[file_name]_
                  _..._
    
                  **[process]**
                  _executable_file_name_
                  _[executable_file_name]_
                  _..._
    
           Where:
                  **[files]**
                         The start of the file list block.
                  _file_name_
                         One or more fully qualified file names, each on a
                         new line will that will have its context displayed.
                         If the file does not exist, then it is ignored. If
                         the file is a symbolic link, then **sestatus -v** will
                         also display the target file context.
    
                  **[process]**
                         The start of the process list block.
                  _executable_file_name_
                         One or more fully qualified executable file names
                         that should it be an active process, have its
                         context displayed. Each entry is on a new line.
    


## EXAMPLE



           # /etc/sestatus.conf
           [files]
           /etc/passwd
           /etc/shadow
           /bin/bash
           /bin/login
           /lib/libc.so.6
           /lib/ld-linux.so.2
           /lib/ld.so.1
    
           [process]
           /sbin/mingetty
           /sbin/agetty
           /usr/sbin/sshd
    


* * *
# lxc.conf

## NAME



           lxc.conf - Configuration files for LXC.
    


## DESCRIPTION



           LXC configuration is split in two parts. Container configuration
           and system configuration.
    
       **CONTAINER CONFIGURATION**
           The container configuration is held in the _config_ stored in the
           container's directory.
    
           A basic configuration is generated at container creation time with
           the default's recommended for the chosen template as well as extra
           default keys coming from the _default.conf_ file.
    
           That _default.conf_ file is either located at _/etc/lxc/default.conf_
           or for unprivileged containers at _~/.config/lxc/default.conf_.
    
           Details about the syntax of this file can be found in:
           lxc.container.conf(5)
    
       **SYSTEM CONFIGURATION**
           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.
    
           Details about the syntax of this file can be found in:
           lxc.system.conf(5)
    


* * *
# intro

## NAME



           intro - introduction to file formats and filesystems
    


## DESCRIPTION



           Section 5 of the manual describes various file formats, as well as
           the corresponding C structures, if any.
    
           In addition, this section contains a number of pages that document
           various filesystems.
    


## NOTES



       **Authors and copyright conditions**
           Look at the header of the manual page source for the author(s) and
           copyright conditions.  Note that these can be different from page
           to page!
    


* * *
# proc_interrupts

## NAME



           /proc/interrupts - number of interrupts
    


## DESCRIPTION



           _/proc/interrupts_
                  This is used to record the number of interrupts per CPU per
                  IO device.  Since Linux 2.6.24, for the i386 and x86-64
                  architectures, at least, this also includes interrupts
                  internal to the system (that is, not associated with a
                  device as such), such as NMI (nonmaskable interrupt), LOC
                  (local timer interrupt), and for SMP systems, TLB (TLB
                  flush interrupt), RES (rescheduling interrupt), CAL (remote
                  function call interrupt), and possibly others.  Very easy
                  to read formatting, done in ASCII.
    


* * *
# dselect.cfg

## NAME



           dselect.cfg - dselect configuration file
    


## DESCRIPTION



           This file contains default options for dselect.  Each line
           contains a single option which is exactly the same as a normal
           command line option for dselect 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/dselect.cfg.d/[0-9a-zA-Z_-]*_
    
           _/usr/local/etc/dpkg/dselect.cfg_
    
           _~/.dselect.cfg_
    


* * *
# slapd-wt

## NAME



           slapd-wt - WiredTiger backend to slapd
    


## SYNOPSIS



           **ETCDIR/slapd.conf**
    


## DESCRIPTION



           The **wt** backend to slapd(8) uses WiredTiger database library to
           store data.
    
           The **wt** backend is experimental module that have potential high
           write performance and high concurrency performance.  This backend
           have not some basic feature yet. Please backup data using slapcat
           before update the module.
    


## CONFIGURATION



           These **slapd.conf** options apply to the **wt** backend database.  That
           is, they must follow a "database wt" line and come before any
           subsequent "backend" or "database" lines.  Other database options
           are described in the slapd.conf(5) manual page.
    
           **directory** _< directory>_
                  Specify WiredTiger home directory that containing this
                  database and associated indexes live.  A separate directory
                  must be specified for each database.  The default is
                  **LOCALSTATEDIR/openldap-data**.
    
           **idlcache** _< boolean>_
                  Use the in-memory idlcache. The default is true.
    
           **index**{_< attrlist>_|**default**} [**pres** ,**eq** ,**approx** ,**sub** ,_< special>_]
                  Specify the indexes to maintain for the given attribute (or
                  list of attributes).  Some attributes only support a subset
                  of indexes.  If only an _< attr>_ is given, the indices
                  specified for **default** are maintained.  Note that setting a
                  default does not imply that all attributes will be indexed.
                  Also, for best performance, an **eq** index should always be
                  configured for the **objectClass** attribute.
    
           **mode** _< integer>_
                  back-wt does not support mode option. use umask instead.
    
           **wtconfig**{**create** ,**cache_size=512M** ,**async=(enabled)**}
                  Specify configuration for wiredtiger, This parameter is
                  pass to **wiredtiger_open**(3).
    
                  **create** create the database if it does not exist.
    
                  **cache_size**
                         maximum heap memory to allocate for the cache.
    
                  **async** asynchronous operations configuration options.
                         disabled by default.
    


## ACCESS CONTROL



           The **wt** backend honors access control semantics as indicated in
           slapd.access(5).
    


## FILES



           **ETCDIR/slapd.conf**
                  default **slapd** configuration file
    


## ACKNOWLEDGEMENTS



           **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.  Written by
           HAMANO Tsukasa <hamano@osstech.co.jp>.
    


* * *
# slapd-ldif

## NAME



           slapd-ldif - LDIF backend to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The LDIF backend to slapd(8) is a basic storage backend that
           stores entries in text files in LDIF format, and exploits the
           filesystem to create the tree structure of the database.  It is
           intended as a cheap, low performance easy to use backend, and it
           is exploited by higher-level internal structures to provide a
           permanent storage.
    


## CONFIGURATION



           These **slapd.conf** options apply to the LDIF backend database.  That
           is, they must follow a "database ldif" line and come before any
           subsequent "backend" or "database" lines.  Other database options
           are described in the slapd.conf(5) manual page.
    
           **directory <dir>**
                  Specify the directory where the database tree starts.  The
                  directory must exist and grant appropriate permissions
                  (rwx) to the identity slapd is running with.
    


## ACCESS CONTROL



           The **LDIF** backend does not honor any of the access control
           semantics described in slapd.access(5).  Only **read (=r)** access to
           the **entry** pseudo-attribute and to the other attribute values of
           the entries returned by the **search** operation is honored, which is
           performed by the frontend.
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


* * *
# cups-snmp.conf

## NAME



           snmp.conf - snmp configuration file for cups (deprecated)
    


## DESCRIPTION



           The **snmp.conf** file configures how the standard CUPS network
           backends (http, https, ipp, ipps, lpd, snmp, and socket) access
           printer information using SNMPv1 and is normally located in the
           _/etc/cups_ directory.  Each line in the file can be a configuration
           directive, a blank line, or a comment. Comment lines start with
           the # character.
    
           The Community and DebugLevel directives are used by all backends.
           The remainder apply only to the SNMP backend - cups-snmp(8).
    


## DIRECTIVES



           The following directives are understood by the CUPS network
           backends:
    
           **Address @IF(**_name_**)**
    
           **Address @LOCAL**
    
           **Address** _address_
                Sends SNMP broadcast queries (for discovery) to the specified
                address(es).  There is no default for the broadcast address.
    
           **Community** _name_
                Specifies the community name to use.  Only a single community
                name may be specified.  The default community name is
                "public".  If no name is specified, all SNMP functions are
                disabled.
    
           **DebugLevel** _number_
                Specifies the logging level from 0 (none) to 3 (everything).
                Typically only used for debugging (thus the name).  The
                default debug level is 0.
    
           **DeviceURI "**_regular expression_**"**_device-uri_ [... _device-uri_]
                Specifies one or more device URIs that should be used for a
                given make and model string.  The regular expression is used
                to match the detected make and model, and the device URI
                strings must be of the form "scheme://%s[:port]/[path]",
                where "%s" represents the detected address or hostname.
                There are no default device URI matching rules.
    
           **HostNameLookups on**
    
           **HostNameLookups off**
                Specifies whether the addresses of printers should be
                converted to hostnames or left as numeric IP addresses.  The
                default is "off".
    
           **MaxRunTime** _seconds_
                Specifies the maximum number of seconds that the SNMP backend
                will scan the network for printers.  The default is 120
                seconds (2 minutes).
    


## NOTES



           CUPS backends 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).
    


* * *
# proc_uptime

## NAME



           /proc/uptime - system uptime
    


## DESCRIPTION



           _/proc/uptime_
                  This file contains two numbers (values in seconds): the
                  uptime of the system (including time spent in suspend) and
                  the amount of time spent in the idle process.
    


* * *
# proc_sysvipc

## NAME



           /proc/sysvipc/ - System V IPC
    


## DESCRIPTION



           _/proc/sysvipc/_
                  Subdirectory containing the pseudo-files _msg_ , _sem_ and _shm_.
                  These files list the System V Interprocess Communication
                  (IPC) objects (respectively: message queues, semaphores,
                  and shared memory) that currently exist on the system,
                  providing similar information to that available via
                  ipcs(1).  These files have headers and are formatted (one
                  IPC object per line) for easy understanding.  sysvipc(7)
                  provides further background on the information shown by
                  these files.
    


* * *
# deb-conffiles

## NAME



           deb-conffiles - package conffiles
    


## SYNOPSIS



           **DEBIAN/conffiles**
    


## DESCRIPTION



           A package declares its list of conffiles by including a _conffiles_
           file in its control archive (i.e. _DEBIAN/conffiles_ during package
           creation).
    
           This file contains a list of files, one per line, with an optional
           leading flag separated by whitespace.  The conffiles must be
           listed as absolute pathnames.  Trailing whitespace will be
           trimmed, but empty or whitespace-only lines are not accepted.
    
           Files without a flag should exist in the binary package, otherwise
           dpkg(1) will ignore them.
    
           There is currently only one flag supported, **remove-on-upgrade** , to
           mark that a conffile needs to be removed on the next upgrade
           (since dpkg 1.20.6).  These files must not exist in the binary
           package, as both dpkg(1) and dpkg-deb(1) will not accept building
           nor processing such binary packages.
    


## EXAMPLE



            /usr/local/etc/alternatives/README
            /usr/local/etc/cron.daily/dpkg
            /usr/local/etc/dpkg/dpkg.cfg
            /usr/local/etc/logrotate.d/dpkg
            remove-on-upgrade /etc/some-old-file.conf
    


* * *
# failsafe_context

## NAME



           failsafe_context - The SELinux fail safe context configuration
           file
    


## DESCRIPTION



           The _failsafe_context_ file allows SELinux-aware applications such
           as PAM(8) to obtain a known valid login context for an
           administrator if no valid default entries can be found elsewhere.
    
           selinux_failsafe_context_path(3) will return the active policy
           path to this file. The default failsafe context file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/failsafe_context_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           The following functions read this file from the active policy path
           if they cannot obtain a default context:
                  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)
    


## FILE FORMAT



           The file consists of a single line entry as follows:
                  _role_**:**_type_[**:**_range_]
    
           Where:
                  _role type range_
                         A role, type and optional range (for MCS/MLS),
                         separated by colons (:) to form a valid login
                         process context for an administrator to access the
                         system.
    


## EXAMPLE



           # ./contexts/failsafe_context
           unconfined_r:unconfined_t:s0
    


* * *
# subuid

## NAME



           subuid - the configuration for subordinate user ids
    


## DESCRIPTION



           Subuid authorizes a user id to map ranges of user ids from its
           namespace into child namespaces.
    
           The delegation of the subordinate uids can be configured via the
           _subid_ field in /etc/nsswitch.conf file. Only one value can be set
           as the delegation source. Setting this field to _files_ configures
           the delegation of uids to /etc/subuid. Setting any other value
           treats the delegation as a plugin following with a name of the
           form _libsubid_$value.so_. If the value or plugin is missing, then
           the subordinate uid delegation falls back to _files_.
    
           Note, that **newusers** , **useradd** , and **usermod** will only create entries
           in /etc/subuid if subid delegation is managed via subid files.
    


## LOCAL SUBORDINATE DELEGATION



           Each line in /etc/subuid contains a user name and a range of
           subordinate user ids that user is allowed to use. This is
           specified with three fields delimited by colons (“:”). These
           fields are:
    
           •   login name or UID
    
           •   numerical subordinate user ID
    
           •   numerical subordinate user ID count
    
           This file specifies the user IDs that ordinary users can use, with
           the **newuidmap** command, to configure uid mapping in a user
           namespace.
    
           Multiple ranges may be specified per user.
    
           When large number of entries (10000-100000 or more) are defined in
           /etc/subuid, parsing performance penalty will become noticeable.
           In this case it is recommended to use UIDs instead of login names.
           Benchmarks have shown speed-ups up to 20x.
    


## FILES



           /etc/subuid
               Per user subordinate user IDs.
    
           /etc/subuid-
               Backup file for /etc/subuid.
    


* * *
# deb-postinst

## NAME



           deb-postinst - package post-installation maintainer script
    


## SYNOPSIS



           **DEBIAN/postinst**
    


## DESCRIPTION



           A package can perform several post-installation actions via
           maintainer scripts, by including an executable _postinst_ file in
           its control archive (i.e. _DEBIAN/postinst_ during package
           creation).
    
           The script can be called in the following ways:
    
           _postinst_ **configure** _old-version_
               After the package was installed.
    
           _postinst_ **triggered** "_trigger-name..._ "
               After the package was triggered.  The list of space-separated
               _trigger-name_ s is passed as the second argument.
    
           _old-postinst_ **abort-upgrade** _new-version_
               If _prerm_ fails during **upgrade** or fails on **failed-upgrade**.
    
           _old-postinst_ **abort-remove**
               If _prerm_ fails during **remove**.
    
           _postinst_ **abort-deconfigure in-favour** _new-package new-version_
                  [ **removing** _old-package old-version_ ]
               If _prerm_ fails during **deconfigure in-favour** of a package.
    
           _postinst_ **abort-remove in-favour** _new-package new-version_
               If _prerm_ fails during **remove in-favour** for replacement due to
               conflict.
    


* * *
# proc_pid_ns

## NAME



           /proc/pid/ns/ - namespaces
    


## DESCRIPTION



           _/proc/_ pid _/ns/_ (since Linux 3.0)
                  This is a subdirectory containing one entry for each
                  namespace that supports being manipulated by setns(2).  For
                  more information, see namespaces(7).
    


* * *
# proc_buddyinfo

## NAME



           /proc/buddyinfo - memory fragmentation
    


## DESCRIPTION



           _/proc/buddyinfo_
                  This file contains information which is used for diagnosing
                  memory fragmentation issues.  Each line starts with the
                  identification of the node and the name of the zone which
                  together identify a memory region.  This is then followed
                  by the count of available chunks of a certain order in
                  which these zones are split.  The size in bytes of a
                  certain order is given by the formula:
    
                      (2^order) * PAGE_SIZE
    
                  The binary buddy allocator algorithm inside the kernel will
                  split one chunk into two chunks of a smaller order (thus
                  with half the size) or combine two contiguous chunks into
                  one larger chunk of a higher order (thus with double the
                  size) to satisfy allocation requests and to counter memory
                  fragmentation.  The order matches the column number, when
                  starting to count at zero.
    
                  For example on an x86-64 system:
             Node 0, zone     DMA     1    1    1    0    2    1    1    0    1    1    3
             Node 0, zone   DMA32    65   47    4   81   52   28   13   10    5    1  404
             Node 0, zone  Normal   216   55  189  101   84   38   37   27    5    3  587
    
                  In this example, there is one node containing three zones
                  and there are 11 different chunk sizes.  If the page size
                  is 4 kilobytes, then the first zone called _DMA_ (on x86 the
                  first 16 megabyte of memory) has 1 chunk of 4 kilobytes
                  (order 0) available and has 3 chunks of 4 megabytes (order
                  10) available.
    
                  If the memory is heavily fragmented, the counters for
                  higher order chunks will be zero and allocation of large
                  contiguous areas will fail.
    
                  Further information about the zones can be found in
                  _/proc/zoneinfo_.
    


* * *
# libaudit.conf

## NAME



           libaudit.conf - libaudit configuration file
    


## DESCRIPTION



           The file _/etc/libaudit.conf_ contains configuration information for
           user space applications that link to libaudit. The applications
           are responsible for querying the settings in this file and obeying
           the admin's preferences. This file contains one configuration
           keyword per line, an equal sign, and then followed by appropriate
           configuration information. The keywords recognized are:
           _failure_action_.  These keywords are described below.
    
           _failure_action_
                  This keyword specifies what action the admin wishes a user
                  space application to take when there is a failure to send
                  an audit event to the kernel. The possible values are:
                  _IGNORE_
                   - meaning do nothing, _LOG_ - write to syslog the inability
                  to send an audit event, and _TERMINATE_ - the user space
                  application should exit.
    


* * *
# proc_slabinfo

## NAME



           /proc/slabinfo - kernel caches
    


## DESCRIPTION



           _/proc/slabinfo_
                  Information about kernel caches.  See slabinfo(5) for
                  details.
    


* * *
# proc_sys_user

## NAME



           /proc/sys/user/ - limits on the number of namespaces of various
           types
    


## DESCRIPTION



           _/proc/sys/user/_ (since Linux 4.9)
                  See namespaces(7).
    


* * *
# proc_zoneinfo

## NAME



           /proc/zoneinfo - memory zones
    


## DESCRIPTION



           _/proc/zoneinfo_ (since Linux 2.6.13)
                  This file displays information about memory zones.  This is
                  useful for analyzing virtual memory behavior.
    


* * *
# proc_sys_dev

## NAME



           /proc/sys/dev/ - device-specific information
    


## DESCRIPTION



           _/proc/sys/dev/_
                  This directory contains device-specific information (e.g.,
                  _dev/cdrom/info_).  On some systems, it may be empty.
    


* * *
# lxc-usernet

## NAME



           lxc-usernet - unprivileged user network administration file.
    


## DESCRIPTION



           _/etc/lxc/lxc-usernet_ controls the limits which the program **lxc-**
           **user-nic** places on network interfaces which an unprivileged user
           may create.
    
       **CONFIGURATION**
           This file consists of multiple entries, one per line, of the form:
    
           **user type bridge number**
    
           or
    
           **@group type bridge number**
    
           Where
    
           **user** is the username to whom this entry applies.
    
           **@group** is the groupname to which this entry applies.
    
           **type** is the type of network interface being allowed. Only veth
                  is currently supported.
    
           **bridge** is the bridge to which the network interfaces may be
                  attached, for instance _lxcbr0_.
    
           **number** is the number or quota of network interfaces of the given
                  type which the given user or group may attach to the given
                  bridge, for instance _2_.
    
           Since a user can be specified both by username as well as one or
           more usergroups, it is possible that several configuration lines
           enable that user to create network interfaces. In such cases, any
           interfaces create are counted towards the quotas of the user or
           group in the order in which they appear in the file. If the quota
           of one line is full, the rest will be parsed until one is found or
           the end of the file.
    


* * *
# proc_fb

## NAME



           /proc/fb - frame buffer
    


## DESCRIPTION



           _/proc/fb_
                  Frame buffer information when **CONFIG_FB** is defined during
                  kernel compilation.
    


* * *