tripathysagar/man_text huggingface dataset:
# migspeed

## NAME



           migspeed - Test the speed of page migration
    


## SYNOPSIS



           **migspeed** -p pages from-nodes to-nodes
    


## DESCRIPTION



           **migspeed** attempts to move a sample of pages from the indicated
           node to the target node and measures the time it takes to perform
           the move.
    
           **-p pages**
    
           The default sample is 1000 pages. Override that with another
           number.
    


## NOTES



           Requires a NUMA policy aware kernel with support for page
           migration (Linux 2.6.16 and later).
    


* * *
# sa2

## NAME



           sa2 - Create a report from the current standard system activity
           daily data file.
    


## SYNOPSIS



           **/usr/local/lib64/sa/sa2**
    


## DESCRIPTION



           The **sa2** command is a shell procedure variant of the **sar** command
           which writes a daily report in the _sarDD_ or the _sarYYYYMMDD_ file,
           where _YYYY_ stands for the current year, _MM_ for the current month
           and _DD_ for the current day. By default the report is saved in the
           _/var/log/sa_ directory. The **sa2** command will also remove reports
           more than one week old by default.  You can however keep reports
           for a longer (or a shorter) period by setting the **HISTORY**
           environment variable. Read the sysstat(5) manual page for details.
    
           The **sa2** command accepts most of the flags and parameters of the
           **sar** command.
    
           The **sa2** command is designed to be started automatically by the
           **cron** command.
    


## EXAMPLES



           To run the **sa2** command daily, place the following entry in your
           root crontab file:
    
           **5 19 * * 1-5 /usr/local/lib64/sa/sa2 -A**
    
           This will generate by default a daily report called _sarDD_ in the
           _/var/log/sa_ directory, where the _DD_ parameter is a number
           representing the day of the month.
    


## FILES



           _/var/log/sa/sarDD_
           _/var/log/sa/sarYYYYMMDD_
                  The standard system activity daily report files and their
                  default location.  _YYYY_ stands for the current year, _MM_ for
                  the current month and _DD_ for the current day.
    


* * *
# genpolusers

## NAME



           genpolusers - Generate new binary policy with updated user
           configuration
    


## SYNOPSIS



           genpolusers in-policy usersdir out-policy
    


## DESCRIPTION



           Given an existing binary policy file _in-policy,_ generate a new
           binary policy _out-policy_ with an updated user configuration based
           on any **system.users** and **local.users** files in the specified
           _usersdir._
    


* * *
# captest

## NAME



           captest - a program to demonstrate capabilities
    


## SYNOPSIS



           **captest [ --ambient --drop-all | --drop-caps | --id ] [ --init-grp**
           **] [ --lock ] [ --text ]**
    


## DESCRIPTION



           **captest** is a program that demonstrates and prints out the current
           process capabilities. Each option prints the same report. It will
           output current capabilities. then it will try to access
           /etc/shadow directly to show if that can be done. Then it creates
           a child process that attempts to read /etc/shadow and outputs the
           results of that. Then it outputs the capabilities that a child
           process would have.
    
           You can also apply file system capabilities to this program to
           study how they work. For example, filecap /usr/bin/captest chown.
           Then run captest as a normal user. Another interesting test is to
           make captest suid root so that you can see what the interaction is
           between root's credentials and capabilities. For example, chmod
           4755 /usr/bin/captest. When run as a normal user, the program will
           see if privilege escalation is possible. But do not leave this app
           setuid root after you are don testing so that an attacker cannot
           take advantage of it.
    


## OPTIONS



           **--ambient**
                  This attempts to add CAP_CHOWN ambient capability.
    
           **--drop-all**
                  This drops all capabilities including ambient and clears
                  the bounding set.
    
           **--drop-caps**
                  This drops just traditional capabilities.
    
           **--id** This changes to uid and gid 99, drops supplemental groups,
                  and clears the bounding set.
    
           **--init-grp**
                  This changes to uid and gid 99 and then adds any
                  supplemental groups that comes with that account. You would
                  have add them prior to testing because by default there are
                  no supplemental groups on account 99.
    
           **--text** This option outputs the effective capabilities in text
                  rather than numerically.
    
           **--lock** This prevents the ability for child processes to regain
                  privileges if the uid is 0.
    


* * *
# tipc

## NAME



           tipc - a TIPC configuration and management tool
    


## SYNOPSIS



           **tipc**[ _OPTIONS_ ] _COMMAND ARGUMENTS_
    
           _COMMAND_ := { **bearer** | **link** | **media** | **nametable** | **node** | **socket**}
    
           _OPTIONS_ := { **-h**[_help_] }
    


