tripathysagar/man_text huggingface dataset:
# customizable_types

## NAME



           customizable_types - The SELinux customizable types configuration
           file
    


## DESCRIPTION



           The _customizable_types_ file contains a list of types that can be
           customised in some way by SELinux-aware applications.
    
           Generally this is a file context type that is usually set on files
           that need to be shared among certain domains and where the
           administrator wants to manually manage the type.
    
           The  use  of customizable types is deprecated as the preferred
           approach is to use semanage(8) **fcontext**(8) **...**(8).  However,
           SELinux-aware applications such as setfiles(8) will use this
           information to obtain a list of types relating to files that
           should not be relabeled.
    
           **selinux_customizable_types_path**(3) will return the active policy
           path to this file. The default customizable types file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/customizable_types_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           is_context_customizable(3) reads this file to determine if a
           context is customisable or not for the active policy.
    


## FILE FORMAT



           Each line in the file consists of the following:
                  _type_
    
           Where:
                  _type_
                         The type defined in the policy that can be
                         customised.
    


## EXAMPLE



           # ./contexts/customizable_types
           mount_loopback_t
           public_content_rw_t
           public_content_t
           swapfile_t
           sysadm_untrusted_content_t
    


* * *
# virtual_domain_context

## NAME



           virtual_domain_context - The SELinux virtual machine domain
           context configuration file
    


## DESCRIPTION



           The _virtual_domain_context_ file contains a list of domain contexts
           that are available for use by the SELinux-aware virtualization API
           libvirt (see **libvirtd**(8)).
    
           **selinux_virtual_domain_context_path**(3) will return the active
           policy path to this file. The default virtual domain context file
           is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/virtual_domain_context_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    


## FILE FORMAT



           Each line in the file consists of an 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 can be used as a
                         virtual domain context.
    


## EXAMPLE



           # ./contexts/virtual_domain_context
           system_u:object_r:svirt_t:s0
    


* * *
# pkgtorrent-service.conf

## NAME



           pkgtorrent-service.conf(5) is an example Apache 2 configuration
           file for the pkgtorrent-service(8).
    


## SYNOPSIS



           The default configuration maps the name **torrent_service** in any
           "subdirectory" of the web server root to the WSGI program.  The
           service cannot be installed in web server root because all multi-
           file torrents contain a concept of a name, which is expanded to a
           directory name when unpacked.  The service generates .torrent
           files which populates the **url-list** metadata with the URL prefix to
           the **torrent_service** name. All files within the torrent are
           relative to this prefix.  The pkgtorrent-service(8) has been
           tested extensively with Apache 2 and mod_wsgi, but should work
           equally well with any other WSGI capable web server.
    
           To use this configuration with Apache 2, install and enable
           **mod_wsgi** then enable this "site" using:
    
                  **a2ensite pkgtorrent-service.conf**
    


* * *
# proc_malloc

## NAME



           /proc/malloc - debug malloc (obsolete)
    


## DESCRIPTION



           _/proc/malloc_ (only up to and including Linux 2.2)
                  This file is present only if **CONFIG_DEBUG_MALLOC** was
                  defined during compilation.
    


* * *
# proc_driver

## NAME



           /proc/driver/ - empty dir
    


## DESCRIPTION



           _/proc/driver/_
                  Empty subdirectory.
    


* * *
# sepermit.conf

## NAME



           sepermit.conf - configuration file for the pam_sepermit module
    


## DESCRIPTION



           The lines of the configuration file have the following syntax:
    
           _< user>_[:_< option>_:_< option>_...]
    
           The **user** can be specified in the following manner:
    
           •   a username
    
           •   a groupname, with **@group** syntax. This should not be confused
               with netgroups.
    
           •   a SELinux user name with **%seuser** syntax.
    
           The recognized options are:
    
           **exclusive**
               Only single login session will be allowed for the user and the
               user's processes will be killed on logout.
    
           **ignore**
               The module will never return PAM_SUCCESS status for the user.
               It will return PAM_IGNORE if SELinux is in the enforcing mode,
               and PAM_AUTH_ERR otherwise. It is useful if you want to
               support passwordless guest users and other confined users with
               passwords simultaneously.
    
           The lines which start with # character are comments and are
           ignored.
    


## EXAMPLES



           These are some example lines which might be specified in
           /etc/security/sepermit.conf.
    
               %guest_u:exclusive
               %staff_u:ignore
               %user_u:ignore
    


* * *
# proc_config.gz

## NAME



           /proc/config.gz - kernel build configuration
    


