tripathysagar/man_text huggingface dataset:
# srp-entry

## NAME



           srp-entry - Generate a SRP-SHA1 Server Entry
    


## SYNOPSIS



           **srp-entry**[ _-i index_ ] [ _clientname_ ]
    


## DESCRIPTION



           This utility generates an entry suitable for use in the
           /etc/ppp/srp-secrets file on a PPP EAP SRP-SHA1 authenticator
           ("server").  This file has the same basic layout as the other
           pppd(8) authentication files, /etc/ppp/pap-secrets and
           /etc/ppp/chap-secrets.  Thus, the entry generated has at least
           four main fields separated by spaces.  The first field is the
           authenticatee ("client") name.  The second is the server name.
           The third is the secret.  The fourth is the allowed (or assigned)
           IP address for the client, and defaults to "*".  Additional fields
           can contain additional IP addresses or pppd options; see pppd(8)
           for details.
    
           The third field has three subfields, separated by colons.  The
           first subfield is the index of the modulus and generator from
           SRP's /etc/tpasswd.conf.  The special value 0 is used to represent
           the well-known modulus and generator specified in the EAP SRP-SHA1
           draft.  The second subfield is the password validator.  The third
           is the password salt.  These latter two values are encoded in
           base64 notation.
    


## OPTIONS



           _-i <index>_
                  Specifies the modulus/generator index in /etc/tpasswd.conf.
                  In order to use this option, you will need to run the
                  "tconf" utility from the SRP package to generate local
                  entries for this file.  Note that if these values are not
                  known to the client, the client will be forced to run time-
                  consuming safety tests on the values used.  For this
                  reason, using the well-known values is recommended.
    
           _< clientname>_
                  Specifies the client name.  The password validator is a
                  hashed combination of the client's name and password, and
                  both are required.  If the client name is not supplied on
                  the command line, srp-entry will prompt for the client name
                  first.
    


## FILES



           **/etc/ppp/srp-secrets**
                  Usernames, passwords and IP addresses for SRP
                  authentication.  This file should be owned by root and not
                  readable or writable by any other user.  Pppd will log a
                  warning if this is not the case.  Note that srp-entry does
                  not write to this file.  The user is responsible for
                  copying the output of srp-entry into this file.
    
           **/etc/tpasswd.conf**
                  Indexed copies of tested modulus/generator combinations;
                  part of the SRP package.
    


* * *
# arptables-nft-restore

## NAME



           arptables-restore — Restore ARP Tables (nft-based)
    


## SYNOPSIS



           **arptables-restore**
    


## DESCRIPTION



           **arptables-restore** is used to restore ARP Tables from data
           specified on STDIN or via a file as first argument.  Use I/O
           redirection provided by your shell to read from a file
    
           **arptables-restore**
                  flushes (deletes) all previous contents of the respective
                  ARP Table.
    


* * *
# getpcaps

## NAME



           getpcaps - display process capabilities
    


## SYNOPSIS



           **getpcaps**[optional args] _pid_...
    


## DESCRIPTION



           **getpcaps** displays the capabilities on the processes indicated by
           the _pid_ value(s) given on the command line.  A _pid_ of 0 displays
           the capabilities of the process that is running **getpcaps** itself.
    
           The capability Set of the process is displayed in the text
           represenation described here: cap_text_formats(7).
    
           Optional arguments:
    
           **--help** or **--usage**
                  Displays usage information and exits.
    
           **--ugly** or **--legacy**
                  Displays output in a somewhat ugly legacy format.
    
           **--verbose**
                  Displays usage in a legacy-like format but not quite so
                  ugly in modern default terminal fonts.
    
           **--iab** Displays IAB tuple capabilities from the process. The
                  output format here is also described in
                  cap_text_formats(7).  Double quotes encase the regular
                  process capabilities and square brackets encase the IAB
                  tuple. This format is also used by captree(8).
    


* * *
# systemd-vconsole-setup.service

## NAME



           systemd-vconsole-setup.service, systemd-vconsole-setup - Configure
           the virtual consoles
    


## SYNOPSIS



           systemd-vconsole-setup.service
    
           **/usr/lib/systemd/systemd-vconsole-setup**[TTY]
    


## DESCRIPTION



           **systemd-vconsole-setup** sets up and configures either all virtual
           consoles, or — if the optional _TTY_ parameter is provided — a
           specific one. When the system is booting up,
           systemd-vconsole-setup.service is called by systemd-udevd(8)
           during VT console subsystem initialization. Also,
           systemd-localed.service(8) invokes it as needed when language or
           console changes are made. Internally, this program calls
           loadkeys(1) and setfont(8).
    
           Execute **systemctl restart systemd-vconsole-setup.service** in order
           to apply any manual changes made to /etc/vconsole.conf.
    
           See vconsole.conf(5) for information about the configuration files
           and kernel command line options understood by this program.
    


