tripathysagar/man_text huggingface dataset:
# xfs_estimate

## NAME



           xfs_estimate - estimate the space that an XFS filesystem will take
    


## SYNOPSIS



           **xfs_estimate**[ **-h**] [ **-b** blocksize ] [ **-i** logsize ]
                        [ **-e** logsize ] [ **-v**] directory ...
           **xfs_estimate -V**
    


## DESCRIPTION



           For each _directory_ argument, _xfs_estimate_ estimates the space that
           directory would take if it were copied to an XFS filesystem.
           _xfs_estimate_ does not cross mount points.  The following
           definitions are used:
                  KB = *1024
                  MB = *1024*1024
                  GB = *1024*1024*1024
    
           The _xfs_estimate_ options are:
    
           **-b** _blocksize_
                  Use _blocksize_ instead of the default blocksize of 4096
                  bytes.  The modifier **k** can be used after the number to
                  indicate multiplication by 1024.  For example,
    
                       **xfs_estimate -b 64k /**
    
                  requests an estimate of the space required by the directory
                  / on an XFS filesystem using a blocksize of 64K (65536)
                  bytes.
    
           **-v** Display more information, formatted.
    
           **-h** Display usage message.
    
           **-i, -e** _logsize_
                  Use _logsize_ instead of the default log size of 1000 blocks.
                  **-i** refers to an internal log, while **-e** refers to an
                  external log.  The modifiers **k** or **m** can be used after the
                  number to indicate multiplication by 1024 or 1048576,
                  respectively.
    
                  For example,
    
                       **xfs_estimate -i 1m /**
    
                  requests an estimate of the space required by the directory
                  / on an XFS filesystem using an internal log of 1 megabyte.
    
           **-V** Print the version number and exits.
    


## EXAMPLES



           % **xfs_estimate -e 10m /var/tmp**
           /var/tmp will take about 4.2 megabytes
                   with the external log using 2560 blocks or about 10.0 megabytes
    
           % **xfs_estimate -v -e 10m /var/tmp**
           directory                     bsize   blocks    megabytes    logsize
           /var/tmp                       4096      792        4.0MB   10485760
    
           % **xfs_estimate -v /var/tmp**
           directory                     bsize   blocks    megabytes    logsize
           /var/tmp                       4096     3352       14.0MB   10485760
    
           % **xfs_estimate /var/tmp**
           /var/tmp will take about 14.0 megabytes
    


* * *
# pktsetup

## NAME



           pktsetup - set up and tear down packet device associations
    


## SYNOPSIS



           **pktsetup** _packet_device block_device_
           **pktsetup -d** _packet_device_
           **pktsetup -s**
    


## DESCRIPTION



           **Pktsetup** is used to associate packet devices with CD or DVD block
           devices, so that  the  packet  device  can  then  be  mounted  and
           potentially  used as a read/write filesystem. This requires kernel
           support for the packet device, and the UDF filesystem.
    
           See: HOWTO.udf (in the udftools documents directory)
    


## EXIT STATUS



           **Pktsetup** returns 0 on success, nonzero on failure.
    


## OPTIONS



           **-d** _packet-device_
                  Delete the association between the specified _packet-device_
                  and its block device.
    
           **-s** Show the current device mapping, one device per line, in
                  the format
                   _name_ : _pktdevid_ -> _blkdevid_
                  (e.g. "0 : 253:0 -> 22:0")
    


## EXAMPLE



           The following commands provide an example of using the packet
           device.
    
                  cdrwtool -d /dev/sr0 -q
                  pktsetup 0 /dev/sr0
    
                  mount -t udf /dev/pktcdvd0 /mnt
                   ...
                  umount /dev/pktcdvd0
                  pktsetup -d 0
    


## FILES



           /dev/pktcdvd0,/dev/pktcdvd1,...  CD/DVD packet devices
    


## AVAILABILITY



           **pktsetup** is part of the udftools package and is available from
           https://github.com/pali/udftools/.
    


* * *
# quota_nld

## NAME



           quota_nld - quota netlink message daemon
    


## SYNOPSIS



           **quota_nld**[[ **-D** | **-C**][ **-F**][ **-b**]]
    


## DESCRIPTION



           **quota_nld** listens on netlink socket and processes received quota
           warnings. By default **quota_nld** forwards warning messages to both
           the system's DBUS (so that the desktop manager can display a
           dialog) and the last-accessed terminal of the user to whom each
           warning is directed. Either of these destinations can be disabled
           with the **-D** and **-C** options, respectively.
    
           In the case of the user's terminal, quota messages about falling
           below the hard and soft limits are not sent unless the **-b** option
           is specified. In the case of the DBUS, all quota messages are
           sent.
    
           Note, that you have to enable the kernel support for sending quota
           messages over netlink (in Filesystems->Quota menu).
    


## OPTIONS



           **-V, --version**
                  Show version of quota tools and exit.
    
           **-h, --help**
                  Show a usage message and exit.
    
           **-D, --no-dbus**
                  Do not forward quota warnings to DBUS.
    
           **-C, --no-console**
                  Do not print quota warnings to the user's last-accessed
                  terminal.
    
           **-b, --print-below**
                  If quota warnings are printed to users' terminals, include
                  messages about falling below their hard and soft limits.
    
           **-F, --foreground**
                  Run daemon in foreground (may be useful for debugging
                  purposes).
    


* * *
# lsusb

## NAME



           lsusb - list USB devices
    


## SYNOPSIS



           **lsusb**[ _options_ ]
    


## DESCRIPTION



           **lsusb** is a utility for displaying information about USB buses in
           the system and the devices connected to them. It uses udev's
           hardware database to associate a full human-readable name to the
           vendor ID and the product ID.
    


## OPTIONS



           **-v** , **--verbose**
                  Tells _lsusb_ to be verbose and display detailed information
                  about the devices shown.  This includes configuration
                  descriptors for the device's current speed.  Class
                  descriptors will be shown, when available, for USB device
                  classes including hub, audio, HID, communications, and
                  chipcard. Can be used with the **-t** option.
    
           **-s**[[_bus_]**:**][_devnum_]
                  Show only devices in specified _bus_ and/or _devnum_.  Both IDs
                  are given in decimal and may be omitted.
    
           **-d**[_vendor_]**:**[_product_]
                  Show only devices with the specified vendor and product ID.
                  Both IDs are given in hexadecimal.
    
           **-D** _device_
                  Do not scan the /dev/bus/usb directory, instead display
                  only information about the device whose device file is
                  given.  The device file should be something like
                  /dev/bus/usb/001/001.  This option displays detailed
                  information like the **-v** option; you must be root to do
                  this.
    
           **-t** , **--tree**
                  Tells _lsusb_ to dump the physical USB device hierarchy as a
                  tree. Verbosity can be increased twice with the **-v** option.
    
           **-V** , **--version**
                  Print version information on standard output, then exit
                  successfully.
    


## RETURN VALUE



           If the specified device is not found, a non-zero exit code is
           returned.
    


* * *
# pam_timestamp_check

## NAME



           pam_timestamp_check - Check to see if the default timestamp is
           valid
    


## SYNOPSIS



    
           **pam_timestamp_check**[-k] [-d] [_target_user_]
    


## DESCRIPTION



           With no arguments **pam_timestamp_check** will check to see if the
           default timestamp is valid, or optionally remove it.
    


## OPTIONS



           **-k**
               Instead of checking the validity of a timestamp, remove it.
               This is analogous to sudo's _-k_ option.
    
           **-d**
               Instead of returning validity using an exit status, loop
               indefinitely, polling regularly and printing the status on
               standard output.
    
           _target_user_
               By default **pam_timestamp_check** checks or removes timestamps
               generated by _pam_timestamp_ when the user authenticates as
               herself. When the user authenticates as a different user, the
               name of the timestamp file changes to accommodate this.
               _target_user_ allows one to specify this user name.
    


## RETURN VALUES



           0
               The timestamp is valid.
    
           2
               The binary is not setuid root.
    
           3
               Invalid invocation.
    
           4
               User is unknown.
    
           5
               Permissions error.
    
           6
               Invalid controlling tty.
    
           7
               Timestamp is not valid.
    


## NOTES



           Users can get confused when they are not always asked for
           passwords when running a given program. Some users reflexively
           begin typing information before noticing that it is not being
           asked for.
    


## EXAMPLES



               auth sufficient pam_timestamp.so verbose
               auth required   pam_unix.so
    
               session required pam_unix.so
               session optional pam_timestamp.so
    


## FILES



           /var/run/sudo/...
               timestamp files and directories
    


* * *
# migratepages

## NAME



           migratepages - Migrate the physical location a processes pages
    


## SYNOPSIS



           **migratepages** pid from-nodes to-nodes
    


## DESCRIPTION



           **migratepages** moves the physical location of a processes pages
           without any changes of the virtual address space of the process.
           Moving the pages allows one to change the distances of a process
           to its memory. Performance may be optimized by moving a processes
           pages to the node where it is executing.
    
           If multiple nodes are specified for from-nodes or to-nodes then an
           attempt is made to preserve the relative location of each page in
           each nodeset.
    
           For example if we move from nodes 2-5 to 7,9,12-13 then the
           preferred mode of operation is to move pages from 2->7, 3->9,
           4->12 and 5->13. However, this is only posssible if enough memory
           is available.
    
           Valid node specifiers
                  all                 All nodes
                  number              Node number
                  number1{,number2}   Node number1 and Node number2
                  number1-number2     Nodes from number1 to number2
                  ! nodes             Invert selection of the following specification.
    


## NOTES



           Requires a NUMA policy aware kernel with support for page
           migration (linux 2.6.16 and later).
    
           migratepages will only move pages that are not shared with other
           processes if called by a user without administrative priviledges
           (but with the right to modify the process).
    
           migratepages will move all pages if invoked from root (or a user
           with administrative priviledges).
    


## FILES



           _/proc/ <pid>/numa_maps_ for information about the NUMA memory use of
           a process.
    


* * *
# ibcacheedit

## NAME



           ibcacheedit - edit an ibnetdiscover cache
    


## SYNOPSIS



           ibcacheedit [options] <orig.cache> <new.cache>
    


## DESCRIPTION



           ibcacheedit allows users to edit an ibnetdiscover cache created
           through the **--cache** option in ibnetdiscover(8) .
    


## OPTIONS



           **--switchguid BEFOREGUID:AFTERGUID**
                  Specify a switchguid that should be changed.  The before
                  and after guid should be separated by a colon.  On
                  switches, port guids are identical to the switch guid, so
                  port guids will be adjusted as well on switches.
    
           **--caguid BEFOREGUID:AFTERGUID**
                  Specify a caguid that should be changed.  The before and
                  after guid should be separated by a colon.
    
           **--sysimgguid BEFOREGUID:AFTERGUID**
                  Specify a sysimgguid that should be changed.  The before
                  and after guid should be spearated by a colon.
    
           **--portguid NODEGUID:BEFOREGUID:AFTERGUID**
                  Specify a portguid that should be changed.  The nodeguid of
                  the port (e.g. switchguid or caguid) should be specified
                  first, followed by a colon, the before port guid, another
                  colon, then the after port guid.  On switches, port guids
                  are identical to the switch guid, so the switch guid will
                  be adjusted as well on switches.
    
       **Debugging flags**
           **-h, --help** show the usage message
    
           **-V, --version** show the version info.
    


* * *
# semanage-permissive

## NAME



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


## SYNOPSIS



           **semanage permissive [-h] [-n] [-N] [-S STORE] (--add TYPE |**
           **--delete TYPE | --deleteall | --extract | --list)**
    


## DESCRIPTION



           semanage is used to configure certain elements of SELinux policy
           without requiring modification to or recompilation from policy
           sources.  **semanage permissive** adds or removes a SELinux Policy
           permissive module. Please note that this command can make any
           domain permissive, but can only remove the permissive property
           from domains where it was added by semanage permissive ("semanage
           permissive -d" can only be used on types listed as "Customized
           Permissive Types" by "semanage permissive -l").
    


## OPTIONS



           _-h, --help_
                  Show this help message and exit
    
           _-a, --add_
                  Add a record of the specified object type
    
           _-d, --delete_
                  Delete a record of the specified object type
    
           _-D, --deleteall_
                  Remove all local customizations of permissive domains
    
           _-l, --list_
                  List records of the specified object type
    
           _-E, --extract_
                  Extract customizable commands, for use within a transaction
    
           _-n, --noheading_
                  Do not print heading when listing the specified object type
    
           _-N, --noreload_
                  Do not reload the policy after commit
    
           _-S STORE, --store STORE_
                  Select an alternate SELinux Policy Store to manage
    


## EXAMPLE



           List all permissive domains ("Builtin Permissive Types" where set by the system policy, or a custom policy module)
           # semanage permissive -l
           Make httpd_t (Web Server) a permissive domain
           # semanage permissive -a httpd_t
    


* * *
# ibidsverify

## NAME



           ibidsverify - validate IB identifiers in subnet and report errors
    


## SYNOPSIS



           ibidsverify.pl [-h] [-R]
    


## DESCRIPTION



           ibidsverify.pl is a perl script which uses a full topology file
           that was created by ibnetdiscover, scans the network to validate
           the LIDs and GUIDs in the subnet. The validation consists of
           checking that there are no zero or duplicate identifiers.
    
           Finally, ibidsverify.pl will also reuse the cached ibnetdiscover
           output from some of the other diag tools which makes it a bit
           faster than running ibnetdiscover from scratch.
    


## OPTIONS



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


## EXIT STATUS



           Exit status is 1 if errors are found, 0 otherwise.
    


## FILES



       **CONFIG FILE**
           /ssd11/FOSS/rdma-core/build/etc/infiniband-diags/ibdiag.conf
    
           A global config file is provided to set some of the common options
           for all tools.  See supplied config file for details.
    


* * *
# filecap

## NAME



           filecap - a program to see capabilities
    


## SYNOPSIS



           **filecap [ -a | -d | /dir | /dir/file [cap1 cap2 ...] ]**
    


## DESCRIPTION



           **filecap** is a program that prints out a report of programs with
           file based capabilities. If a file is not in the report or there
           is no report at all, no capabilities were found. For expedience,
           the default is to check only the directories in the PATH
           environmental variable. If the -a command line option is given,
           then all directories will be checked. If a directory is passed, it
           will recursively check that directory. If a path to a file is
           given, it will only check that file. If a file is given followed
           by capabilities, then the capabilities are written to the file.
    


## OPTIONS



           **-a** This tells the program to show all capabilities starting
                  from the / directory. Normally the PATH environmental
                  variable is used to show you capabilities on files you are
                  likely to execute.
    
           **-d** This dumps all capabilities for reference.
    


## EXAMPLES



           To check file capabilities in $PATH:
           **filecap**
    
           To check file capabilities of whole system:
           **filecap -a**
    
           To check file capabilities recursively in a directory:
           **filecap /usr**
    
           To check file capabilities of a specific program:
           **filecap /bin/passwd**
    
           To list all possible capabilities:
           **filecap -d**
    
           To set a file capability on a specific program:
           **filecap /bin/ping net_raw net_admin**
    
           To remove file capabilities on a specific program:
           **filecap /bin/ping none**
    


* * *
# cifs.idmap

## NAME



           cifs.idmap - Userspace helper for mapping ids for Common Internet
           File System (CIFS)
    


## SYNOPSIS



              cifs.idmap [--help|-h] [--timeout|-t] [--version|-v] {keyid}
    


## DESCRIPTION



           This tool is part of the cifs-utils suite.
    
           **cifs.idmap** is a userspace helper program for the linux CIFS
           client filesystem. There are a number of activities that the
           kernel cannot easily do itself. This program is a callout program
           that does these things for the kernel and then returns the result.
    
           **cifs.idmap** is generally intended to be run when the kernel calls
           request-key(8) for a particular key type. While it can be run
           directly from the command-line, it is not generally intended to be
           run that way.
    
           This program is only called if a share is mounted with the **cifsacl**
           mount option. The kernel will only upcall to do this conversion if
           that mount option is specified.
    
           **cifs.idmap** relies on a plugin to handle the ID mapping. If it
           can't find the plugin then it will not work properly. The plugin
           (or a symlink to it) must be at /etc/cifs-utils/idmap-plugin.
    
           In the case where **cifs.idmap** or the plugin are unavailable, file
           objects in a mounted share are assigned uid and gid of the
           credentials of the process that mounted the share. It is strongly
           recomemended to use mount options of uid and gid to specify a
           default uid and gid to map owner SIDs and group SIDs in this
           situation.
    


## OPTIONS



           **--help|-h**
                  Print the usage message and exit.
    
           **--timeout|-t**
                  Set the expiration timer, in seconds on the key. The
                  default is 600 seconds (10 minutes). Setting this to 0 will
                  cause the key to never expire.
    
           **--version|-v**
                  Print version number and exit.
    


## CONFIGURATION FOR KEYCTL



           **cifs.idmap** is designed to be called from the kernel via the
           request-key callout program. This requires that request-key be
           told where and how to call this program.  Currently **cifs.idmap**
           handles a key type of:
    
              cifs.idmap
    
           This keytype is for mapping a SID to either an uid or a gid.
    
           To make this program useful for CIFS, you will need to set up
           entry for it in request-key.conf(5). Here is an example of an
           entry for this key type:
    
              #OPERATION  TYPE           D C PROGRAM ARG1 ARG2...
              #=========  =============  = = ================================
              create      cifs.idmap     * * /usr/local/sbin/cifs.idmap %k
    
           See request-key.conf(5) for more info on each field.
    


## NOTES



           Support for upcalls to cifs.idmap was initially introduced in the
           3.0 kernel.
    


* * *
# pam_echo

## NAME



           pam_echo - PAM module for printing text messages
    


## SYNOPSIS



    
           **pam_echo.so**[file=_/path/message_]
    


## DESCRIPTION



           The _pam_echo_ PAM module is for printing text messages to inform
           user about special things. Sequences starting with the _%_ character
           are interpreted in the following way:
    
           _%H_
               The name of the remote host (PAM_RHOST).
    
           _%h_
               The name of the local host.
    
           _%s_
               The service name (PAM_SERVICE).
    
           _%t_
               The name of the controlling terminal (PAM_TTY).
    
           _%U_
               The remote user name (PAM_RUSER).
    
           _%u_
               The local user name (PAM_USER).
    
           All other sequences beginning with _%_ expands to the characters
           following the _%_ character.
    


## OPTIONS



           **file=**_/path/message_
               The content of the file /path/message will be printed with the
               PAM conversion function as PAM_TEXT_INFO.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_SUCCESS
               Message was successful printed.
    
           PAM_IGNORE
               PAM_SILENT flag was given or message file does not exist, no
               message printed.
    


## EXAMPLES



           For an example of the use of this module, we show how it may be
           used to print information about good passwords:
    
               password optional pam_echo.so file=/usr/share/doc/good-password.txt
               password required pam_unix.so
    


* * *
# newaliases

## NAME



           **newaliases** — rebuild mail aliases
    


## SYNOPSIS



           **newaliases**[**-f** _file_]
    


## DESCRIPTION



           The **newaliases** utility makes changes to the mail aliases file
           visible to _smtpd_(8).  It should be run every time the _aliases_(5)
           file is changed.  The location of the alias file is defined in
           _smtpd.conf_(5), and defaults to _/etc/mail/aliases_.
    
           The options are as follows:
    
           **-f** _file_
                   Use _file_ as the configuration file, instead of the default
                   _/etc/mail/smtpd.conf_.
    
           If using database (db) files, **newaliases** is equivalent to running
           _makemap_(8) as follows:
    
                 # makemap -t aliases /etc/mail/aliases
    
           If using plain text files, **newaliases** is equivalent to running
           _smtpctl_(8) as follows:
    
                 # smtpctl update table aliases
    


## FILES



           _/etc/mail/aliases_     List of local user mail aliases.
           _/etc/mail/virtual_     List of virtual host aliases.
    


## EXIT STATUS



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


* * *
# pppd-radattr

## NAME



           radattr.so - RADIUS utility plugin for pppd(8)
    


## SYNOPSIS



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


## DESCRIPTION



           The radattr plugin for pppd causes all radius attributes returned
           by the RADIUS server at authentication time to be stored in the
           file _/var/run/radattr.pppN_ where _pppN_ is the name of the PPP
           interface.  The RADIUS attributes are stored one per line in the
           format "Attribute-Name Attribute-Value".  This format is
           convenient for use in /etc/ppp/ip-up and /etc/ppp/ip-down scripts.
    
           Note that you _must_ load the radius.so plugin before loading the
           radattr.so plugin; radattr.so depends on symbols defined in
           radius.so.
    


## USAGE



           To use the plugin, simply supply the **plugin radius.so plugin**
           **radattr.so** options to pppd.
    


* * *
# devlink-dpipe

## NAME



           devlink-dpipe - devlink dataplane pipeline visualization
    


## SYNOPSIS



           **devlink**[ _OPTIONS_ ] **dpipe**{ **table** | **header**} { _COMMAND_ | **help**}
    
           _OPTIONS_ := { **-V**[_ersion_] }
    
           **devlink dpipe table show** _DEV_ [ **name** _TABLE_NAME_ ]
    
           **devlink dpipe table set** _DEV_ **name** _TABLE_NAME_
    
           **devlink dpipe table dump** _DEV_ **name** _TABLE_NAME_
    
           **devlink dpipe header show** _DEV_
    
           **devlink dpipe help**
    


## DESCRIPTION



       **devlink dpipe table show - display devlink dpipe table attributes**
           **name** _TABLE_NAME_
                  Specifies the table to operate on.
    
       **devlink dpipe table set - set devlink dpipe table attributes**
           **name** _TABLE_NAME_
                  Specifies the table to operate on.
    
       **devlink dpipe table dump - dump devlink dpipe table entries**
           **name** _TABLE_NAME_
                  Specifies the table to operate on.
    
       **devlink dpipe header show - display devlink dpipe header attributes**
           **name** _TABLE_NAME_
                  Specifies the table to operate on.
    


## EXAMPLES



           devlink dpipe table show pci/0000:01:00.0
               Shows all dpipe tables on specified devlink device.
    
           devlink dpipe table show pci/0000:01:00.0 name mlxsw_erif
               Shows mlxsw_erif dpipe table on specified devlink device.
    
           devlink dpipe table set pci/0000:01:00.0 name mlxsw_erif
           counters_enabled true
               Turns on the counters on mlxsw_erif table.
    
           devlink dpipe table dump pci/0000:01:00.0 name mlxsw_erif
               Dumps content of mlxsw_erif table.
    
           devlink dpipe header show pci/0000:01:00.0
               Shows all dpipe headers on specified devlink device.
    


* * *
# iconvconfig

## NAME



           iconvconfig - create iconv module configuration cache
    


## SYNOPSIS



           **iconvconfig**[_options_] [_directory_]...
    


## DESCRIPTION



           The iconv(3) function internally uses _gconv_ modules to convert to
           and from a character set.  A configuration file is used to
           determine the needed modules for a conversion.  Loading and
           parsing such a configuration file would slow down programs that
           use iconv(3), so a caching mechanism is employed.
    
           The **iconvconfig** program reads iconv module configuration files and
           writes a fast-loading gconv module configuration cache file.
    
           In addition to the system provided gconv modules, the user can
           specify custom gconv module directories with the environment
           variable **GCONV_PATH**.  However, iconv module configuration caching
           is used only when the environment variable **GCONV_PATH** is not set.
    


## OPTIONS



           **--nostdlib**
                  Do not search the system default gconv directory, only the
                  directories provided on the command line.
    
           **--output=**_outputfile_
           **-o** _outputfile_
                  Use _outputfile_ for output instead of the system default
                  cache location.
    
           **--prefix=**_pathname_
                  Set the prefix to be prepended to the system pathnames.
                  See FILES, below.  By default, the prefix is empty.
                  Setting the prefix to _foo_ , the gconv module configuration
                  would be read from _foo/usr/lib/gconv/gconv-modules_ and the
                  cache would be written to
                  _foo/usr/lib/gconv/gconv-modules.cache_.
    
           **--help**
           **-?** Print a usage summary and exit.
    
           **--usage**
                  Print a short usage summary and exit.
    
           **--version**
           **-V** Print the version number, license, and disclaimer of
                  warranty for **iconv**.
    


## EXIT STATUS



           Zero on success, nonzero on errors.
    


## FILES



           _/usr/lib/gconv_
                  Usual default gconv module path.
    
           _/usr/lib/gconv/gconv-modules_
                  Usual system default gconv module configuration file.
    
           _/usr/lib/gconv/gconv-modules.cache_
                  Usual system gconv module configuration cache.
    
           Depending on the architecture, the above files may instead be
           located at directories with the path prefix _/usr/lib64_.
    


* * *
# mklost+found

## NAME



           mklost+found - create a lost+found directory on a mounted
           ext2/ext3/ext4 file system
    


## SYNOPSIS



           **mklost+found**
    


## DESCRIPTION



           **mklost+found** is used to create a _lost+found_ directory in the
           current working directory on an ext2/ext3/ext4 file system.  There
           is normally a _lost+found_ directory in the root directory of each
           file system.
    
           **mklost+found** pre-allocates disk blocks to the _lost+found_ directory
           so that when e2fsck(8) is being run to recover a file system, it
           does not need to allocate blocks in the file system to store a
           large number of unlinked files.  This ensures that **e2fsck** will not
           have to allocate data blocks in the file system during recovery.
    


## OPTIONS



           There are none.
    


## BUGS



           There are none :-)
    


## AVAILABILITY



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


* * *
# systemd-run-generator

## NAME



           systemd-run-generator - Generator for invoking commands specified
           on the kernel command line as system service
    


## SYNOPSIS



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


## DESCRIPTION



           systemd-run-generator is a generator that reads the kernel command
           line and understands three options:
    
           If the **systemd.run=** option is specified and followed by a command
           line, a unit named kernel-command-line.service is generated for it
           and booted into. The service has _Type=oneshot_ set, and has
           _SuccessAction=exit_ and _FailureAction=exit_ configured by default,
           thus ensuring that the system is shut down as soon as the command
           completes. The exit status of the command line is propagated to
           the invoking container manager, if this applies (which might
           propagate this further, to the calling shell — e.g.
           systemd-nspawn(1) does this). If this option is used multiple
           times the unit file will contain multiple _ExecStart=_ lines, to
           execute all commands in order. The command is started as regular
           service, i.e. with _DefaultDependencies=_ on.
    
           Use **systemd.run_success_action=** and **systemd.run_failure_action=** to
           tweak how to react to the process completing. In particular
           assigning "none" will leave the system running after the command
           completes. For further details on supported arguments, see
           systemd.unit(5).
    
           systemd-run-generator implements systemd.generator(7).
    


## EXAMPLE



           Use a command like the following to add a user to the user
           database inside a container run with systemd-nspawn(1):
    
               # systemd-nspawn -D mycontainer -b systemd.run='"adduser test"'
    
           (Note the requirement for double quoting in the command line
           above. The first level of quoting ('') is processed and removed by
           the command shell used to invoke **systemd-nspawn**. The second level
           of quoting ("") is propagated to the kernel command line of the
           container and processed and removed by **systemd-run-generator**. Both
           together make sure both words of the specified command line
           **adduser test** end up in the generated unit file together and are
           neither split apart by the command shell nor by the generator.)
    


* * *
# accessdb

## NAME



           accessdb - dumps the content of a man-db database in a human
           readable format
    


## SYNOPSIS



           **/usr/sbin/accessdb**[**-d?V**] [_< index-file>_]
    