## DESCRIPTION



           _/proc/config.gz_ (since Linux 2.6)
                  This file exposes the configuration options that were used
                  to build the currently running kernel, in the same format
                  as they would be shown in the _.config_ file that resulted
                  when configuring the kernel (using _make xconfig_ , _make_
                  _config_ , or similar).  The file contents are compressed;
                  view or search them using **zcat**(1) and **zgrep**(1).  As long as
                  no changes have been made to the following file, the
                  contents of _/proc/config.gz_ are the same as those provided
                  by:
    
                      cat /lib/modules/$(uname -r)/build/.config
    
                  _/proc/config.gz_ is provided only if the kernel is
                  configured with **CONFIG_IKCONFIG_PROC**.
    


* * *
# group

## NAME



           group - user group file
    


## DESCRIPTION



           The _/etc/group_ file is a text file that defines the groups on the
           system.  There is one entry per line, with the following format:
    
               group_name:password:GID:user_list
    
           The fields are as follows:
    
           _group_name_
                  the name of the group.
    
           _password_
                  the (encrypted) group password.  If this field is empty, no
                  password is needed.
    
           _GID_    the numeric group ID.
    
           _user_list_
                  a list of the usernames that are members of this group,
                  separated by commas.
    


## FILES



           _/etc/group_
    


## BUGS



           As the 4.2BSD initgroups(3) man page says: no one seems to keep
           _/etc/group_ up-to-date.
    


* * *
# locale.conf

## NAME



           locale.conf - Configuration file for locale settings
    


## SYNOPSIS



           /etc/locale.conf
    


## DESCRIPTION



           The /etc/locale.conf file configures system-wide locale settings.
           It is read at early boot by systemd(1).
    
           The format of locale.conf is a newline-separated list of
           environment-like shell-compatible variable assignments, ignoring
           comments and empty lines. It is possible to source the
           configuration from shell scripts, however, beyond mere variable
           assignments, no shell features are supported, allowing
           applications to read the file without implementing a shell
           compatible execution engine. See os-release(5) for a detailed
           description of the format.
    
           Note that the kernel command line options _locale.LANG=_ ,
           _locale.LANGUAGE=_ , _locale.LC_CTYPE=_ , _locale.LC_NUMERIC=_ ,
           _locale.LC_TIME=_ , _locale.LC_COLLATE=_ , _locale.LC_MONETARY=_ ,
           _locale.LC_MESSAGES=_ , _locale.LC_PAPER=_ , _locale.LC_NAME=_ ,
           _locale.LC_ADDRESS=_ , _locale.LC_TELEPHONE=_ , _locale.LC_MEASUREMENT=_ ,
           _locale.LC_IDENTIFICATION=_ may be used to override the locale
           settings at boot.
    
           The locale settings configured in /etc/locale.conf are system-wide
           and are inherited by every service or user, unless overridden or
           unset by individual programs or users.
    
           Depending on the operating system, other configuration files might
           be checked for locale configuration as well, however only as
           fallback.
    
           /etc/locale.conf can be updated using systemd-localed.service(8).
           localectl(1) may be used to alter the settings in this file during
           runtime from the command line. Use systemd-firstboot(1) to
           customize them on mounted (but not booted) system images.
    


## OPTIONS



           The following locale settings may be set using /etc/locale.conf:
           _LANG=_ , _LANGUAGE=_ , _LC_CTYPE=_ , _LC_NUMERIC=_ , _LC_TIME=_ , _LC_COLLATE=_ ,
           _LC_MONETARY=_ , _LC_MESSAGES=_ , _LC_PAPER=_ , _LC_NAME=_ , _LC_ADDRESS=_ ,
           _LC_TELEPHONE=_ , _LC_MEASUREMENT=_ , _LC_IDENTIFICATION=_. Note that
           _LC_ALL_ may not be configured in this file. For details about the
           meaning and semantics of these settings, refer to locale(7).
    


## EXAMPLE



           **Example 1. German locale with English messages**
    
           /etc/locale.conf:
    
               # Custom settings
    
               LANG=de_DE.UTF-8
               LC_MESSAGES=en_US.UTF-8
    


* * *
# deb-old

## NAME



           deb-old - old style Debian binary package format
    


## SYNOPSIS



           _filename_**.deb**
    


## DESCRIPTION



           The **.deb** format is the Debian binary package file format.  This
           manual page describes the **old** format, used before Debian 0.93.
           Please see deb(5) for details of the new format.
    


