tripathysagar/man_text huggingface dataset:
# vipw

## NAME



           vipw, vigr - edit the password, group, shadow-password or
           shadow-group file
    


## SYNOPSIS



    
           **vipw**[_options_]
    
           **vigr**[_options_]
    


## DESCRIPTION



           The **vipw** and **vigr** commands edit the files /etc/passwd and
           /etc/group, respectively. With the **-s** flag, they will edit the
           shadow versions of those files, /etc/shadow and /etc/gshadow,
           respectively. The programs will set the appropriate locks to
           prevent file corruption. When looking for an editor, the programs
           will first try the environment variable **$VISUAL** , then the
           environment variable **$EDITOR** , and finally the default editor,
           **vi**(1).
    


## OPTIONS



           The options which apply to the **vipw** and **vigr** commands are:
    
           **-g** , **--group**
               Edit group database.
    
           **-h** , **--help**
               Display help message and exit.
    
           **-p** , **--passwd**
               Edit passwd database.
    
           **-q** , **--quiet**
               Quiet mode.
    
           **-R** , **--root** _CHROOT_DIR_
               Apply changes in the _CHROOT_DIR_ directory and use the
               configuration files from the _CHROOT_DIR_ directory. Only
               absolute paths are supported.
    
           **-s** , **--shadow**
               Edit shadow or gshadow database.
    


## ENVIRONMENT



           **VISUAL**
               Editor to be used.
    
           **EDITOR**
               Editor to be used if **VISUAL** is not set.
    


## FILES



           /etc/group
               Group account information.
    
           /etc/gshadow
               Secure group account information.
    
           /etc/passwd
               User account information.
    
           /etc/shadow
               Secure user account information.
    


* * *
# systemd-ask-password-console.service

## NAME



           systemd-ask-password-console.service, systemd-ask-password-
           console.path, systemd-ask-password-wall.service, systemd-ask-
           password-wall.path - Query the user for system passwords on the
           console and via wall
    


## SYNOPSIS



               systemd-ask-password-console.service
               systemd-ask-password-console.path
               systemd-ask-password-wall.service
               systemd-ask-password-wall.path
    


## DESCRIPTION



           systemd-ask-password-console.service is a system service that
           queries the user for system passwords (such as hard disk
           encryption keys and SSL certificate passphrases) on the console.
           It is intended to be used during boot to ensure proper handling of
           passwords necessary for boot.  systemd-ask-password-wall.service
           is a system service that informs all logged in users for system
           passwords via wall(1). It is intended to be used after boot to
           ensure that users are properly notified.
    
           See the **developer documentation******[1] for more information about the
           system password logic.
    
           Note that these services invokesystemd-tty-ask-password-agent(1)
           with either the **--watch --console** or **--watch --wall** command line
           parameters.
    


## NOTES



            1. developer documentation
               https://systemd.io/PASSWORD_AGENTS/
    


* * *
# autofs

## NAME



           autofs - Service control for the automounter
    


## SYNOPSIS



           If a SysV init script system is being used:
           **@initdir@/autofs** _start|stop|restart|reload|status_
    
           or if the systemd init system is being used:
           **systemctl** _start|stop|restart|reload|status_ **autofs.service**
    


## DESCRIPTION



           **autofs** controls the operation of the automount(8) daemon(s)
           running on the Linux system. Usually **autofs** is invoked at system
           boot time with the _start_ parameter and at shutdown time with the
           _stop_ parameter. Service control actions can also be manually
           invoked by the system administrator to shut down, restart, reload
           or obtain service status.
    


## OPERATION



           **autofs** will consult a configuration file _@mapdir@/auto.master_ (see
           auto.master(5)) by default to find mount points on the system. For
           each of those mount points automount(8) will mount and start a
           thread, with the appropriate parameters, to manage the mount
           point.
    
           **@initdir@/autofs reload** or **systemctl autofs.service reload** will
           check the current auto.master map against the current automount
           managed mounts. It will terminate those daemons or threads
           (depending on **autofs** version) whose entries have been removed, re-
           read the automount maps for entries that have changed and start
           new daemons or threads for entries that have been added.
    
           If an indirect map is modified then the change will become
           effective immediately.  If an indirect map uses the **browse** option,
           the master map contains direct mount maps or the _auto.master_ map
           is modified then the **autofs** service control reload action must be
           rerun to activate the changes.
    
           However, if a map entry has offsets and is currently in use the
           offset mounts cannot be updated due to potential mount
           dependencies. In this case the map entry offsets will not be
           updated until after the map entry has expired.
    
           **@initdir@/autofs status** or **systemctl status autofs.service** will
           display the status of, automount(8), running or not. When using
           the systemd init system the status output includes somewhat more
           information related to the service status.
    
           systemctl(1) has more functions than the actions mentioned here,
           see systemctl(1) for more information.
    