## DESCRIPTION



           **accessdb** will output the data contained within a man-db database
           in a human readable form.  By default, it will dump the data from
           **/var/cache/man/index. <db-type>, **where <db-type> is dependent on
           the database library in use.
    
           Supplying an argument to accessdb will override this default.
    


## OPTIONS



           **-d** , **--debug**
                  Print debugging information.
    
           **-?** , **--help**
                  Print a help message and exit.
    
           **--usage**
                  Print a short usage message and exit.
    
           **-V** , **--version**
                  Display version information.
    


## BUGS



           https://gitlab.com/man-db/man-db/-/issues
           https://savannah.nongnu.org/bugs/?group=man-db
    


* * *
# lsmod

## NAME



           lsmod - Show the status of modules in the Linux Kernel
    


## SYNOPSIS



           **lsmod**[_OPTIONS_]
    


## DESCRIPTION



           **lsmod** is a trivial program which nicely formats the contents of
           the _/proc/modules_ , showing what kernel modules are currently
           loaded.
    


## OPTIONS



           **-s** , **--syslog**
               Send errors to syslog instead of standard error.
    
           **-v** , **--verbose**
               Print messages about what the program is doing. Usually **lsmod**
               prints messages only if something goes wrong.
    
           **-V** , **--version**
               Show version of program and exit.
    
           **-h** , **--help**
               Print the help message and exit.
    