## FORMAT



           The file is two lines of format information as ASCII text,
           followed by two concatenated gzipped ustar files.
    
           The first line is the format version number padded to 8 digits,
           and is **0.939000** for all old-format archives.
    
           The second line is a decimal string (without leading zeroes)
           giving the length of the first gzipped tarfile.
    
           Each of these lines is terminated with a single newline character.
    
           The first tarfile contains the control information, as a series of
           ordinary files.  The file **control** must be present, as it contains
           the core control information.
    
           In some very old archives, the files in the control tarfile may
           optionally be in a **DEBIAN** subdirectory.  In that case, the **DEBIAN**
           subdirectory will be in the control tarfile too, and the control
           tarfile will have only files in that directory.  Optionally the
           control tarfile may contain an entry for ‘**.** ’, that is, the current
           directory.
    
           The second gzipped tarfile is the filesystem archive, containing
           pathnames relative to the root directory of the system to be
           installed on.  The pathnames do not have leading slashes.
    


* * *
# proc_sys_proc

## NAME



           /proc/sys/proc/ - ???
    


## DESCRIPTION



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


* * *
# proc_sys_sunrpc

## NAME



           /proc/sys/sunrpc/ - Sun remote procedure call for NFS
    


## DESCRIPTION



           _/proc/sys/sunrpc/_
                  This directory supports Sun remote procedure call for
                  network filesystem (NFS).  On some systems, it is not
                  present.
    


* * *
# subscriptions.conf

## NAME



           subscriptions.conf - subscription configuration file for cups
    


## DESCRIPTION



           The **subscriptions.conf** file defines the local event notification
           subscriptions that are active.  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.
    


* * *
# securetty_types

## NAME



           securetty_types - The SELinux secure tty type configuration file
    


## DESCRIPTION



           The _securetty_types_ file contains a list of types associated to
           secure tty type that are defined in the policy for use by SELinux-
           aware applications.
    
           selinux_securetty_types_path(3) will return the active policy path
           to this file. The default securetty types file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/securetty_types_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           selinux_check_securetty_context(3) reads this file to determine if
           a context is for a secure tty defined in the active policy.
    
           SELinux-aware applications such as newrole(1) use this information
           to check the status of a tty.
    


## FILE FORMAT



           Each line in the file consists of the following entry:
    
                  _type_
                         One or more type entries that are defined in the
                         policy for secure tty devices.
    


## EXAMPLE



           # ./contexts/securetty_types
           sysadm_tty_device_t
           user_tty_device_t
           staff_tty_device_t
    


* * *
# proc_kcore

## NAME



           /proc/kcore - physical memory
    


## DESCRIPTION



           _/proc/kcore_
                  This file represents the physical memory of the system and
                  is stored in the ELF core file format.  With this pseudo-
                  file, and an unstripped kernel (_/usr/src/linux/vmlinux_)
                  binary, GDB can be used to examine the current state of any
                  kernel data structures.
    
                  The total length of the file is the size of physical memory
                  (RAM) plus 4 KiB.
    


* * *
# proc_pid_map_files

## NAME



           /proc/pid/map_files/ - memory-mapped files
    


## DESCRIPTION



           _/proc/_ pid _/map_files/_ (since Linux 3.3)
                  This subdirectory contains entries corresponding to memory-
                  mapped files (see mmap(2)).  Entries are named by memory
                  region start and end address pair (expressed as hexadecimal
                  numbers), and are symbolic links to the mapped files
                  themselves.  Here is an example, with the output wrapped
                  and reformatted to fit on an 80-column display:
    
                      # **ls -l /proc/self/map_files/**
                      lr--------. 1 root root 64 Apr 16 21:31
                                  3252e00000-3252e20000 -> /usr/lib64/ld-2.15.so
                      ...
    
                  Although these entries are present for memory regions that
                  were mapped with the **MAP_FILE** flag, the way anonymous
                  shared memory (regions created with the **MAP_ANON |**
                  **MAP_SHARED** flags) is implemented in Linux means that such
                  regions also appear on this directory.  Here is an example
                  where the target file is the deleted _/dev/zero_ one:
    
                      lrw-------. 1 root root 64 Apr 16 21:33
                                  7fc075d2f000-7fc075e6f000 -> /dev/zero (deleted)
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    
                  Until Linux 4.3, this directory appeared only if the
                  **CONFIG_CHECKPOINT_RESTORE** kernel configuration option was
                  enabled.
    
                  Capabilities are required to read the contents of the
                  symbolic links in this directory: before Linux 5.9, the
                  reading process requires **CAP_SYS_ADMIN** in the initial user
                  namespace; since Linux 5.9, the reading process must have
                  either **CAP_SYS_ADMIN** or **CAP_CHECKPOINT_RESTORE** in the
                  initial (i.e. root) user namespace.
    