* * *
# ibcheckwidth

## NAME



           ibcheckwidth - find 1x links in IB subnet
    


## SYNOPSIS



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


## DESCRIPTION



           ibcheckwidth is a script which uses a full topology file that was
           created by ibnetdiscover, scans the network to validate the active
           link widths and reports any 1x links.
    


## OPTIONS



           -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.
    


* * *
# systemd-nsresourced.service

## NAME



           systemd-nsresourced.service, systemd-nsresourced - User Namespace
           Resource Delegation Service
    


## SYNOPSIS



           systemd-nsresourced.service
    
           /usr/lib/systemd/systemd-nsresourced
    


## DESCRIPTION



           **systemd-nsresourced** is a system service that permits transient
           delegation of a UID/GID range to a user namespace (see
           user_namespaces(7)) allocated by a client, via a Varlink IPC API.
    
           Unprivileged clients may allocate a user namespace, and then
           request a UID/GID range to be assigned to it via this service. The
           user namespace may then be used to run containers and other
           sandboxes, and/or apply it to an id-mapped mount.
    
           Allocations of UIDs/GIDs this way are transient: when a user
           namespace goes away, its UID/GID range is returned to the pool of
           available ranges. In order to ensure that clients cannot gain
           persistency in their transient UID/GID range a BPF-LSM based
           policy is enforced that ensures that user namespaces set up this
           way can only write to file systems they allocate themselves or
           that are explicitly allowlisted via **systemd-nsresourced**.
    
           **systemd-nsresourced** automatically ensures that any registered UID
           ranges show up in the system's NSS database via the **User/Group**
           **Record Lookup API via Varlink******[1].
    
           Currently, only UID/GID ranges consisting of either exactly 1 or
           exactly 65536 UIDs/GIDs can be registered with this service.
           Moreover, UIDs and GIDs are always allocated together, and
           symmetrically.
    
           The service provides API calls to allowlist mounts (referenced via
           their mount file descriptors as per Linux**fsmount()** API), to pass
           ownership of a cgroup subtree to the user namespace and to
           delegate a virtual Ethernet device pair to the user namespace.
           When used in combination this is sufficient to implement fully
           unprivileged container environments, as implemented by
           systemd-nspawn(1), fully unprivileged _RootImage=_ (see
           systemd.exec(5)) or fully unprivileged disk image tools such as
           systemd-dissect(1).
    
           This service provides one **Varlink******[2] service:**io.systemd.NamespaceResource** allows registering user namespaces,
           and assign mounts, cgroups and network interfaces to it.
    


## NOTES



            1. User/Group Record Lookup API via Varlink
               https://systemd.io/USER_GROUP_API
    
            2. Varlink
               https://varlink.org/
    


* * *
# genl

## NAME



           genl - generic netlink utility frontend
    


## SYNOPSIS



           **genl**[ **-s**[**tatistics**] ] [ **-d**[**etails**] ] [ **-r**[**aw**] ] **OBJECT**
    
           **genl**{ **-V**[**ersion**] | **-h**[**elp**] }
    
           _OBJECT_ := { **ctrl** _CTRL_OPTS_ }
    
           _CTRL_OPTS_ := { **help** | **list** | **monitor** | **get** _PARMS_ }
    
           _PARMS_ := { **name** _NAME_ | **id** _ID_ }
    


## DESCRIPTION



           The **genl** utility provides a simple frontend to the generic netlink
           library. Although it's designed to support multiple _OBJECT_ s, for
           now only the **ctrl** object is available, which is used to query the
           generic netlink controller.
    
       **ctrl**
           The generic netlink controller can be queried in various ways:
    
           **help** This command just prints a help text for the **ctrl** object.
    
           **list** Show the registered netlink users.
    
           **monitor**
                  Listen for generic netlink notifications.
    
           **get** Query the controller for a given user, identified either by
                  **name** or **id**.
    


## OPTIONS



           genl supports the following options.
    
           **-h, -help**
                  Show summary of options.
    
           **-V, -Version**
                  Show version of program.
    
           **-s, -stats, -statistics**
                  Show object statistics.
    
           **-d, -details**
                  Show object details.
    
           **-r, -raw**
                  Dump raw output only.
    


* * *
# semanage-export

## NAME



           **semanage-export - SELinux Policy Management import tool**
    


## SYNOPSIS



           **semanage export [-h] [-S STORE] [-f OUTPUT_FILE]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage import** and **export** can be used to extract the
           SELinux modifications from one machine and apply them to another.
           Please note that this will remove all current semanage
           customizations on the second machine as the command list generated
           using **semanage export** start with _< command> -D_ for all semanage
           sub-commands. You can put a whole group of semanage commands
           within a file and apply them to a machine in a single transaction.
    