## BUGS



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


* * *
# selinux-polgengui

## NAME



           selinux-polgengui - SELinux Policy Generation Tool
    


## SYNOPSIS



           **selinux-polgengui**
    


## DESCRIPTION



           **selinux-polgengui** is a graphical tool, which can be used to create
           a framework for building SELinux Policy.
    


## OPTIONS



           None
    


## FILES



           /usr/bin/selinux-polgengui
    


## Examples



           To run the program type:
    
           selinux-polgengui
    


* * *
# fsck.xfs

## NAME



           fsck.xfs - do nothing, successfully
    


## SYNOPSIS



           **fsck.xfs**[ _filesys_ ... ]
    


## DESCRIPTION



           **fsck.xfs** is called by the generic Linux fsck(8) program at startup
           to check and repair an XFS filesystem.  XFS is a journaling
           filesystem and performs recovery at mount(8) time if necessary, so
           **fsck.xfs** simply exits with a zero exit status.
    
           If you wish to check the consistency of an XFS filesystem, or
           repair a damaged or corrupt XFS filesystem, see xfs_repair(8).
    
           However, the system administrator can force **fsck.xfs** to run
           xfs_repair(8) at boot time by creating a /forcefsck file or
           booting the system with "fsck.mode=force" on the kernel command
           line.
    


