tripathysagar/man_text huggingface dataset:
# proc_bus

## NAME



           /proc/bus/ - installed buses
    


## DESCRIPTION



           _/proc/bus/_
                  Contains subdirectories for installed buses.
    
           _/proc/bus/pccard/_
                  Subdirectory for PCMCIA devices when **CONFIG_PCMCIA** is set
                  at kernel compilation time.
    
           _/proc/bus/pccard/drivers_
    
           _/proc/bus/pci/_
                  Contains various bus subdirectories and pseudo-files
                  containing information about PCI buses, installed devices,
                  and device drivers.  Some of these files are not ASCII.
    
           _/proc/bus/pci/devices_
                  Information about PCI devices.  They may be accessed
                  through lspci(8) and setpci(8).
    


* * *
# proc_ioports

## NAME



           /proc/ioports - I/O port regions
    


## DESCRIPTION



           _/proc/ioports_
                  This is a list of currently registered Input-Output port
                  regions that are in use.
    


* * *
# deb-extra-override

## NAME



           deb-extra-override - Debian archive extra override file
    


## SYNOPSIS



           **override**
    


## DESCRIPTION



           While most information about a binary/source package can be found
           in the control/.dsc file, all of it can be overridden when it's
           exported to Packages/Sources files.  The extra override file
           contains those overrides.
    
           The extra override file has a simple whitespace-delimited format.
           Comments are allowed (denoted with a **#**).
    
               _package field-name value_
    
           _package_ is the name of the binary/source package.
    
           _field-name_ is the name of the field that is overridden.
    
           _value_ is the value to put in the field.  It can contain spaces as
           the line is split in no more than 3 columns when it's parsed.
    
           The extra override files used to make the official Packages lists
           may be found in the _indices_ directory on any Debian mirror.
    


* * *
# deb-src-rules

## NAME



           deb-src-rules - Debian source package rules file
    


## SYNOPSIS



           **debian/rules**
    


## DESCRIPTION



           This file contains the instructions necessary to build the binary
           packages from the source package.
    
           The _debian/rules_ file is an executable Makefile, with a shebang
           that is usually set to "#!/usr/bin/make -f".
    
           It must support the following make targets:
    
           **clean**
               Clean up the source tree, by undoing any change done by any of
               the build and binary targets.  This target will be called with
               root privileges.
    
           **build-indep**
               Build architecture independent files required to build any
               architecture independent binary package.  If there are no
               architecture independent binary packages to generate, the
               target must still exist but do nothing.  This target must not
               require root privileges.
    
           **build-arch**
               Build architecture dependent files required to build any
               architecture dependent binary package.  If there are no
               architecture dependent binary packages to generate, the target
               must still exist but do nothing.  This target must not require
               root privileges.
    
           **build**
               Build architecture independent and dependent files, either by
               depending (at least transitively) on **build-indep** and/or **build-**
               **arch** or by inlining what those targets would do.  This target
               must not require root privileges.
    
           **binary-indep**
               Build architecture independent binary packages.  This target
               must depend (at least transitively) on either **build-indep** or
               **build**.  This target will be called with root privileges.
    
           **binary-arch**
               Build architecture dependent binary packages.  This target
               must depend (at least transitively) on either **build-arch** or
               **build**.  This target will be called with root privileges.
    
           **binary**
               Build architecture independent and dependent binary packages,
               either by depending (at least transitively) on **binary-indep**
               and/or **binary-arch** or by inlining what those targets would do.
               This target will be called with root privileges.
    


* * *
# ethers

## NAME



           ethers - Ethernet address to IP number database
    


## DESCRIPTION



           **/etc/ethers** contains 48 bit Ethernet addresses and their
           corresponding IP numbers, one line for each IP number:
    
                  _Ethernet-address_  _IP-number_
    
           The two items are separated by any number of SPACE and/or TAB
           characters.  A **#** at the beginning of a line starts a comment which
           extends to the end of the line.  The _Ethernet-address_ is written
           as _x_ :_x_ :_x_ :_x_ :_x_ :_x_ , where _x_ is a hexadecimal number between **0** and **ff**
           which represents one byte of the address, which is in network byte
           order (big-endian).  The _IP-number_ may be a hostname which can be
           resolved by DNS or a dot separated number.
    


## EXAMPLES



           08:00:20:00:61:CA  pal
    


## FILES



           /etc/ethers
    


* * *
# shells

## NAME



           shells - pathnames of valid login shells
    


## DESCRIPTION



           _/etc/shells_ is a text file which contains the full pathnames of
           valid login shells.  This file is consulted by chsh(1) and
           available to be queried by other programs.
    
           Be aware that there are programs which consult this file to find
           out if a user is a normal user; for example, FTP daemons
           traditionally disallow access to users with shells not included in
           this file.
    


## FILES



           _/etc/shells_
    


## EXAMPLES



           _/etc/shells_ may contain the following paths:
    
               _/bin/sh_
               _/bin/bash_
               _/bin/csh_
    


* * *
# proc_filesystems

## NAME



           /proc/filesystems - supported filesystems
    


## DESCRIPTION



           _/proc/filesystems_
                  A text listing of the filesystems which are supported by
                  the kernel, namely filesystems which were compiled into the
                  kernel or whose kernel modules are currently loaded.  (See
                  also filesystems(5).)  If a filesystem is marked with
                  "nodev", this means that it does not require a block device
                  to be mounted (e.g., virtual filesystem, network
                  filesystem).
    
                  Incidentally, this file may be used by mount(8) when no
                  filesystem is specified and it didn't manage to determine
                  the filesystem type.  Then filesystems contained in this
                  file are tried (excepted those that are marked with
                  "nodev").
    


* * *
# seusers

## NAME



           seusers - The SELinux GNU/Linux user to SELinux user mapping
           configuration file
    


## DESCRIPTION



           The _seusers_ file contains a list GNU/Linux user to SELinux user
           mapping for use by SELinux-aware login applications such as
           PAM(8).
    
           selinux_usersconf_path(3) will return the active policy path to
           this file. The default SELinux users mapping file is located at:
                  _/etc/selinux/{SELINUXTYPE}/seusers_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           getseuserbyname(3) reads this file to map a GNU/Linux user or
           group to an SELinux user.
    


## FILE FORMAT



           Each line of the _seusers_ configuration file consists of the
           following:
    
                  [**%**_group_id_]|[_user_id_]**:**_seuser_id_[**:**_range_]
    
           Where:
                  _group_id_ |_user_id_
                         The  GNU/Linux user id, or if preceded by the
                         percentage (**%**) symbol, then a GNU/Linux group id.
                         An optional entry set to **__default__** can be provided
                         as a fall back if required.
                  _seuser_id_
                         The SELinux  user identity.
                  _range_
                         The optional level or range for an MLS/MCS policy.
    


## EXAMPLE



           # ./seusers
           system_u:system_u:s0-s15:c0.c255
           root:root:s0-s15:c0.c255
           fred:user_u:s0
           __default__:user_u:s0
           %user_group:user_u:s0
    


* * *
# printers.conf

## NAME



           printers.conf - printer configuration file for cups
    


## DESCRIPTION



           The **printers.conf** file defines the local printers 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_personality

## NAME



           /proc/pid/personality - execution domain
    


## DESCRIPTION



           _/proc/_ pid _/personality_ (since Linux 2.6.28)
                  This read-only file exposes the process's execution domain,
                  as set by personality(2).  The value is displayed in
                  hexadecimal notation.
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_ATTACH_FSCREDS** check; see
                  ptrace(2).
    


* * *
# deb-md5sums

## NAME



           deb-md5sums - package MD5 file digests
    


## SYNOPSIS



           **DEBIAN/md5sums**
    


## DESCRIPTION



           A package declares the MD5 digests for the package file contents
           by including an _md5sums_ file in its control archive (i.e.
           _DEBIAN/md5sums_ during package creation).  This file is used for
           integrity verification and deduplication purposes, and not for any
           kind of security purpose.
    
           This file contains a list of MD5 digests (as 32 case-insensitive
           hexadecimal characters) followed by two spaces (U+0020 **SPACE**) and
           the absolute pathname of a plain file, one per line.
    
           Trailing slashes (U+002F **/**) in the pathname will be trimmed.
           Neither trailing whitespace nor empty or whitespace-only lines are
           accepted.
    
           If the control file does not exist in the binary package, dpkg(1)
           will generate the matching information at unpack time (since **dpkg**
           1.16.3).
    


## EXAMPLE



            53c0d4afe4bc4eccb5cb234d2e06ef4d  usr/bin/dpkg
            f8da2bc74cdcad8b81c48a4f0d7bb0a8  usr/bin/dpkg-deb
            70b913132de56e95e75de504979309b4  usr/bin/dpkg-divert
            […]
    


* * *
# yum-versionlock.conf

## NAME



           yum-versionlock.conf(5)
    


## SYNOPSIS



           yum-versionlock.conf(5) is the configuration file for
           yum-versionlock(1) Yum plugin for excluding packages that aren't
           listed in the versionlock file.  The plugin will walk each line of
           the versionlock file, parse out the name and version of the
           package. It will then exclude any package by that name that
           doesn't match one of the versions listed within the file (or,
           optionally, any obsoleter of that package).  This is basically the
           same as doing an exclude for the package name itself (as you
           cannot exclude installed packages), but yum will still see the
           versions you have installed/versionlocked as available so that
           "yum reinstall" will still work, etc.  It can also work in the
           opposite way, like a fast exclude, by prefixing a '!'  character
           to the version.
    


## FILES



           _/etc/yum/pluginconf.d/versionlock.conf_
    


## FILE FORMAT



           yum-versionlock.conf(5) utilizes configuration options in the form
           of
    
           OPTION=VALUE
    


## OPTIONS



           follow_obsoletes
                  This option is a boolean flag which specifies if the
                  versionlock plugin should look at all the obsoletes, and
                  see if any of the packages specified have an obsoleter. If
                  an obsoleter is found then all versions of that package
                  will be excluded. This option is off by default, as
                  yum-versionlock(1) will take some time to do the obsoletes
                  processing, and for non-rename obsoletes any issues you had
                  which kept you at a specific version of a package should be
                  different with another package.
    
           locklist
                  This option is a string with points to the file which will
                  have the versionlock information in it. Note that the file
                  **has** to exist (or the versionlock plugin will make yum
                  exit). However it can be empty.
    
           show_hint
                  This option is a boolean flag which specifies if the
                  versionlock plugin should print a hint message whenever yum
                  runs saying how many package updates available from the
                  repos are being blocked due to versionlocks.  This hint
                  serves as a reminder that there are locks in effect and
                  that you may want to reconsider them since newer versions
                  of those packages have been released.  Default is 1 (show
                  the hint).
    


* * *
# proc_sys

## NAME



           /proc/sys/ - system information, and sysctl pseudo-filesystem
    


## DESCRIPTION



           _/proc/sys/_
                  This directory (present since Linux 1.3.57) contains a
                  number of files and subdirectories corresponding to kernel
                  variables.  These variables can be read and in some cases
                  modified using the _/proc_ filesystem, and the (deprecated)
                  sysctl(2) system call.
    
                  String values may be terminated by either '\0' or '\n'.
    
                  Integer and long values may be written either in decimal or
                  in hexadecimal notation (e.g., 0x3FFF).  When writing
                  multiple integer or long values, these may be separated by
                  any of the following whitespace characters: ' ', '\t', or
                  '\n'.  Using other separators leads to the error **EINVAL**.
    


* * *
# proc_sys_net

## NAME



           /proc/sys/net/ - networking
    


## DESCRIPTION



           _/proc/sys/net/_
                  This directory contains networking stuff.  Explanations for
                  some of the files under this directory can be found in
                  tcp(7) and ip(7).
    
           _/proc/sys/net/core/bpf_jit_enable_
                  See bpf(2).
    
           _/proc/sys/net/core/somaxconn_
                  This file defines a ceiling value for the _backlog_ argument
                  of listen(2); see the listen(2) manual page for details.
    


* * *
# proc_pid_syscall

## NAME



           /proc/pid/syscall - currently executed system call
    


## DESCRIPTION



           _/proc/_ pid _/syscall_ (since Linux 2.6.27)
                  This file exposes the system call number and argument
                  registers for the system call currently being executed by
                  the process, followed by the values of the stack pointer
                  and program counter registers.  The values of all six
                  argument registers are exposed, although most system calls
                  use fewer registers.
    
                  If the process is blocked, but not in a system call, then
                  the file displays -1 in place of the system call number,
                  followed by just the values of the stack pointer and
                  program counter.  If process is not blocked, then the file
                  contains just the string "running".
    
                  This file is present only if the kernel was configured with
                  **CONFIG_HAVE_ARCH_TRACEHOOK**.
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_ATTACH_FSCREDS** check; see
                  ptrace(2).
    


* * *
# proc_sys_debug

## NAME



           /proc/sys/debug/ - debug
    


## DESCRIPTION



           _/proc/sys/debug/_
                  This directory may be empty.
    


* * *
# proc_kpageflags

## NAME



           /proc/kpageflags - physical pages frame masks
    


## DESCRIPTION



           _/proc/kpageflags_ (since Linux 2.6.25)
                  This file contains 64-bit masks corresponding to each
                  physical page frame; it is indexed by page frame number
                  (see the discussion of _/proc/_ pid _/pagemap_).  The bits are as
                  follows:
    
                          0   -   KPF_LOCKED
                          1   -   KPF_ERROR
                          2   -   KPF_REFERENCED
                          3   -   KPF_UPTODATE
                          4   -   KPF_DIRTY
                          5   -   KPF_LRU
                          6   -   KPF_ACTIVE
                          7   -   KPF_SLAB
                          8   -   KPF_WRITEBACK
                          9   -   KPF_RECLAIM
                         10   -   KPF_BUDDY
                         11   -   KPF_MMAP            (since Linux 2.6.31)
                         12   -   KPF_ANON            (since Linux 2.6.31)
                         13   -   KPF_SWAPCACHE       (since Linux 2.6.31)
                         14   -   KPF_SWAPBACKED      (since Linux 2.6.31)
                         15   -   KPF_COMPOUND_HEAD   (since Linux 2.6.31)
                         16   -   KPF_COMPOUND_TAIL   (since Linux 2.6.31)
                         17   -   KPF_HUGE            (since Linux 2.6.31)
                         18   -   KPF_UNEVICTABLE     (since Linux 2.6.31)
                         19   -   KPF_HWPOISON        (since Linux 2.6.31)
                         20   -   KPF_NOPAGE          (since Linux 2.6.31)
                         21   -   KPF_KSM             (since Linux 2.6.32)
                         22   -   KPF_THP             (since Linux 3.4)
                         23   -   KPF_BALLOON         (since Linux 3.18)
                         24   -   KPF_ZERO_PAGE       (since Linux 4.0)
                         25   -   KPF_IDLE            (since Linux 4.3)
                         26   -   KPF_PGTABLE         (since Linux 4.18)
    
                  For further details on the meanings of these bits, see the
                  kernel source file
                  _Documentation/admin-guide/mm/pagemap.rst_.  Before Linux
                  2.6.29, **KPF_WRITEBACK** , **KPF_RECLAIM** , **KPF_BUDDY** , and
                  **KPF_LOCKED** did not report correctly.
    
                  The _/proc/kpageflags_ file is present only if the
                  **CONFIG_PROC_PAGE_MONITOR** kernel configuration option is
                  enabled.
    


* * *
# rpc

## NAME



           rpc - RPC program number data base
    


## SYNOPSIS



           **/etc/rpc**
    


## DESCRIPTION



           The _rpc_ file contains user readable names that can be used in
           place of RPC program numbers.  Each line has the following
           information:
    
           •  name of server for the RPC program
           •  RPC program number
           •  aliases
    
           Items are separated by any number of blanks and/or tab characters.
           A '#' indicates the beginning of a comment; characters from the
           '#' to the end of the line are not interpreted by routines which
           search the file.
    
           Here is an example of the _/etc/rpc_ file from the Sun RPC Source
           distribution.
    
               #
               # rpc 88/08/01 4.0 RPCSRC; from 1.12   88/02/07 SMI
               #
               portmapper      100000  portmap sunrpc
               rstatd          100001  rstat rstat_svc rup perfmeter
               rusersd         100002  rusers
               nfs             100003  nfsprog
               ypserv          100004  ypprog
               mountd          100005  mount showmount
               ypbind          100007
               walld           100008  rwall shutdown
               yppasswdd       100009  yppasswd
               etherstatd      100010  etherstat
               rquotad         100011  rquotaprog quota rquota
               sprayd          100012  spray
               3270_mapper     100013
               rje_mapper      100014
               selection_svc   100015  selnsvc
               database_svc    100016
               rexd            100017  rex
               alis            100018
               sched           100019
               llockmgr        100020
               nlockmgr        100021
               x25.inr         100022
               statmon         100023
               status          100024
               bootparam       100026
               ypupdated       100028  ypupdate
               keyserv         100029  keyserver
               tfsd            100037
               nsed            100038
               nsemntd         100039
    


## FILES



           _/etc/rpc_
                  RPC program number data base
    


* * *
# org.freedesktop.oom1

## NAME



           org.freedesktop.oom1 - The D-Bus interface of systemd-oomd
    


## INTRODUCTION



           systemd-oomd.service(8) is a system service which implements a
           userspace out-of-memory (OOM) killer. This page describes the
           D-Bus interface.
    


## THE MANAGER OBJECT



           The service exposes the following interfaces on the Manager object
           on the bus:
    
               node /org/freedesktop/oom1 {
                 interface org.freedesktop.oom1.Manager {
                   methods:
                     DumpByFileDescriptor(out h fd);
                   signals:
                     Killed(s cgroup,
                            s reason);
                 };
                 interface org.freedesktop.DBus.Peer { ... };
                 interface org.freedesktop.DBus.Introspectable { ... };
                 interface org.freedesktop.DBus.Properties { ... };
               };
    
       **Methods**
           **Killed()** signal is sent when any cgroup is killed by oomd.
    
           Note that more reasons will be added in the future, and the table
           below will be expanded accordingly.
    
           **Table 1. Killing reasons**
           ┌─────────────────┬──────────────────────────┐
           │ **Reason** │ **Description** │
           ├─────────────────┼──────────────────────────┤
           │ memory-used     │ Application took too     │
           │                 │ much memory and swap.    │
           ├─────────────────┼──────────────────────────┤
           │ memory-pressure │ Application took enough  │
           │                 │ memory and swap to cause │
           │                 │ sufficient slowdown of   │
           │                 │ other applications.      │
           └─────────────────┴──────────────────────────┘
    


## VERSIONING



           These D-Bus interfaces follow **the usual interface versioning**
           **guidelines******[1].


## NOTES



            1. the usual interface versioning guidelines
               https://0pointer.de/blog/projects/versioning-dbus.html
    


* * *
# issue

## NAME



           issue - prelogin message and identification file
    


## DESCRIPTION



           _/etc/issue_ is a text file which contains a message or system
           identification to be printed before the login prompt.  It may
           contain various **@**_char_ and **\**_char_ sequences, if supported by the
           **getty** -type program employed on the system.
    


## FILES



           _/etc/issue_
    


* * *
# slapo-sssvlv

## NAME



           slapo-sssvlv - Server Side Sorting and Virtual List View overlay
           to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           This overlay implements the LDAP Server Side Sorting (RFC2891)
           control as well as the Virtual List View control. It also replaces
           the default implementation of the LDAP PagedResults (RFC2696)
           control, to ensure that it works with Sorting. The overlay can be
           used with any backend or globally for all backends.
    
           Since a complete result set must be generated in memory before
           sorting can be performed, processing sort requests can have a
           large impact on the server's memory use. As such, any connection
           is limited to having only a limited number of sort requests active
           at a time. Additional limits may be configured as described below.
    


## CONFIGURATION



           These **slapd.conf** options apply to the SSSVLV overlay.  They should
           appear after the **overlay** directive.
    
           **sssvlv-max <num>**
                  Set the maximum number of concurrent sort requests allowed
                  across all connections. The default is one half of the
                  number of server threads.
    
           **sssvlv-maxkeys <num>**
                  Set the maximum number of keys allowed in a sort request.
                  The default is 5.
    
           **sssvlv-maxperconn <num>**
                  Set the maximum number of concurrent paged search requests
                  per connection. The default is 5. The number of concurrent
                  requests remains limited by **sssvlv-max.**
    


## FILES



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


* * *
# protocols

## NAME



           protocols - protocols definition file
    


## DESCRIPTION



           This file is a plain ASCII file, describing the various DARPA
           internet protocols that are available from the TCP/IP subsystem.
           It should be consulted instead of using the numbers in the ARPA
           include files, or, even worse, just guessing them.  These numbers
           will occur in the protocol field of any IP header.
    
           Keep this file untouched since changes would result in incorrect
           IP packages.  Protocol numbers and names are specified by the IANA
           (Internet Assigned Numbers Authority).
    
           Each line is of the following format:
    
                  _protocol number aliases ..._
    
           where the fields are delimited by spaces or tabs.  Empty lines are
           ignored.  If a line contains a hash mark (#), the hash mark and
           the part of the line following it are ignored.
    
           The field descriptions are:
    
           _protocol_
                  the native name for the protocol.  For example _ip_ , _tcp_ , or
                  _udp_.
    
           _number_ the official number for this protocol as it will appear
                  within the IP header.
    
           _aliases_
                  optional aliases for the protocol.
    
           This file might be distributed over a network using a network-wide
           naming service like Yellow Pages/NIS or BIND/Hesiod.
    


## FILES



           _/etc/protocols_
                  The protocols definition file.
    


* * *
# projects

## NAME



           projects - persistent project root definition
    


## DESCRIPTION



           The _/etc/projects_ file provides a mapping between numeric project
           identifiers and those directories which are the roots of the quota
           tree.  Its format is simply:
    
                # comments are hash-prefixed
                # ...
                10:/export/cage
                42:/var/log
    
           The _/etc/projects_ file is optional, instead xfs_quota(8) can be
           used with the **-p** argument to specify a project root directly for
           each operation.
    


* * *
# sysctl.conf

## NAME



           sysctl.conf - Linux kernel configuration parameters
    


## DESCRIPTION



           **sysctl.conf** is a set of configuration files that contain Linux
           kernel configuration parameters to be read and set by sysctl(8).
    
           This man page describes the configuration files for _procps_ **sysctl**.
           If you are using systemd-sysctl(8), refer to sysctl.d(5) and note
           that it won't use the file _/etc/sysctl.conf_.
    
       **Configuration Format**
           Each line of a file read by _procps_ **sysctl** describes a kernel
           parameter in the following format.
    
                  token = value
    
           There is no need to use quotation marks for _value_ , even if the
           value is a list of items.
    
           Blank lines and lines that start with “**#** ” or “**;** ” are ignored.
    
           If a line begins with a single “**-** ”, a failing attempt to set the
           value is ignored.
    


## FILES



           _procps_ **sysctl** , when run with the **--system** option, reads files from
           directories in the order shown below.
    
                  _/etc/sysctl.d/_ *_.conf_
                  _/run/sysctl.d/_ *_.conf_
                  _/usr/local/lib/sysctl.d/_ *_.conf_
                  _/usr/lib/sysctl.d/_ *_.conf_
                  _/lib/sysctl.d/_ *_.conf_
    
           Finally, _procps_ **sysctl** reads _/etc/sysctl.conf_.  This file is not
           used by **systemd-sysctl** , which means that some kernel parameters
           are not set depending on the implementation of **sysctl** that is
           installed.
    


## BUGS



           The maximum supported length of _value_ is 4096 characters due to a
           limitation on _/proc_ entry length in the Linux kernel.
    


## EXAMPLES



           #
           #
           kernel.domainname = example.com
           ; A value containing a space is written to the sysctl.
           kernel.modprobe = /sbin/mod probe
           # A list of items for the value
           net.ipv4.ip_local_reserved_ports=8080,9148
    


* * *
# proc_pid_cwd

## NAME



           /proc/pid/cwd - symbolic link to current working directory
    


## DESCRIPTION



           _/proc/_ pid _/cwd_
                  This is a symbolic link to the current working directory of
                  the process.  To find out the current working directory of
                  process 20, for instance, you can do this:
    
                      $ **cd /proc/20/cwd; pwd -P**
    
                  In a multithreaded process, the contents of this 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).
    


* * *
# securetty

## NAME



           securetty - list of terminals on which root is allowed to login
    


## DESCRIPTION



           The file _/etc/securetty_ contains the names of terminals (one per
           line, without leading _/dev/_) which are considered secure for the
           transmission of certain authentication tokens.
    
           It is used by (some versions of) login(1) to restrict the
           terminals on which root is allowed to login.  See login.defs(5) if
           you use the shadow suite.
    
           On PAM enabled systems, it is used for the same purpose by
           pam_securetty(8) to restrict the terminals on which empty
           passwords are accepted.
    


## FILES



           _/etc/securetty_
    


* * *
# proc_pid_coredump_filter

## NAME



           /proc/pid/coredump_filter - core dump filter
    


## DESCRIPTION



           _/proc/_ pid _/coredump_filter_ (since Linux 2.6.23)
                  See core(5).
    


* * *
# proc_keys

## NAME



           /proc/keys, /proc/key-users - in-kernel key management
    


## DESCRIPTION



           _/proc/keys_ (since Linux 2.6.10)
                  See keyrings(7).
    
           _/proc/key-users_ (since Linux 2.6.10)
                  See keyrings(7).
    


* * *
# proc_partitions

## NAME



           /proc/partitions - major and minor numbers of partitions
    


## DESCRIPTION



           _/proc/partitions_
                  Contains the major and minor numbers of each partition as
                  well as the number of 1024-byte blocks and the partition
                  name.
    


* * *
# firejail-login

## NAME



           login.users - Login file syntax for Firejail
    


## DESCRIPTION



           /etc/firejail/login.users file describes additional arguments
           passed to the firejail executable upon user logging into a
           Firejail restricted shell. Each user entry in the file consists of
           a user name followed by the arguments passed to firejail. The
           format is as follows:
    
                user_name: arguments
    
           Example:
    
                netblue: --net=none --protocol=unix
    
           Wildcard patterns are accepted in the user name field:
    
                user*: --private
    


## RESTRICTED SHELL



           To configure a restricted shell, replace /bin/bash with
           /usr/bin/firejail in the /etc/passwd file for each user that needs
           to be restricted. Alternatively, you can specify /usr/bin/firejail
           using the `adduser` or `usermod` commands:
    
           adduser --shell /usr/bin/firejail username
           usermod --shell /usr/bin/firejail username
    


## FILES



           /etc/firejail/login.users
    


## LICENSE



           Firejail is free software; you can redistribute it and/or modify
           it under the terms of the GNU General Public License as published
           by the Free Software Foundation; either version 2 of the License,
           or (at your option) any later version.
    
           Homepage: https://firejail.wordpress.com
    


* * *
# proc_pid_auxv

## NAME



           /proc/pid/auxv - exec(3) information
    


## DESCRIPTION



           _/proc/_ pid _/auxv_ (since Linux 2.6.0)
                  This contains the contents of the ELF interpreter
                  information passed to the process at exec time.  The format
                  is one _unsigned long_ ID plus one _unsigned long_ value for
                  each entry.  The last entry contains two zeros.  See also
                  getauxval(3).
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    


* * *
# org.freedesktop.timesync1

## NAME



           org.freedesktop.timesync1 - The D-Bus interface of
           systemd-timesyncd
    


## INTRODUCTION



           systemd-timesyncd.service(8) is a system service that may be used
           to synchronize the local system clock with a remote Network Time
           Protocol (NTP) server. This page describes the D-Bus interface.
    


## THE MANAGER OBJECT



           The service exposes the following interfaces on the Manager object
           on the bus:
    
               node /org/freedesktop/timesync1 {
                 interface org.freedesktop.timesync1.Manager {
                   methods:
                     SetRuntimeNTPServers(in  as runtime_servers);
                   properties:
                     readonly as LinkNTPServers = ['...', ...];
                     readonly as SystemNTPServers = ['...', ...];
                     readonly as RuntimeNTPServers = ['...', ...];
                     readonly as FallbackNTPServers = ['...', ...];
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
                     readonly s ServerName = '...';
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
                     readonly (iay) ServerAddress = ...;
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("const")
                     readonly t RootDistanceMaxUSec = ...;
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("const")
                     readonly t PollIntervalMinUSec = ...;
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("const")
                     readonly t PollIntervalMaxUSec = ...;
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
                     readonly t PollIntervalUSec = ...;
                     readonly (uuuuittayttttbtt) NTPMessage = ...;
                     @org.freedesktop.DBus.Property.EmitsChangedSignal("false")
                     readonly x Frequency = ...;
                 };
                 interface org.freedesktop.DBus.Peer { ... };
                 interface org.freedesktop.DBus.Introspectable { ... };
                 interface org.freedesktop.DBus.Properties { ... };
               };
    
           Provides information about the manager.
    


## EXAMPLES



           **Example 1. Introspect org.freedesktop.timesync1.Manager on the bus**
    
               $ gdbus introspect --system \
                 --dest org.freedesktop.timesync1 \
                 --object-path /org/freedesktop/timesync1
    


## VERSIONING



           These D-Bus interfaces follow **the usual interface versioning**
           **guidelines******[1].


## NOTES



            1. the usual interface versioning guidelines
               https://0pointer.de/blog/projects/versioning-dbus.html
    


* * *
# proc_kmsg

## NAME



           /proc/kmsg - kernel messages
    


## DESCRIPTION



           _/proc/kmsg_
                  This file can be used instead of the syslog(2) system call
                  to read kernel messages.  A process must have superuser
                  privileges to read this file, and only one process should
                  read this file.  This file should not be read if a syslog
                  process is running which uses the syslog(2) system call
                  facility to log kernel messages.
    
                  Information in this file is retrieved with the dmesg(1)
                  program.
    


* * *
# yum-fs-snapshot.conf

## NAME



           yum-fs-snapshot.conf(5)
    


## SYNOPSIS



           yum-fs-snapshot.conf(5) is the configuration file for
           yum-fs-snapshot(1) Yum plugin for snapshotting your filesystems
           before running a yum transaction.  By default, this plugin will
           snapshot all filesystems that it is capable of snapshotting.  This
           includes block-level snapshots using LVM snapshots.
    


## FILES



           _/etc/yum/pluginconf.d/fs-snapshot.conf_
    


## FILE FORMAT



           yum-fs-snapshot.conf(5) utilizes configuration options in the form
           of
    
           OPTION=VALUE
    


## OPTION



           exclude
                  This is a space delimited list of the mount points you do
                  not wish to have snapshotted by this plugin.
    


## OPTION



           create_snapshots_in_post
                  This is a boolean value used to control whether snapshots
                  are also created after running the yum transaction.
    


## OPTION - [lvm] section



           enabled
                  This is a boolean value used to control whether LVM
                  snapshots will be created for filesystems built on LVM
                  logical volumes.
    


## OPTION - [lvm] section



           lvcreate_size_args
                  This is the space delimited lvcreate argument list that is
                  used to specify the size of the snapshot LV.  Valid
                  lvcreate size options are -l or -L.  If not specified then
                  LVM snapshots will not be created for volumes that are not
                  thinly provisioned.
    


* * *
# proc_crypto

## NAME



           /proc/crypto - ciphers provided by kernel crypto API
    


## DESCRIPTION



           _/proc/crypto_
                  A list of the ciphers provided by the kernel crypto API.
                  For details, see the kernel _Linux Kernel Crypto API_
                  documentation available under the kernel source directory
                  _Documentation/crypto/_ (or _Documentation/DocBook_ before
                  Linux 4.10; the documentation can be built using a command
                  such as _make htmldocs_ in the root directory of the kernel
                  source tree).
    


* * *
# pcp.env

## NAME



           **pcp.env** - script to set Performance Co-Pilot run-time environment
           variables
    


## SYNOPSIS



           _/etc/pcp.env_
    


## DESCRIPTION



           The _pcp.env_ script is sourced by assorted Performance Co-Pilot
           (PCP) scripts and utilities to define the PCP operating
           environment variables.  The conjugate for executable programs
           using the PCP libraries is the pmGetConfig(3) function.
    
           Typical usage of _pcp.env_ in a script is as follows :
    
                    #! /bin/sh
    
                    # source the PCP environment variables
                    . /etc/pcp.env
                    rest of script ...
    
           The full syntax and semantics of the _pcp.conf_ file and the
           _pmGetConfig_ function are described in their respective reference
           pages.
    
           If the file _$HOME/.pcp/pcp.conf_ exists then this will be processed
           after the system-wide _pcp.conf_ file.  This provides a mechanism to
           selectively modify or augment the environment settings for PCP
           scripts, which maybe useful if the scripts are run with **sudo**(1)
           which cleans the environment of important settings that are
           required to ensure the correct execution of the PCP scripts, e.g.
           **$PATH** or **$PERL5LIB**.
    


## ENVIRONMENT



           The **PCP_CONF** environment variable specifies an alternative path to
           the _pcp.conf_ file.
    


* * *
# key.dns_resolver.conf

## NAME



           key.dns_resolver.conf - Kernel DNS resolver config
    


## DESCRIPTION



           This file is used by the key.dns_resolver(5) program to set
           parameters.  Unless otherwise overridden with the **-c** flag, the
           program reads:
    
                  /etc/key.dns_resolver.conf
    
           Configuration options are given in **key[=value]** form, where **value**
           is optional.  If present, the value may be surrounded by a pair of
           single ('') or double quotes ("") which will be stripped off.  The
           special characters in the value may be escaped with a backslash to
           turn them into ordinary characters.
    
           Lines beginning with a '#' are considered comments and ignored.  A
           '#' symbol anywhere after the '=' makes the rest of the line into
           a comment unless the '#' is inside a quoted section or is escaped.
    
           Leading and trailing spaces and spaces around the '=' symbol will
           be stripped off.
    
           Available options include:
    
           **default_ttl= <number>**
                  The number of seconds to set as the expiration on a cached
                  record.  This will be overridden if the program manages to
                  retrieve TTL information along with the addresses (if, for
                  example, it accesses the DNS directly).  The default is 5
                  seconds.  The value must be in the range 1 to INT_MAX.
    
           The file can also include comments beginning with a '#' character
           unless otherwise suppressed by being inside a quoted value or
           being escaped with a backslash.
    


## FILES



           _/etc/key.dns_resolver.conf_
    


* * *
# proc_pid_mounts

## NAME



           /proc/pid/mounts - mounted filesystems
    


## DESCRIPTION



           _/proc/_ pid _/mounts_ (since Linux 2.4.19)
                  This file lists all the filesystems currently mounted in
                  the process's mount namespace (see mount_namespaces(7)).
                  The format of this file is documented in fstab(5).
    
                  Since Linux 2.6.15, this file is pollable: after opening
                  the file for reading, a change in this file (i.e., a
                  filesystem mount or unmount) causes select(2) to mark the
                  file descriptor as having an exceptional condition, and
                  poll(2) and epoll_wait(2) mark the file as having a
                  priority event (**POLLPRI**).  (Before Linux 2.6.30, a change
                  in this file was indicated by the file descriptor being
                  marked as readable for select(2), and being marked as
                  having an error condition for poll(2) and epoll_wait(2).)
    
           _/proc/mounts_
                  Before Linux 2.4.19, this file was a list of all the
                  filesystems currently mounted on the system.  With the
                  introduction of per-process mount namespaces in Linux
                  2.4.19 (see mount_namespaces(7)), this file became a link
                  to _/proc/self/mounts_ , which lists the mounts of the
                  process's own mount namespace.  The format of this file is
                  documented in fstab(5).
    


* * *
# deb-shlibs

## NAME



           deb-shlibs - Debian shared library information file
    


## SYNOPSIS



           **debian/shlibs** , **debian/**_binary-name_**.shlibs** , **DEBIAN/shlibs**
    


## DESCRIPTION



           **shlibs** files map shared library names and versions (_SONAMEs_) to
           dependencies suitable for a package control file.  There is one
           entry per line.  Blank lines are **not** allowed.  Lines beginning
           with a **#** character are considered commentary, and are ignored.
           All other lines must have the format:
    
               [_type_**:**] _library version dependencies_
    
           The _library_ and _version_ fields are whitespace-delimited, but the
           _dependencies_ field extends to the end of the line.  The _type_ field
           is optional and normally not needed.
    
           The _dependencies_ field has the same syntax as the **Depends** field in
           a binary control file, see deb-control(5).
    


## SONAME FORMATS



           The SONAME formats supported are:
    
               _name_.so._version_
    
           and
    
               _name_ -_version_.so
    
           where _name_ is usually prefixed by **lib**.
    
           The former tends to be used by shared libraries with stable
           interfaces.  The latter by shared libraries with unstable
           interfaces, where the whole version becomes part of the SONAME and
           needs to be specified in full when linking against those
           libraries.
    


## EXAMPLES



           The **shlibs** file for a typical library package, named _libcrunch1_ ,
           that provides one library whose SONAME is _libcrunch.so.1_ , might
           read
    
            libcrunch 1 libcrunch1 (>= 1.2-1)
    
           The _dependencies_ must mention the most recent version of the
           package that added new symbols to the library: in the above
           example, new symbols were added to version 1.2 of _libcrunch_.  This
           is not the only reason the dependencies might need to be
           tightened.
    


* * *