## DESCRIPTION



           The Transparent Inter-Process Communication (TIPC) protocol offers
           total address transparency between processes which allows
           applications in a clustered computer environment to communicate
           quickly and reliably with each other, regardless of their location
           within the cluster.
    
           TIPC originated at the telecommunications manufacturer Ericsson.
           The first open source version of TIPC was created in 2000 when
           Ericsson released its first Linux version of TIPC. TIPC was
           introduced in the mainline Linux kernel in 2006 and is now widely
           used both within and outside of Ericsson.
    


## OPTIONS



           **-h** , **--help**
                  Show help about last given command. For example **tipc bearer**
                  **--help** will show bearer help and **tipc --help** will show
                  general help. The position of the option in the string is
                  irrelevant.
    
           **-j** , **-json**
                  Output results in JavaScript Object Notation (JSON).
    
           **-p** , **-pretty**
                  The default JSON format is compact and more efficient to
                  parse but hard for most users to read.  This flag adds
                  indentation for readability.
    


## COMMANDS



           **BEARER** - Show or modify TIPC bearers
    
           **LINK** - Show or modify TIPC links
    
           **MEDIA** - Show or modify TIPC media
    
           **NAMETABLE**
                  - Show TIPC nametable
    
           **NODE** - Show or modify TIPC node parameters
    
           **SOCKET** - Show TIPC sockets
    


## ARGUMENTS



           Command arguments are described in a command specific man page and
           typically consists of nested commands along with key value pairs.
           If no arguments are given a command typically shows its help text.
           The explicit help option **-h** or **--help** can occur anywhere among the
           arguments and will show help for the last valid command given.
    


## EXIT STATUS



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


* * *
# ovs-parse-backtrace

## NAME



           ovs-parse-backtrace - parses ovs-appctl backtrace output
    


## SYNOPSIS



           **ovs-appctl backtrace | ovs-parse-backtrace [ <binary>]**
    
           **ovs-parse-backtrace [ <binary>] < <backtrace>**
    


## DESCRIPTION



           In some configurations, many Open vSwitch daemons can produce a
           series of backtraces using the **ovs-appctl backtrace** command.
           Users can analyze these backtraces to figure out what the given
           Open vSwitch daemon may be spending most of its time doing.
           **ovs-parse-backtrace** makes this output easier to interpret.
    
           The **ovs-appctl backtrace** output must be supplied on standard
           input.  The binary that produced the output should be supplied as
           the sole non-option argument.  For best results, the binary should
           have debug symbols.
    


## OPTIONS



           • **--help**
    
             Prints a usage message and exits.
    
           • **--version**
    
             Prints the version and exits.
    


* * *
# systemd-boot-clear-sysfail.service

## NAME



           systemd-boot-clear-sysfail.service - Clear LoaderEntrySysFail
           entry
    


## SYNOPSIS



           systemd-boot-clear-sysfail.service
    


## DESCRIPTION



           systemd-boot-clear-sysfail.service is a system service that
           automatically clears the 'LoaderEntrySysFail' boot loader entry if
           the boot was successful and the 'LoaderSysFailReason' EFI
           variable, which indicates the reason for the system failure, is
           not set.
    
           The systemd-boot-clear-sysfail.service unit invokes the **bootctl**
           **--graceful set-sysfail ""** command, which clears the
           LoaderEntrySysFail entry. The service is conditionalized so that
           it is run only when a LoaderSysFailReason entry is not set.
    
           For further details see bootctl(1), regarding the command this
           service invokes.
    


* * *
# ovs-bugtool

## NAME



           ovs-bugtool - Open vSwitch bug reporting utility
    


## SYNOPSIS



           **ovs-bugtool**
    


## DESCRIPTION



           Generates a debug bundle with useful information about Open
           vSwitch on this system and places it in **/var/log/ovs-bugtool**.
    


## COLLECTION OPTIONS



           These options influence what categories of data **ovs-bugtool**
           collects.
    
           **--entries=**_list_
                  Collect the capabilities specified in the comma-separated
                  _list_.
    
           **--all** Collect all available capabilities.
    
           **--ovs** In addition to Open vSwitch configuration and status,
                  **ovs-bugtool** can collect a variety of relevant system
                  information.  This option limits collection to Open
                  vSwitch-specific categories.
    
           **--log-days=**_days_
                  Include the logs with last modification time in the
                  previous _days_ days in the debug bundle. The number of log
                  files included has a big impact on the eventual bundle
                  size. The default value is 20 days.
    
           **-y**
           **--yestoall**
                  Answer yes to all prompts.
    
           **--capabilities**
                  Writes the categories that **ovs-bugtool** can collect on
                  stdout in XML, then exits.
    