## FILES



           _/etc/fstab_.
    


* * *
# fsadm

## NAME



           fsadm — utility to resize or check filesystem on a device
    


## SYNOPSIS



           **fsadm**[_options_] **check** _device_
           **fsadm**[_options_] **resize** _device_ [_new_size_]
    


## DESCRIPTION



           The  fsadm  utility  checks  or resizes the filesystem on a device
           (which can also be a dm-crypt encrypted device).  It tries to  use
           the same API for **ext2** , **ext3** , **ext4** , **ReiserFS** and **XFS** filesystems.
    


## OPTIONS



           **-e** |**--ext-offline**
                  Unmount ext2/ext3/ext4 filesystem before doing resize.
    
           **-f** |**--force**
                  Bypass some sanity checks.
    
           **-h** |**--help**
                  Display the help text.
    
           **-l** |**--lvresize**
                  Also resize the given lvm2 logical volume. More volume man‐
                  agement functionality is provided with complementary
                  lvresize(8) and the option **-r** |**--resizefs.**
    
           **-n** |**--dry-run**
                  Print commands without running them.
    
           **-v** |**--verbose**
                  Be more verbose.
    
           **-y** |**--yes**
                  Answer "yes" at any prompts.
    
           **-c** |**--cryptresize**
                  Resize dm-crypt mapping together with filesystem detected
                  on the device.  The dm-crypt device must be recognizable by
                  cryptsetup(8).
    
           _new_size_[**B** |**K** |**M** |**G** |**T** |**P** |**E**]
                  Absolute number of filesystem blocks to be in the filesys‐
                  tem, or an absolute size using a suffix (in powers of
                  1024).  If new_size is not supplied, the whole device is
                  used.
    