## CREDENTIALS



           **systemd-vconsole-setup** supports the service credentials logic as
           implemented by _ImportCredential=_ /_LoadCredential=_ /_SetCredential=_
           (see systemd.exec(5) for details). The following credentials are
           used when passed in:
    
           _vconsole.keymap_ , _vconsole.keymap_toggle_
               The keymap (and toggle keymap) to apply. The matching options
               in vconsole.conf and on the kernel command line take
               precedence over these credentials.
    
               Note the relationship to the _firstboot.keymap_ credential
               understood by **systemd-firstboot.service**(8): both ultimately
               affect the same setting, but _firstboot.keymap_ is written into
               /etc/vconsole.conf on first boot (if not already configured),
               and then read from there by **systemd-vconsole-setup** , while
               _vconsole.keymap_ is read on every boot, and is not persisted to
               disk (but any configuration in vconsole.conf will take
               precedence if present).
    
               Added in version 253.
    
           _vconsole.font_ , _vconsole.font_map_ , _vconsole.font_unimap_
               The console font settings to apply. The matching options in
               vconsole.conf and on the kernel command line take precedence
               over these credentials.
    
               Added in version 253.
    


* * *
# xfs_ncheck

## NAME



           xfs_ncheck - generate pathnames from i-numbers for XFS
    


## SYNOPSIS



           **xfs_ncheck**[ **-i** _ino_ ] ... [ **-f**] [ **-s**] [ **-l** _logdev_ ] _device_
           **xfs_ncheck -V**
    


## DESCRIPTION



           **xfs_ncheck** with no **-i** arguments generates an inode number and
           pathname list of all files on the given filesystem. Names of
           directory files are followed by **/.**.  The output is not sorted in
           any particular order.  The filesystem to be examined is specified
           by the _device_ argument, which should be the disk or volume device
           for the filesystem.  Filesystems stored in files can also be
           checked, using the **-f** flag.
    


## OPTIONS



           **-f** Specifies that the filesystem image to be processed is
                    stored in a regular file at _device_ (see the **mkfs.xfs -d**
                    _file_ option). This might happen if an image copy of a
                    filesystem has been made into an ordinary file.
    
           **-l** _logdev_
                    Specifies the device where the filesystem's external log
                    resides.  Only for those filesystems which use an
                    external log. See the **mkfs.xfs -l** option, and refer to
                    xfs(5) for a detailed description of the XFS log.
    
           **-s** Limits the report to special files and files with
                    setuserid mode.  This option may be used to detect
                    violations of security policy.
    
           **-i** _ino_   Limits the report to only those files whose inode numbers
                    follow.  May be given multiple times to select multiple
                    inode numbers.
    
           **-V** Prints the version number and exits.
    
           If the filesystem is seriously corrupted, or very busy and looks
           like it is corrupt, a message of the form that would be generated
           by the xfs_db(8) "check" command may appear.
    
           **xfs_ncheck** is only useful with XFS filesystems.
    


* * *
# genhomedircon

## NAME



           genhomedircon - generate SELinux file context configuration
           entries for user home directories
    


## DESCRIPTION



           **genhomedircon** is a script that executes **semodule** to rebuild the
           currently active SELinux policy (without reloading it) and to
           create the labels for each user home directory based on directory
           paths returned by calls to getpwent().
    
           The latter functionality depends on the "usepasswd" parameter
           being set to "true" (default) in /etc/selinux/semanage.conf.
    
           This script is usually executed by **semanage** although this default
           behavior can be optionally modified by setting to "true" the
           "disable-genhomedircon" in /etc/selinux/semanage.conf.
    
           Directories can be excluded from the list of home directories by
           the setting "ignoredirs" in /etc/selinux/semanage.conf.
    


* * *
# semodule_unpackage

## NAME



           semodule_unpackage - Extract policy module and file context file
           from an SELinux policy module package.
    


## SYNOPSIS



           **semodule_unpackage ppfile modfile [fcfile]**
    


## DESCRIPTION



           semodule_unpackage is a tool used to extract SELinux policy module
           file and file context file from an SELinux Policy Package.
    


## EXAMPLE



           # Extract the httpd module file from httpd policy package.
           $ semodule_unpackage httpd.pp httpd.mod httpd.fc
    


* * *
# e2freefrag

## NAME



           e2freefrag - report free space fragmentation information
    


## SYNOPSIS



           **e2freefrag**[ **-c chunk_kb**] [ **-h**] **filesys**
    


## DESCRIPTION



           **e2freefrag** is used to report free space fragmentation on ext2/3/4
           file systems.  _filesys_ is the file system device name (e.g.
           _/dev/hdc1_ , _/dev/md0_).  The **e2freefrag** program will scan the block
           bitmap information to check how many free blocks are present as
           contiguous and aligned free space. The percentage of contiguous
           free blocks of size and of alignment _chunk_kb_ is reported.  It
           also displays the minimum/maximum/average free chunk size in the
           file system, along with a histogram of all free chunks.  This
           information can be used to gauge the level of free space
           fragmentation in the file system.
    