## OUTPUT OPTIONS



           These options influence the format and destination of **ovs-bugtool**
           output.
    
           **--output=**_filetype_
                  Generates a debug bundle with the specified file type.
                  Options include **tar** , **tar.gz** , **tar.bz2** , and **zip**.
    
           **--outfile=**_file_
                  Write output to _file_.  Mutually exclusive with **--outfd**.
    
           **--outfd=**_fd_
                  Write output to file descriptor _fd_.  This option must be
                  used with **--output=tar**.
    
           **--unlimited**
                  Do not exclude files which are too large. Also skip
                  checking free disk space.  By default up to 90 percent of
                  the free disk space can be used.
    
           **--debug**
                  Print verbose debugging output.
    


## OTHER OPTIONS



           **-s**
           **--silent**
                  Suppress most output to stdout.
    
           **--help** Print a summary of **ovs-bugtool** usage to stdout, then exit.
    


## EXAMPLES



           Here's a collection of some commonly useful options:
    
           **ovs-bugtool -y -s --output=tar.gz --outfile=/var/log/bugtool-**
           **report.tgz**
    


## BUGS



           **ovs-bugtool** makes many assumptions about file locations and the
           availability of system utilities.  It has been tested on Debian
           and Red Hat and derived distributions.  On other distributions it
           is likely to be less useful.
    


* * *
# partprobe

## NAME



           partprobe - inform the OS of partition table changes
    


## SYNOPSIS



           **partprobe**[_-d_] [_-s_] [_devices..._]
    


## DESCRIPTION



           This manual page documents briefly the **partprobe** command.
    
           **partprobe** is a program that informs the operating system kernel of
           partition table changes.
    


## OPTIONS



           This program uses short UNIX style options.
    
           **-d, --dry-run**
                  Don't update the kernel.
    
           **-s, --summary**
                  Show a summary of devices and their partitions.
    
           **-h, --help**
                  Show summary of options.
    
           **-v, --version**
                  Show version of program.
    


* * *
# rdma

## NAME



           rdma - RDMA tool
    


## SYNOPSIS



           **rdma**[ _OPTIONS_ ] _OBJECT_ { _COMMAND_ | **help**}
    
           **rdma**[ **-force**] **-batch** _filename_
    
           _OBJECT_ := { **dev** | **link** | **resource** | **system** | **statistic** | **monitor**}
    
           _OPTIONS_ := { **-V**[_ersion_] | **-d**[_etails_] | **-j**[_son_] | **-o**[_neline_] |
                   **-p**[_retty_] }
    


## OPTIONS



           **-V** , **-Version**
                  Print the version of the **rdma** tool and exit.
    
           **-b** , **-batch** <FILENAME>
                  Read commands from provided file or standard input and
                  invoke them.  First failure will cause termination of rdma.
    
           **-force** Don't terminate rdma on errors in batch mode.  If there
                  were any errors during execution of the commands, the
                  application return code will be non zero.
    
           **-d** , **--details**
                  Output detailed information.  Adding a second -d includes
                  driver-specific details.
    
           **-r** , **--raw**
                  Output includes driver-specific details in raw format.
    
           **-p** , **--pretty**
                  When combined with -j generate a pretty JSON output.
    
           **-j** , **--json**
                  Generate JSON output.
    
           **-o** , **-oneline**
                  output each record on a single line, replacing line feeds
                  with the **'\'** character.
    
       _OBJECT_
           **dev** - RDMA device.
    
           **link** - RDMA port related.
    
           **resource**
                  - RDMA resource configuration.
    
           **sys** - RDMA subsystem related.
    
           **statistic**
                  - RDMA counter statistic related.
    
           **monitor**
                  - RDMA events monitor
    
           The names of all objects may be written in full or abbreviated
           form, for example **stats** can be abbreviated as **stat** or just **s.**
    
       _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.
    


* * *
# semanage-ibendport

## NAME



           **semanage-ibendport - SELinux Policy Management ibendport mapping**
           **tool**
    


## SYNOPSIS



           **semanage ibendport [-h] [-n] [-N] [-S STORE] [ --add -t TYPE -z**
           **IBDEV_NAME -r RANGE port | --delete -z IBDEV_NAME port |**
           **--deleteall | --extract | --list [-C] | --modify -t TYPE -z**
           **IBDEV_NAME -r RANGE port ]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage ibendport** controls the ibendport number to
           ibendport type definitions.
    