## DIAGNOSTICS



           On successful completion, the status code is 0.  A status code of
           2 indicates the operation was interrupted by the user.  A status
           code of 3 indicates the requested check operation could not be
           performed because the filesystem is mounted and does not support
           an online fsck(8).  A status code of 1 is used for other failures.
    


## EXAMPLES



           Resize the filesystem on logical volume _/dev/vg/test_ to 1000 MiB.
           If _/dev/vg/test_ contains ext2/ext3/ext4 filesystem it will be un‐
           mounted prior to the resize.  All [y/n] questions will be answered
           'y'.
    
           **fsadm -e -y resize /dev/vg/test 1000M**
    


## ENVIRONMENT VARIABLES



           **TMPDIR** The temporary directory name for mount points. Defaults to
                  "_/tmp_ ".
    
           **DM_DEV_DIR**
                  The device directory name.  Defaults to "_/dev_ " and must be
                  an absolute path.
    


* * *
# pwhistory_helper

## NAME



           pwhistory_helper - Helper binary that transfers password hashes
           from passwd or shadow to opasswd
    


## SYNOPSIS



    
           **pwhistory_helper**[...]
    


## DESCRIPTION



           _pwhistory_helper_ is a helper program for the _pam_pwhistory_ module
           that transfers password hashes from passwd or shadow file to the
           opasswd file and checks a password supplied by user against the
           existing hashes in the opasswd file.
    
           The purpose of the helper is to enable tighter confinement of
           login and password changing services. The helper is thus called
           only when SELinux is enabled on the system.
    
           The interface of the helper - command line options, and
           input/output data format are internal to the _pam_pwhistory_ module
           and it should not be called directly from applications.
    