* * *
# faillog

## NAME



           faillog - login failure logging file
    


## DESCRIPTION



           /var/log/faillog maintains a count of login failures and the
           limits for each account.
    
           The file contains fixed length records, indexed by numerical UID.
           Each record contains the count of login failures since the last
           successful login; the maximum number of failures before the
           account is disabled; the line on which the last login failure
           occurred; the date of the last login failure; and the duration (in
           seconds) during which the account will be locked after a failure.
    
           The structure of the file is:
    
               struct    faillog {
                    short   fail_cnt;
                    short   fail_max;
                    char    fail_line[12];
                    time_t  fail_time;
                    long    fail_locktime;
               };
    


## FILES



           /var/log/faillog
               Failure logging file.
    


* * *
# proc_pid_cpuset

## NAME



           /proc/pid/cpuset - CPU affinity sets
    


## DESCRIPTION



           _/proc/_ pid _/cpuset_ (since Linux 2.6.12)
                  See cpuset(7).
    


* * *
# slappw-argon2

## NAME



           slappw-argon2 - Argon2 password module to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    
                  **moduleload argon2**[_< parameters>_]
    


## DESCRIPTION



           The **argon2** module to slapd(8) provides support for the use of the
           key derivation function Argon2, that was selected as the winner of
           the Password Hashing Competition in July 2015, in hashed passwords
           in OpenLDAP.
    
           It does so by providing the additional password scheme **{ARGON2}**
           for use in slapd.
    


## CONFIGURATION



           The **argon2** module does not need any configuration, but it can be
           configured by giving the following parameters:
    
           **m=**_< memory>_
                  Set memory usage to _< memory>_ kiB.
    
           **p=**_< parallelism>_
                  Set parallelism to _< parallelism>_ threads. Currently
                  supported only when linked with **libargon2**.
    
           **t=**_< iterations>_
                  Set the number of iterations to _< iterations>_.
    
           These replace defaults when preparing hashes for new passwords
           where possible.
    
           After loading the module, the password scheme **{ARGON2}** will be
           recognised in values of the _userPassword_ attribute.
    
           You can then instruct OpenLDAP to use this scheme when processing
           the LDAPv3 Password Modify (RFC 3062) extended operations by using
           the **password-hash** option in slapd.conf(5):
    
                  **password-hash {ARGON2}**
    
       **NOTES**
           If you want to use the scheme described here with slappasswd(8),
           remember to load the module using its command line options.  The
           relevant option/value is:
    
                  **-o module-load** =**argon2**
    
           Or if non-default parameters are required:
    
                  **-o module-load** ="**argon2**[**< param>**...]"
    
           Depending on **argon2** 's location, you may also need:
    
                  **-o module-path** =_pathspec_
    


## EXAMPLES



           Both userPassword LDAP attributes below encode the password
           '_secret_ ' using different salts:
    
           userPassword: {ARGON2}$argon2i$v=19$m=4096,t=3,p=1$c2FsdHNhbHQ$DKlexoEJUoZTmkAAC3SaMWk30El9/RvVhlqGo6afIng
    
           userPassword: {ARGON2}$argon2i$v=19$m=4096,t=3,p=1$c2FsdHNhbHRzYWx0$qOCkx9nMeFlaGOO4DUmPDgrlUbgMMuO9T1+vQCFuyzw
    


## ACKNOWLEDGEMENTS



           This manual page has been written by Peter Marschall based on the
           module's README file written by Simon Levermann
           ⟨simon@levermann.de⟩.
    
           **OpenLDAP** is developed and maintained by The OpenLDAP Project 
           ⟨http://www.openldap.org/⟩.  **OpenLDAP** is derived from University of
           Michigan LDAP 3.3 Release.
    


* * *
# proc_execdomains

## NAME



           /proc/execdomains - ABI personalities (obsolete)
    


## DESCRIPTION



           _/proc/execdomains_
                  Used to list ABI personalities before Linux 4.1; now
                  contains a constant string for userspace compatibility.
    


* * *
# deb-prerm

## NAME



           deb-prerm - package pre-removal maintainer script
    


## SYNOPSIS



           **DEBIAN/prerm**
    


