tripathysagar/man_text huggingface dataset:
# isosize

## NAME



           isosize - output the length of an iso9660 filesystem
    


## SYNOPSIS



           **isosize**[options] _iso9660_image_file_
    


## DESCRIPTION



           This command outputs the length of an iso9660 filesystem that is
           contained in the specified file. This file may be a normal file or
           a block device (e.g. _/dev/hdd_ or _/dev/sr0_). In the absence of any
           options (and errors), it will output the size of the iso9660
           filesystem in bytes. This can now be a large number (>> 4 GB).
    


## OPTIONS



           **-x** , **--sectors**
               Show the block count and block size in human-readable form.
               The output uses the term "sectors" for "blocks".
    
           **-d** , **--divisor** _number_
               Only has an effect when **-x** is not given. The value shown (if
               no errors) is the iso9660 file size in bytes divided by
               _number_. So if _number_ is the block size then the shown value
               will be the block count.
    
               The size of the file (or block device) holding an iso9660
               filesystem can be marginally larger than the actual size of
               the iso9660 filesystem. One reason for this is that cd writers
               are allowed to add "run out" sectors at the end of an iso9660
               image.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## EXIT STATUS



           **0**
               success
    
           **1**
               generic failure, such as invalid usage
    
           **32**
               all failed
    
           **64**
               some failed
    


## AVAILABILITY



           The **isosize** 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                     _ISOSIZE_(8)
    


* * *
# ibcheckerrors

## NAME



           ibcheckerrors - validate IB subnet and report errors
    


## SYNOPSIS



           **ibcheckerrors**[-h] [-b] [-v] [-N | -nocolor] [<topology-file> | -C
           ca_name -P ca_port -t(imeout) timeout_ms]
    


## DESCRIPTION



           ibcheckerrors is a script which uses a full topology file that was
           created by ibnetdiscover, scans the network to validate the
           connectivity and reports errors (from port counters).
    


## OPTIONS



           -v   increase the verbosity level
    
           -b   brief mode. Reduce the output to show only if errors are
           present,
                not what they are.
    
           -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.
    


* * *
# ibswportwatch

## NAME



           ibswportwatch.pl - poll the counters on the specified switch/port
           and report rate of change information.
    


## SYNOPSIS



           **ibswportwatch.pl**[-p <pause_time> -v -n <cycles> -G] <guid|lid>
           <port>
    


## DESCRIPTION



           ibswportwatch.pl polls the port counters of the specified port and
           calculates rate of change information.
    


## OPTIONS



           **-p <pause_time>**
                  Specify a pause time (polling interval) other than the
                  default.
    
           **-v** Be verbose.
    
           **-n <cycles>**
                  Run for a set number of poll intervals and stop.  (Default
                  == -1 == forever)
    
           **-G** The address provided is a GUID rather than LID.
    


* * *
# pscap

## NAME



           pscap - a program to see capabilities
    


## SYNOPSIS



           **pscap [ -a | -p pid ]**
    


## DESCRIPTION



           **pscap** is a program that prints out a report of process
           capabilities. If the application has any capabilities, it will be
           in the report with the exception of init. By giving the -a command
           line option, init will be included, too. By giving a pid with the
           -p command line option, only the process specified with the pid is
           reported. If a process is not in the report, it has dropped all
           capabilities. If the process has partial capabilities, it is
           further examined to see if it has an open-ended bounding set. If
           this is found to be true, a '+' symbol is added. If the process
           has ambient capabilities, a '@' symbols is added.
    
           The command name in the output may be followed by an asterisk mark
           (*). This mark denotes processes which run in child user
           namespaces (relative to the user namespace of pscap itself).
    


* * *
# pkgtorrent-service

## NAME



           pkgtorrent-service(8) Is a python WSGI web application that can
           generate BitTorrent files for binary files available from the web
           server.
    


## SYNOPSIS



           The program should installed on a site local **yum** mirror and must
           be configured before use. See pkgtorrent-service.conf(5) for more
           information.
    


## USAGE



           The primary use case for this service is implemented in
           yum-torrent(1).
    
           There is a secondary interface to assist with simple file
           downloads involving a single path.
    


