tripathysagar/man_text huggingface dataset:
# systemd-networkd.service

## NAME



           systemd-networkd.service, systemd-networkd - Network manager
    


## SYNOPSIS



           systemd-networkd.service
    
           /usr/lib/systemd/systemd-networkd
    


## DESCRIPTION



           **systemd-networkd** is a system service that manages networks. It
           detects and configures network devices as they appear, as well as
           creating virtual network devices.
    
           Certain low-level settings of physical network devices (e.g.
           device names and altnames) as well as the creation of SR-IOV
           virtual functions on physical network interfaces may be managed by
           systemd-udevd(8) according to the contents of systemd.link(5)
           files.
    
           **systemd-networkd** will create "virtual" network devices (e.g.
           bridges and tunnels) based on the configuration in
           systemd.netdev(5) files, respecting the [Match] sections in those
           files.
    
           **systemd-networkd** will manage network addresses and routes for any
           link for which it finds a .network file with an appropriate
           [Match] section, see systemd.network(5). For those links, it will
           flush existing network addresses and routes when bringing up the
           device (except when directed not to). Any links not matched by one
           of the .network files will be ignored. It is also possible to
           explicitly tell systemd-networkd to ignore a link by using the
           _Unmanaged=yes_ option, see systemd.network(5).
    
           When systemd-networkd exits, it generally leaves existing network
           devices and configuration intact. This makes it possible to
           transition from the initrd and to restart the service without
           breaking connectivity. This also means that when configuration is
           updated and systemd-networkd is restarted, netdev interfaces for
           which configuration was removed will not be dropped, and may need
           to be cleaned up manually.
    
           **systemd-networkd** may be introspected and controlled at runtime
           using networkctl(1).
    
           See org.freedesktop.network1(5) and org.freedesktop.LogControl1(5)
           for a description of the D-Bus API.
    


## CONFIGURATION FILES



           The configuration files are read from the files located in the
           system network directory /usr/lib/systemd/network, the volatile
           runtime network directory /run/systemd/network and the local
           administration network directory /etc/systemd/network.
    
           Networks are configured in .network files, see systemd.network(5),
           and virtual network devices are configured in .netdev files, see
           systemd.netdev(5).
    


* * *
# cupsenable

## NAME



           cupsdisable, cupsenable - stop/start printers and classes
    


## SYNOPSIS



           **cupsdisable**[ **-E**] [ **-U** _username_ ] [ **-c**] [ **-h** _server_[**:**_port_] ] [
           **-r** _reason_ ] [ **--hold**] _destination(s)_
           **cupsenable**[ **-E**] [ **-U** _username_ ] [ **-c**] [ **-h** _server_[**:**_port_] ] [
           **--release**] _destination(s)_
    


## DESCRIPTION



           **cupsenable** starts the named printers or classes while **cupsdisable**
           stops the named printers or classes.
    


## OPTIONS



           The following options may be used:
    
           **-E** Forces encryption of the connection to the server.
    
           **-U** _username_
                Uses the specified username when connecting to the server.
    
           **-c** Cancels all jobs on the named destination.
    
           **-h** _server_[**:**_port_]
                Uses the specified server and port.
    
           **--hold**
                Holds remaining jobs on the named printer.  Useful for
                allowing the current job to complete before performing
                maintenance.
    
           **-r "**_reason_**"**
                Sets the message associated with the stopped state.  If no
                reason is specified then the message is set to "Reason
                Unknown".
    
           **--release**
                Releases pending jobs for printing.  Use after running
                **cupsdisable** with the _--hold_ option to resume printing.
    


## CONFORMING TO



           Unlike the System V printing system, CUPS allows printer names to
           contain any printable character except SPACE, TAB, "/", or "#".
           Also, printer and class names are _not_ case-sensitive.
    
           The System V versions of these commands are **disable** and **enable** ,
           respectively.  They have been renamed to avoid conflicts with the
           bash(1) built-in commands of the same names.
    
           The CUPS versions of **disable** and **enable** may ask the user for an
           access password depending on the printing system configuration.
           This differs from the System V versions which require the root
           user to execute these commands.
    


* * *
# semanage-login

## NAME



           **semanage-login - SELinux Policy Management linux user to SELinux**
           **User mapping tool**
    