## DESCRIPTION



           A package can perform several pre-removal actions via maintainer
           scripts, by including an executable _prerm_ file in its control
           archive (i.e. _DEBIAN/prerm_ during package creation).
    
           The script can be called in the following ways:
    
           _prerm_ **remove**
               Before the package is removed.
    
           _old-prerm_ **upgrade** _new-version_
               Before an upgrade.
    
           _new-prerm_ **failed-upgrade** _old-version new-version_
               If the above **upgrade** fails.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    
           _prerm_ **deconfigure in-favour** _new-package new-version_
               [ **removing** _old-package old-version_ ]
               Before package is deconfigured while dependency is replaced
               due to conflict.
    
           _prerm_ **remove in-favour** _new-package new-version_
               Before the package is replaced due to conflict.
    


* * *
# yum-changelog.conf

## NAME



           yum-changelog.conf(5)
    


## SYNOPSIS



           yum-changelog.conf(5) is the configuration file for
           yum-changelog(1) Yum plugin for viewing package changelogs
           before/after updating.  By default, this plugin will show the
           changelogs before the updates.
    


## FILES



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


## FILE FORMAT



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


## OPTION



           when   This option reflects when yum-changelog(1) will allow
                  changelog viewing during yum updates.
    


## VALUE



           pre    To make **yum-changelog**(5) show the changelog **before** the yum
                  updates
    
           post   To make **yum-changelog**(5) show the changelog **after** the yum
                  updates.
    


## OPTION



           always This option reflects specifies if the changelog should
                  always be shown.
    


## VALUE



           true   The changelog is always displayed.
    
           false  A command line option is required for the changelog to be
                  displayed.
    


## OPTION



           updateinfo
                  This option specifies that the "changelog" from the repo.
                  updateinfo should be shown.
    


## VALUE



           true   The updateinfo is displayed.
    
           false  The updateinfo is never displayed.
    


## OPTION



           updateinfo_always
                  This option reflects specifies if the "changelog" from the
                  repo. should always be shown (note that if updateinfo is
                  false then this option has no meaning).
    


## VALUE



           true   The updateinfo is always displayed.
    
           false  A command line option is required for the updateinfo to be
                  displayed.
    


* * *
# pcp.conf

## NAME



           **pcp.conf** - the Performance Co-Pilot configuration and environment
           file
    


## SYNOPSIS



           _/etc/pcp.conf_
    


## DESCRIPTION



           When using Performance Co-Pilot (PCP) tools and utilities and when
           calling PCP library functions, a standard set of environment
           variables are defined in _/etc/pcp.conf_.  These variables are
           generally used to specify the location of various PCP pieces in
           the file system and may be loaded into shell scripts by sourcing
           the _/etc/pcp.env_(5) shell script and queried by C/C++ programs
           using the pmGetConfig(3) library function.  If a variable is
           already defined in the environment, the values in _pcp.conf_ do **not**
           override those values, i.e. the values in _pcp.conf_ serve as
           installation defaults only.
    
           Both the _pcp.env_ and _pcp.conf_ files are expected to be found in
           _/etc_ by default.  If required, the _pcp.conf_ file may be relocated
           and **PCP_CONF** set in the environment to specify the full path to
           the new location.  The _pcp.env_ file can not be relocated (this is
           the only hard coded path required by PCP).
    
           The syntax rules for _pcp.conf_ are as follows :
    
           1.  the general syntax is
                      **PCP_VARIABLE_NAME=variable value to end of line**
    
           2.  lines that begin with **#** and all blank lines are ignored.
    
           3.  all variables must be prefixed with **PCP_**.  This is a security
               issue - variables that do not have this prefix will be
               silently ignored.
    
           4.  there should be no space between the variable name and the
               literal **=** and no space between the **=** and the variable value
               (unless the value actually starts with a space).  This is
               required because the _pcp.conf_ file may be sourced directly by
               Makefiles as well as interpreted by the _pcp.env_ script and the
               _pmGetConfig_ function.
    
           5.  variable values may contain spaces and should **not** be quoted.
               The _pcp.env_ script automatically quotes all variable values
               from the character immediately following the **=** through to the
               end of the line.
    
           For further details and an explanation of the use of each
           variable, see the comments in the _/etc/pcp.conf_ file itself.
    


## ENVIRONMENT



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


* * *
# deb-src-files

## NAME



           deb-src-files - Debian distribute files format
    


## SYNOPSIS



           **debian/files**
    


## DESCRIPTION



           This file contains the list of artifacts that are to be
           distributed via the **.changes** control file.
    
           The _debian/files_ file has a simple whitespace-delimited format.
    
               _filename section priority_ [ _keyword=value..._  ]
    
           _filename_ is the name of the artifact to distribute.
    
           _section_ and _priority_ correspond to the respective control fields
           available in the .deb.  The allowed values are specific to each
           distribution archive.
    
           _keyword=value..._  corresponds to an optional whitespace-delimited
           list of attributes for this entry.  The only currently supported
           keyword is **automatic** with value **yes** , to mark automatically
           generated files.
    