## OPTIONS



           _-h, --help_
                  Show this help message and exit
    
           _-n, --noheading_
                  Do not print heading when listing the specified object type
    
           _-N, --noreload_
                  Do not reload policy after commit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-C, --locallist_
                  List local customizations
    
           _-a, --add_
                  Add a record of the specified object type
    
           _-d, --delete_
                  Delete a record of the specified object type
    
           _-m, --modify_
                  Modify a record of the specified object type
    
           _-l, --list_
                  List records of the specified object type
    
           _-E, --extract_
                  Extract customizable commands, for use within a transaction
    
           _-D, --deleteall_
                  Remove all local customizations
    
           _-t TYPE, --type TYPE_
                  SELinux type for the object
    
           _-r RANGE, --range RANGE_
                  MLS/MCS Security Range (MLS/MCS Systems only) SELinux Range
                  for SELinux login mapping defaults to the SELinux user
                  record range. SELinux Range for SELinux user defaults to
                  s0.
    
           _-z IBDEV_NAME, --ibdev_name IBDEV_NAME_
                  The name of the infiniband device for the port to be
                  labeled.  (ex. mlx5_0)
    


## EXAMPLE



           List all ibendport definitions
           # semanage ibendport -l
           Label mlx4_0 port 2.
           # semanage ibendport -a -t allowed_ibendport_t -z mlx4_0 2
    


* * *
# systemd-volatile-root.service

## NAME



           systemd-volatile-root.service, systemd-volatile-root - Make the
           root file system volatile
    


## SYNOPSIS



           systemd-volatile-root.service
    
           /usr/lib/systemd/systemd-volatile-root
    


## DESCRIPTION



           systemd-volatile-root.service is a service that replaces the root
           directory with a volatile memory file system ("tmpfs"), mounting
           the original (non-volatile) /usr/ inside it read-only. This way,
           vendor data from /usr/ is available as usual, but all
           configuration data in /etc/, all state data in /var/ and all other
           resources stored directly under the root directory are reset on
           boot and lost at shutdown, enabling fully stateless systems.
    
           This service is only enabled if full volatile mode is selected,
           for example by specifying "systemd.volatile=yes" on the kernel
           command line. This service runs only in the initrd, before the
           system transitions to the host's root directory. Note that this
           service is not used if "systemd.volatile=state" is used, as in
           that mode the root directory is non-volatile.
    


* * *
# key.dns_resolver

## NAME



           key.dns_resolver - upcall for request-key to handle dns_resolver
           keys
    


## SYNOPSIS



           **/sbin/key.dns_resolver** <key>
           **/sbin/key.dns_resolver** --dump-config [-c <configfile>]
           **/sbin/key.dns_resolver** -D [-v] [-v] [-c <configfile>] <desc>
           <calloutinfo>
    


## DESCRIPTION



           This program is invoked by request-key on behalf of the kernel
           when kernel services (such as NFS, CIFS and AFS) want to perform a
           hostname lookup and the kernel does not have the key cached.  It
           is not ordinarily intended to be called directly.
    
           There program has internal parameters that can be changed with a
           configuration file (see key.dns_resolver.conf(5) for more
           information).  The default configuration file is in /etc, but this
           can be overridden with the **-c** flag.
    
           The program can be called in debugging mode to test its
           functionality by passing a **-D** or **--debug** flag on the command line.
           For this to work, the key description and the callout information
           must be supplied.  Verbosity can be increased by supplying one or
           more **-v** flags.
    
           The program may also be called with **--dump-config** to show the
           values that configurable parameters will have after parsing the
           config file.
    


## ERRORS



           All errors will be logged to the syslog.
    


* * *
# insmod

## NAME



           insmod - Simple program to insert a module into the Linux Kernel
    


## SYNOPSIS



           **insmod**[_OPTIONS_] [_filename_] [_module options_]
    


## DESCRIPTION



           **insmod** is a trivial program to insert a module into the kernel.
           Most users will want to use modprobe(8) instead, which is more
           clever and can handle module dependencies.
    
           Only the most general of error messages are reported: as the work
           of trying to link the module is now done inside the kernel, the
           dmesg(1) usually gives more information about errors.
    


