tripathysagar/man_text huggingface dataset:
# proc_pid_cmdline

## NAME



           /proc/pid/cmdline - command line
    


## DESCRIPTION



           _/proc/_ pid _/cmdline_
                  This read-only file holds the complete command line for the
                  process, unless the process is a zombie.  In the latter
                  case, there is nothing in this file: that is, a read on
                  this file will return 0 characters.
    
                  For processes which are still running, the command-line
                  arguments appear in this file in the same layout as they do
                  in process memory: If the process is well-behaved, it is a
                  set of strings separated by null bytes ('\0'), with a
                  further null byte after the last string.
    
                  This is the common case, but processes have the freedom to
                  override the memory region and break assumptions about the
                  contents or format of the _/proc/_ pid _/cmdline_ file.
    
                  If, after an execve(2), the process modifies its _argv_
                  strings, those changes will show up here.  This is not the
                  same thing as modifying the _argv_ array.
    
                  Furthermore, a process may change the memory location that
                  this file refers via prctl(2) operations such as
                  **PR_SET_MM_ARG_START**.
    
                  Think of this file as the command line that the process
                  wants you to see.
    


* * *
# proc_pid_autogroup

## NAME



           proc_pid_autogroup - group tasks for the scheduler
    


## DESCRIPTION



           _/proc/_ pid _/autogroup_ (since Linux 2.6.38)
                  See sched(7).
    


* * *
# deb-postrm

## NAME



           deb-postrm - package post-removal maintainer script
    


## SYNOPSIS



           **DEBIAN/postrm**
    


## DESCRIPTION



           A package can perform several post-removal actions via maintainer
           scripts, by including an executable _postrm_ file in its control
           archive (i.e. _DEBIAN/postrm_ during package creation).
    
           The script can be called in the following ways:
    
           _postrm_ **remove**
               After the package was removed.
    
           _postrm_ **purge**
               After the package was purged.
    
           _old-postrm_ **upgrade** _new-version_
               After the package was upgraded.
    
           _new-postrm_ **failed-upgrade** _old-version new-version_
               If the above **upgrade** call fails.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    
           _postrm_ **disappear** _overwriter-package overwriter-version_
               After all of the packages files have been replaced.
    
           _new-postrm_ **abort-install**
               If _preinst_ fails during **install**.
    
           _new-postrm_ **abort-install** _old-version new-version_
               If _preinst_ fails during **install** for an upgrade of a removed
               package.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    
           _new-postrm_ **abort-upgrade** _old-version new-version_
               If _preinst_ fails during **upgrade**.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    


* * *
# capability.conf

## NAME



           **capability.conf** - pam_cap module configuration file
    


## SYNOPSIS



           **/etc/security/capability.conf**
    


## DESCRIPTION



           The syntax for lines in this configuration file is:
    
           **# <-- ´#´ precedes a comment**
    
           **< IAB><SPACE><WHO>**
    
           Where **< IAB> **refers to the text format for an inheritable IAB
           capability tuple, see cap_text_formats(7) , or the words **all** or
           **none**.
    
           The reserved word **all** does _not_ grant _all the inheritable_
           _capabilities_ , but acts as a simple _pass-through_ for any prevailing
           IAB tuple capabilities. The reserved word **none** refers to an empty
           _Inheritable_ capability set (and by extension an empty _Ambient_
           vector).
    
           Here **< WHO> **refers to the space separated PAM username values that
           will be granted the specified _IAB_ tuple. A name prefixed with the
           character **@** refers to the locally defined **/etc/group** _etc_ users
           listed under that group name. An asterisk "***** " can be used to
           denote all users.
    
           The parsing of the file chooses the first line that applies to the
           authenticating user, and attempts to apply that and only that.
    
           Examples of valid syntax are:
    
               # only root gets to keep what it had
               all                                root
    
               # this should fire for user beta only, who will have
               # cap_chown dropped from their bounding set.
               !cap_chown                         beta
    
               # the next one should snag the members of the ´three´ group
               # granting them cap_setuid and cap_chown
               cap_setuid,cap_chown               @three
    
               # this would apply to beta and gamma, but beta is already
               # granted a lack of cap_chown above. Further, if gamma is
               # in the ´three´ group, it would not reach this line.
               cap_chown                          beta gamma
    
               # members of the ´one´ group are granted the cap_setuid Inheritable
               # capability, but cap_chown is dropped from their bounding set.
               !cap_chown,cap_setuid              @one
    
               # user alpha gets an ambient capability (unless it is also
               # a member of the groups ´one´ or ´three´).
               ^cap_setuid                        alpha
    
               # user delta (if not a member of groups ´one´ and ´three´) will get
               # cap_chown and cap_setgid Ambient capabilities, but have cap_setuid
               # dropped from its bounding set.
               ^cap_chown,^cap_setgid,!cap_setuid delta
    
               # any remaining members of group ´four´ will get the cap_setuid
               # Inheritable capability.
               cap_setuid                         @four
    