## OPTIONS



           **-c** _chunk_kb_
                  If a chunk size is specified, then **e2freefrag** will print
                  how many free chunks of size _chunk_kb_ are available in
                  units of kilobytes (Kb).  The chunk size must be a power of
                  two and be larger than file system block size.
    
           **-h** Print the usage of the program.
    


## EXAMPLE



           # e2freefrag /dev/vgroot/lvhome
           Device: /dev/vgroot/lvhome
           Blocksize: 4096 bytes
           Total blocks: 1504085
           Free blocks: 292995 (19.5%)
    
           Min. free extent: 4 KB
           Max. free extent: 24008 KB
           Avg. free extent: 252 KB
    
           HISTOGRAM OF FREE EXTENT SIZES:
           Extent Size Range :   Free extents   Free Blocks  Percent
               4K...    8K- :           704           704     0.2%
               8K...   16K- :           810          1979     0.7%
              16K...   32K- :           843          4467     1.5%
              32K...   64K- :           579          6263     2.1%
              64K...  128K- :           493         11067     3.8%
             128K...  256K- :           394         18097     6.2%
             256K...  512K- :           281         25477     8.7%
             512K... 1024K- :           253         44914    15.3%
               1M...    2M- :           143         51897    17.7%
               2M...    4M- :            73         50683    17.3%
               4M...    8M- :            37         52417    17.9%
               8M...   16M- :             7         19028     6.5%
              16M...   32M- :             1          6002     2.0%
    


* * *
# genpolbools

## NAME



           genpolbools - Rewrite a binary policy with different boolean
           settings
    


## SYNOPSIS



           **genpolbools oldpolicy booleans newpolicy**
    


## DESCRIPTION



           **genpolbools** rewrites an existing binary policy with different
           boolean settings, generating a new binary policy.  The booleans
           file specifies the different boolean settings using name=value
           lines, where value can be 0 or false to disable the boolean or 1
           or true to enable it.
    


* * *
# sepolicy-manpage

## NAME



           sepolicy-manpage - Generate a man page based on the installed
           SELinux Policy
    


## SYNOPSIS



           **sepolicy manpage [-w] [-h] [-p PATH ] [-r ROOTDIR ] [-a | -d ]**
    


## DESCRIPTION



           Use **sepolicy manpage** to generate manpages based on SELinux Policy.
    


## OPTIONS



           _-a, --all_
                  Generate Man Pages for All Domains
    
           _-d, --domain_
                  Generate a Man Page for the specified domain. (Supports
                  multiple commands)
    
           _-h, --help_
                  Display help message
    
           _-o, --os_
                  Specify the name of the OS to be used in the man page (only
                  affects HTML man pages)
    
           _-p, --path_
                  Specify the directory to store the created man pages.
                  (Default to /tmp)
    
           _-r, --root_
                  Specify alternative root directory to generate man pages
                  from. (Default to /)
    
           _--source_files_
                  Use file_contexts and policy.xml files from the specified
                  root directory (the alternative root needs to include both
                  files)
    
           _-w, --web_
                  Generate an additional HTML man pages for the specified
                  domain(s)
    


## EXAMPLE



           Generate man pages for all available domains
           # sepolicy manpage -a
           Generate an HTML man page for domain alsa_t, setting the OS name to "My_distro"
           # sepolicy manpage -o My_distro -d alsa_t -w
    


* * *
# sefcontext_compile

## NAME



           sefcontext_compile - compile file context regular expression files
    


## SYNOPSIS



           **sefcontext_compile**[**-o** _outputfile_] [**-p** _policyfile_] _inputfile_
    


## DESCRIPTION



           **sefcontext_compile** is used to compile file context regular
           expressions into **pcre**(3) format.
    
           The compiled file is used by libselinux file labeling functions.
    
           By default **sefcontext_compile** writes the compiled pcre file with
           the **.bin** suffix appended (e.g. _inputfile_**.bin**).
    


## OPTIONS



           **-o** Specify an _outputfile_ that must be a fully qualified file
                  name as the **.bin** suffix is not automatically added.
    
           **-p** Specify a binary _policyfile_ that will be used to validate
                  the context entries in the _inputfile_
                  If an invalid context is found the pcre formatted file will
                  not be written and an error will be returned.
    


## RETURN VALUE



           On error -1 is returned.  On success 0 is returned.
    


## EXAMPLES



           **Example 1:**
           sefcontext_compile
           /etc/selinux/targeted/contexts/files/file_contexts
    
           Results in the following file being generated:
                  /etc/selinux/targeted/contexts/files/file_contexts.bin
    
           **Example 2:**
           sefcontext_compile -o new_fc.bin
           /etc/selinux/targeted/contexts/files/file_contexts
    
           Results in the following file being generated in the cwd:
                  new_fc.bin
    


* * *
# xfs_mkfile

## NAME



           xfs_mkfile - create an XFS file
    


## SYNOPSIS



           **xfs_mkfile**[ **-v**] [ **-n**] [ **-p**] _size_[**k** |**b** |**m** |**g**] _filename_ ...
           **xfs_mkfile -V**
    