## OPTIONS



           **-f** , **--force**
               This option can be extremely dangerous: it tells the kernel to
               ignore the module version and vermagic fields when loading.
               With this option, you can load modules build locally or by
               third parties, although this can lead to memory corruption,
               system crashes and data loss. This is the same as using both
               **--force-vermagic** and **--force-modversion**.
    
           **--force-modversion**
               When modules are compiled with CONFIG_MODVERSIONS set, a
               section detailing the versions of every interfaced used by (or
               supplied by) the module is created. If a module fails to load
               and the kernel complains that the module disagrees about a
               version of some interface, you can use **--force-modversion** to
               remove the version information altogether.
    
           **--force-vermagic**
               Every module contains a small string containing important
               information, such as the kernel and compiler versions. If a
               module fails to load and the kernel complains that the
               "version magic" doesn't match, you can use this option to
               remove it. Naturally, this check is there for your protection,
               so using this option is dangerous unless you know what you're
               doing.
    
           **-s** , **--syslog**
               Send errors to syslog instead of standard error.
    
           **-v** , **--verbose**
               Print messages about what the program is doing. Usually **insmod**
               prints messages only if something goes wrong.
    
           **-V** , **--version**
               Show version of program and exit.
    
           **-h** , **--help**
               Print the help message and exit.
    


## BUGS



           Please direct any bug reports to kmod's issue tracker at
           https://github.com/kmod-project/kmod/issues/ alongside with
           version used, steps to reproduce the problem and the expected
           outcome.
    


* * *
# btrfs-image

## NAME



           btrfs-image - create/restore an image of the filesystem
    


## SYNOPSIS



           **btrfs-image**[options] _< source> <target>_
    


## DESCRIPTION



           **btrfs-image** is used to create an image of a btrfs filesystem. All
           data will be zeroed, but metadata and the like is preserved.
           Mainly used for debugging purposes.
    
           In the dump mode, source is the btrfs device/file and target is
           the output file (use _-_ for stdout).
    
           In the restore mode (option -r), source is the dumped image and
           target is the btrfs device/file.
    


## OPTIONS



           -r
               Restore metadump image. By default, this fixes super’s chunk
               tree, by using 1 stripe pointing to primary device, so that
               file system can be restored by running tree log reply if
               possible. To restore without changing number of stripes in
               chunk tree check -o option.
    
           -c _< value>_
               Compression level (0 ~ 9).
    
           -t _< value>_
               Number of threads (1 ~ 32) to be used to process the image
               dump or restore.
    
           -o
               Use the old restore method, this does not fixup the chunk tree
               so the restored file system will not be able to be mounted.
    
           -s
               Sanitize the file names when generating the image. One -s
               means just generate random garbage, which means that the
               directory indexes won’t match up since the hashes won’t match
               with the garbage filenames. Using -ss will calculate a
               collision for the filename so that the hashes match, and if it
               can’t calculate a collision then it will just generate
               garbage. The collision calculator is very time and CPU
               intensive so only use it if you are having problems with your
               file system tree and need to have it mostly working.
    
           -w
               Walk all the trees manually and copy any blocks that are
               referenced. Use this option if your extent tree is corrupted
               to make sure that all of the metadata is captured.
    
           -m
               Restore for multiple devices, more than 1 device should be
               provided.
    


## EXIT STATUS



           **btrfs-image** will return 0 if no error happened. If any problems
           happened, 1 will be returned.
    


* * *
# switch_root

## NAME



           switch_root - switch to another filesystem as the root of the
           mount tree
    


## SYNOPSIS



           **switch_root**[**-hV**]
    
           **switch_root** _newroot init_ [_arg_...]
    


## DESCRIPTION



           **switch_root** moves already mounted _/proc_ , _/dev_ , _/sys_ and _/run_ to
           _newroot_ and makes _newroot_ the new root filesystem and starts _init_
           process.
    
           **WARNING: switch_root removes recursively all files and directories**
           **on the current root filesystem.**
    


## OPTIONS



           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## EXIT STATUS



           **switch_root** returns 1 on failure, it never returns on success.
    


## NOTES



           **switch_root** will fail to function if _newroot_ is not the root of a
           mount. If you want to switch root into a directory that does not
           meet this requirement then you can first use a bind-mounting trick
           to turn any directory into a mount point:
    
               mount --bind $DIR $DIR
    


## AVAILABILITY



           The **switch_root** command is part of the util-linux package which
           can be downloaded from Linux Kernel Archive
           <https://www.kernel.org/pub/linux/utils/util-linux/>. This page is
           part of the _util-linux_ (a random collection of Linux utilities)
           project. Information about the project can be found at 
           ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a
           bug report for this manual page, send it to
           util-linux@vger.kernel.org. This page was obtained from the
           project's upstream Git repository
           ⟨git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git⟩ on
           2025-08-11. (At that time, the date of the most recent commit that
           was found in the repository was 2025-08-05.) If you discover any
           rendering problems in this HTML version of the page, or you
           believe there is a better or more up-to-date source for the page,
           or you have corrections or improvements to the information in this
           COLOPHON (which is _not_ part of the original manual page), send a
           mail to man-pages@man7.org
    
    util-linux 2.42-start-521-ec46  2025-01-16                 _SWITCH_ROOT_(8)
    