## NOTES



           This file is not intended to be modified directly, please use one
           of **dpkg-gencontrol** or **dpkg-distaddfile** to add entries to it.
    


* * *
# proc_sys_abi

## NAME



           /proc/sys/abi/ - application binary information
    


## DESCRIPTION



           _/proc/sys/abi/_ (since Linux 2.4.10)
                  This directory may contain files with application binary
                  information.  See the Linux kernel source file
                  _Documentation/sysctl/abi.rst_ (or
                  _Documentation/sysctl/abi.txt_ before Linux 5.3) for more
                  information.
    


* * *
# proc_sysrq-trigger

## NAME



           /proc/sysrq-trigger - SysRq function
    


## DESCRIPTION



           _/proc/sysrq-trigger_ (since Linux 2.4.21)
                  Writing a character to this file triggers the same SysRq
                  function as typing ALT-SysRq-<character> (see the
                  description of _/proc/sys/kernel/sysrq_).  This file is
                  normally writable only by _root_.  For further details see
                  the Linux kernel source file
                  _Documentation/admin-guide/sysrq.rst_ (or
                  _Documentation/sysrq.txt_ before Linux 4.10).
    


* * *
# proc_tid_children

## NAME



           /proc/tid/children - child tasks
    


## DESCRIPTION



           _/proc/_ tid _/children_ (since Linux 3.5)
                  A space-separated list of child tasks of this task.  Each
                  child task is represented by its TID.
    
                  This option is intended for use by the checkpoint-restore
                  (CRIU) system, and reliably provides a list of children
                  only if all of the child processes are stopped or frozen.
                  It does not work properly if children of the target task
                  exit while the file is being read!  Exiting children may
                  cause non-exiting children to be omitted from the list.
                  This makes this interface even more unreliable than classic
                  PID-based approaches if the inspected task and its children
                  aren't frozen, and most code should probably not use this
                  interface.
    
                  Until Linux 4.2, the presence of this file was governed by
                  the **CONFIG_CHECKPOINT_RESTORE** kernel configuration option.
                  Since Linux 4.2, it is governed by the **CONFIG_PROC_CHILDREN**
                  option.
    


* * *
# proc_diskstats

## NAME



           /proc/diskstats - disk I/O statistics
    


## DESCRIPTION



           _/proc/diskstats_ (since Linux 2.5.69)
                  This file contains disk I/O statistics for each disk
                  device.  See the Linux kernel source file
                  _Documentation/admin-guide/iostats.rst_ (or
                  _Documentation/iostats.txt_ before Linux 5.3) for further
                  information.
    


* * *
# proc_pid_projid_map

## NAME



           /proc/pid/projid_map - project ID mappings
    


## DESCRIPTION



           _/proc/_ pid _/projid_map_ (since Linux 3.7)
                  See user_namespaces(7).
    


* * *
# default_type

## NAME



           default_type - The SELinux default type configuration file
    


## DESCRIPTION



           The _default_type_ file contains entries that allow SELinux-aware
           applications such as newrole(1) to select a default type for a
           role if one is not supplied.
    
           selinux_default_type_path(3) will return the active policy path to
           this file. The default, default type file is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/default_type_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           get_default_type(3) reads this file to determine a type for the
           active policy.
    


## FILE FORMAT



           Each line within the _default_type_ file is formatted with _role_**:**_type_
           entries where:
                  _role_
                         The SELinux role.
                  _type_
                         The domain type that is returned for this role.
    


## EXAMPLE



           # ./contexts/default_type
           auditadm_r:auditadm_t
           user_r:user_t
    


* * *
# slapo-nestgroup

## NAME



           slapo-nestgroup - Nested Group overlay to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The **nestgroup** overlay to slapd(8) supports evaluation of nested
           groups in Search operations. Support consists of four possible
           features: inclusion of parent groups when searching with (member=)
           filters, inclusion of child groups when searching with (memberOf=)
           filters, expansion of child groups when returning member
           attributes, and expansion of parent groups when returning memberOf
           attributes. Each of these features may be enabled independently.
           By default, no features are enabled, so this overlay does nothing
           unless explicitly enabled.
    