## DESCRIPTION



           **xfs_mkfile** creates one or more files. The file is padded with
           zeroes by default.  The default size is in bytes, but it can be
           flagged as kilobytes, blocks, megabytes, or gigabytes with the **k** ,
           **b** , **m** , or **g** suffixes, respectively.
    


## OPTIONS



           **-v** Verbose. Report the names and sizes of created files.
    
           **-n** No bytes. Create a holey file - that is, do not write out
                  any data, just seek to end of file and write a block.
    
           **-p** Preallocate.  The file is preallocated, then overwritten
                  with zeroes, then truncated to the desired size.
    
           **-V** Prints the version number and exits.
    


* * *
# pppoe-discovery

## NAME



           pppoe-discovery - perform PPPoE discovery
    


## SYNOPSIS



           **pppoe-discovery**[ _options_ ]
           **pppoe-discovery**{ **-V** | **-h**}
    


## DESCRIPTION



           **pppoe-discovery** performs the same discovery process as **pppoe** , but
           does not initiate a session.  It sends a PADI packet and then
           prints the names of access concentrators in each PADO packet it
           receives.
    


## OPTIONS



           **-I** _interface_
                  The **-I** option specifies the Ethernet interface to use.
                  Under Linux, it is typically eth0 or eth1.  The interface
                  should be “up” before you start **pppoe-discovery** , but should
                  _not_ be configured to have an IP address.  This option is
                  mandatory.
    
           **-D** _file_name_
                  The **-D** option causes every packet to be dumped to the
                  specified _file_name_.  This is intended for debugging only.
    
           **-U**
                  Causes **pppoe-discovery** to use the Host-Uniq tag in its
                  discovery packets.  This lets you run multiple instances of
                  **pppoe-discovery** and/or **pppoe** without having their discovery
                  packets interfere with one another.  You must supply this
                  option to _all_ instances that you intend to run
                  simultaneously.
    
           **-S** _service_name_
                  Specifies the desired service name.  **pppoe-discovery** will
                  only accept access concentrators which can provide the
                  specified service.  In most cases, you should _not_ specify
                  this option.  Use it only if you know that there are
                  multiple access concentrators or know that you need a
                  specific service name.
    
           **-C** _ac_name_
                  Specifies the desired access concentrator name.
                  **pppoe-discovery** will only accept the specified access
                  concentrator.  In most cases, you should _not_ specify this
                  option.  Use it only if you know that there are multiple
                  access concentrators.  If both the **-S** and **-C** options are
                  specified, they must _both_ match.
    
           **-A**
                  This option is accepted for compatibility with **pppoe** , but
                  has no effect.
    
           **-V** | **-h**
                  Either of these options causes **pppoe-discovery** to print its
                  version number and usage information, then exit.
    


* * *
# rarp

## NAME



           rarp - manipulate the system RARP table
    


## SYNOPSIS



           **rarp [-V] [--version] [-h] [--help]**
           **rarp -a**
           **rarp [-v] -d hostname ...**
           **rarp [-v] [-t type] -s hostname hw_addr**
    


## NOTE



           This program is obsolete.  From version 2.3, the Linux kernel no
           longer contains RARP support.  For a replacement RARP daemon, see
           _ftp://ftp.dementia.org/pub/net-tools_
    


## DESCRIPTION



           **Rarp** manipulates the kernel's RARP table in various ways.  The
           primary options are clearing an address mapping entry and manually
           setting up one.  For debugging purposes, the **rarp** program also
           allows a complete dump of the RARP table.
    