* * *
# rtacct

## NAME



           nstat, rtacct - network statistics tools.
    


## SYNOPSIS



           Usage: nstat [ -h?vVzrnasd:t:jp ] [ PATTERN [ PATTERN ] ]
           Usage: rtacct [ -h?vVzrnasd:t: ] [ ListOfRealms ]
    


## DESCRIPTION



           **nstat** and **rtacct** are simple tools to monitor kernel snmp counters
           and network interface statistics.
    
           **nstat** can filter kernel snmp counters by name with one or several
           specified wildcards. Wildcards are case-insensitive and can
           include special symbols **?** and *****
    


## OPTIONS



           **-h, --help** Print help
    
           **-V, --version**
                  Print version
    
           **-z, --zeros**
                  Dump zero counters too. By default they are not shown.
    
           **-r, --reset**
                  Reset history.
    
           **-n, --nooutput**
                  Do not display anything, only update history.
    
           **-a, --ignore**
                  Dump absolute values of counters. The default is to
                  calculate increments since the previous use.
    
           **-s, --noupdate**
                  Do not update history, so that the next time you will see
                  counters including values accumulated to the moment of this
                  measurement too.
    
           **-j, --json**
                  Display results in JSON format.
    
           **-p, --pretty**
                  When combined with **--json** , pretty print the output.
    
           **-d, --scan <INTERVAL>**
                  Run in daemon mode collecting statistics. <INTERVAL> is
                  interval between measurements in seconds.
    
           **-t, --interval <INTERVAL>**
                  Time interval to average rates. Default value is 60
                  seconds.
    


* * *
# rdma-dev

## NAME



           rdma-dev - RDMA device configuration
    


## SYNOPSIS



           **rdma**[ _OPTIONS_ ] **dev**{ _COMMAND_ | **help**}
    
           _OPTIONS_ := { **-V**[_ersion_] | **-d**[_etails_] }
    
           **rdma dev show**[ _DEV_ ]
    
           **rdma dev set**[ _DEV_ ] **name NEWNAME**
    
           **rdma dev set**[ _DEV_ ] **netns NSNAME**
    
           **rdma dev set**[ _DEV_ ] **adaptive-moderation [on/off]**
    
           **rdma dev add**[ _NAME_ ] **type**[ _TYPE_ ] **parent**[ _PARENT_DEV_ ]
    
           **rdma dev delete**[ _NAME_ ]
    
           **rdma dev help**
    


## DESCRIPTION



       **rdma dev set - rename RDMA device or set network namespace or set RDMA**
           **device adaptive-moderation**
       **rdma dev show - display RDMA device attributes**
           _DEV_ - specifies the RDMA device to show.  If this argument is
           omitted all devices are listed.
    
       **rdma dev add - Add a RDMA device with a specific type and parent IB**
           **device; This new device provides subset of functionalities defined**
           **in IBTA spec.**
       **rdma dev delete - Delete a RDMA device which is created with the add**
           **command.**
           _NAME_ - The name of the device being added/deleted.
    
           _TYPE_ - The type of the device being added; It specifies which
           functionalities it provides. Supported device type:
    
                   **SMI** - A device with this type provides SMI (QP0)
                   interface. This device and it's parent associates with the
                   same HCA port and shares the physical link, so when the
                   parent doesn't support SMI, then this type of device can
                   be created to allow the subnet manager to configure the
                   link.
    
           _PARENT_DEV_ - The name of its parent IB device.
    


## EXAMPLES



           rdma dev
               Shows the state of all RDMA devices on the system.
    
           rdma dev show mlx5_3
               Shows the state of specified RDMA device.
    
           rdma dev set mlx5_3 name rdma_0
               Renames the mlx5_3 device to rdma_0.
    
           rdma dev set mlx5_3 netns foo
               Changes the network namespace of RDMA device to foo where foo
               is previously created using iproute2 ip command.
    
           rdma dev set mlx5_3 adaptive-moderation [on/off]
               Sets the state of adaptive interrupt moderation for the RDMA
               device.
               This is a global setting for the RDMA device but the value is
               printed for each CQ individually because the state is constant
               from CQ allocation.
    
           rdma dev add smi1 type SMI parent ibp8s0f1
               Add a new IB device with name "smi1", type "SMI", and
               "ibp8s0f1" as its parent device.
    
           rdma dev delete smi1
               Delete the IB device "smi1".
    


* * *
# tc-gact

## NAME



           gact - generic action
    