## CONFIGURATION



           The config directives that are specific to the **nestgroup** overlay
           must be prefixed by **nestgroup-** , to avoid potential conflicts with
           directives specific to the underlying database or to other stacked
           overlays.
    
           **overlay nestgroup**
                  This directive adds the nestgroup overlay to the current
                  database; see slapd.conf(5) for details.
    
           The following **slapd.conf** configuration options are defined for the
           nestgroup overlay.
    
           **nestgroup-member** _< member-ad>_
                  The value _< member-ad>_ is the name of the attribute that
                  contains the names of the members in the group objects; it
                  must be DN-valued.  It defaults to _member_.
    
           **nestgroup-memberof** _< memberof-ad>_
                  The value _< memberof-ad>_ is the name of the attribute that
                  contains the names of the groups an entry is member of; it
                  must be DN-valued.  It defaults to _memberOf_.
    
           **nestgroup-base** _< dn>_
                  The value _< dn>_ specifies a subtree that contains group
                  entries in the DIT. This may be specified multiple times
                  for multiple distinct subtrees.  It has no default and the
                  overlay does no processing unless it is explicitly
                  configured.
    
           **nestgroup-flags {**_member-filter_**,**_memberof-filter_**,**_member-values_**,**
           _memberof-values_**}**
                  This option specifies which features to enable in the
                  overlay.  By default, nothing is enabled and the overlay is
                  a no-op.
    
           The nestgroup overlay may be used with any backend that provides
           standard search functionality.
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


## ACKNOWLEDGEMENTS



           This module was written in 2024 by Howard Chu of Symas
           Corporation.
    


* * *
# slapd-passwd

## NAME



           slapd-passwd - /etc/passwd backend to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The PASSWD backend to slapd(8) serves up the user account
           information listed in the system passwd(5) file.  This backend is
           provided for demonstration purposes only.  The DN of each entry is
           "uid=<username>,<suffix>".  Note that non-base searches scan the
           entire passwd file, and are best suited for hosts with small
           passwd files.
    


## CONFIGURATION



           This **slapd.conf** option applies to the PASSWD backend database.
           That is, it must follow a "database passwd" line and come before
           any subsequent "backend" or "database" lines.  Other database
           options are described in the slapd.conf(5) manual page.
    
           **file <filename>**
                  Specifies an alternate passwd file to use.  The default is
                  **/etc/passwd**.
    


## ACCESS CONTROL



           The **passwd** 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
    
           /etc/passwd
                  user account information
    


* * *
# proc_swaps

## NAME



           /proc/swaps - swap areas
    


## DESCRIPTION



           _/proc/swaps_
                  Swap areas in use.  See also swapon(8).
    


* * *
# localtime

## NAME



           localtime - Local timezone configuration file
    


## SYNOPSIS



           /etc/localtime -> ../usr/share/zoneinfo/...
    


## DESCRIPTION



           The /etc/localtime file configures the system-wide timezone of the
           local system that is used by applications for presentation to the
           user. It should be an absolute or relative symbolic link pointing
           to /usr/share/zoneinfo/, followed by a timezone identifier such as
           "Europe/Berlin" or "Etc/UTC". The resulting link should lead to
           the corresponding binary tzfile(5) timezone data for the
           configured timezone.
    
           Because the timezone identifier is extracted from the symlink
           target name of /etc/localtime, this file may not be a normal file
           or hardlink.
    
           If /etc/localtime is missing, the default "UTC" timezone is used.
    
           The timezone may be overridden for individual programs by using
           the _$TZ_ environment variable. See environ(7).
    
           You may use timedatectl(1) to change the settings of this file
           from the command line during runtime. Use systemd-firstboot(1) to
           initialize the time zone on mounted (but not booted) system
           images.
    


* * *
# proc_modules

## NAME



           /proc/modules - loaded modules
    


## DESCRIPTION



           _/proc/modules_
                  A text list of the modules that have been loaded by the
                  system.  See also lsmod(8).
    


* * *
# projid

## NAME



           projid - the project name mapping file
    


## DESCRIPTION



           The _/etc/projid_ file provides a mapping between numeric project
           identifiers and a simple human readable name (similar relationship
           to the one that exists between usernames and uids).  Its format is
           simply:
    
                # comments are hash-prefixed
                # ...
                cage:10
                logfiles:42
    
           This file is optional, if a project identifier cannot be mapped to
           a name, it will be parsed and displayed as a numeric value.
    


* * *
# ftpusers

## NAME



           ftpusers - list of users that may not log in via the FTP daemon
    