## OPTIONS



           **-V** Display the version of RARP in use.
    
           **-v** Tell the user what is going on by being verbose.
    
           **-t type**
                  When setting or reading the RARP table, this optional
                  parameter tells **rarp** which class of entries it should check
                  for.  The default value of this parameter is **ether**(i.e.
                  hardware code **0x01** for **IEEE 802.3 10Mbps Ethernet .** Other
                  values might include network technologies such as **AX.25**
                  **(ax25)** and **NET/ROM (netrom).**
    
           **-a**
    
           **--list** Lists the entries in the RARP table.
    
           **-d hostname**
    
           **--delete hostname**
                  Remove all RARP entries for the specified host.
    
           **-s hostname hw_addr**
    
           **--set hostname hw_addr**
                  Create a RARP address mapping entry for host **hostname** with
                  hardware address set to **hw_addr**.  The format of the
                  hardware address is dependent on the hardware class, but
                  for most classes one can assume that the usual presentation
                  can be used.  For the Ethernet class, this is 6 bytes in
                  hexadecimal, separated by colons.
    


## WARNING



           Some systems (notably older Suns) assume that the host replying to
           a RARP query can also provide other remote boot services.
           Therefore never gratuitously add rarp entries unless you wish to
           meet the wrath of the network administrator.
    


## FILES



           _/proc/net/rarp,_
    


* * *
# idmapd

## NAME



           **rpc.idmapd** — NFSv4 ID <-> Name Mapper
    


## SYNOPSIS



           **rpc.idmapd**[**-h**] [**-f**] [**-v**] [**-C**] [**-S**] [**-p** _path_] [**-c** _path_]
    


## DESCRIPTION



           **rpc.idmapd** is the NFSv4 ID <-> name mapping daemon.  It provides
           functionality to the NFSv4 kernel client and server, to which it
           communicates via upcalls, by translating user and group IDs to
           names, and vice versa.
    
           The system derives the _user_ part of the string by performing a
           password or group lookup.  The lookup mechanism is configured in
           _/etc/idmapd.conf_
    
           By default, the _domain_ part of the string is the system's DNS
           domain name.  It can also be specified in _/etc/idmapd.conf_ if the
           system is multi-homed, or if the system's DNS domain name does not
           match the name of the system's Kerberos realm.
    
           When the domain is not specified in /etc/idmapd.conf the local DNS
           server will be queried for the **_nfsv4idmapdomain** text record. If
           the record exists that will be used as the domain. When the record
           does not exist, the domain part of the DNS domain will used.
    
           Note that on more recent kernels only the NFSv4 server uses
           **rpc.idmapd**.  The NFSv4 client instead uses _nfsidmap_(8), and only
           falls back to **rpc.idmapd** if there was a problem running the
           _nfsidmap_(8) program.
    
           The options are as follows:
    
           **-h** Display usage message.
    
           **-v** Increases the verbosity level (can be specified
                        multiple times).
    
           **-f** Runs **rpc.idmapd** in the foreground and prints all
                        output to the terminal.
    
           **-p** _path_      Specifies the location of the RPC pipefs to be _path_.
                        The default value is "/var/lib/nfs/rpc_pipefs".
    
           **-c** _path_      Use configuration file _path_.  This option is
                        deprecated.
    
           **-C** Client-only: perform no idmapping for any NFS server,
                        even if one is detected.
    
           **-S** Server-only: perform no idmapping for any NFS client,
                        even if one is detected.
    


## CONFIGURATION FILES



           **rpc.idmapd** recognizes the following value from the **[general]**
           section of the _/etc/nfs.conf_ configuration file:
    
           **pipefs-directory**
                        Equivalent to **-p**.
    
           All other settings related to id mapping are found in the
           _/etc/idmapd.conf_ configuration file.
    


## EXAMPLES



           **rpc.idmapd -f -vvv**
    
           Runs **rpc.idmapd** printing all messages to console, and with a
           verbosity level of 3.
    


## FILES



           _/etc/idmapd.conf_ , _/etc/nfs.conf_
    


* * *
# systemd-integritysetup@.service

## NAME



           systemd-integritysetup@.service, systemd-integritysetup - Disk
           integrity protection logic
    


## SYNOPSIS



           systemd-integritysetup@.service
    
           /usr/lib/systemd/systemd-integritysetup
    


## DESCRIPTION



           systemd-integritysetup@.service is a service responsible for
           setting up integrity protected block devices. It should be
           instantiated for each device that requires integrity protection.
    
           At early boot and when the system manager configuration is
           reloaded, entries from integritytab(5) are converted into
           systemd-integritysetup@.service units by
           systemd-integritysetup-generator(8).
    
           systemd-integritysetup@.service calls **systemd-integritysetup**.
    


## COMMANDS



           The following commands are understood by **systemd-integritysetup** :
    
           **attach** _volume device_ [_key-file|-_] [_option(s)|-_]
               Create a block device _volume_ using _device_. See integritytab(5)
               and **Kernel dm-integrity******[1] documentation for details.
    
               Added in version 250.**detach** _volume_
               Detach (destroy) the block device _volume_.
    
               Added in version 250.
    
           **help**
               Print short information about command syntax.
    
               Added in version 250.
    


## NOTES



            1. Kernel dm-integrity
               https://docs.kernel.org/admin-guide/device-mapper/dm-integrity.html
    


* * *
# update-pciids

## NAME



           update-pciids - download new version of the PCI ID list
    


## SYNOPSIS



           **update-pciids**[**-q**]
    


## DESCRIPTION



           **update-pciids** fetches the current version of the pci.ids file from
           the primary distribution site and installs it.
    
           This utility requires curl, wget or lynx to be installed. If gzip
           or bzip2 are available, it automatically downloads the compressed
           version of the list.
    


## OPTIONS



           **-q** Be quiet and do not report anything except errors.
    


## FILES



           **/usr/local/share/pci.ids.gz**
                  Here we install the new list.
    


* * *
# rpm-plugin-selinux

## NAME



           rpm-plugin-selinux - SELinux plugin for the RPM Package Manager
    


## Description



           The plugin sets SELinux contexts for installed files and executed
           scriptlets.  It needs SELinux to be enabled to work but will work
           in both enforcing and permissive mode.
    


## Configuration



           The plugin can be disabled temporarily by passing **--nocontexts** at
           the rpm(8) command line or setting the transaction flag
           **RPMTRANS_FLAG_NOCONTEXTS** in the API.
    
           See rpm-plugins(8) on how to control plugins in general.
    


* * *
# systemd-backlight@.service

## NAME



           systemd-backlight@.service, systemd-backlight - Load and save the
           display backlight brightness at boot and shutdown
    


## SYNOPSIS



           systemd-backlight@.service
    
           /usr/lib/systemd/systemd-backlight save [backlight|leds]:DEVICE
    
           /usr/lib/systemd/systemd-backlight load [backlight|leds]:DEVICE
    


## DESCRIPTION



           systemd-backlight@.service is a service that restores the
           brightness of a display backlight or LED (e.g. keyboard backlight)
           device at early boot, and saves it at shutdown. The brightness is
           stored in /var/lib/systemd/backlight/.
    
           On restoring brightness of a display backlight device,
           **systemd-backlight** reads _ID_BACKLIGHT_CLAMP_ udev property, that
           takes a boolean value or a percentage (needs to be suffixed with
           "%", e.g.  "30%"). When a percentage is specified, the saved
           brightness is clamped to a value of at least 1 or the specified
           percentage of the maximum brightness, whichever is greater. When
           unset or set to true, the brightness is clamped in the same way
           with percentage 5%. When false, the saved brightness will not be
           clamped, and loaded as is.
    
           On restoring brightness of a LED device, **systemd-backlight** reads
           _ID_LEDS_CLAMP_ udev property, that also takes a boolean value or a
           percentage. When a percentage is specified, the saved brightness
           is clamped to the specified percentage of the maximum brightness.
           When set to true, the brightness is clamped in the same way with
           percentage 5%. When unset or set to false, the saved brightness
           will not be clamped, and loaded as is.
    


## KERNEL COMMAND LINE



           systemd-backlight understands the following kernel command line
           parameter:
    
           _systemd.restore_state=_
               Takes a boolean argument. Defaults to "1". If "0", does not
               restore the backlight settings on boot. However, settings will
               still be stored on shutdown.
    
               Added in version 209.
    


* * *
# ibprintrt

## NAME



           ibprintrt.pl - print either only the router specified or a list of
           routers from the ibnetdiscover output
    


## SYNOPSIS



           **ibprintrt.pl**[-R -l -C <ca_name> -P <ca_port>]
           [<rt_guid|node_name>]
    


## DESCRIPTION



           Faster than greping/viewing with an editor the output of
           ibnetdiscover, ibprintrt.pl will parse out and print either the
           router information for the specified IB router or a list of all IB
           routers in the subnet.
    
           Finally, ibprintrt.pl will also reuse the cached ibnetdiscover
           output from some of the other diag tools which makes it a bit
           faster than running ibnetdiscover from scratch.
    


## OPTIONS



           **-l** List the Rts (simply a wrapper for ibrouters).
    
           **-R** Recalculate the ibnetdiscover information, ie do not use
                  the cached information.  This option is slower but should
                  be used if the diag tools have not been used for some time
                  or if there are other reasons to believe that the fabric
                  has changed.
    
           **-C <ca_name>    **use the specified ca_name for the search.
    
           **-P <ca_port>    **use the specified ca_port for the search.
    


* * *
# pam_mkhomedir

## NAME



           pam_mkhomedir - PAM module to create users home directory
    


## SYNOPSIS



    
           **pam_mkhomedir.so**[silent] [debug] [umask=_mode_] [skel=_skeldir_]
    


## DESCRIPTION



           The pam_mkhomedir PAM module will create a users home directory if
           it does not exist when the session begins. This allows users to be
           present in central database (such as NIS, kerberos or LDAP)
           without using a distributed file system or pre-creating a large
           number of directories. The skeleton directory (usually /etc/skel/)
           is used to copy default files and also sets a umask for the
           creation.
    
           The new users home directory will not be removed after logout of
           the user.
    


## OPTIONS



           **silent**
               Don't print informative messages.
    
           **debug**
               Turns on debugging via syslog(3).
    
           **umask=**_mask_
               The file mode creation mask is set to _mask_. The default value
               of mask is 0022. If this option is not specified, then the
               permissions of created user home directory is set to the value
               of **HOME_MODE** configuration item from /etc/login.defs. If there
               is no such configuration item then the value is computed from
               the value of **UMASK** in the same file. If there is no such
               configuration option either the default value of 0755 is used
               for the mode.
    
           **skel=**_/path/to/skel/directory_
               Indicate an alternative skel directory to override the default
               /etc/skel.
    


## MODULE TYPES PROVIDED



           Only the **session** module type is provided.
    


## RETURN VALUES



           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_PERM_DENIED
               Not enough permissions to create the new directory or read the
               skel directory.
    
           PAM_USER_UNKNOWN
               User not known to the underlying authentication module.
    
           PAM_SUCCESS
               Environment variables were set.
    


## FILES



           /etc/skel
               Default skel directory
    


## EXAMPLES



           A sample /etc/pam.d/login file:
    
                 auth       requisite   pam_securetty.so
                 auth       sufficient  pam_ldap.so
                 auth       required    pam_unix.so
                 auth       required    pam_nologin.so
                 account    sufficient  pam_ldap.so
                 account    required    pam_unix.so
                 password   required    pam_unix.so
                 session    required    pam_mkhomedir.so skel=/etc/skel/ umask=0022
                 session    required    pam_unix.so
                 session    optional    pam_lastlog.so
                 session    optional    pam_mail.so standard
    


* * *
# devlink

## NAME



           devlink - Devlink tool
    


## SYNOPSIS



           **devlink**[ _OPTIONS_ ] {
                   _dev_ |_port_ |_monitor_ |_sb_ |_resource_ |_region_ |_health_ |_trap_ } {
                   _COMMAND_ | **help**}
    
           **devlink**[ **-force**] **-batch** _filename_
    


## OPTIONS



           **-V** , **--Version**
                  Print the version of the **devlink** utility and exit.
    
           **-b** , **-batch** <FILENAME>
                  Read commands from provided file or standard input and
                  invoke them.  First failure will cause termination of
                  devlink.
    
           **-force** Don't terminate devlink on errors in batch mode.  If there
                  were any errors during execution of the commands, the
                  application return code will be non zero.
    
           **-n** , **--no-nice-names**
                  Turn off printing out nice names, for example netdevice
                  ifnames instead of devlink port identification.
    
           **-j** , **--json**
                  Generate JSON output.
    
           **-p** , **--pretty**
                  When combined with -j generate a pretty JSON output.
    
           **-v** , **--verbose**
                  Turn on verbose output.
    
           **-s** , **--statistics**
                  Output statistics.
    
           **-N** , **-Netns** <NETNSNAME>
                  Switches to the specified network namespace.
    
           **-i** , **--iec**
                  Print human readable rates in IEC units (e.g. 1Ki = 1024).
    
           **-x** , **--hex**
                  Print dump numbers in hexadecimal format.
    
       _OBJECT_
           **dev** - devlink device.
    
           **port** - devlink port.
    
           **monitor**
                  - watch for netlink messages.
    
           **sb** - devlink shared buffer configuration.
    
           **resource**
                  - devlink device resource configuration.
    
           **region** - devlink address region access
    
           **health** - devlink reporting and recovery
    
           **trap** - devlink trap configuration
    
       _COMMAND_
           Specifies the action to perform on the object.  The set of
           possible actions depends on the object type.  As a rule, it is
           possible to **show**(or **list**) objects, but some objects do not allow
           all of these operations or have some additional commands. The **help**
           command is available for all objects. It prints out a list of
           available commands and argument syntax conventions.
    
           If no command is given, some default command is assumed.  Usually
           it is **list** or, if the objects of this class cannot be listed,
           **help**.
    


## EXIT STATUS



           Exit status is 0 if command was successful or a positive integer
           upon failure.
    


* * *
# getcap

## NAME



           getcap - examine file capabilities
    


## SYNOPSIS



           **getcap**[-v] [-n] [-r] [-h] _filename_ [ ... ]
    


## DESCRIPTION



           **getcap** displays the name and capabilities of each specified file.
    


## OPTIONS



           **-h** prints quick usage.
    
           **-n** prints any non-zero user namespace root user ID value found to
               be associated with a file's capabilities.
    
           **-r** enables recursive search.
    
           **-v** display all searched entries, even if the have no file-
               capabilities.
    
           NOTE: an _empty_ value of **'='** is **not** equivalent to an omitted (or
           removed) capability on a file. This is most significant with
           respect to the Ambient capability vector, since a process with
           Ambient capabilities will lose them when executing a file having
           **'='** capabilities, but will retain the Ambient inheritance of
           privilege when executing a file with an omitted file capability.
           This special _empty_ setting can be used to prevent a binary from
           executing with privilege. For some time, the kernel honored this
           suppression for root executing the file, but the kernel developers
           decided after a number of years that this behavior was unexpected
           for the superuser and reverted it just for that user identity.
           Suppression of root privilege, for a process tree, is possible,
           using the capsh(1) **--mode** option.
    
           _filename_
               One file per line.
    


* * *
# mount.nfs

## NAME



           mount.nfs, mount.nfs4 - mount a Network File System
    


## SYNOPSIS



           **mount.nfs** _remotetarget dir_ **[-rvVwfnsh ] [-o** _options_**]**
    


## DESCRIPTION



           **mount.nfs** is a part of nfs(5) utilities package, which provides
           NFS client functionality.
    
           **mount.nfs** is meant to be used by the mount(8) command for mounting
           NFS shares. This subcommand, however, can also be used as a
           standalone command with limited functionality.
    
           _remotetarget_ is a server share usually in the form of
           **servername:/path/to/share.**_dir_ is the directory on which the file
           system is to be mounted.
    
           Under Linux 2.6.32 and later kernel versions, **mount.nfs** can mount
           all NFS file system versions.  Under earlier Linux kernel
           versions, **mount.nfs4** must be used for mounting NFSv4 file systems
           while **mount.nfs** must be used for NFSv3.
    


## OPTIONS



           **-r** Mount file system readonly.
    
           **-v** Be verbose.
    
           **-V** Print version.
    
           **-w** Mount file system read-write.
    
           **-f** Fake mount. Don't actually call the mount system call.
    
           **-n** Do not update _/etc/mtab._  By default, an entry is created
                  in _/etc/mtab_ for every mounted file system. Use this option
                  to skip making an entry.
    
           **-s** Tolerate sloppy mount options rather than fail.
    
           **-h** Print help message.
    
           **nfsoptions**
                  Refer to nfs(5) or mount(8) manual pages.
    


## NOTE



           For further information please refer nfs(5) and mount(8) manual
           pages.
    


## FILES



           _/etc/fstab_
                  file system table
    
           _/etc/mtab_
                  table of mounted file systems
    
           _/etc/nfsmount.conf_
                  Configuration file for NFS mounts
    


* * *
# tipc-node

## NAME



           tipc-node - modify and show local node parameters or list peer
           nodes
    


## SYNOPSIS



           **tipc node set**{ **address** _ADDRESS_ | **netid** _NETID_ }
    
           **tipc node get**{ **address** | **netid**}
    
           **tipc node list**
    


## OPTIONS



           Options (flags) that can be passed anywhere in the command chain.
    
           **-h** , **--help**
                  Show help about last valid command. For example **tipc node**
                  **--help** will show node help and **tipc --help** will show
                  general help. The position of the option in the string is
                  irrelevant.
    


## DESCRIPTION



       **Node parameters**
           **address**
                  The TIPC logical address. On the form x.y.z where x, y and
                  z are unsigned integers.
    
           **netid**
                  Network identity. Can by used to create individual TIPC
                  clusters on the same media.
    


## EXIT STATUS



           Exit status is 0 if command was successful or a positive integer
           upon failure.
    


* * *
# tc-basic

## NAME



           basic - basic traffic control filter
    


## SYNOPSIS



           **tc filter**... **basic**[ **match** _EMATCH_TREE_ ] [ **action** _ACTION_SPEC_ ] [
                   **classid** _CLASSID_ ]
    


## DESCRIPTION



           The **basic** filter allows one to classify packets using the extended
           match infrastructure.
    


## OPTIONS



           **action** _ACTION_SPEC_
                  Apply an action from the generic actions framework on
                  matching packets.
    
           **classid** _CLASSID_
                  Push matching packets into the class identified by _CLASSID_.
    
           **match** _EMATCH_TREE_
                  Match packets using the extended match infrastructure. See
                  tc-ematch(8) for a detailed description of the allowed
                  syntax in _EMATCH_TREE_.
    


* * *
# rdma-system

## NAME



           rdma-system - RDMA subsystem configuration
    


## SYNOPSIS



           **rdma**[ _OPTIONS_ ] **sys**{ _COMMAND_ | **help**}
    
           _OPTIONS_ := { **-V**[_ersion_] | **-d**[_etails_] }
    
           **rdma system show**
    
           **rdma system set netns NEWMODE**
    
           **rdma system set privileged-qkey NEWSTATE**
    
           **rdma system help**
    


## DESCRIPTION



       **rdma system set - set RDMA subsystem network namespace mode or**
           privileged qkey mode
    
       **rdma system show - display RDMA subsystem network namespace mode,**
           privileged qkey state and whether RDMA monitoring is supported.
    
           _NEWMODE_ - specifies the RDMA subsystem mode. Either exclusive or
           shared.  When user wants to assign dedicated RDMA device to a
           particular network namespace, exclusive mode should be set before
           creating any network namespace. If there are active network
           namespaces and if one or more RDMA devices exist, changing mode
           from shared to exclusive returns error code EBUSY.
    
           When RDMA subsystem is in shared mode, RDMA device is accessible
           in all network namespace. When RDMA device isolation among
           multiple network namespaces is not needed, shared mode can be
           used.
    
           It is preferred to not change the subsystem mode when there is
           active RDMA traffic running, even though it is supported.
    
           _NEWSTATE_ - Specifies the new state of the privileged-qkey
           parameter, either on or off.  This parameter determines whether a
           non-privileged user is allowed to specify a controlled QKEY or
           not.
    


## EXAMPLES



           rdma system show
               Shows the state of RDMA subsystem network namespace mode on
               the system, the state of privileged qkey parameter and whether
               RDMA monitor is supported.
    
           rdma system set netns exclusive
               Sets the RDMA subsystem in network namespace exclusive mode.
               In this mode RDMA devices are visible only in single network
               namespace.
    
           rdma system set netns shared
               Sets the RDMA subsystem in network namespace shared mode. In
               this mode RDMA devices are shared among network namespaces.
    
           rdma system set privileged-qkey on
               Sets the privileged-qkey parameter to on. In this state non-
               privileged user is allowed to specify a controlled QKEY.
    
           rdma system set privileged-qkey off
               Sets the privileged-qkey parameter to off. In this state non-
               privileged user is *not* allowed to specify a controlled QKEY.
    


* * *