## SYNOPSIS



           **tc**... **action gact** _CONTROL_ [ _RAND_ ] [ _INDEX_ ]
           _CONTROL_ := { **reclassify** | **drop** | **continue** | **pass** | **pipe** |
                   **goto chain** _CHAIN_INDEX_ |
                   **jump** _JUMP_COUNT_ }
    
           _RAND_ := **random** _RANDTYPE CONTROL VAL_
           _RANDTYPE_ := { **netrand** | **determ**}
           _VAL_ := number not exceeding 10000
           _JUMP_COUNT_ := absolute jump from start of action list
           _INDEX_ := index value used
    


## DESCRIPTION



           The **gact** action allows reclassify, dropping, passing, or accepting
           packets.  At the moment there are only two algorithms. One is
           deterministic and the other uses internal kernel netrand.
    


## OPTIONS



           **random** _RANDTYPE CONTROL VAL_
                  The probability of taking the action expressed in terms of
                  1 out of _VAL_ packets.
    
           _CONTROL_
                  Indicate how **tc** should proceed if the packet matches.  For
                  a description of the possible _CONTROL_ values, see
                  tc-actions(8).
    


## EXAMPLES



           Apply a rule on ingress to drop packets from a given source
           address.
                  # tc filter add dev eth0 parent ffff: protocol ip prio 6 u32 match ip src 10.0.0.9/32 flowid 1:16 action drop
    
           Allow 1 out 10 packets from source randomly using the netrand
           generator
                  # tc filter add dev eth0 parent ffff: protocol ip prio 6 u32 match ip src 10.0.0.9/32 flowid 1:16 action drop random netrand ok 10
    
           Deterministically accept every second packet
                  # tc filter add dev eth0 parent ffff: protocol ip prio 6 u32 match ip src 10.0.0.9/32 flowid 1:16 action drop random determ ok 2
    


* * *
# pam_shells

## NAME



           pam_shells - PAM module to check for valid login shell
    


## SYNOPSIS



    
           **pam_shells.so**
    


## DESCRIPTION



           pam_shells is a PAM module that only allows access to the system
           if the user's shell is listed in /etc/shells.
    
           It also checks if /etc/shells is a plain file and not world
           writable.
    


## OPTIONS



           This module does not recognise any options.
    


## MODULE TYPES PROVIDED



           The **auth** and **account** module types are provided.
    


## RETURN VALUES



           PAM_AUTH_ERR
               Access to the system was denied.
    
           PAM_SUCCESS
               The user's login shell was listed as valid shell in
               /etc/shells.
    
           PAM_SERVICE_ERR
               The module was not able to get the name of the user.
    


## EXAMPLES



               auth  required  pam_shells.so
    


* * *
# open_init_pty

## NAME



           open_init_pty - run an program under a pseudo terminal
    


## SYNOPSIS



           **open_init_pty** _SCRIPT_ [[_ARGS_]...]
    


## DESCRIPTION



           Run a program under a pseudo terminal. This is used by **run_init** to
           run actually run the program after setting up the proper context.
           This program acquires a new Pseudo terminal, forks a child process
           that binds to the pseudo terminal, and then sits around and
           connects the physical terminal it was invoked upon with the pseudo
           terminal, passing keyboard input into to the child process, and
           passing the output of the child process to the physical terminal.
    
           It sets up the pseudo terminal properly based on the physical
           terminal attributes, and then sets the user's terminal to RAW
           mode, taking care to reset it on exit.
    


* * *
# svcgssd

## NAME



           rpc.svcgssd - server-side rpcsec_gss daemon
    


## SYNOPSIS



           **rpc.svcgssd [-n] [-v] [-r] [-i] [-f] [-p principal]**
    


## DESCRIPTION



           The rpcsec_gss protocol gives a means of using the gss-api generic
           security api to provide security for protocols using rpc (in
           particular, nfs).  Before exchanging any rpc requests using
           rpcsec_gss, the rpc client must first establish a security context
           with the rpc server.  The linux kernel's implementation of
           rpcsec_gss depends on the userspace daemon **rpc.svcgssd** to handle
           context establishment on the rpc server.  The daemon uses files in
           the proc filesystem to communicate with the kernel.
    


## OPTIONS



           **-f** Runs **rpc.svcgssd** in the foreground and sends output to
                  stderr (as opposed to syslogd)
    
           **-v** Increases the verbosity of the output (can be specified
                  multiple times).
    
           **-r** If the rpcsec_gss library supports setting debug level,
                  increases the verbosity of the output (can be specified
                  multiple times).
    
           **-i** If the nfsidmap library supports setting debug level,
                  increases the verbosity of the output (can be specified
                  multiple times).
    
           **-p** Use _principal_ instead of the default nfs/_FQDN_ @_REALM_.
    
           **-n** Use the system default credentials (host/_FQDN_ @_REALM_) rather
                  than the default nfs/_FQDN_ @_REALM_.
    