## OPTIONS



           _-h, --help_
                  show this help message and exit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-f OUTPUT_FILE, --output_file OUTPUT_FILE_
                  Output file
    


## EXAMPLE



           Import semanage modifications from another machine
           # semanage export -f semanage.mods
           # scp semanage.mod remotemachine:
           # ssh remotemachine
           # semanage import -f semanage.mods
    


* * *
# lvmsadc

## NAME



           lvmsadc — LVM system activity data collector
    


## SYNOPSIS



           **lvmsadc**
    


## DESCRIPTION



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


* * *
# rpm-misc

## NAME



           rpm - lesser need options for rpm(8)
    


## OPTIONS



           **--predefine='**_MACRO EXPR_**'**
                  Defines _MACRO_ with value _EXPR_ before loading macro files.
    


## Switching off features



           **--color [never|auto|always]**
                  Use terminal colors for highlighting error and debug
                  message.  Default is turning colors on for ttys only
                  (**auto**).
    
           **--nocontexts** Disable the SELinux plugin if available.  This stops
           the plugin from setting SELinux contexts for files and scriptlets.
    
           **--noglob**
                  Do not glob arguments when installing package files.
    
           **--nocaps**
                  Don't verify capabilities of files.
    
           **--excludeconfigs, --noconfigs**
                  Do not install configuration files.
    
           **--nohdrchk**
                  Don't verify database header(s) when retrieved.
    


## Debugging



           **-d, --debug**
                  Print debugging information.
    
           **--deploops**
                  Print dependency loops as warning.
    
           **--fsmdebug**
                  Print debuging information of payload handling code.
    
           **--rpmfcdebug**
                  Print debug information about files packaged.
    
           **--rpmiodebug**
                  Print debug information about file IO.
    
           **--stats**
                  Print runtime statistics of often used functions.
    


## Obsolete Options



           **-K, --checksig**
                  See and use rpmkeys(8).
    
           **--nodocs**
                  Do not install documentation.  Use **--excludedocs** instead.
    
           **--promoteepoch**
                  Enable obsolete epoch handling used in rpm 3.x time frame.
    
           **--prtpkts**
                  OBSOLETE!  Used to print the packages containing and
                  representing the pgp keys for debugging purposes.
    


* * *
# systemd-sysv-generator

## NAME



           systemd-sysv-generator - Unit generator for SysV init scripts
    


## SYNOPSIS



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