* * *
# pam_issue

## NAME



           pam_issue - PAM module to add issue file to user prompt
    


## SYNOPSIS



    
           **pam_issue.so**[noesc] [issue=_issue-file-name_]
    


## DESCRIPTION



           pam_issue is a PAM module to prepend an issue file to the username
           prompt. It also by default parses escape codes in the issue file
           similar to some common getty's (using \x format).
    
           Recognized escapes:
    
           **\d**
               current day
    
           **\l**
               name of this tty
    
           **\m**
               machine architecture (uname -m)
    
           **\n**
               machine's network node hostname (uname -n)
    
           **\o**
               domain name of this system
    
           **\r**
               release number of operating system (uname -r)
    
           **\t**
               current time
    
           **\s**
               operating system name (uname -s)
    
           **\u**
               number of users currently logged in
    
           **\U**
               same as \u except it is suffixed with "user" or "users" (eg.
               "1 user" or "10 users")
    
           **\v**
               operating system version and build date (uname -v)
    


## OPTIONS



           **noesc**
               Turns off escape code parsing.
    
           **issue=**_issue-file-name_
               The file to output if not using the default.
    


## MODULE TYPES PROVIDED



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


## RETURN VALUES



           PAM_BUF_ERR
               Memory buffer error.
    
           PAM_IGNORE
               The prompt was already changed.
    
           PAM_SERVICE_ERR
               A service module error occurred.
    
           PAM_SUCCESS
               The new prompt was set successfully.
    