## SYNOPSIS



           **semanage login [-h] [-n] [-N] [-S STORE] [ --add -s SEUSER -r**
           **RANGE LOGIN | --delete LOGIN | --deleteall | --extract | --list**
           **[-C] | --modify -s SEUSER -r RANGE LOGIN ]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage login** controls the mapping between a Linux User
           and the SELinux User. It can be used to turn on confined users.
           For example you could define that a particular user or group of
           users will login to a system as the user_u user. Prefix the group
           name with a '%' sign to indicate a group name.
    


## 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
    
           _-C, --locallist_
                  List local customizations
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-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
    
           _-s SEUSER, --seuser SEUSER_
                  SELinux user name
    
           _-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.
    


## EXAMPLE



           Set the default SELinux user on the system to guest_u
           # semanage login -m -s guest_u __default__
           Map user gijoe to SELinux user staff_u and assign MLS range SystemLow-Secret
           # semanage login -a -s staff_u -rSystemLow-Secret gijoe
           Map all users in the engineering group to SELinux user staff_u
           # semanage login -a -s staff_u %engineering
    


* * *
# pam_usertype

## NAME



           pam_usertype - check if the authenticated user is a system or
           regular account
    


## SYNOPSIS



    
           **pam_usertype.so**[_flag_...] {_condition_}
    


## DESCRIPTION



           pam_usertype.so is designed to succeed or fail authentication
           based on type of the account of the authenticated user. The type
           of the account is decided with help of _SYS_UID_MAX_ settings in
           _/etc/login.defs_. One use is to select whether to load other
           modules based on this test.
    
           The module should be given only one condition as module argument.
           Authentication will succeed only if the condition is met.
    


## OPTIONS



           The following _flag_ s are supported:
    
           **use_uid**
               Evaluate conditions using the account of the user whose UID
               the application is running under instead of the user being
               authenticated.
    
           **audit**
               Log unknown users to the system log.
    
           Available _condition_ s are:
    
           **issystem**
               Succeed if the user is a system user.
    
           **isregular**
               Succeed if the user is a regular user.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_SUCCESS
               The condition was true.
    
           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_AUTH_ERR
               The condition was false.
    
           PAM_SERVICE_ERR
               A service error occurred or the arguments can't be parsed
               correctly.
    
           PAM_USER_UNKNOWN
               User was not found.
    


## EXAMPLES



           Skip remaining modules if the user is a system user:
    
               account sufficient pam_usertype.so issystem
    


* * *
# ifstat

## NAME



           ifstat - handy utility to read network interface statistics
    


## SYNOPSIS



           **ifstat**[ _OPTIONS_ ] [ _INTERFACE_LIST_ ]
    
           _INTERFACE_LIST_ := _INTERFACE_LIST_ | _interface_
    


## DESCRIPTION



           **ifstat** neatly prints out network interface statistics.  The
           utility keeps records of the previous data displayed in history
           files and by default only shows difference between the last and
           the current call.  Location of the history files defaults to
           /tmp/.ifstat.u$UID but may be overridden with the IFSTAT_HISTORY
           environment variable. Similarly, the default location for xstat
           (extended stats) is /tmp/.<xstat name>_ifstat.u$UID.
    


## OPTIONS



           **-h, --help**
                  Show summary of options.
    
           **-V, --version**
                  Show version of program.
    
           **-a, --ignore**
                  Ignore the history file.
    
           **-d, --scan=SECS**
                  Sample statistics every SECS second.
    
           **-e, --errors**
                  Show errors.
    
           **-n, --nooutput**
                  Don't display any output.  Update the history file only.
    
           **-r, --reset**
                  Reset history.
    
           **-s, --noupdate**
                  Don't update the history file.
    
           **-t, --interval=SECS**
                  Report average over the last SECS seconds.
    
           **-z, --zeros**
                  Show entries with zero activity.
    
           **-j, --json**
                  Display results in JSON format
    
           **-p, --pretty**
                  If combined with **--json** , pretty print the output.
    
           **-x, --extended=TYPE**
                  Show extended stats of TYPE. Supported types are:
    
                          **cpu_hits** - Counts only packets that went via the
                          CPU.
    


## ENVIRONMENT



           **IFSTAT_HISTORY**
                  If set, it's value is interpreted as alternate history file
                  path.
    


* * *
# xfs_property

## NAME



           xfs_property - examine and edit properties about an XFS filesystem
    


## SYNOPSIS



           **xfs_property** _target_ **get** _name_...
           **xfs_property** _target_ **list [ -v ]**
           **xfs_property** _target_ **set** _name=value_...
           **xfs_property** _target_ **remove** _name_...
           **xfs_property -V**
    