* * *
# deb-preinst

## NAME



           deb-preinst - package pre-installation maintainer script
    


## SYNOPSIS



           **DEBIAN/preinst**
    


## DESCRIPTION



           A package can perform several pre-installation actions via
           maintainer scripts, by including an executable _preinst_ file in its
           control archive (i.e. _DEBIAN/preinst_ during package creation).
    
           The script can be called in the following ways:
    
           _new-preinst_ **install**
               Before the package is installed.
    
           _new-preinst_ **install** _old-version new-version_
               Before a removed package is upgraded.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    
           _new-preinst_ **upgrade** _old-version new-version_
               Before the package is upgraded.
    
               The _new-version_ is passed only since dpkg 1.18.5.
    
           _old-preinst_ **abort-upgrade** _new-version_
               If _postrm_ fails during upgrade or fails on failed upgrade.
    


* * *
# proc_pid

## NAME



           /proc/pid/, /proc/self/ - process information
    


## DESCRIPTION



           _/proc/_ pid _/_
                  There is a numerical subdirectory for each running process;
                  the subdirectory is named by the process ID.  Each
                  _/proc/_ pid subdirectory contains the pseudo-files and
                  directories described below.
    
                  The files inside each _/proc/_ pid directory are normally
                  owned by the effective user and effective group ID of the
                  process.  However, as a security measure, the ownership is
                  made _root:root_ if the process's "dumpable" attribute is set
                  to a value other than 1.
    
                  Before Linux 4.11, _root:root_ meant the "global" root user
                  ID and group ID (i.e., UID 0 and GID 0 in the initial user
                  namespace).  Since Linux 4.11, if the process is in a
                  noninitial user namespace that has a valid mapping for user
                  (group) ID 0 inside the namespace, then the user (group)
                  ownership of the files under _/proc/_ pid is instead made the
                  same as the root user (group) ID of the namespace.  This
                  means that inside a container, things work as expected for
                  the container "root" user.
    
                  The process's "dumpable" attribute may change for the
                  following reasons:
    
                  •  The attribute was explicitly set via the prctl(2)
                     **PR_SET_DUMPABLE** operation.
    
                  •  The attribute was reset to the value in the file
                     _/proc/sys/fs/suid_dumpable_ (described below), for the
                     reasons described in prctl(2).
    
                  Resetting the "dumpable" attribute to 1 reverts the
                  ownership of the _/proc/_ pid _/*_ files to the process's
                  effective UID and GID.  Note, however, that if the
                  effective UID or GID is subsequently modified, then the
                  "dumpable" attribute may be reset, as described in
                  prctl(2).  Therefore, it may be desirable to reset the
                  "dumpable" attribute _after_ making any desired changes to
                  the process's effective UID or GID.
    
           _/proc/self/_
                  This directory refers to the process accessing the _/proc_
                  filesystem, and is identical to the _/proc_ directory named
                  by the process ID of the same process.
    


* * *
# firejail-users

## NAME



           firejail.users - Firejail user access database
    


## DESCRIPTION



           /etc/firejail/firejail.users lists the users allowed to run
           firejail SUID executable.  root user is allowed by default, user
           nobody is never allowed.
    
           If the user is not allowed to start the sandbox, Firejail will
           attempt to run the program without sandboxing it.
    
           If the file is not present in the system, all users are allowed to
           use the sandbox.
    
           Example:
    
                $ cat /etc/firejail/firejail.users
                dustin
                lucas
                mike
                eleven
    
           Use a text editor to add or remove users from the list. You can
           also use firecfg --add-users command. Example:
    
                $ sudo firecfg --add-users dustin lucas mike eleven
    
           By default, running firecfg creates the file and adds the current
           user to the list. Example:
    
                $ sudo firecfg
    
           See **man 1 firecfg** for details.
    


## ALTERNATIVE SOLUTION



           An alternative way of restricting user access to firejail
           executable is to create a special firejail user group and allow
           only users in this group to run the sandbox:
    
                # addgroup --system firejail
                # chown root:firejail /usr/bin/firejail
                # chmod 4750 /usr/bin/firejail
    


## FILES



           /etc/firejail/firejail.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_seccomp

## NAME



           /proc/pid/seccomp - secure computing mode
    


## DESCRIPTION



           _/proc/_ pid _/seccomp_ (Linux 2.6.12 to Linux 2.6.22)
                  This file can be used to read and change the process's
                  secure computing (seccomp) mode setting.  It contains the
                  value 0 if the process is not in seccomp mode, and 1 if the
                  process is in strict seccomp mode (see seccomp(2)).
                  Writing 1 to this file places the process irreversibly in
                  strict seccomp mode.  (Further attempts to write to the
                  file fail with the **EPERM** error.)
    
                  In Linux 2.6.23, this file went away, to be replaced by the
                  prctl(2) **PR_GET_SECCOMP** and **PR_SET_SECCOMP** operations (and
                  later by seccomp(2) and the _Seccomp_ field in
                  _/proc/_ pid _/status_).
    


* * *
# proc_pid_mountstats

## NAME



           /proc/pid/mountstats - mount statistics
    


## DESCRIPTION



           _/proc/_ pid _/mountstats_ (since Linux 2.6.17)
                  This file exports information (statistics, configuration
                  information) about the mounts in the process's mount
                  namespace (see mount_namespaces(7)).  Lines in this file
                  have the form:
    
                      device /dev/sda7 mounted on /home with fstype ext3 [stats]
                      (       1      )            ( 2 )             (3 ) (  4  )
    
                  The fields in each line are:
    
                  (1)  The name of the mounted device (or "nodevice" if there
                       is no corresponding device).
    
                  (2)  The mount point within the filesystem tree.
    
                  (3)  The filesystem type.
    
                  (4)  Optional statistics and configuration information.
                       Currently (as at Linux 2.6.26), only NFS filesystems
                       export information via this field.
    
                  This file is readable only by the owner of the process.
    


* * *
# proc_devices

## NAME



           /proc/devices - major numbers and device groups
    


## DESCRIPTION



           _/proc/devices_
                  Text listing of major numbers and device groups.  This can
                  be used by MAKEDEV scripts for consistency with the kernel.
    


* * *
# quotagrpadmins

## NAME



           quotagrpadmins - users responsible for group disk usage
    


## SYNOPSIS



           **/etc/quotagrpadmins**
    