## EXAMPLES



           Add the following line to /etc/pam.d/login to set the user
           specific issue at login:
    
                       auth optional pam_issue.so issue=/etc/issue
    


* * *
# ssh-keysign

## NAME



           **ssh-keysign** — OpenSSH helper for host-based authentication
    


## SYNOPSIS



           **ssh-keysign**
    


## DESCRIPTION



           **ssh-keysign** is used by _ssh_(1) to access the local host keys and
           generate the digital signature required during host-based
           authentication.
    
           **ssh-keysign** is disabled by default and can only be enabled in the
           global client configuration file _/etc/ssh/ssh_config_ by setting
           **EnableSSHKeysign** to “yes”.
    
           **ssh-keysign** is not intended to be invoked by the user, but from
           _ssh_(1).  See _ssh_(1) and _sshd_(8) for more information about host-
           based authentication.
    


## FILES



           _/etc/ssh/ssh_config_
                   Controls whether **ssh-keysign** is enabled.
    
           _/etc/ssh/ssh_host_ecdsa_key_
           _/etc/ssh/ssh_host_ed25519_key_
           _/etc/ssh/ssh_host_rsa_key_
                   These files contain the private parts of the host keys
                   used to generate the digital signature.  They should be
                   owned by root, readable only by root, and not accessible
                   to others.  Since they are readable only by root,
                   **ssh-keysign** must be set-uid root if host-based
                   authentication is used.
    
           _/etc/ssh/ssh_host_ecdsa_key-cert.pub_
           _/etc/ssh/ssh_host_ed25519_key-cert.pub_
           _/etc/ssh/ssh_host_rsa_key-cert.pub_
                   If these files exist, they are assumed to contain public
                   certificate information corresponding with the private
                   keys above.
    