## DESCRIPTION



           **xfs_property** retrieves, lists, sets, or removes properties of an
           XFS filesystem.  Filesystem properties are root-controlled
           attributes set on the root directory of the filesystem to enable
           the system administrator to coordinate with userspace programs.
    
           _target_ is one of: the root directory of a mounted filesystem; a
           block device containing an XFS filesystem; or a regular file
           containing an XFS filesystem.
    


## OPTIONS



           **-V** Print the version number and exits.
    


## COMMANDS



           **get** _name_...  Prints the values of the given filesystem
                  properties.
    
           **list** Lists the names of all filesystem properties.  If the **-v**
                  flag is specified, prints the values as well.
    
           **set** _name_ =_value_...  Sets the given filesystem properties to the
                  specified values and prints what was set.
    
           **remove** _name_...  Unsets the given filesystem properties.
    


## FILESYSTEM PROPERTIES



           Known filesystem properties for XFS are:
    
           _autofsck_ See xfs_scrub(8) for more information.
    


* * *
# check_lft_balance

## NAME



           check_lft_balance - check InfiniBand unicast forwarding tables
           balance
    


## SYNOPSIS



           check_lft_balance.sh [-hRv]
    


## DESCRIPTION



           check_lft_balance.sh is a script which checks for balancing in
           Infiniband unicast forwarding tables.  It analyzes the output of
           dump_lfts(8) and iblinkinfo(8)
    


## OPTIONS



           **-h** show help
    
           **-R** Recalculate dump_lfts 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.
    
           **-v** verbose output
    


* * *
# fsck.btrfs

## NAME



           fsck.btrfs - do nothing, successfully
    


## SYNOPSIS



           **fsck.btrfs**[-aApy] [_< device>_...]
    


## DESCRIPTION



           **fsck.btrfs** is a type of utility that should exist for any
           filesystem and is called during system setup when the
           corresponding **/etc/fstab** entries contain non-zero value for
           **fs_passno** , see fstab(5) for more.
    
           Traditional filesystems need to run their respective fsck utility
           in case the filesystem was not unmounted cleanly and the log needs
           to be replayed before mount. This is not needed for BTRFS. You
           should set fs_passno to 0.
    
           If you wish to check the consistency of a BTRFS filesystem or
           repair a damaged filesystem, see btrfs-check(8). By default
           filesystem consistency is checked, the repair mode is enabled via
           the _--repair_ option (use with care!).
    


## OPTIONS



           The options are all the same and detect if **fsck.btrfs** is executed
           in non-interactive mode and exits with success, otherwise prints a
           message about btrfs check.
    


## EXIT STATUS



           There are two possible exit codes returned:
    
           0
               No error
    
           8
               Operational error, eg. device does not exist
    


## FILES



           **/etc/fstab**
    


* * *
# ibdiscover

## NAME



           ibdiscover.pl - annotate and compare InfiniBand topology
    


## SYNOPSIS



           **ibdiscover.pl**
    


## DESCRIPTION



           ibdiscover.pl uses a topology file create by ibnetdiscover and a
           discover.map file which the network administrator creates which
           indicates the nodes to be expected and a ibdiscover.topo file
           which is the expected connectivity and produces a new connectivity
           file (discover.topo.new) and outputs the changes to stdout. The
           network administrator can choose to replace the "old" topo file
           with the new one or certain changes in.
    
           The syntax of the ibdiscover.map file is:
    
           <nodeGUID>|port|"Text for node"|<NodeDescription from
           ibnetdiscover format>
    
           e.g.
    
           8f10400410015|8|"ISR 6000"|# SW-6IB4 Voltaire port 0 lid 5
    
           8f10403960558|2|"HCA 1"|# MT23108 InfiniHost Mellanox Technologies
    
           The syntax of the old and new topo files (ibdiscover.topo and
           ibdiscover.topo.new) are:
    
           <LocalPort>|<LocalNodeGUID>|<RemotePort>|<RemoteNodeGUID>
    
           e.g.
    
           10|5442ba00003080|1|8f10400410015
    
           These topo files are produced by the ibdiscover.pl tool.
    


## USAGE



           ibnetdiscover | ibdiscover.pl
    


* * *
# semanage-boolean

## NAME



           semanage-boolean - SELinux Policy Management boolean tool
    