## DESCRIPTION



           The **quotagrpadmins** file lists administrators of user groups who
           will receive a warning if **warnquota --group** command finds a group
           exceeding its disk usage limits.
    
           Each line consists of a group name followed by a colon and a user
           name. White space characters surrounding the names are allowed.
           Empty lines or lines starting with a hash sign or a semicolon are
           ignored.
    


## EXAMPLE



           # comment
           users: root
    


## FILES



           **/etc/quotagrpadmins**
                  list of group administrators
    


* * *
# proc_pid_numa_maps

## NAME



           /proc/pid/numa_maps - NUMA memory policy and allocation
    


## DESCRIPTION



           _/proc/_ pid _/numa_maps_ (since Linux 2.6.14)
                  See numa(7).
    


* * *
# proc_pid_uid_map

## NAME



           /proc/pid/gid_map, /proc/pid/uid_map - user and group ID mappings
    


## DESCRIPTION



           _/proc/_ pid _/gid_map_ (since Linux 3.5)
                  See user_namespaces(7).
    
           _/proc/_ pid _/uid_map_ (since Linux 3.5)
                  See user_namespaces(7).
    


* * *
# slapd-null

## NAME



           slapd-null - Null backend to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The Null backend to slapd(8) is surely the most useful part of
           **slapd** :
           - Searches return success but no entries.
           - Compares return compareFalse.
           - Updates return success (unless readonly is on) but do nothing.
           - Binds other than as the rootdn fail unless the database option
           "bind on" is given.
           - The slapadd(8) and slapcat(8) tools are equally exciting.
           Inspired by the /dev/null device.
    


## CONFIGURATION



           This **slapd.conf** option applies to the NULL backend database.  That
           is, it must follow a "database null" line and come before any
           subsequent "database" lines.  Other database options are described
           in the slapd.conf(5) manual page.
    
           **bind <on/off>**
                  Allow binds as any DN in this backend's suffix, with any
                  password.  The default is "off".
    
           **dosearch <on/off>**
                  If enabled, a single entry will be returned on all search
                  requests.  The entry's DN will be the same as the database
                  suffix.  The default is "off".
    


## EXAMPLE



           Here is a possible slapd.conf extract using the Null backend:
    
                  database null
                  suffix   "cn=Nothing"
                  bind     on
    


## ACCESS CONTROL



           The **null** backend does not honor any of the access control
           semantics described in slapd.access(5).
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


* * *
# proc_cpuinfo

## NAME



           /proc/cpuinfo - CPU and system architecture information
    