* * *
# filefrag

## NAME



           filefrag - report on file fragmentation
    


## SYNOPSIS



           **filefrag**[ **-b** _blocksize_ ] [ **-BeEkPsvVxX**] [ _files..._  ]
    


## DESCRIPTION



           **filefrag** reports on how badly fragmented a particular file might
           be.  It makes allowances for indirect blocks for ext2 and ext3
           file systems, but can be used on files for any file system.
    
           The **filefrag** program initially attempts to get the extent
           information using FIEMAP ioctl which is more efficient and faster.
           If FIEMAP is not supported then filefrag will fall back to using
           FIBMAP.
    


## OPTIONS



           **-B** Force the use of the older FIBMAP ioctl instead of the
                  FIEMAP ioctl for testing purposes.
    
           **-b** _blocksize_
                  Use _blocksize_ in bytes, or with [KMG] suffix, up to 1GB for
                  output instead of the file system blocksize.  For
                  compatibility with earlier versions of **filefrag** , if
                  _blocksize_ is unspecified it defaults to 1024 bytes.  Since
                  _blocksize_ is an optional argument, it must be added without
                  any space after **-b**.
    
           **-e** Print output in extent format, even for block-mapped files.
    
           **-E** Display the contents of ext4's extent status cache.  This
                  feature is not supported on all kernels, and is only
                  supported on ext4 file systems.
    
           **-k** Use 1024-byte blocksize for output (identical to '-b1024').
    
           **-P** Pre-load the ext4 extent status cache for the file.  This
                  is not supported on all kernels, and is only supported on
                  ext4 file systems.
    
           **-s** Sync the file before requesting the mapping.
    
           **-v** Be verbose when checking for file fragmentation.
    
           **-V** Print version number of program and library.  If given
                  twice, also print the FIEMAP flags that are understood by
                  the current version.
    
           **-x** Display mapping of extended attributes.
    
           **-X** Display extent block numbers in hexadecimal format.
    


* * *