## SYNOPSIS



           **semanage boolean [-h] [-n] [-N] [-S STORE] [ --extract |**
           **--deleteall | --list [-C] | --modify ( --on | --off ) boolean ]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage boolean** command controls the settings of
           booleans in SELinux policy. Booleans are if-then-else rules
           written in SELinux Policy. They can be used to customize the way
           that SELinux Policy rules effect a confined domain.
    


## 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
    
           _-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
    
           _-1, --on_
                  Enable the boolean
    
           _-0, --off_
                  Disable the boolean
    


## EXAMPLE



           Turn on the "apache can send mail" boolean (persistent version of #setsebool httpd_can_sendmail on)
           # semanage boolean -m --on httpd_can_sendmail
    
           List customized booleans
           # semanage boolean -l -C
    


* * *
# pam_rootok

## NAME



           pam_rootok - Gain only root access
    


## SYNOPSIS



    
           **pam_rootok.so**[debug]
    


## DESCRIPTION



           pam_rootok is a PAM module that authenticates the user if their
           _UID_ is _0_. Applications that are created setuid-root generally
           retain the _UID_ of the user but run with the authority of an
           enhanced effective-UID. It is the real _UID_ that is checked.
    


## OPTIONS



           **debug**
               Print debug information.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_SUCCESS
               The _UID_ is _0_.
    
           PAM_AUTH_ERR
               The _UID_ is **not** _0_.
    


## EXAMPLES



           In the case of the su(1) application the historical usage is to
           permit the superuser to adopt the identity of a lesser user
           without the use of a password. To obtain this behavior with PAM
           the following pair of lines are needed for the corresponding entry
           in the /etc/pam.d/su configuration file:
    
               # su authentication. Root is granted access by default.
               auth  sufficient   pam_rootok.so
               auth  required     pam_unix.so
    


* * *
# systemd-tpm2-generator

## NAME



           systemd-tpm2-generator - Generator for inserting TPM2
           synchronization point in the boot process
    


## SYNOPSIS



           /usr/lib/systemd/system-generators/systemd-tpm2-generator
    


## DESCRIPTION



           **systemd-tpm2-generator** is a generator that adds a _Wants=_
           dependency from sysinit.target to tpm2.target when it detects that
           the firmware discovered a TPM2 device but the OS kernel so far did
           not.  tpm2.target is supposed to act as synchronization point for
           all services that require TPM2 device access. See
           systemd.special(7) for details.
    
           The **systemd.tpm2_wait=** kernel command line option may be used to
           override behaviour of the generator. It accepts a boolean value:
           if true then tpm2.target will be added as synchronization point
           even if the firmware has not detected a TPM2 device. If false, the
           target will not be inserted even if firmware reported a device but
           the OS kernel does not expose a device for it yet. The latter
           might be useful in environments where a suitable TPM2 driver for
           the available hardware is not available.
    
           **systemd-tpm2-generator** implements systemd.generator(7).
    


* * *
# setvtrgb

## NAME



           setvtrgb - set the virtual terminal RGB colors
    


## SYNOPSIS



           **setvtrgb**[_options_] _vga|FILE|-_
    


## DESCRIPTION



           The _setvtrgb_ command takes a single argument, either the string
           **vga** , or a path to a file containing the colors to be used by the
           Linux virtual terminals.
    
           You can choose to write the colors in decimal or hexadecimal
           format, it will be detected on runtime.
    
           Decimal **FILE** format should be exactly 3 lines of 16 comma-
           separated decimal values for RED, GREEN, and BLUE.
    
           To seed a valid **FILE** :
                  **cat /sys/module/vt/parameters/default_{red,grn,blu} > FILE**
    
           And then edit the values in **FILE**
    
           Hexadecimal **FILE** format should be exactly 16 lines of hex triplets
           for RED, GREEN and BLUE, prefixed with a number sign (#). For
           example:
                  **#000000**
                  **#AA0000**
                  **#00AA00**
                  **#AA5500**
                  **#0000AA**
                  **#AA00AA**
                  **#00AAAA**
                  **#AAAAAA**
                  **#555555**
                  **#FF5555**
                  **#55FF55**
                  **#FFFF55**
                  **#5555FF**
                  **#FF55FF**
                  **#55FFFF**
                  **#FFFFFF**
    


## OPTIONS



           **-C** , **--console** =_DEV_
                  the console device to be used.
    
           **-h** , **--help**
                  Prints usage message and exits.
    
           **-V** , **--version**
                  Prints version number and exists.
    


## DOCUMENTATION



           Documentation by Dustin Kirkland.
    


* * *
# getsebool

## NAME



           getsebool - get SELinux boolean value(s)
    


## SYNOPSIS



           **getsebool**[**-a**] [_boolean_]
    


## DESCRIPTION



           **getsebool** reports whether a particular SELinux boolean, or all
           SELinux booleans, are on or off.  In certain situations a boolean
           can be in one state with a pending change to the other state.
           getsebool will report this as a pending change.  The pending value
           indicates the value that will be applied upon the next boolean
           commit.
    
           The setting of boolean values occurs in two stages; first the
           pending value is changed, then the booleans are committed, causing
           their active values to become their pending values. This allows a
           group of booleans to be changed in a single transaction, by
           setting all of their pending values as desired and then committing
           once.
    


## OPTIONS



           **-a** Show all SELinux booleans.
    


## EXAMPLE



           Show current state of httpd_can_connect_ftp
           # getsebool httpd_can_connect_ftp
    


* * *
# checkmodule

## NAME



           checkmodule - SELinux policy module compiler
    


## SYNOPSIS



           **checkmodule** _[-h] [-b] [-c policy_version] [-C] [-E] [-m] [-M] [-N]_
           _[-L] [-U handle_unknown] [-V] [-o output_file] [input_file]_
    


## DESCRIPTION



           This manual page describes the **checkmodule** command.
    
           **checkmodule** is a program that checks and compiles a SELinux
           security policy module into a binary representation.  It can
           generate either a base policy module (default) or a non-base
           policy module (-m option); typically, you would build a non-base
           policy module to add to an existing module store that already has
           a base module provided by the base policy.  Use
           semodule_package(8) to combine this module with its optional file
           contexts to create a policy package, and then use semodule(8) to
           install the module package into the module store and load the
           resulting policy.
    


## OPTIONS



           **-b,--binary**
                  Read an existing binary policy module file rather than a
                  source policy module file.  This option is a
                  development/debugging aid.
    
           **-C,--cil**
                  Write CIL policy file rather than binary policy file.
    
           **-E,--werror**
                  Treat warnings as errors
    
           **-h,--help**
                  Print usage.
    
           **-m** Generate a non-base policy module.
    
           **-M,--mls**
                  Enable the MLS/MCS support when checking and compiling the
                  policy module.
    
           **-N,--disable-neverallow**
                  Do not check neverallow rules.
    
           **-L,--line-marker-for-allow**
                  Output line markers for allow rules, in addition to
                  neverallow rules. This option increases the size of the
                  output CIL policy file, but the additional line markers
                  helps debugging, especially neverallow failure reports. Can
                  only be used when writing a CIL policy file.
    
           **-V,--version**
                  Show policy versions created by this program.
    
           **-o,--output filename**
                  Write a binary policy module file to the specified
                  filename.  Otherwise, checkmodule will only check the
                  syntax of the module source file and will not generate a
                  binary module at all.
    
           **-U,--handle-unknown <action>**
                  Specify how the kernel should handle unknown classes or
                  permissions (deny, allow or reject).
    
           **-c policyvers**
                  Specify the policy version, defaults to the latest.
    


## EXAMPLE



           # Build a MLS/MCS-enabled non-base policy module.
           $ checkmodule -M -m httpd.te -o httpd.mod
    


* * *
# tipc-socket

## NAME



           tipc-socket - show TIPC socket (port) information
    


## SYNOPSIS



           **tipc socket list**
    


## OPTIONS



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


## DESCRIPTION



           A TIPC socket is represented by an unsigned integer.
    
              **Bound state**
                  A bound socket has a logical TIPC port name associated with
                  it.
    
              **Connected state**
                  A connected socket is directly connected to another socket
                  creating a point to point connection between TIPC sockets.
                  If the connection to X was made using a logical port name Y
                  that name will show up as **connected to** X **via** Y
    


## EXIT STATUS



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


* * *
# pam_wheel

## NAME



           pam_wheel - Only permit root access to members of group wheel
    


## SYNOPSIS



    
           **pam_wheel.so**[debug] [deny] [group=_name_] [root_only] [trust]
                        [use_uid]
    


## DESCRIPTION



           The pam_wheel PAM module is used to enforce the so-called _wheel_
           group. By default it permits access to the target user if the
           applicant user is a member of the _wheel_ group. If no group with
           this name exist, the module is using the group with the group-ID
           **0**.
    


## OPTIONS



           **debug**
               Print debug information.
    
           **deny**
               Reverse the sense of the auth operation: if the user is trying
               to get UID 0 access and is a member of the wheel group (or the
               group of the **group** option), deny access. Conversely, if the
               user is not in the group, return PAM_IGNORE (unless **trust** was
               also specified, in which case we return PAM_SUCCESS).
    
           **group=**_name_
               Instead of checking the wheel or GID 0 groups, use the _name_
               group to perform the authentication.
    
           **root_only**
               The check for wheel membership is done only when the target
               user UID is 0.
    
           **trust**
               The pam_wheel module will return PAM_SUCCESS instead of
               PAM_IGNORE if the user is a member of the wheel group (thus
               with a little play stacking the modules the wheel members may
               be able to su to root without being prompted for a passwd).
    
           **use_uid**
               The check will be done against the real uid of the calling
               process, instead of trying to obtain the user from the login
               session associated with the terminal in use.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_AUTH_ERR
               Authentication failure.
    
           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_IGNORE
               The return value should be ignored by PAM dispatch.
    
           PAM_PERM_DENY
               Permission denied.
    
           PAM_SERVICE_ERR
               Cannot determine the user name.
    
           PAM_SUCCESS
               Success.
    
           PAM_USER_UNKNOWN
               User not known.
    


## EXAMPLES



           The root account gains access by default (rootok), only wheel
           members can become root (wheel) but Unix authenticate non-root
           applicants.
    
               su      auth     sufficient     pam_rootok.so
               su      auth     required       pam_wheel.so
               su      auth     required       pam_unix.so
    


* * *
# systemd-bless-boot-generator

## NAME



           systemd-bless-boot-generator - Pull systemd-bless-boot.service
           into the initial boot transaction when boot counting is in effect
    


## SYNOPSIS



           /usr/lib/systemd/system-generators/systemd-bless-boot-generator
    


## DESCRIPTION



           systemd-bless-boot-generator is a generator that pulls
           systemd-bless-boot.service into the initial boot transaction when
           boot counting, as implemented by systemd-boot(7), is enabled.
    
           systemd-bless-boot-generator implements systemd.generator(7).
    


* * *
# ibchecknode

## NAME



           ibchecknode - validate IB node and report errors
    


## SYNOPSIS



           **ibchecknode**[-h] [-v] [-N | -nocolor] [-G] [-C ca_name] [-P
           ca_port] [-t(imeout) timeout_ms] <lid|guid>
    


## DESCRIPTION



           Check connectivity and do some simple sanity checks for the
           specified node.  Port address is a lid unless -G option is used to
           specify a GUID address.
    


## OPTIONS



           -G      use GUID address argument. In most cases, it is the Port
           GUID.
                   Example:
                   "0x08f1040023"
    
           -v      increase the verbosity level
    
           -N | -nocolor use mono rather than color mode
    
           -C <ca_name>    use the specified ca_name.
    
           -P <ca_port>    use the specified ca_port.
    
           -t <timeout_ms> override the default timeout for the solicited
           mads.
    


## EXAMPLE



           ibchecknode 2           # check node via lid 2
    


* * *
# pam_loginuid

## NAME



           pam_loginuid - Record user's login uid to the process attribute
    


## SYNOPSIS



    
           **pam_loginuid.so**[require_auditd]
    


## DESCRIPTION



           The pam_loginuid module sets the loginuid process attribute for
           the process that was authenticated. This is necessary for
           applications to be correctly audited. This PAM module should only
           be used for entry point applications like: login, sshd, gdm,
           vsftpd, crond and atd. There are probably other entry point
           applications besides these. You should not use it for applications
           like sudo or su as that defeats the purpose by changing the
           loginuid to the account they just switched to.
    


## OPTIONS



           **require_auditd**
               This option, when given, will cause this module to query the
               audit daemon status and deny logins if it is not running.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_SUCCESS
               The loginuid value is set and auditd is running if check
               requested.
    
           PAM_IGNORE
               The /proc/self/loginuid file is not present on the system or
               the login process runs inside uid namespace and kernel does
               not support overwriting loginuid.
    
           PAM_SESSION_ERR
               Any other error prevented setting loginuid or auditd is not
               running.
    


## EXAMPLES



               #%PAM-1.0
               auth       required     pam_unix.so
               auth       required     pam_nologin.so
               account    required     pam_unix.so
               password   required     pam_unix.so
               session    required     pam_unix.so
               session    required     pam_loginuid.so
    


* * *
# systemd-rfkill.service

## NAME



           systemd-rfkill.service, systemd-rfkill.socket, systemd-rfkill -
           Load and save the RF kill switch state at boot and change
    


## SYNOPSIS



           systemd-rfkill.service
    
           systemd-rfkill.socket
    
           /usr/lib/systemd/systemd-rfkill
    


## DESCRIPTION



           systemd-rfkill.service is a service that restores the RF kill
           switch state at early boot and saves it on each change. On disk,
           the RF kill switch state is stored in /var/lib/systemd/rfkill/.
    


## KERNEL COMMAND LINE



           **systemd-rfkill** understands the following kernel command line
           parameter. See also kernel-command-line(7).
    
           _systemd.restore_state=_
               Takes a boolean argument. Defaults to "1". If "0", does not
               restore the rfkill settings on boot. However, settings will
               still be stored on shutdown.
    
               Added in version 227.
    


* * *
# sestatus

## NAME



           sestatus - SELinux status tool
    


## SYNOPSIS



           **sestatus** _[-v] [-b]_
    
           This tool is used to get the status of a system running SELinux.
    


## DESCRIPTION



           This manual page describes the **sestatus** program.
    
           This tool is used to get the status of a system running SELinux.
           It displays data about whether SELinux is enabled or disabled,
           location of key directories, and the loaded policy with its status
           as shown in the example:
                  > sestatus
                  SELinux status:              enabled
                  SELinuxfs mount:             /selinux
                  SELinux root directory:      /etc/selinux
                  Loaded policy name:          targeted
                  Current mode:                permissive
                  Mode from config file:       enforcing
                  Policy MLS status:           enabled
                  Policy deny_unknown status:  allow
                  Memory protection checking:  actual (secure)
                  Max kernel policy version:   26
    
           **sestatus** can also be used to display:
    
                  -   The security context of files and processes listed in
                      the _/etc/sestatus.conf_ file. The format of this file is
                      described in sestatus.conf(5).
    
                  -   The status of booleans.
    


## OPTIONS



           **-v**
                  Displays the contexts of files and processes listed in the
                  _/etc/sestatus.conf_ file. It also checks whether the file is
                  a symbolic link, if so then the context of the target file
                  is also shown.
    
                  The following contexts will always be displayed:
                         The current process context
                         The init process context
                         The controlling terminal file context
    
           **-b**
                  Display the current state of booleans.
    


## FILES



           _/etc/sestatus.conf_
    


* * *
# lvmsar

## NAME



           lvmsar — LVM system activity reporter
    


## SYNOPSIS



           **lvmsar**
    


## DESCRIPTION



           lvmsar is not supported under LVM2. The device-mapper statistics
           facility provides similar performance metrics using the dmstats(8)
           command.
    


* * *
# btrfs-map-logical

## NAME



           btrfs-map-logical - map btrfs logical extent to physical extent
    


## SYNOPSIS



           **btrfs-map-logical** _< options> <device>_
    


## DESCRIPTION



           **btrfs-map-logical** can be used to find out what the physical
           offsets are on the mirrors, the result is dumped to stdout by
           default.
    
           Mainly used for debug purpose.
    


## OPTIONS



           -l|--logical _< logical_num>_
               Logical extent to map.
    
           -c|--copy _< copy>_
               Copy of the extent to read(usually 1 or 2).
    
           -o|--output _< filename>_
               Output file to hold the extent.
    
           -b|--bytes _< bytes>_
               Number of bytes to read.
    


## EXIT STATUS



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


* * *
# delpart

## NAME



           delpart - tell the kernel to forget about a partition
    


## SYNOPSIS



           **delpart** _device partition_
    


## DESCRIPTION



           **delpart** asks the Linux kernel to forget about the specified
           _partition_ (a number) on the specified _device_. The command is a
           simple wrapper around the "del partition" ioctl.
    
           This command doesn’t manipulate partitions on a block device.
    


## OPTIONS



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


## AVAILABILITY



           The **delpart** 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-08-09                     _DELPART_(8)
    


* * *
# kbdrate

## NAME



           kbdrate - reset the keyboard repeat rate and delay time
    


## SYNOPSIS



           **kbdrate**[_options_...]
    


## DESCRIPTION



           **kbdrate** is used to change the keyboard repeat rate and delay time.
           The delay is the amount of time that a key must be depressed
           before it will start to repeat.
    
           Using **kbdrate** without any options will reset the repeat rate to
           10.9 characters per second (cps) and the delay to 250 milliseconds
           (ms) for Intel- and M68K-based systems.  These are the IBM
           defaults. On SPARC-based systems it will reset the repeat rate to
           5 cps and the delay to 200 ms.
    


## OPTIONS



           **-r** , **--rate** =_NUMBER_
                  Change the keyboard repeat rate to _NUMBER_ cps. For Intel-
                  based systems, the allowable range is from 2.0 to 30.0 cps.
                  Only certain, specific values are possible, and the program
                  will select the nearest possible value to the one
                  specified. The possible values are given, in characters per
                  second, as follows: 2.0, 2.1, 2.3, 2.5, 2.7, 3.0, 3.3, 3.7,
                  4.0, 4.3, 4.6, 5.0, 5.5, 6.0, 6.7, 7.5, 8.0, 8.6, 9.2,
                  10.0, 10.9, 12.0, 13.3, 15.0, 16.0, 17.1, 18.5, 20.0, 21.8,
                  24.0, 26.7, 30.0.  For SPARC-based systems, the allowable
                  range is from 0 (no repeat) to 50 cps.
    
           **-d** , **--delay** =_NUMBER_
                  Change the delay to _NUMBER_ milliseconds.  For Intel-based
                  systems, the allowable range is from 250 to 1000 ms, in 250
                  ms steps. For SPARC systems, possible values are between 10
                  ms and 1440 ms, in 10 ms steps.
    
           **-s** , **--silent**
                  Silent. No messages are printed.
    
           **-h** , **--help**
                  Display a help text.
    
           **-V** , **--version**
                  Display a version number and exit.
    


## BUGS



           Not all keyboards support all rates.
    
           Not all keyboards have the rates mapped in the same way.
    
           Setting the repeat rate on the Gateway AnyKey keyboard does not
           work.  If someone with a Gateway figures out how to program the
           keyboard, please send mail to util-linux@math.uio.no.
    
           All this is very architecture dependent.  Nowadays **kbdrate** first
           tries the KDKBDREP and KIOCSRATE ioctls.  (The former usually
           works on an m68k/i386 machine, the latter for SPARC.)  When these
           ioctls fail an ioport interface.
    


## FILES



           _/etc/rc.local_
           _/dev/port_
    


* * *
# lpmove

## NAME



           lpmove - move a job or all jobs to a new destination
    


## SYNOPSIS



           **lpmove**[ **-h** _server_[**:**_port_] ] [ **-E**] [ **-U** _username_ ] _job destination_
           **lpmove**[ **-h** _server_[**:**_port_] ] [ **-E**] [ **-U** _username_ ] _source_
           _destination_
    


## DESCRIPTION



           **lpmove** moves the specified _job_ or all jobs from _source_ to
           _destination_. _job_ can be the job ID number or the old destination
           and job ID.
    


## OPTIONS



           The **lpmove** command supports the following options:
    
           **-E** Forces encryption when connecting to the server.
    
           **-U** _username_
                Specifies an alternate username.
    
           **-h** _server_[**:**_port_]
                Specifies an alternate server.  Note: This option must occur
                before all others.
    


## EXAMPLES



           Move job 123 from "oldprinter" to "newprinter":
    
               lpmove 123 newprinter
    
                       _or_
    
               lpmove oldprinter-123 newprinter
    
           Move all jobs from "oldprinter" to "newprinter":
    
               lpmove oldprinter newprinter
    


* * *
# btrfs-find-root

## NAME



           btrfs-find-root - filter to find btrfs root
    


## SYNOPSIS



           **btrfs-find-root**[options] _< device>_
    


## DESCRIPTION



           **btrfs-find-root** is used to find the satisfied root, you can filter
           by root tree’s objectid, generation, level.
    


## OPTIONS



           -a
               Search through all metadata extents, even the root has been
               already found.
    
           -g _< generation>_
               Filter root tree by it’s original transaction id, tree root’s
               generation in default.
    
           -o _< objectid>_
               Filter root tree by it’s objectid,tree root’s objectid in
               default.
    
           -l _< level>_
               Filter root tree by B-+ tree’s level, level 0 in default.
    


## EXIT STATUS



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


* * *