## DESCRIPTION



           _/proc/cpuinfo_
                  This is a collection of CPU and system architecture
                  dependent items, for each supported architecture a
                  different list.  Two common entries are _processor_ which
                  gives CPU number and _bogomips_ ; a system constant that is
                  calculated during kernel initialization.  SMP machines have
                  information for each CPU.  The lscpu(1) command gathers its
                  information from this file.
    


* * *
# mailto.conf

## NAME



           mailto.conf - configuration file for cups email notifier
    


## DESCRIPTION



           The **mailto.conf** file defines the local mail server and email
           notification preferences for CUPS.
    
           Each line in the file can be a configuration directive, a blank
           line, or a comment.  Configuration directives typically consist of
           a name and zero or more values separated by whitespace.  The
           configuration directive name and values are case-insensitive.
           Comment lines start with the # character.
    
       **DIRECTIVES**
           **Cc** _cc-address@domain.com_
                Specifies an additional recipient for all email
                notifications.
    
           **From** _from-address@domain.com_
                Specifies the sender of email notifications.
    
           **Sendmail** _sendmail command and options_
                Specifies the sendmail command to use when sending email
                notifications.  Only one _Sendmail_ or _SMTPServer_ line may be
                present in the **mailto.conf** file.  If multiple lines are
                present, only the last one is used.
    
           **SMTPServer** _servername_
                Specifies a SMTP server to send email notifications to.  Only
                one _Sendmail_ or _SMTPServer_ line may be present in the
                **mailto.conf** file.  If multiple lines are present, only the
                last one is used.
    
           **Subject** _subject-prefix_
                Specifies a prefix string for the subject line of an email
                notification.
    


* * *
# proc_cgroups

## NAME



           /proc/cgroups - control groups
    


## DESCRIPTION



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


* * *
# slapo-dyngroup

## NAME



           slapo-dyngroup - Dynamic Group overlay to slapd
    


## SYNOPSIS



           ETCDIR/slapd.conf
    


## DESCRIPTION



           The Dynamic Group overlay allows clients to use LDAP Compare
           operations to test the membership of a dynamic group the same way
           they would check against a static group. Compare operations
           targeting a group's static member attribute will be intercepted
           and tested against the configured dynamic group's URL attribute.
    
           Note that this intercept only happens if the actual Compare
           operation does not return a LDAP_COMPARE_TRUE result. So if a
           group has both static and dynamic members, the static member list
           will be checked first.
    


## CONFIGURATION



           This **slapd.conf** option applies to the Dynamic Group overlay.  It
           should appear after the **overlay** directive.
    
           **attrpair <memberAttr> <URLattr>**
                  Specify the attributes to be compared. A compare operation
                  on the _memberAttr_ will cause the _URLattr_ to be evaluated
                  for the result.
    


## EXAMPLES



             database mdb
             ...
             overlay dyngroup
             attrpair member memberURL
    


## FILES



           ETCDIR/slapd.conf
                  default slapd configuration file
    


## BACKWARD COMPATIBILITY



           The dyngroup overlay has been reworked with the 2.5 release to use
           a consistent namespace as with other overlays. As a side-effect
           the following cn=config parameters are deprecated and will be
           removed in a future release: **olcDGAttrPair** is replaced with
           olcDynGroupAttrPair **olcDGConfig** is replaced with olcDynGroupConfig
    


* * *
# systemd.dns-delegate

## NAME



           systemd.dns-delegate - DNS Server Delegation Configuration
    