## EXAMPLE



                  $ curl http://example.com/**path/to/large/file** > **file**
    
           can be converted to using BitTorrent with:
    
                  $ curl http://example.com/**path** /torrent_service/single/**path/to/large/file** > **file**.torrent
                  $ btclient **file**.torrent
    
           Note the repetition of **path** before the service name, and the
           addition of **torrent_service/single** to pass control to the single
           path mode.  Simple file mode supports simple globbing, so you can
           specify ...**/directory/*.foo**.  If the path resolves to only one
           file, the multi-file support in the .torrent file is skipped,
           making the downloaded file easier to handle.
    


## INPUT FILES



           /var/lib/torrent_service/trackers
                  The service needs to include one or more BitTorrent tracker
                  servers.  The format is one "announce" URL per line.
                  Example: **http://example.com:6969/announce** This text file is
                  scanned each minute for updates.
    


## OUTPUT FILES



           The service makes extensive use of cache files. The files are
           relatively small. It is recommended you periodically clean these
           caches for files not used in the past month or so.
    
           /var/cache/torrent_service/info/**input_digest**
                  This directory caches _info_hashes_ for the previously
                  requested path digests.  These are used with the current
                  list of trackers to generate .torrent files in constant
                  time.
    
           /var/cache/torrent_service/pieces/path/to/file/_blocksize_
                  Every file within a torrent is represented by a list of
                  SHA1 digests, one for each _blocksize_ of the file.  The SHA1
                  list is expensive to generate.  The same binaries may be
                  downloaded in different permutations by different clients.
                  The cache is invalidated if the original file has a
                  different mtime or is a different size.
    


## BUGS



           Single file mode should be called simple.
    


* * *
# system-config-selinux

## NAME



           system-config-selinux - SELinux Management tool
    


## SYNOPSIS



           **system-config-selinux**
    


## DESCRIPTION



           **system-config-selinux** provides a graphical interface for managing
           the SELinux configuration.
    


## OPTIONS



           None
    


## FILES



           /usr/bin/system-config-selinux
    


## Examples



           To run the program type:
    
           system-config-selinux
    


* * *
# systemd-makefs@.service

## NAME



           systemd-makefs@.service, systemd-mkswap@.service, systemd-
           growfs@.service, systemd-growfs-root.service, systemd-makefs,
           systemd-growfs - Creating and growing file systems on demand
    


## SYNOPSIS



           systemd-makefs@_device_.service
    
           systemd-mkswap@_device_.service
    
           systemd-growfs@_mountpoint_.service
    
           systemd-growfs-root.service
    
           /usr/lib/systemd/systemd-makefs
    
           /usr/lib/systemd/systemd-growfs
    


## DESCRIPTION



           systemd-makefs@.service, systemd-mkswap@.service,
           systemd-growfs@.service, and systemd-growfs-root.service are used
           to implement the **x-systemd.makefs** and **x-systemd.growfs** options in
           fstab(5), see systemd.mount(5). They are instantiated for each
           device for which the file system or swap structure needs to be
           initialized, and for each mount point where the file system needs
           to be grown.
    
           These services are started at boot, either right before or right
           after the mount point or swap device are used.
    
           systemd-makefs knows very little about specific file systems and
           swap devices, and after checking that the block device does not
           already contain a file system or other content, it will execute
           binaries specific to each filesystem type (/sbin/mkfs._type_ or
           /sbin/mkswap). For certain file system types (currently
           ext2/ext3/ext4(5), **btrfs**(5), xfs(5), f2fs, vfat) and for swap
           devices, it will configure reasonable defaults and set the file
           system label and UUID based on the device name.
    
           systemd-growfs knows very little about specific file systems and
           swap devices, and will instruct the kernel to grow the mounted
           filesystem to full size of the underlying block device.
           Nevertheless, it needs to know the ioctl(2) number specific to
           each file system, so only certain types are supported. Currently:
           ext4(5), **btrfs**(5), xfs(5), and dm-crypt partitions (see
           cryptsetup(8)).
    
           If the creation of a file system or swap device fails, the mount
           point or swap is failed too. If the growing of a file system
           fails, a warning is emitted.
    


* * *
# systemd-remount-fs.service

## NAME



           systemd-remount-fs.service, systemd-remount-fs - Remount root and
           kernel file systems
    


## SYNOPSIS



           systemd-remount-fs.service
    
           /usr/lib/systemd/systemd-remount-fs
    


## DESCRIPTION



           systemd-remount-fs.service is an early boot service that applies
           mount options listed in fstab(5), or gathered from the partition
           table (when systemd-gpt-auto-generator(8) is active) to the root
           file system, the /usr/ file system, and the kernel API file
           systems. This is required so that the mount options of these file
           systems — which are pre-mounted by the kernel, the initrd,
           container environments or system manager code — are updated to
           those configured in /etc/fstab and the other sources. This service
           ignores normal file systems and only changes the root file system
           (i.e.  /), /usr/, and the virtual kernel API file systems such as
           /proc/, /sys/ or /dev/. This service executes no operation if no
           configuration is found (/etc/fstab does not exist or lists no
           entries for the mentioned file systems, or the partition table
           does not contain relevant entries).
    
           For a longer discussion of kernel API file systems see **API File**
           **Systems******[1].
    
           Note: systemd-remount-fs.service is usually pulled in bysystemd-fstab-generator(8), hence it is also affected by the
           kernel command line option _fstab=_ , which may be used to disable
           the generator. It may also be pulled in by
           systemd-gpt-auto-generator(8), which is affected by
           _systemd.gpt_auto_ and other options.
    


## NOTES



            1. API File Systems
               https://systemd.io/API_FILE_SYSTEMS
    


* * *
# mcstransd

## NAME



           mcstransd - MCS (Multiple Category System) daemon.  Translates
           SELinux MCS/MLS labels to human readable form.
    


## SYNOPSIS



           **mcstransd [-f] [-h]**
    


## DESCRIPTION



           This manual page describes the **mcstransd** program.
    
           This daemon reads /etc/selinux/{SELINUXTYPE}/setrans.conf
           configuration file, and communicates with libselinux via a socket
           in /var/run/setrans.
    


## OPTIONS



           -f     Run mcstransd in the foreground.  Do not run as a daemon.
    
           -h     Output a short summary of available command line options.
    


## FILES



           /etc/selinux/{SELINUXTYPE}/setrans.conf
    


* * *
# stapsh

## NAME



           stapsh
    


## SYNOPSIS



           **stapsh**
    


## DESCRIPTION



           The stapsh executable is used by the stap _--remote_ functionality,
           as a wrapper shell on the remote machines.  It is not intended to
           be run directly by users.
    


## BUGS



           Use the Bugzilla link of the project web page or our mailing list.
           **http://sourceware.org/systemtap/ **,**< systemtap@sourceware.org>**.
    


* * *
# setcap

## NAME



           setcap - set file capabilities
    


## SYNOPSIS



           **setcap**[-q] [-n <rootuid>] [-v] {_capabilities|-|-r} filename_ [ ...
           _capabilitiesN fileN_ ]
    


## DESCRIPTION



           In the absence of the **-v**(verify) option **setcap** sets the
           capabilities of each specified _filename_ to the _capabilities_
           specified.  The optional **-n <rootuid> **argument can be used to set
           the file capability for use only in a user namespace with this
           root user ID owner. The **-v** option is used to verify that the
           specified capabilities are currently associated with the file. If
           -v and -n are supplied, the **-n <rootuid> **argument is also
           verified.
    
           The _capabilities_ Set are specified in the form described in
           cap_text_formats(7).
    
           The special capability string, **'-'** , can be used to indicate that
           capabilities are read from the standard input. In such cases, the
           capability set is terminated with a blank line.
    
           The special capability string, **'-r'** , is used to remove a
           capability set from a file. Note, setting an empty capability set
           is **not the same** as removing it. An empty set can be used to
           guarantee a file is not executed with privilege in spite of the
           fact that the prevailing ambient+inheritable sets would otherwise
           bestow capabilities on executed binaries.
    
           The **'-f'** , is used to force completion even when it is in some way
           considered an invalid operation. This can affect **'-r'** and setting
           file capabilities the kernel will not be able to make sense of.
    
           The **-q** flag is used to make the program less verbose in its
           output.
    


## EXIT CODE



           The **setcap** program will exit with a 0 exit code if successful. On
           failure, the exit code is 1.
    


* * *
# pppd-radius

## NAME



           radius.so - RADIUS authentication plugin for pppd(8)
    


## SYNOPSIS



           **pppd**[ _options_ ] plugin radius.so
    


## DESCRIPTION



           The RADIUS plugin for pppd permits pppd to perform PAP, CHAP, MS-
           CHAP and MS-CHAPv2 authentication against a RADIUS server instead
           of the usual _/etc/ppp/pap-secrets_ and _/etc/ppp/chap-secrets_ files.
    
           The RADIUS plugin is built on a library called **radiusclient** which
           has its own configuration files (usually in _/etc/radiusclient_),
           consult those files for more information on configuring the RADIUS
           plugin
    


## OPTIONS



           The RADIUS plugin introduces one additional pppd option:
    
           **radius-config-file** _filename_
                  The file _filename_ is taken as the radiusclient
                  configuration file.  If this option is not used, then the
                  plugin uses _/etc/radiusclient/radiusclient.conf_ as the
                  configuration file.
    
           **avpair** _attribute=value_
                  Adds an Attribute-Value pair to be passed on to the RADIUS
                  server on each request.
    
           **map-to-ifname**
                  Sets Radius NAS-Port attribute to number equal to interface
                  name (Default)
    
           **map-to-ttyname**
                  Sets Radius NAS-Port attribute value via libradiusclient
                  library
    


## USAGE



           To use the plugin, simply supply the **plugin radius.so** option to
           pppd, and edit _/etc/radiusclient/radiusclient.conf_ appropriately.
           If you use the RADIUS plugin, the normal pppd authentication
           schemes (login, checking the /etc/ppp/*-secrets files) are
           skipped.  The RADIUS server should assign an IP address to the
           peer using the RADIUS Framed-IP-Address attribute.
    


* * *
# umount.nfs

## NAME



           umount.nfs, umount.nfs4 - unmount a Network File System
    


## SYNOPSIS



           **umount.nfs** _dir_ **[-fvnrlh ]**
    


## DESCRIPTION



           **umount.nfs** and **umount.nfs4** are a part of nfs(5) utilities package,
           which provides NFS client functionality.
    
           **umount.nfs4** and **umount.nfs** are meant to be used by the umount(8)
           command for unmounting NFS shares. This subcommand, however, can
           also be used as a standalone command with limited functionality.
    
           _dir_ is the directory on which the file system is mounted.
    


## OPTIONS



           **-f** Force unmount the file system in case of unreachable NFS
                  system.
    
           **-v** Be verbose.
    
           **-n** Do not update _/etc/mtab._  By default, an entry is created
                  in _/etc/mtab_ for every mounted file system. Use this option
                  to skip deleting an entry.
    
           **-r** In case unmounting fails, try to mount read-only.
    
           **-l** Lazy unmount. Detach the file system from the file system
                  hierarchy now, and cleanup all references to the file
                  system as soon as it is not busy anymore.
    
           **-h** Print help message.
    


## NOTE



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


## FILES



           _/etc/fstab_
                  file system table
    
           _/etc/mtab_
                  table of mounted file systems
    


* * *
# shutdown

## NAME



           shutdown - Halt, power off or reboot the machine
    


## SYNOPSIS



    
           **shutdown**[OPTIONS...] [TIME] [WALL...]
    


## DESCRIPTION



           **shutdown** may be used to halt, power off, or reboot the machine.
    
           The first argument may be a time string (which is usually "now").
           Optionally, this may be followed by a wall message to be sent to
           all logged-in users before going down.
    
           The time string may either be in the format "hh:mm" for
           hour/minutes specifying the time to execute the shutdown at,
           specified in 24h clock format. Alternatively it may be in the
           syntax "+m" referring to the specified number of minutes m from
           now.  "now" is an alias for "+0", i.e. for triggering an immediate
           shutdown. If no time argument is specified, "+1" is implied.
    
           Note that to specify a wall message you must specify a time
           argument, too.
    
           If the time argument is used, 5 minutes before the system goes
           down the /run/nologin file is created to ensure that further
           logins shall not be allowed.
    


## OPTIONS



           The following options are understood:
    
           **--help**
               Print a short help text and exit.
    
           **-H** , **--halt**
               Halt the machine.
    
           **-P** , **--poweroff**
               Power the machine off (the default).
    
           **-r** , **--reboot**
               Reboot the machine.
    
           **-h**
               The same as **--poweroff** , but does not override the action to
               take if it is "halt". E.g.  **shutdown --reboot -h** means
               "poweroff", but **shutdown --halt -h** means "halt".
    
           **-k**
               Do not halt, power off, or reboot, but just write the wall
               message.
    
           **--no-wall**
               Do not send wall message before halt, power off, or reboot.
    
           **-c**
               Cancel a pending shutdown. This may be used to cancel the
               effect of an invocation of **shutdown** with a time argument that
               is not "+0" or "now".
    
           **--show**
               Show a pending shutdown action and time if there is any.
    
               Added in version 250.
    


## EXIT STATUS



           On success, 0 is returned, a non-zero failure code otherwise.
    


## COMPATIBILITY



           The
            **shutdown** command in previous init systems (including sysvinit)
           defaulted to single-user mode instead of powering off the machine.
           To change into single-user mode, use **systemctl rescue** instead.
    


* * *
# showconsolefont

## NAME



           showconsolefont - Show the current EGA/VGA console screen font
    


## SYNOPSIS



           **showconsolefont**[_options_]
    


## DESCRIPTION



           The **showconsolefont** command outputs the current console font to
           stdout.  On Linux 2.6.1 and later, the option **-C** allows one to
           indicate the console involved. Its argument is a pathname.
    


## OPTIONS



           **-i** , **--info**
                  don't print out the font table, just show: ROWSxCOLSxCOUNT
                  and exit.
    
           **-C** , **--console** =_DEV_
                  the console device to be used.
    
           **-v** , **--verbose**
                  be more verbose.
    
           **-V** , **--version**
                  print version number.
    
           **-h** , **--help**
                  print this usage message.
    


* * *
# poweroff

## NAME



           poweroff, reboot, halt - Power off, reboot, or halt the machine
    


## SYNOPSIS



    
           **poweroff**[OPTIONS...]
    
           **reboot**[OPTIONS...]
    
           **halt**[OPTIONS...]
    


## DESCRIPTION



           **poweroff** , **reboot** , and **halt** may be used to power off, reboot, or
           halt the machine. All three commands take the same options.
    


## OPTIONS



           The following options are understood:
    
           **--help**
               Print a short help text and exit.
    
               Added in version 253.
    
           **--halt**
               Halt the machine, regardless of which one of the three
               commands is invoked.
    
               Added in version 253.
    
           **-p** , **--poweroff**
               Power off the machine, when either **halt** or **poweroff** is
               invoked. This option is ignored when **reboot** is invoked.
    
               Added in version 253.
    
           **--reboot**
               Reboot the machine, regardless of which one of the three
               commands is invoked.
    
               Added in version 253.
    
           **-f** , **--force**
               Force immediate power-off, halt, or reboot. If specified, the
               command does not contact the init system. In most cases,
               filesystems are not properly unmounted before shutdown. For
               example, the command **reboot -f** is mostly equivalent to
               **systemctl reboot -ff** , instead of **systemctl reboot -f**.
    
               Added in version 253.
    
           **-w** , **--wtmp-only**
               Only write wtmp shutdown entry, do not actually power off,
               reboot, or halt.
    
               Added in version 253.
    
           **-d** , **--no-wtmp**
               Do not write wtmp shutdown entry.
    
               Added in version 253.
    
           **-n** , **--no-sync**
               Do not sync hard disks/storage media before power-off, reboot,
               or halt.
    
               Added in version 253.
    
           **--no-wall**
               Do not send wall message before power-off, reboot, or halt.
    
               Added in version 253.
    


## EXIT STATUS



           On success, 0 is returned, a non-zero failure code otherwise.
    


## NOTES



           These commands are implemented in a way that preserves basic
           compatibility with the original SysV commands.  systemctl(1) verbs
           **poweroff** , **reboot** , **halt** provide the same functionality with some
           additional features.
    
           Note that on many SysV systems **halt** used to be synonymous to
           **poweroff** , i.e. both commands would equally result in powering the
           machine off. systemd is more accurate here, and **halt** results in
           halting the machine only (leaving power on), and **poweroff** is
           required to actually power it off.
    


* * *
# ip-ioam

## NAME



           ip-ioam - IPv6 In-situ OAM (IOAM)
    


## SYNOPSIS



           **ip ioam**{ _COMMAND_ | **help**}
    
           **ip ioam namespace show**
    
           **ip ioam namespace add** _ID_  **[ data** _DATA32_ **]  [ wide** _DATA64_ **]**
    
           **ip ioam namespace del** _ID_
    
           **ip ioam schema show**
    
           **ip ioam schema add** _ID DATA_
    
           **ip ioam schema del** _ID_
    
           **ip ioam namespace set** _ID_ **schema**{ _ID_ | **none**}
    
           **ip ioam monitor**
    


## DESCRIPTION



           The **ip ioam** command is used to configure IPv6 In-situ OAM (IOAM6)
           internal parameters, namely IOAM namespaces and schemas.
    
           Those parameters also include the mapping between an IOAM
           namespace and an IOAM schema.
    
           The **ip ioam monitor** command displays IOAM data received.
    


## EXAMPLES



       **Configure an IOAM namespace (ID = 1) with both data (32 bits) and wide**
           **data (64 bits)**
           # ip ioam namespace add 1 data 0xdeadbeef wide 0xcafec0caf00dc0de
    
       **Link an existing IOAM schema (ID = 7) to an existing IOAM namespace**
           **(ID = 1)**
           # ip ioam namespace set 1 schema 7
    


* * *
# mail.mboxfile

## NAME



           **mail.mboxfile** — deliver mail to a file in mbox format
    


## SYNOPSIS



           **mail.mboxfile** _file_
    


## DESCRIPTION



           **mail.mboxfile** appends mail to a file in mbox format and
           acknowledges delivery success or failure with its exit status.
    


## EXIT STATUS



           The **mail.mboxfile** utility exits 0 on success, and >0 if an error
           occurs.
    


* * *
# ovs-tcpdump

## NAME



           ovs-tcpdump - Dump traffic from an Open vSwitch port using tcpdump
    


## SYNOPSIS



           **ovs-tcpdump -i <port> <tcpdump options>...**
    


## DESCRIPTION



           **ovs-tcpdump** creates switch mirror ports in the **ovs-vswitchd** daemon
           and executes **tcpdump** to listen against those ports. When the
           **tcpdump** instance exits, it then cleans up the mirror port it
           created.
    
           **ovs-tcpdump** will not allow multiple mirrors for the same port. It
           has some logic to parse the current configuration and prevent
           duplicate mirrors.
    
           The **-i** option may not appear multiple times.
    
           It is important to note that under Linux-based kernels, tap
           devices do not receive packets unless the specific tuntap device
           has been opened by an application.  This requires **CAP_NET_ADMIN**
           privileges, so the **ovs-tcpdump** command must be run as a user with
           such permissions (this is usually a super-user).
    


## OPTIONS



           • **-h** or **--help**
    
             Prints a brief help message to the console.
    
           • **-V** or **--version**
    
             Prints version information to the console.
    
           • **--db-sock <socket>**
    
             The Open vSwitch database socket connection string. The default
             is **unix: <rundir>/db.sock**.
    
           • **--dump-cmd <command>**
    
             The command to run instead of **tcpdump**.
    
           • **-i** or **--interface**
    
             The interface for which a mirror port should be created, and
             packets should be dumped.
    
           • **--mirror-to**
    
             The name of the interface which should be the destination of the
             mirrored packets. If the specified interface does not exist, it
             will be created as part of the setup process. If the interface
             already exists, it must be a port type that can be used with the
             **tcpdump** utility.  Mirror ports cannot be used for normal
             traffic. The default value is **mi <port>**.
    
           • **--span**
    
             If specified, mirror all ports (optional).
    
           • **--filter <flow>**
    
             If specified, only mirror packets that match the provided
             OpenFlow filter.  The available fields are documented in
             ovs-fields(7).
    


* * *
# booleans

## NAME



           booleans - Policy booleans enable runtime customization of SELinux
           policy
    


## DESCRIPTION



           This manual page describes SELinux policy booleans.  The SELinux
           policy can include conditional rules that are enabled or disabled
           based on the current values of a set of policy booleans.  These
           policy booleans allow runtime modification of the security policy
           without having to load a new policy.
    
           For example, the boolean httpd_enable_cgi allows the httpd daemon
           to run cgi scripts if it is enabled.  If the administrator does
           not want to allow execution of cgi scripts, he can simply disable
           this boolean value.
    
           The policy defines a default value for each boolean, typically
           false.  These default values can be overridden via local settings
           created via the setsebool(8) utility, using **-P** to make the setting
           persistent across reboots.  The **system-config-securitylevel** tool
           provides a graphical interface for altering the settings.  The
           load_policy(8) program will preserve current boolean settings upon
           a policy reload by default, or can optionally reset booleans to
           the boot-time defaults via the **-b** option.
    
           Boolean values can be listed by using the getsebool(8) utility and
           passing it the **-a** option.
    
           Boolean values can also be changed at runtime via the setsebool(8)
           utility or the togglesebool(8) utility.  By default, these
           utilities only change the current boolean value and do not affect
           the persistent settings, unless the **-P** option is used to
           setsebool.
    


* * *
# e2label

## NAME



           e2label - Change the label on an ext2/ext3/ext4 file system
    


## SYNOPSIS



           **e2label** _device_ [ _volume-label_ ]
    


## DESCRIPTION



           **e2label** will display or change the volume label on the ext2, ext3,
           or ext4 file system located on _device._
    
           If the optional argument _volume-label_ is not present, **e2label** will
           simply display the current volume label.
    
           If the optional argument _volume-label_ is present, then **e2label**
           will set the volume label to be _volume-label_.  Ext2 volume labels
           can be at most 16 characters long; if _volume-label_ is longer than
           16 characters, **e2label** will truncate it and print a warning
           message.  For other file systems that support online label
           manipulation and are mounted **e2label** will work as well, but it
           will not attempt to truncate the _volume-label_ at all.
    
           It is also possible to set the volume label using the **-L** option of
           tune2fs(8).
    


## AVAILABILITY



           **e2label** is part of the e2fsprogs package and is available from
           http://e2fsprogs.sourceforge.net.
    


* * *
# systemd-tpm2-setup.service

## NAME



           systemd-tpm2-setup.service, systemd-tpm2-setup-early.service,
           systemd-tpm2-setup - Set up the TPM2 Storage Root Key (SRK) at
           boot
    


## SYNOPSIS



           systemd-tpm2-setup.service
    
           /usr/lib/systemd/systemd-tpm2-setup
    


## DESCRIPTION



           systemd-tpm2-setup.service and systemd-tpm2-setup-early.service
           are services that generate the Storage Root Key (SRK) if it has
           not been generated yet, and stores it in the TPM.
    
           The services will store the public key of the SRK key pair in a
           PEM file in /run/systemd/tpm2-srk-public-key.pem and
           /var/lib/systemd/tpm2-srk-public-key.pem. They will also store it
           in TPM2B_PUBLIC format in
           /run/systemd/tpm2-srk-public-key.tpm2_public and
           /var/lib/systemd/tpm2-srk-public-key.tpm2b_public.
    
           systemd-tpm2-setup-early.service runs very early at boot (possibly
           in the initrd), and writes the SRK public key to
           /run/systemd/tpm2-srk-public-key.*  (as /var/ is generally not
           accessible this early yet), while systemd-tpm2-setup.service runs
           during a later boot phase and saves the public key to
           /var/lib/systemd/tpm2-srk-public-key.*.
    


## FILES



           /run/systemd/tpm2-srk-public-key.pem,
           /run/systemd/tpm2-srk-public-key.tpm2b_public
               The SRK public key in PEM and TPM2B_PUBLIC format, written
               during early boot.
    
               Added in version 255.
    
           /var/lib/systemd/tpm2-srk-public-key.pem,
           /var/lib/systemd/tpm2-srk-public-key.tpm2_public
               The SRK public key in PEM and TPM2B_PUBLIC format, written
               during later boot (once /var/ is available).
    
               Added in version 255.
    


* * *
# xfs_info

## NAME



           xfs_info - display XFS filesystem geometry information
    


## SYNOPSIS



           **xfs_info**[ **-t** _mtab_ ] [ _mount-point_ | _block-device_ | _file-image_ ]
           **xfs_info -V**
    


## DESCRIPTION



           **xfs_info** displays geometry information about an existing XFS
           filesystem.  The _mount-point_ argument is the pathname of a
           directory where the filesystem is mounted.  The _block-device_ or
           _file-image_ contain a raw XFS filesystem.  The existing contents of
           the filesystem are undisturbed.
    


## OPTIONS



           **-t** Specifies an alternate mount table file (default is
                  _/proc/mounts_ if it exists, else _/etc/mtab_).  This is used
                  when working with filesystems mounted without writing to
                  _/etc/mtab_ file - refer to mount(8) for further details.
                  This option has no effect with the _block-device_ or _file-_
                  _image_ parameters.
    
           **-V** Prints the version number and exits. The _mount-point_
                  argument is not required with **-V**.
    


## EXAMPLES



           Understanding xfs_info output.
    
           Suppose one has the following "xfs_info /dev/sda" output:
    
             meta-data=/dev/pmem0             isize=512    agcount=8, agsize=5974144 blks
                      =                       sectsz=512   attr=2, projid32bit=1
                      =                       crc=1        finobt=1, sparse=1, rmapbt=1
                      =                       reflink=1
             data     =                       bsize=4096   blocks=47793152, imaxpct=25
                      =                       sunit=32     swidth=128 blks
             naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
             log      =internal log           bsize=4096   blocks=23336, version=2
                      =                       sectsz=512   sunit=0 blks, lazy-count=1
             realtime =none                   extsz=4096   blocks=0, rtextents=0
    
           Here, the data section of the output indicates "bsize=4096",
           meaning the data block size for this filesystem is 4096 bytes.
           This section also shows "sunit=32 swidth=128 blks", which means
           the stripe unit is 32*4096 bytes = 128 kibibytes and the stripe
           width is 128*4096 bytes = 512 kibibytes.  A single stripe of this
           filesystem therefore consists of four stripe units (128 blocks /
           32 blocks per unit).
    


* * *
# ip-maddress

## NAME



           ip-maddress - multicast addresses management
    


## SYNOPSIS



           **ip**[ _OPTIONS_ ] **maddress**{ _COMMAND_ | **help**}
    
           **ip maddress**[ **add** | **del**] _MULTIADDR_ **dev** _NAME_
    
           **ip maddress show**[ **dev** _NAME_ ]
    


## DESCRIPTION



           **maddress** objects are multicast addresses.
    
       **ip maddress show - list multicast addresses**
           **dev** _NAME_ **(default)**
                  the device name.
    
           **ip maddress add - add a multicast address**
    
           **ip maddress delete - delete a multicast address**
    
                  These commands attach/detach a static link-layer multicast
                  address to listen on the interface.  Note that it is
                  impossible to join protocol multicast groups statically.
                  This command only manages link-layer addresses.
    
                  **address** _LLADDRESS_ **(default)**
                         the link-layer multicast address.
    
                  **dev** _NAME_
                         the device to join/leave this multicast address.
    


* * *
# semodule_link

## NAME



           semodule_link - Link SELinux policy module packages together
    


## SYNOPSIS



           **semodule_link [-hVv] [-o outfile] basemodpkg modpkg1 [modpkg2]...**
    


## DESCRIPTION



           semodule_link is a developer tool for manually linking together a
           set of SELinux policy module packages into a single policy module
           package.  This tool is not necessary for normal operation of
           SELinux.  In normal operation, such linking is performed
           internally by libsemanage in response to semodule commands.
           Module packages are created by semodule_package.
    


## OPTIONS



           **-h** show help
    
           **-V** show version
    
           **-v** verbose mode
    
           **-o <output file>**
                  Linked policy module package generated by this tool.
    


* * *
# ip-sr

## NAME



           ip-sr - IPv6 Segment Routing management
    


## SYNOPSIS



           **ip sr**{ _COMMAND_ | **help**}
    
           **ip sr hmac show**
    
           **ip sr hmac set** _KEYID ALGO_
    
           **ip sr tunsrc show**
    
           **ip sr tunsrc set** _ADDRESS_
    


## DESCRIPTION



           The **ip sr** command is used to configure IPv6 Segment Routing (SRv6)
           internal parameters.
    
           Those parameters include the mapping between an HMAC key ID and
           its associated hashing algorithm and secret, and the IPv6 address
           to use as source for encapsulated packets.
    
           The **ip sr hmac set** command prompts for a passphrase that will be
           used as the HMAC secret for the corresponding key ID. A blank
           passphrase removes the mapping.  The currently supported
           algorithms for _ALGO_ are **sha1** and **sha256**.
    
           If the tunnel source is set to the address :: (which is the
           default), then an address of the egress interface will be
           selected. As this operation may hinder performances, it is
           recommended to set a non-default address.
    


## EXAMPLES



       **Configure an HMAC mapping for key ID 42 and hashing algorithm SHA-256**
           # ip sr hmac set 42 sha256
    
       **Set the tunnel source address to 2001:db8::1**
           # ip sr tunsrc set 2001:db8::1
    


* * *
# systemd-integritysetup-generator

## NAME



           systemd-integritysetup-generator - Unit generator for integrity
           protected block devices
    


## SYNOPSIS



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


## DESCRIPTION



           **systemd-integritysetup-generator** is a generator that translates
           /etc/integritytab entries into native systemd units early at boot.
           This will create systemd-integritysetup@.service(8) units as
           necessary.
    
           **systemd-integritysetup-generator** implements systemd.generator(7).
    


* * *
# load_policy

## NAME



           load_policy - load a new SELinux policy into the kernel
    


## SYNOPSIS



           **load_policy**[-qi]
    


## DESCRIPTION



           load_policy loads the installed policy file into the kernel.  The
           existing policy boolean values are automatically preserved across
           policy reloads rather than being reset to the default values in
           the policy file.
    


## OPTIONS



           **-q** suppress warning messages.
    
           **-i** initial policy load. Only use this if this is the first
                  time policy is being loaded since boot (usually called from
                  initramfs).
    


## EXIT STATUS



           **0** Success
    
           **1** Invalid option
    
           **2** Policy load failed
    
           **3** Initial policy load failed and enforcing mode requested
    


* * *
# systemd-veritysetup@.service

## NAME



           systemd-veritysetup@.service, systemd-veritysetup - Disk verity
           protection logic
    


## SYNOPSIS



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


## DESCRIPTION



           systemd-veritysetup@.service is a service responsible for setting
           up verity protection block devices. It should be instantiated for
           each device that requires verity protection.
    
           At early boot and when the system manager configuration is
           reloaded kernel command line configuration for verity protected
           block devices is translated into systemd-veritysetup@.service
           units by systemd-veritysetup-generator(8).
    
           systemd-veritysetup@.service calls **systemd-veritysetup**.
    


## COMMANDS



           The following commands are understood by **systemd-veritysetup** :
    
           **attach** _volume datadevice hashdevice roothash_ [_option_...]
               Create a block device _volume_ using _datadevice_ and _hashdevice_
               as the backing devices.  _roothash_ forms the root of the tree
               of hashes stored on _hashdevice_. See **Kernel dm-verity******[1]
               documentation for details.
    
               Added in version 250.**detach** _volume_
               Detach (destroy) the block device _volume_.
    
               Added in version 250.
    
           **help**
               Print short information about command syntax.
    
               Added in version 250.
    


## NOTES



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


* * *
# fsck.cramfs

## NAME



           fsck.cramfs - fsck compressed ROM file system
    


## SYNOPSIS



           **fsck.cramfs**[options] _file_
    


## DESCRIPTION



           **fsck.cramfs** is used to check the cramfs file system.
    


## OPTIONS



           **-v** , **--verbose**
               Enable verbose messaging.
    
           **-b** , **--blocksize** _blocksize_
               Use this blocksize, defaults to page size. Must be equal to
               what was set at creation time. Only used for **--extract**.
    
           **--extract**[**=**_directory_]
               Test to uncompress the whole file system. Optionally extract
               contents of the _file_ to _directory_.
    
           **-a**
               This option is silently ignored.
    
           **-y**
               This option is silently ignored.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## EXIT STATUS



           **0**
               success
    
           **4**
               file system was left uncorrected
    
           **8**
               operation error, such as unable to allocate memory
    
           **16**
               usage information was printed
    


## AVAILABILITY



           The **fsck.cramfs** 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                 _FSCK.CRAMFS_(8)
    


* * *