## CONFIGURATION FILE



           Some of the options that can be set on the command line can also
           be controlled through values set in the **[svcgssd]** section of the
           _/etc/nfs.conf_ configuration file.  Values recognized include:
    
           **principal**
                  If set to **system** this is equivalent to the **-n** option.  If
                  set to any other value, that is used like the **-p** option.
    
           **verbosity**
                  Value which is equivalent to the number of **-v**.
    
           **rpc-verbosity**
                  Value which is equivalent to the number of **-r**.
    
           **idmap-verbosity**
                  Value which is equivalent to the number of **-i**.
    


* * *
# systemd-battery-check.service

## NAME



           systemd-battery-check.service, systemd-battery-check - Check
           battery level whether there's enough charge, and power off if not
    


## SYNOPSIS



           systemd-battery-check.service
    
           **/usr/lib/systemd/systemd-battery-check**[OPTIONS...]
    


## DESCRIPTION



           This service checks the presence of an external power supply and
           the battery level during the early boot stage to determine whether
           there is sufficient power to carry on with the booting process.
    
           **systemd-battery-check** returns success if the device is connected
           to an AC power source or if the battery charge is greater than 5%.
           It returns failure otherwise.
    


## OPTIONS



           The following options are understood by **systemd-battery-check** :
    
           **-h** , **--help**
               Print a short help text and exit.
    
           **--version**
               Print a short version string and exit.
    


## EXIT STATUS



           On success (running on AC power or battery capacity greater than
           5%), 0 is returned, a non-zero failure code otherwise.
    


## KERNEL COMMAND LINE



           The following variables are understood:
    
           _systemd.battery_check=BOOL_
               Takes a boolean. If specified with false,
               **systemd-battery-check** command will return immediately with
               exit status 0 without checking battery capacity and AC power
               existence, and the service systemd-battery-check.service will
               succeed. This may be useful when the command wrongly detects
               and reports battery capacity percentage or AC power existence,
               or when you want to boot the system forcibly.
    
               Added in version 254.
    


* * *
# pam_localuser

## NAME



           pam_localuser - require users to be listed in /etc/passwd
    


## SYNOPSIS



    
           **pam_localuser.so**[debug] [file=_/path/passwd_]
    


## DESCRIPTION



           pam_localuser is a PAM module to help implementing site-wide login
           policies, where they typically include a subset of the network's
           users and a few accounts that are local to a particular
           workstation. Using pam_localuser and pam_wheel or pam_listfile is
           an effective way to restrict access to either local users and/or a
           subset of the network's users.
    
           This could also be implemented using pam_listfile.so and a very
           short awk script invoked by cron, but it's common enough to have
           been separated out.
    


## OPTIONS



           **debug**
               Print debug information.
    
           **file=**_/path/passwd_
               Use a file other than /etc/passwd.
    


## MODULE TYPES PROVIDED



           All module types (**account** , **auth** , **password** and **session**) are
           provided.
    


## RETURN VALUES



           PAM_SUCCESS
               The new localuser was set successfully.
    
           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_CONV_ERR
               The conversation method supplied by the application failed to
               obtain the username.
    
           PAM_INCOMPLETE
               The conversation method supplied by the application returned
               PAM_CONV_AGAIN.
    
           PAM_SERVICE_ERR
               The user name is not valid or the passwd file is unavailable.
    
           PAM_PERM_DENIED
               The user is not listed in the passwd file.
    


## EXAMPLES



           Add the following lines to /etc/pam.d/su to allow only local users
           or group wheel to use su.
    
               account sufficient pam_localuser.so
               account required pam_wheel.so
    


## FILES



           /etc/passwd
               Local user account information.
    


* * *
# mkhomedir_helper

## NAME



           mkhomedir_helper - Helper binary that creates home directories
    


## SYNOPSIS



    
           **mkhomedir_helper**{_user_} [_umask_ [ _path-to-skel_ [ _home_mode_ ] ]]
    


## DESCRIPTION



           _mkhomedir_helper_ is a helper program for the _pam_mkhomedir_ module
           that creates home directories and populates them with contents of
           the specified skel directory.
    
           The default value of _umask_ is 0022 and the default value of
           _path-to-skel_ is _/etc/skel_. The default value of _home_mode_ is
           computed from the value of _umask_.
    
           The helper is separated from the module to not require direct
           access from login SELinux domains to the contents of user home
           directories. The SELinux domain transition happens when the module
           is executing the _mkhomedir_helper_.
    
           The helper never touches home directories if they already exist.
    


* * *