## DESCRIPTION



           _Note: this component is deprecated and scheduled for removal._
           _Please replace remaining SysV init scripts with native unit files._
    
           systemd-sysv-generator is a generator that creates wrapper
           .service units for **System V init******[1] scripts in /etc/init.d/* at
           boot and when configuration of the system manager is reloaded.
           This allowssystemd(1) to support them similarly to native units.
    
           **LSB headers******[2] in SysV init scripts are interpreted, and the
           ordering specified in the header is turned into dependencies
           between the generated unit and other units. The LSB facilities
           "$remote_fs", "$network", "$named", "$portmap", "$time" are
           supported and will be turned into dependencies on specific native
           systemd targets. Seesystemd.special(7) for more details.
    
           Note that compatibility is quite comprehensive but not 100%, for
           more details see **Compatibility with SysV******[3].**systemd** does not support SysV scripts as part of early boot, so
           all wrapper units are ordered after basic.target.
    
           systemd-sysv-generator implements systemd.generator(7).
    


## NOTES



            1. System V init
               https://savannah.nongnu.org/projects/sysvinit
    
            2. LSB headers
               http://refspecs.linuxbase.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
    
            3. Compatibility with SysV
               https://systemd.io/INCOMPATIBILITIES
    


* * *
# mail.maildir

## NAME



           **mail.maildir** — store mail in a maildir
    


## SYNOPSIS



           **mail.maildir**[**-j**] [_pathname_]
    


## DESCRIPTION



           **mail.maildir** reads the standard input up to an end-of-file and
           adds it to the mail directory located in _pathname_ or to the mail
           directory _Maildir_ located in the user's home directory.
    
           The options are as follows:
    
           **-j** Scan the message for an X-Spam header and move to the Junk
                   folder if the result is positive.
    


## EXIT STATUS



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


* * *
# systemd-mountfsd.service

## NAME



           systemd-mountfsd.service, systemd-mountfsd - Disk Image File
           System Mount Service
    


## SYNOPSIS



           systemd-mountfsd.service
    
           /usr/lib/systemd/systemd-mountfsd
    


## DESCRIPTION



           **systemd-mountfsd** is a system service that dissects disk images,
           and returns mount file descriptors for the file systems contained
           therein to clients, via a Varlink IPC API.
    
           The disk images provided must contain a raw file system image or
           must follow the **Discoverable Partitions Specification******[1]. Before
           mounting any file systems authenticity of the disk image is
           established in one or a combination of the following ways:
    
            1. If the disk image is located in a regular file in one of the
               directories /var/lib/machines/, /var/lib/portables/,
               /var/lib/extensions/, /var/lib/confexts/ or their counterparts
               in the /etc/, /run/, /usr/lib/ it is assumed to be trusted.
    
            2. If the disk image contains a Verity enabled disk image, along
               with a signature partition with a key in the kernel keyring or
               in /etc/verity.d/ (and related directories) the disk image is
               considered trusted.
    
           This service provides one**Varlink******[2] service:**io.systemd.MountFileSystem** which accepts a file descriptor to a
           regular file or block device, and returns a number of file
           descriptors referring to an **fsmount()** file descriptor the client
           may then attach to a path of their choice.
    
           The returned mounts are automatically allowlisted in the
           per-user-namespace allowlist maintained by
           systemd-nsresourced.service(8).
    
           The file systems are automatically fsck(8)'ed before mounting.
    


## NOTES



            1. Discoverable Partitions Specification
               https://uapi-group.org/specifications/specs/discoverable_partitions_specification/
    
            2. Varlink
               https://varlink.org/
    


* * *
# pam_time

## NAME



           pam_time - PAM module for time control access
    


## SYNOPSIS



    
           **pam_time.so**[conffile=conf-file] [debug] [noaudit]
    


## DESCRIPTION



           The pam_time PAM module does not authenticate the user, but
           instead it restricts access to a system and or specific
           applications at various times of the day and on specific days or
           over various terminal lines. This module can be configured to deny
           access to (individual) users based on their name, the time of day,
           the day of week, the service they are applying for and their
           terminal from which they are making their request.
    
           By default rules for time/port access are taken from config file
           /etc/security/time.conf. An alternative file can be specified with
           the _conffile_ option.
    
           If Linux PAM is compiled with audit support the module will report
           when it denies access.
    


## OPTIONS



           **conffile=/path/to/time.conf**
               Indicate an alternative time.conf style configuration file to
               override the default.
    
           **debug**
               Some debug information is printed with syslog(3).
    
           **noaudit**
               Do not report logins at disallowed time to the audit
               subsystem.
    


## MODULE TYPES PROVIDED



           Only the **account** type is provided.
    


## RETURN VALUES



           PAM_SUCCESS
               Access was granted.
    
           PAM_ABORT
               Not all relevant data could be gotten.
    
           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_PERM_DENIED
               Access was not granted.
    
           PAM_USER_UNKNOWN
               The user is not known to the system.
    


## FILES



           /etc/security/time.conf
               Default configuration file
    


## EXAMPLES



               #%PAM-1.0
               #
               # apply pam_time accounting to login requests
               #
               login  account  required  pam_time.so
    


* * *
# sepolicy-gui

## NAME



           sepolicy-gui - Graphical User Interface for SELinux policy.
    


## SYNOPSIS



           Common options
    
           **sepolicy gui [-h ] [ -d DOMAIN ]**
    


## DESCRIPTION



           Use **sepolicy gui** to run the graphical user interface, which allows
           you to explore how SELinux confines different process domains.
    


## OPTIONS



           _-h, --help_
                  Display help message
    
           _-d, --domain_
                  Initialize gui to the selected domain
    


* * *
# arping

## NAME



           arping - send ARP REQUEST to a neighbour host
    


## SYNOPSIS



    
           **arping**[**-AbDfhqUV**] [**-c** _count_] [**-w** _deadline_] [**-i** _interval_]
                  [**-s** _source_] [**-I** _interface_] {destination}
    


## DESCRIPTION



           Ping _destination_ on device _interface_ by ARP packets, using source
           address _source_.
    
           arping supports IPv4 addresses only. For IPv6, see **ndisc6**(8).
    


## OPTIONS



           **-A**
               The same as **-U** , but ARP REPLY packets used instead of ARP
               REQUEST.
    
           **-b**
               Send only MAC level broadcasts. Normally **arping** starts from
               sending broadcast, and switch to unicast after reply received.
    
           **-c** _count_
               Stop after sending _count_ ARP REQUEST packets. With _deadline_
               option, instead wait for _count_ ARP REPLY packets, or until the
               timeout expires.
    
           **-D**
               Duplicate address detection mode (DAD). See RFC2131, 4.4.1.
               Returns 0, if DAD succeeded i.e. no replies are received.
    
           **-f**
               Finish after the first reply confirming that target is alive.
    
           **-I** _interface_
               Name of network device where to send ARP REQUEST packets.
    
           **-h**
               Print help page and exit.
    
           **-q**
               Quiet output. Nothing is displayed.
    
           **-s** _source_
               IP source address to use in ARP packets. If this option is
               absent, source address is:
    
                   • In DAD mode (with option **-D**) set to 0.0.0.0.
    
                   • In Unsolicited ARP mode (with options **-U** or **-A**) set to
                   _destination_.
    
                   • Otherwise, it is calculated from routing tables.
    
           **-U**
               Unsolicited ARP mode to update neighbours' ARP caches. No
               replies are expected.
    
           **-V**
               Print version of the program and exit.
    
           **-w** _deadline_
               Specify a timeout, in seconds, before **arping** exits regardless
               of how many packets have been sent or received. If any replies
               are received, exit with status 0, otherwise status 1. When
               combined with the _count_ option, exit with status 0 if _count_
               replies are received before the deadline expiration, otherwise
               status 1.
    
           **-i** _interval_
               Specify an interval, in seconds, between packets.
    


## SECURITY



           **arping** requires CAP_NET_RAW capability to be executed. It is not
           recommended to be used as set-uid root, because it allows user to
           modify ARP caches of neighbour hosts.
    


## AVAILABILITY



           **arping** is part of _iputils_ package.
    


* * *
# semanage-import

## NAME



           **semanage-import - SELinux Policy Management import tool**
    


## SYNOPSIS



           **semanage import [-h] [-N] [-S STORE] [-f INPUT_FILE]**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage import** and **export** can be used to extract the
           SELinux modifications from one machine and apply them to another.
           Please note that this will remove all current semanage
           customizations on the second machine as the command list generated
           using **semanage export** start with _< command> -D_ for all semanage
           sub-commands. You can put a whole group of semanage commands
           within a file and apply them to a machine in a single transaction.
    


## OPTIONS



           _-h, --help_
                  show this help message and exit
    
           _-N, --noreload_
                  Do not reload policy after commit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-f INPUT_FILE, --input_file INPUT_FILE_
                  Input file
    


## EXAMPLE



           Import semanage modifications from another machine
           # semanage import -f semanage.mods
    


* * *
# ibclearerrors

## NAME



           ibclearerrors - clear error counters in IB subnet
    


## SYNOPSIS



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


## DESCRIPTION



           ibclearerrors is a script which clears the PMA error counters in
           PortCounters by either walking the IB subnet topology or using an
           already saved topology file.
    


## OPTIONS



           -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.
    


* * *
# lpinfo

## NAME



           lpinfo - show available devices or drivers (deprecated)
    


## SYNOPSIS



           **lpinfo**[ **-h** _server_[**:**_port_] ] [ **-E**] [ **-l**] [ **--device-id** _device-id-_
           _string_ ] [ **--exclude-schemes** _scheme-list_ ] [ **--include-schemes**
           _scheme-list_ ] [ **--language** _locale_ ] [ **--make-and-model** _name_ ] [
           **--product** _name_ ] **-m**
           **lpinfo**[ **-h** _server_[**:**_port_] ] [ **-E**] [ **-l**] [ **--exclude-schemes**
           _scheme-list_ ] [ **--include-schemes** _scheme-list_ ] [ **--timeout**
           _seconds_ ] **-v**
    


## DESCRIPTION



           **lpinfo** lists the available devices or drivers known to the CUPS
           server.  The first form (_-m_) lists the available drivers, while
           the second form (_-v_) lists the available devices.
    


## OPTIONS



           **lpinfo** accepts the following options:
    
           **-E** Forces encryption when connecting to the server.
    
           **-h** _server_[**:**_port_]
                Selects an alternate server.  Note: This option must occur
                before all others.
    
           **-l** Shows a "long" listing of devices or drivers.
    
           **--device-id** _device-id-string_
                Specifies the IEEE-1284 device ID to match when listing
                drivers with the _-m_ option.
    
           **--exclude-schemes** _scheme-list_
                Specifies a comma-delimited list of device or PPD schemes
                that should be excluded from the results.  Static PPD files
                use the "file" scheme.
    
           **--include-schemes** _scheme-list_
                Specifies a comma-delimited list of device or PPD schemes
                that should be included in the results.  Static PPD files use
                the "file" scheme.
    
           **--language** _locale_
                Specifies the language to match when listing drivers with the
                _-m_ option.
    
           **--make-and-model** _name_
                Specifies the make and model to match when listing drivers
                with the _-m_ option.
    
           **--product** _name_
                Specifies the product to match when listing drivers with the
                _-m_ option.
    
           **--timeout** _seconds_
                Specifies the timeout when listing devices with the _-v_
                option.
    


## CONFORMING TO



           The _lpinfo_ command is unique to CUPS.
    


## EXAMPLES



           List all devices:
    
               lpinfo -v
    
           List all drivers:
    
               lpinfo -m
    
           List drivers matching "HP LaserJet":
    
               lpinfo --make-and-model "HP LaserJet" -m
    


## NOTES



           CUPS printer drivers and backends are deprecated and will no
           longer be supported in a future feature release of CUPS.  Printers
           that do not support IPP can be supported using applications such
           as ippeveprinter(1).
    


* * *
# xfs_bmap

## NAME



           xfs_bmap - print block mapping for an XFS file
    


## SYNOPSIS



           **xfs_bmap**[ **-adelpv**] [ **-n** _num_extents_ ] _file_
           **xfs_bmap -V**
    


## DESCRIPTION



           **xfs_bmap** prints the map of disk blocks used by files in an XFS
           filesystem.  The map lists each _extent_ used by the file, as well
           as regions in the file that do not have any corresponding blocks
           (holes).  Each line of the listings takes the following form:
    
                  _extent_ : [_startoffset_.._endoffset_]: _startblock_.._endblock_
    
           Holes are marked by replacing the _startblock_.._endblock_ with _hole_.
           All the file offsets and disk blocks are in units of 512-byte
           blocks, no matter what the filesystem's block size is.
    


## OPTIONS



           **-a** If this option is specified, information about the file's
                  attribute fork is printed instead of the default data fork.
    
           **-e** If this option is used, **xfs_bmap** obtains all delayed
                  allocation extents, and does not flush dirty pages to disk
                  before querying extent data. With the **-v** option, the _flags_
                  column will show which extents have not yet been allocated.
    
           **-l** If this option is used, then
    
                       <_nblocks_ >  blocks
    
                  will be appended to each line.  _nblocks_ is the length of
                  the extent described on the line in units of 512-byte
                  blocks.
    
                  This flag has no effect if the **-v** option is used.
    
           **-n** _num_extents_
                  If this option is given, **xfs_bmap** will display at most
                  _num_extents_ extents. In the absence of **-n** , **xfs_bmap** will
                  display all extents in the file.
    
           **-p** If this option is used, **xfs_bmap** obtains all unwritten
                  (preallocated) extents that do not contain written data.
                  With the **-v** option, the _flags_ column will show which
                  extents are preallocated/unwritten.
    
           **-v** Shows verbose information. When this flag is specified,
                  additional AG specific information is appended to each line
                  in the following form:
    
                       _agno_ (_startagoffset_.._endagoffset_) _nblocks flags_
    
                  A second **-v** option will print out the _flags_ legend.
    
           **-V** Prints the version number and exits.
    


* * *
# lvmdbusd

## NAME



           lvmdbusd — LVM D-Bus daemon
    


## SYNOPSIS



           **lvmdbusd**[**--debug**] [**--udev**]
    


## DESCRIPTION



           lvmdbusd  is  a  service which provides a D-Bus API to the logical
           volume manager (LVM).  Run lvmdbusd(8) as root.
    


## OPTIONS



           **--debug** Enable debug statements
    
           **--udev** Use udev events to trigger updates
    


* * *
# systemd-loop@.service

## NAME



           systemd-loop@.service - Attach a loopback block device
    


## SYNOPSIS



           systemd-loop@_path_.service
    


## DESCRIPTION



           systemd-loop@.service is a template service that may be used to
           automatically attach a loopback block device at boot (or later).
           Its instance string may reference an (escaped) file system path
           pointing to a disk image to attach as loopback block device. Use
           systemd-escape(1)'s **--path** to properly escape a file system path.
    
           This unit invokes **systemd-dissect --attach --quiet --loop-ref-auto**
           on the specified files, see systemd-dissect(1) for details.
    


* * *
# semanage-dontaudit

## NAME



           **semanage-dontaudit - SELinux Policy Management dontaudit tool**
    


## SYNOPSIS



           **semanage dontaudit [-h] [-S STORE] [-N] {on,off}**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage dontaudit** toggles whether or not dontaudit
           rules will be in the policy. Policy writers use dontaudit rules to
           cause confined applications to use alternative paths. Dontaudit
           rules are denied but not reported in the logs. Sometimes dontaudit
           rules can cause bugs in applications but policy writers will not
           realize it since the AVC is not audited. Turn off dontaudit rules
           with this command to see if the kernel is blocking an access.
    


## OPTIONS



           _-h, --help_
                  Show this help message and exit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    
           _-N, --noreload_
                  Do not reload the policy after commit
    


## EXAMPLE



           Turn off dontaudit rules
           # semanage dontaudit off
    


* * *
# blkiomon

## NAME



           blkiomon - monitor block device I/O based o blktrace data
    


## SYNOPSIS



           **blkiomon -I** _interval_ [ -h _file_ ] [ -b _file_ ] [ -d _file_ ] [ -D _file_
           ] [ -Q _path_name_ -q _msg_queue_id_ -m _msg_id_ ] [ -V ]
    


## DESCRIPTION



           blkiomon is a block device I/O monitor. It periodically generates
           per-device request size and request latency statistics from
           blktrace data. It provides histograms as well as data that can be
           used to calculate min, max, average and variance. For this
           purpose, it consumes D and C traces read from stdin.  Note, that
           this doesn't work for logical volumes, as high-level drivers don't
           see the completion of the events (C).
    
           There are options for binary output and human-readable output to
           files and stdout. Output to a message queue is supported as well.
    
           There is no need to use blkparse with blkiomon. blkiomon is
           capable of consuming binary output written to stdout by blktrace.
    


## OPTIONS



           -I _interval_
           --interval=_interval_
                  Set sample interval
    
           -h _file_
           --human-readable=_file_
                  Human-readable output file. Use '-' for stdout.
    
           -b _file_
           --binary=_file_
                  Binary output file. Use '-' for stdout.
    
           -d _file_
           --dump-lldd=_file_
                  Output file for data emitted by low level device driver.
    
           -D _file_
           --debug=_file_
                  Output file for debugging data. Use '-' for stdout.
    
           -Q _path_name_
           --msg-queue=_path_name_
                  Sets _path_name_ as path name for existing message queue to
                  be used for binary output.
    
           -q _msg_queue_id_
           --msg-queue-id=_msg_queue_id_
                  Sets _msg_queue_id_ as ID for an existing message queue to be
                  used for binary output.
    
           -m _msg_id_
           --msg-id=_msg_id_
                  Sets _msg_id_ as message identifier to be used for binary
                  output messages written to an existing message queue.
    
           -V
           --version
                  Print program version.
    


## EXAMPLES



           To get I/O statistics for /dev/sdw every 10 seconds for a period
           of one hour, use the following command:
    
               % blktrace /dev/sdw -a issue -a complete -w 3600 -o - |
           blkiomon -I 10 -h -
    


* * *
# systemd-user-sessions.service

## NAME



           systemd-user-sessions.service, systemd-user-sessions - Permit user
           logins after boot, prohibit user logins at shutdown
    


## SYNOPSIS



           systemd-user-sessions.service
    
           /usr/lib/systemd/systemd-user-sessions
    


## DESCRIPTION



           systemd-user-sessions.service is a service that controls user
           logins through pam_nologin(8). After basic system initialization
           is complete, it removes /run/nologin, thus permitting logins.
           Before system shutdown, it creates /run/nologin, thus prohibiting
           further logins.
    


* * *
# iptables-apply

## NAME



           iptables-apply — a safer way to update iptables remotely
    


## SYNOPSIS



           **iptables-apply**[-**hV**] [**-t** _timeout_] [**-w** _savefile_] {[_rulesfile]|-c_
           _[runcmd]}_
    


## DESCRIPTION



           iptables-apply will try to apply a new rulesfile (as output by
           iptables-save, read by iptables-restore) or run a command to
           configure iptables and then prompt the user whether the changes
           are okay. If the new iptables rules cut the existing connection,
           the user will not be able to answer affirmatively. In this case,
           the script rolls back to the previous working iptables rules after
           the timeout expires.
    
           Successfully applied rules can also be written to savefile and
           later used to roll back to this state. This can be used to
           implement a store last good configuration mechanism when
           experimenting with an iptables setup script: iptables-apply -w
           /etc/network/iptables.up.rules -c /etc/network/iptables.up.run
    
           When called as ip6tables-apply, the script will use
           ip6tables-save/-restore and IPv6 default values instead. Default
           value for rulesfile is '/etc/network/iptables.up.rules'.
    


## OPTIONS



           **-t** _seconds_ , **--timeout** _seconds_
                  Sets the timeout in seconds after which the script will
                  roll back to the previous ruleset (default: 10).
    
           **-w** _savefile_ , **--write** _savefile_
                  Specify the savefile where successfully applied rules will
                  be written to (default if empty string is given:
                  /etc/network/iptables.up.rules).
    
           **-c** _runcmd_ , **--command** _runcmd_
                  Run command runcmd to configure iptables instead of
                  applying a rulesfile (default:
                  /etc/network/iptables.up.run).
    
           **-h** , **--help**
                  Display usage information.
    
           **-V** , **--version**
                  Display version information.
    


## LEGALESE



           Original iptables-apply - Copyright 2006 Martin F. Krafft
           <madduck@madduck.net>.  Version 1.1 - Copyright 2010 GW
           <gw.2010@tnode.com or http://gw.tnode.com/>.
    
           This manual page was written by Martin F. Krafft
           <madduck@madduck.net> and extended by GW <gw.2010@tnode.com or
           http://gw.tnode.com/>.
    
           Permission is granted to copy, distribute and/or modify this
           document under the terms of the Artistic License 2.0.
    


* * *
# systemd-boot-check-no-failures.service

## NAME



           systemd-boot-check-no-failures.service, systemd-boot-check-no-
           failures - verify that the system booted up cleanly
    


## SYNOPSIS



           systemd-boot-check-no-failures.service
    
           /usr/lib/systemd/system-boot-check-no-failures
    


## DESCRIPTION



           systemd-boot-check-no-failures.service is a system service that
           checks whether the system booted up successfully. This service
           implements a very minimal test only: whether there are any failed
           units on the system. This service is disabled by default. When
           enabled, it is ordered before boot-complete.target, thus ensuring
           the target cannot be reached when the system booted up with failed
           services.
    
           Note that due the simple nature of this check this service is
           probably not suitable for deployment in most scenarios. It is
           primarily useful only as example for developing more fine-grained
           checks to order before boot-complete.target.
    


* * *
# systemd-system-update-generator

## NAME



           systemd-system-update-generator - Generator for redirecting boot
           to offline update mode
    


## SYNOPSIS



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


## DESCRIPTION



           systemd-system-update-generator is a generator that automatically
           redirects the boot process to system-update.target, if
           /system-update or /etc/system-update exists. This is required to
           implement the logic explained in the systemd.offline-updates(7).
    
           systemd-system-update-generator implements systemd.generator(7).
    


* * *
# sepolicy-booleans

## NAME



           sepolicy-booleans - Query SELinux Policy to see description of
           booleans
    


## SYNOPSIS



           **sepolicy booleans [-h] [ -a | -b booleanname ... ]**
    


## DESCRIPTION



           **sepolicy booleans** will show all booleans and their descriptions,
           or you can choose individual booleans to display.  Please make
           sure that selinux-policy-devel is present in your system since it
           contains boolean descriptions extracted from the policy source
           code. Otherwise **sepolicy booleans** will only show descriptions
           generated based on boolean names.
    


## OPTIONS



           _-h, --help_
                  Display help message
    
           _-a, --all_
                  Display all boolean descriptions
    
           _-b, --boolean_
                  boolean to get description
    


## EXAMPLE



           List descriptions of samba_create_home_dirs and samba_enable_home_dirs booleans
           # sepolicy booleans -b samba_create_home_dirs samba_enable_home_dirs
    


* * *
# systemd-hibernate-resume-generator

## NAME



           systemd-hibernate-resume-generator - Unit generator for resume=
           kernel parameter
    


## SYNOPSIS



           /usr/lib/systemd/system-generators/systemd-hibernate-resume-generator
    


## DESCRIPTION



           **systemd-hibernate-resume-generator** is a generator that initiates
           the procedure to resume the system from hibernation. When **resume=**
           kernel command line option or _HibernateLocation_ EFI variable is
           detected, it enables the systemd-hibernate-resume.service(8) unit,
           which will instruct the kernel to resume the system from the
           hibernation image.
    


## KERNEL COMMAND LINE



           systemd-hibernate-resume-generator understands the following
           kernel command line parameters:
    
           _resume=_
               Takes a path to the resume device. Both persistent block
               device paths like /dev/disk/by-foo/bar and fstab(5)-style
               specifiers like "FOO=bar" are supported.
    
               Added in version 217.
    
           _resume_offset=_
               Takes the page offset of the swap space from the resume
               device. Defaults to "0".
    
               Added in version 254.
    
           _resumeflags=_
               Takes the resume device mount options to use. Defaults
               _rootflags=_ if not specified.
    
               Added in version 243.
    
           _noresume_
               Do not try to resume from hibernation. If this parameter is
               present, _resume=_ is ignored.
    
               Added in version 240.
    


* * *
# rpm2cpio

## NAME



           rpm2cpio - Extract cpio archive from RPM Package Manager (RPM)
           package.
    


## SYNOPSIS



           **rpm2cpio**[filename]
    


## DESCRIPTION



           **rpm2cpio** converts the .rpm file specified as a single argument to
           a cpio archive on standard out.  If a '-' argument is given, an
           rpm stream is read from standard in.
    
           **Note:** the CPIO format cannot host individual files over 4GB in
           size, and so this tool is considered obsolete.  Use **rpm2archive**
           instead.
    
           **rpm2cpio glint-1.0-1.i386.rpm | cpio -dium**
           **cat glint-1.0-1.i386.rpm | rpm2cpio - | cpio -tv**
    


* * *