## SYNOPSIS



               /etc/systemd/dns-delegate.d/*.dns-delegate
               /run/systemd/dns-delegate.d/*.dns-delegate
               /usr/local/lib/systemd/dns-delegate.d/*.dns-delegate
               /usr/lib/systemd/dns-delegate.d/*.dns-delegate
    


## DESCRIPTION



           *.dns-delegate files may be used to delegate DNS lookups in
           specific domains to specific DNS servers. These files are read by
           systemd-resolved.service(8). Each such file defines a combination
           of one or more DNS servers and one or more DNS domains. Each such
           definition synthesizes a DNS lookup scope that ensure lookups
           below the specified domains are sent to the specified DNS servers,
           possibly in addition to any per-interface scopes and the global
           scope that **systemd-resolved** maintains anyway.
    


## [DELEGATE] SECTION OPTIONS



           _DNS=_
               Takes one or more DNS server specifications, in the same
               syntax as the option of the same name in resolved.conf(5).
    
               Added in version 258.
    
           _Domains=_
               Takes one or more domain name specifications, in the same
               syntax as the option of the same name in resolved.conf(5).
    
               Added in version 258.
    
           _DefaultRoute=_
               Takes a boolean value, defaults to off. Controls whether this
               DNS server is a candidate for looking up records for which no
               better route exists.
    
               Added in version 258.
    


## EXAMPLES



           **Example 1.**
    
               # /etc/systemd/dns-delegate.d/foobar.dns-delegate
               [Delegate]
               DNS=203.0.113.47
               Domains=foobar.com
    
           This ensures lookups of "foobar.com" and any domains below it are
           directed to DNS server 203.0.113.47.
    


* * *
# proc_fs

## NAME



           /proc/fs/ - mounted filesystems
    


## DESCRIPTION



           _/proc/fs/_
                  Contains subdirectories that in turn contain files with
                  information about (certain) mounted filesystems.
    


* * *
# proc_pid_limits

## NAME



           /proc/pid/limits - resource limits
    


## DESCRIPTION



           _/proc/_ pid _/limits_ (since Linux 2.6.24)
                  This file displays the soft limit, hard limit, and units of
                  measurement for each of the process's resource limits (see
                  getrlimit(2)).  Up to and including Linux 2.6.35, this file
                  is protected to allow reading only by the real UID of the
                  process.  Since Linux 2.6.36, this file is readable by all
                  users on the system.
    


* * *
# proc_loadavg

## NAME



           /proc/loadavg - load average
    


## DESCRIPTION



           _/proc/loadavg_
                  The first three fields in this file are load average
                  figures giving the number of jobs in the run queue (state
                  R) or waiting for disk I/O (state D) averaged over 1, 5,
                  and 15 minutes.  They are the same as the load average
                  numbers given by uptime(1) and other programs.  The fourth
                  field consists of two numbers separated by a slash (/).
                  The first of these is the number of currently runnable
                  kernel scheduling entities (processes, threads).  The value
                  after the slash is the number of kernel scheduling entities
                  that currently exist on the system.  The fifth field is the
                  PID of the process that was most recently created on the
                  system.
    


* * *
# proc_pid_pagemap

## NAME



           /proc/pid/pagemap - mapping of virtual pages
    


## DESCRIPTION



           _/proc/_ pid _/pagemap_ (since Linux 2.6.25)
                  This file shows the mapping of each of the process's
                  virtual pages into physical page frames or swap area.  It
                  contains one 64-bit value for each virtual page, with the
                  bits set as follows:
    
                  63     If set, the page is present in RAM.
    
                  62     If set, the page is in swap space
    
                  61 (since Linux 3.5)
                         The page is a file-mapped page or a shared anonymous
                         page.
    
                  60–58 (since Linux 3.11)
                         Zero
    
                  57 (since Linux 5.14)
                         If set, the page is write-protected through
                         userfaultfd(2).
    
                  56 (since Linux 4.2)
                         The page is exclusively mapped.
    
                  55 (since Linux 3.11)
                         PTE is soft-dirty (see the kernel source file
                         _Documentation/admin-guide/mm/soft-dirty.rst_).
    
                  54–0   If the page is present in RAM (bit 63), then these
                         bits provide the page frame number, which can be
                         used to index _/proc/kpageflags_ and _/proc/kpagecount_.
                         If the page is present in swap (bit 62), then bits
                         4–0 give the swap type, and bits 54–5 encode the
                         swap offset.
    
                  Before Linux 3.11, bits 60–55 were used to encode the
                  base-2 log of the page size.
    
                  To employ _/proc/_ pid _/pagemap_ efficiently, use _/proc/_ pid _/maps_
                  to determine which areas of memory are actually mapped and
                  seek to skip over unmapped regions.
    
                  The _/proc/_ pid _/pagemap_ file is present only if the
                  **CONFIG_PROC_PAGE_MONITOR** kernel configuration option is
                  enabled.
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    


* * *
# srp_daemon_port@.service

## NAME



           srp_daemon_port@.service - srp_daemon_port@ systemd service that
           controls a single port
    


## SYNOPSIS



           srp_daemon_port@.service
    


## DESCRIPTION



           The srp_daemon_port@.service controls whether or not an srp_daemon
           process is monitoring the RDMA port specified as template
           argument. The format for the RDMA port name is _dev:port_ where _dev_
           is the name of an RDMA device and _port_ is an port number starting
           from one. Starting an instance of this template will start an
           srp_daemon process. Stopping an instance of this template will
           stop the srp_daemon process for the specified port. It can be
           prevented that srp_daemon is started for a certain port by masking
           the corresponding systemd service, e.g. **systemctl mask**
           **srp_daemon_port@mlx4_0:1**.
    
           A list of all RDMA device and port number pairs can be obtained
           e.g. as follows:
    
                  $ (cd /sys/class/infiniband >&/dev/null && for p in */ports/*; do
                     [ -e "$p" ] && echo "${p/\/ports\//:}"; done)
                  mlx4_0:1
                  mlx4_0:2
                  mlx4_1:1
                  mlx4_1:2
    


* * *
# user_contexts

## NAME



           user_contexts - The SELinux user contexts configuration files
    


## DESCRIPTION



           These optional user context configuration files contain entries
           that allow SELinux-aware login applications such as PAM(8)
           (running in their own process context), to determine the context
           that a users login session should run under.
    
           SELinux-aware login applications generally use one or more of the
           following libselinux functions that read these files from the
           active policy path:
                  get_default_context(3)
                  get_ordered_context_list(3)
                  get_ordered_context_list_with_level(3)
                  get_default_context_with_level(3)
                  get_default_context_with_role(3)
                  get_default_context_with_rolelevel(3)
                  query_user_context(3)
                  manual_user_enter_context(3)
    
           There can be one file for each SELinux user configured on the
           system. The file  path is formed using the path returned by
           selinux_user_contexts_path(3) for the active policy, with the
           SELinux user name appended, for example:
                  _/etc/selinux/{SELINUXTYPE}/contexts/users/unconfined_u_
                  _/etc/selinux/{SELINUXTYPE}/contexts/users/xguest_u_
    
           Where _{SELINUXTYPE}_ is the entry from the selinux configuration
           file _config_ (see selinux_config(5)).
    
           These files contain context information as described in the **FILE**
           **FORMAT** section.
    


## FILE FORMAT



           Each line in the user context configuration file consists of the
           following:
                  _login_process user_login_process_
    
           Where:
                  _login_process_
                         This consists of a _role_**:**_type_[**:**_range_] entry that
                         represents the login process context.
                  _user_login_process_
                         This consists of a _role_**:**_type_[**:**_range_] entry that
                         represents the user login process context.
    


## EXAMPLE



           # Example for xguest_u at
           /etc/selinux/targeted/contexts/users/xguest_u
           system_r:crond_t:s0           xguest_r:xguest_t:s0
           system_r:initrc_t:s0          xguest_r:xguest_t:s0
           system_r:local_login_t:s0     xguest_r:xguest_t:s0
           system_r:remote_login_t:s0    xguest_r:xguest_t:s0
           system_r:sshd_t:s0            xguest_r:xguest_t:s0
           system_r:xdm_t:s0             xguest_r:xguest_t:s0
           xguest_r:xguest_t:s0          xguest_r:xguest_t:s0
    


* * *
# deb-override

## NAME



           deb-override - Debian archive override file
    


## SYNOPSIS



           **override**
    


## DESCRIPTION



           While most information about a package can be found in the control
           file, some is managed centrally by the distribution czars rather
           than by the maintainer in order to offer some global consistency.
           This information is found in the override file.
    
           The override file has a simple whitespace-delimited format.
           Comments are allowed (denoted with a **#**).
    
               _package priority section_ [_maintainer-info_]
    
           _package_ is the name of the package.  Entries in the override file
           for packages not found in the tree of binary packages are ignored.
    
           _priority_ and _section_ correspond to the respective control fields
           available in the .deb.  The allowed values are specific to each
           distribution archive.
    
           _maintainer-info_ , if present, can be either the name of a
           maintainer for an unconditional override, or else _old-maintainer_
           **= > **_new-maintainer_ to perform a substitution.
    
           The override files used to make the official Packages lists may be
           found in the _indices_ directory on any Debian mirror.
    


* * *
# subgid

## NAME



           subgid - the configuration for subordinate group ids
    


## DESCRIPTION



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


## LOCAL SUBORDINATE DELEGATION



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


## FILES



           /etc/subgid
               Per user subordinate group IDs.
    
           /etc/subgid-
               Backup file for /etc/subgid.
    


* * *
# proc_pid_wchan

## NAME



           /proc/pid/wchan - wait channel
    


## DESCRIPTION



           _/proc/_ pid _/wchan_ (since Linux 2.6.0)
                  The symbolic name corresponding to the location in the
                  kernel where the process is sleeping.
    
                  Permission to access this file is governed by a ptrace
                  access mode **PTRACE_MODE_READ_FSCREDS** check; see ptrace(2).
    


* * *
# proc_tty

## NAME



           /proc/tty/ - tty
    


## DESCRIPTION



           _/proc/tty/_
                  Subdirectory containing the pseudo-files and subdirectories
                  for tty drivers and line disciplines.
    


* * *
# deb-split

## NAME



           deb-split - Debian multi-part binary package format
    


## SYNOPSIS



           _filename_**.deb**
    


## DESCRIPTION



           The multi-part **.deb** format is used to split big packages into
           smaller pieces to ease transport in small media.
    


## FORMAT



           The file is an **ar** archive with a magic value of **! <arch>**.  The file
           names might contain a trailing slash (since dpkg 1.15.6).
    
           The first member is named **debian-split** and contains a series of
           lines, separated by newlines.  Currently eight lines are present:
    
           •   The format version number, **2.1** at the time this manual page
               was written.
    
           •   The package name.
    
           •   The package version.
    
           •   The md5sum of the package.
    
           •   The total size of the package.
    
           •   The maximum part size.
    
           •   The current part number, followed by a slash and the total
               amount of parts (as in ‘1/10’).
    
           •   The package architecture (since dpkg 1.16.1).
    
           Programs which read multi-part archives should be prepared for the
           minor format version number to be increased and additional lines
           to be present, and should ignore these if this is the case.
    
           If the major format version number has changed, an incompatible
           change has been made and the program should stop.  If it has not,
           then the program should be able to safely continue, unless it
           encounters an unexpected member in the archive (except at the
           end), as described below.
    
           The second, last required member is named **data.**_N_ , where _N_ denotes
           the part number.  It contains the raw part data.
    
           These members must occur in this exact order.  Current
           implementations should ignore any additional members after **data.**_N_.
           Further members may be defined in the future, and (if possible)
           will be placed after these two.
    


* * *
# proc_timer_list

## NAME



           /proc/timer_list - pending timers
    


## DESCRIPTION



           _/proc/timer_list_ (since Linux 2.6.21)
                  This read-only file exposes a list of all currently pending
                  (high-resolution) timers, all clock-event sources, and
                  their parameters in a human-readable form.
    


* * *
# nfsrahead

## NAME



           nfsrahead - Configure the readahead for NFS mounts
    


## SYNOPSIS



           nfsrahead [-F] [-d] <device>
    


## DESCRIPTION



           _nfsrahead_ is a tool intended to be used with udev to set the
           _read_ahead_kb_ parameter of NFS mounts, according to the
           configuration file (see _CONFIGURATION_). _device_ is the device
           number for the NFS backing device as provided by the kernel.
    


## OPTIONS



           **-F** Send messages to _stderr_ instead of _syslog_
    
           **-d** Increase the debugging level.
    


## CONFIGURATION



           _nfsrahead_ is configured in _/etc/nfs.conf_ , in the section titled
           _nfsrahead_.  It accepts the following configurations.
    
           **nfs= <value>**
                  The readahead value applied to NFSv3 mounts.
    
           **nfs4= <value>**
                  The readahead value applied to NFSv4 mounts.
    
           **default= <value>**
                  The default configuration when none of the configurations
                  above is set.
    


## EXAMPLE CONFIGURATION



           [nfsrahead]
           nfs=15000              # readahead of 15000 for NFSv3 mounts
           nfs4=16000             # readahead of 16000 for NFSv4 mounts
           default=128            # default is 128
    


## BUGS



           No known bugs.
    


* * *
# srp_daemon.service

## NAME



           srp_daemon.service - srp_daemon systemd service that controls all
           ports
    


## SYNOPSIS



           srp_daemon.service
    


## DESCRIPTION



           The srp_daemon.service controls whether or not any srp_daemon
           processes are running. Although no srp_daemon processes are
           controlled directly by the srp_daemon.service, this service
           controls whether or not any srp_daemon_port@.service are allowed
           to be active. Each srp_daemon_port@.service controls one
           srp_daemon process.
    


* * *
# nologin

## NAME



           nologin - prevent unprivileged users from logging into the system
    


## DESCRIPTION



           If the file _/etc/nologin_ exists and is readable, login(1) will
           allow access only to root.  Other users will be shown the contents
           of this file and their logins will be refused.  This provides a
           simple way of temporarily disabling all unprivileged logins.
    


## FILES



           _/etc/nologin_
    


* * *
# proc_pid_timers

## NAME



           /proc/pid/timers - POSIX timers
    


## DESCRIPTION



           _/proc/_ pid _/timers_ (since Linux 3.10)
                  A list of the POSIX timers for this process.  Each timer is
                  listed with a line that starts with the string "ID:".  For
                  example:
    
                      ID: 1
                      signal: 60/00007fff86e452a8
                      notify: signal/pid.2634
                      ClockID: 0
                      ID: 0
                      signal: 60/00007fff86e452a8
                      notify: signal/pid.2634
                      ClockID: 1
    
                  The lines shown for each timer have the following meanings:
    
                  _ID_     The ID for this timer.  This is not the same as the
                         timer ID returned by timer_create(2); rather, it is
                         the same kernel-internal ID that is available via
                         the _si_timerid_ field of the _siginfo_t_ structure (see
                         sigaction(2)).
    
                  _signal_ This is the signal number that this timer uses to
                         deliver notifications followed by a slash, and then
                         the _sigev_value_ value supplied to the signal
                         handler.  Valid only for timers that notify via a
                         signal.
    
                  _notify_ The part before the slash specifies the mechanism
                         that this timer uses to deliver notifications, and
                         is one of "thread", "signal", or "none".
                         Immediately following the slash is either the string
                         "tid" for timers with **SIGEV_THREAD_ID** notification,
                         or "pid" for timers that notify by other mechanisms.
                         Following the "." is the PID of the process (or the
                         kernel thread ID of the thread)  that will be
                         delivered a signal if the timer delivers
                         notifications via a signal.
    
                  _ClockID_
                         This field identifies the clock that the timer uses
                         for measuring time.  For most clocks, this is a
                         number that matches one of the user-space **CLOCK_***
                         constants exposed via _< time.h>_.
                         **CLOCK_PROCESS_CPUTIME_ID** timers display with a value
                         of -6 in this field.  **CLOCK_THREAD_CPUTIME_ID** timers
                         display with a value of -2 in this field.
    
                  This file is available only when the kernel was configured
                  with **CONFIG_CHECKPOINT_RESTORE**.
    


* * *
# networks

## NAME



           networks - network name information
    


## DESCRIPTION



           The file _/etc/networks_ is a plain ASCII file that describes known
           DARPA networks and symbolic names for these networks.  Each line
           represents a network and has the following structure:
    
                  _name number aliases ..._
    
           where the fields are delimited by spaces or tabs.  Empty lines are
           ignored.  The hash character (**#**) indicates the start of a comment:
           this character, and the remaining characters up to the end of the
           current line, are ignored by library functions that process the
           file.
    
           The field descriptions are:
    
           _name_   The symbolic name for the network.  Network names can
                  contain any printable characters except white-space
                  characters or the comment character.
    
           _number_ The official number for this network in numbers-and-dots
                  notation (see inet(3)).  The trailing ".0" (for the host
                  component of the network address) may be omitted.
    
           _aliases_
                  Optional aliases for the network.
    
           This file is read by the route(8) and netstat(8) utilities.  Only
           Class A, B, or C networks are supported, partitioned networks
           (i.e., network/26 or network/28) are not supported by this file.
    


## FILES



           _/etc/networks_
                  The networks definition file.
    


* * *
# proc_ide

## NAME



           /proc/ide/ - IDE channels and attached devices
    


## DESCRIPTION



           _/proc/ide_
                  This directory exists on systems with the IDE bus.  There
                  are directories for each IDE channel and attached device.
                  Files include:
    
                      cache              buffer size in KB
                      capacity           number of sectors
                      driver             driver version
                      geometry           physical and logical geometry
                      identify           in hexadecimal
                      media              media type
                      model              manufacturer's model number
                      settings           drive settings
                      smart_thresholds   IDE disk management thresholds (in hex)
                      smart_values       IDE disk management values (in hex)
    
                  The hdparm(8) utility provides access to this information
                  in a friendly format.
    


* * *
# sandbox

## NAME



           sandbox.conf - user config file for the SELinux sandbox
    


## DESCRIPTION



           When running sandbox with the -C argument, it will be confined
           using control groups and a system administrator can specify how
           the sandbox is confined.
    
           Everything after "#" is ignored, as are empty lines.  All
           arguments should be separated by and equals sign ("=").
    
           These keywords are allowed.
    
                  **NAME** The name of the sandbox control group.  Default is
                         "sandbox".
    
                  **CPUAFFINITY**
                         Which cpus to assign sandbox to.  The default is
                         ALL, but users can specify a comma-separated list
                         with dashes ("-") to represent ranges.  Ex: 0-2,5
    
                  **MEMUSAGE**
                         How much memory to allow sandbox to use.  The
                         default is 80%.  Users can specify either a
                         percentage or a value in the form of a number
                         followed by one of the suffixes K, M, G to denote
                         kilobytes, megabytes or gigabytes respectively.  Ex:
                         50% or 100M
    
                  **CPUUSAGE**
                         Percentage of cpu sandbox should be allowed to use.
                         The default is 80%.  Specify a value followed by a
                         percent sign ("%"). Ex: 50%
    


* * *