## DESCRIPTION



           The text file **ftpusers** contains a list of users that may not log
           in using the File Transfer Protocol (FTP) server daemon.  This
           file is used not merely for system administration purposes but
           also for improving security within a TCP/IP networked environment.
    
           The **ftpusers** file will typically contain a list of the users that
           either have no business using ftp or have too many privileges to
           be allowed to log in through the FTP server daemon.  Such users
           usually include root, daemon, bin, uucp, and news.
    
           If your FTP server daemon doesn't use **ftpusers** , then it is
           suggested that you read its documentation to find out how to block
           access for certain users.  Washington University FTP server Daemon
           (wuftpd) and Professional FTP Daemon (proftpd) are known to make
           use of **ftpusers**.
    
       **Format**
           The format of **ftpusers** is very simple.  There is one account name
           (or username) per line.  Lines starting with a # are ignored.
    


## FILES



           _/etc/ftpusers_
    


* * *
# proc_version

## NAME



           /proc/version - kernel version
    


## DESCRIPTION



           _/proc/version_
                  This string identifies the kernel version that is currently
                  running.  It includes the contents of
                  _/proc/sys/kernel/ostype_ , _/proc/sys/kernel/osrelease_ , and
                  _/proc/sys/kernel/version_.  For example:
    
                      Linux version 1.0.9 (quinlan@phaze) #1 Sat May 14 01:51:54 EDT 1994
    


* * *
# yum-updatesd.conf

## NAME



           **yum-updatesd.conf** - Configuration file for yum-updatesd(8).
    


## DESCRIPTION



           yum-updatesd uses a configuration file at **/etc/yum/yum-**
           **updatesd.conf**.
    
           Additional configuration information is read from the main
           **yum.conf (5)** configuration file.
    


## PARAMETERS



           There is one section in the yum-updatesd configuration file, main,
           which defines all of the global configuration options.
    


## [main] OPTIONS



           The [main] section must exist for yum-updatesd to do anything. It
           consists of the following options:
    
           **run_interval**
                  Number of seconds to wait between checks for available
                  updates.
    
           **updaterefresh**
                  Minimum number of seconds between update information
                  refreshes to avoid hitting the server too often.
    
           **emit_via**
                  List of ways to emit update notification.  Valid values are
                  `email', `dbus' and `syslog'.
    
           **do_update**
                  Boolean option to decide whether or not updates should be
                  automatically applied.  Defaults to False.
    
           **do_download_deps**
                  Boolean option to decide whether or not updates should be
                  automatically downloaded.  Defaults to False.
    
           **do_download_deps**
                  Boolean option to automatically download dependencies of
                  packages which need updating as well.  Defaults to False.
    


## MAIL OPTIONS



           **email_to**
                  List of email addresses to send update notification to.
                  Defaults to `root@localhost'.
    
           **email_from**
                  Email address for update notifications to be from.
                  Defaults to `yum-updatesd@localhost'.
    


## SYSLOG OPTIONS



           **syslog_facility**
                  What syslog facility should be used.  Defaults to `DAEMON'.
    
           **syslog_level**
                  Level of syslog messages.  Defaults to `WARN'.
    


## FILES



           /etc/yum/yum-updatesd.conf
    


* * *
# proc_pid_environ

## NAME



           /proc/pid/environ - initial environment
    


## DESCRIPTION



           _/proc/_ pid _/environ_
                  This file contains the initial environment that was set
                  when the currently executing program was started via
                  execve(2).  The entries are separated by null bytes ('\0'),
                  and there may be a null byte at the end.  Thus, to print
                  out the environment of process 1, you would do:
    
                      $ **cat /proc/1/environ | tr '\000' '\n'**
    
                  If, after an execve(2), the process modifies its
                  environment (e.g., by calling functions such as putenv(3)
                  or modifying the environ(7) variable directly), this file
                  will _not_ reflect those changes.
    
                  Furthermore, a process may change the memory location that
                  this file refers via prctl(2) operations such as
                  **PR_SET_MM_ENV_START**.
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    


* * *
# virtual_image_context

## NAME



           virtual_image_context - The SELinux virtual machine image context
           configuration file
    


## DESCRIPTION



           The _virtual_image_context_ file contains a list of image contexts
           for use by the SELinux-aware virtualization API libvirt (see
           **libvirtd**(8)).
    
           **selinux_virtual_image_context_path**(3) will return the active
           policy path to this file. The default virtual image context file
           is:
                  _/etc/selinux/{SELINUXTYPE}/contexts/virtual_image_context_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    


## FILE FORMAT



           Each line in the file consists of an 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 can be used as a
                         virtual image context.
    


## EXAMPLE



           # ./contexts/virtual_image_context
           system_u:object_r:svirt_image_t:s0
           system_u:object_r:svirt_content_t:s0
    


* * *