tripathysagar/man_text huggingface dataset:
# git-stage

## NAME



           git-stage - Add file contents to the staging area
    


## SYNOPSIS



           _git stage_ <arg>...
    


## DESCRIPTION



           This is a synonym for git-add(1). Please refer to the
           documentation of that command.
    


## GIT



           Part of the git(1) suite
    


* * *
# shred

## NAME



           shred - overwrite a file to hide its contents, and optionally
           delete it
    


## SYNOPSIS



           **shred**[_OPTION_]... _FILE_...
    


## DESCRIPTION



           Overwrite the specified FILE(s) repeatedly, in order to make it
           harder for even very expensive hardware probing to recover the
           data.
    
           If FILE is -, shred standard output.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-f** , **--force**
                  change permissions to allow writing if necessary
    
           **-n** , **--iterations** =_N_
                  overwrite N times instead of the default (3)
    
           **--random-source** =_FILE_
                  get random bytes from FILE
    
           **-s** , **--size** =_N_
                  shred this many bytes (suffixes like K, M, G accepted)
    
           **-u** deallocate and remove file after overwriting
    
           **--remove**[=_HOW_]
                  like **-u** but give control on HOW to delete;  See below
    
           **-v** , **--verbose**
                  show progress
    
           **-x** , **--exact**
                  do not round file sizes up to the next full block; this is
                  the default for non-regular files
    
           **-z** , **--zero**
                  add a final overwrite with zeros to hide shredding
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Delete FILE(s) if **--remove**(**-u**) is specified.  The default is not
           to remove the files because it is common to operate on device
           files like _/dev/hda_ , and those files usually should not be
           removed.  The optional HOW parameter indicates how to remove a
           directory entry: 'unlink' => use a standard unlink call.  'wipe'
           => also first obfuscate bytes in the name.  'wipesync' => also
           sync each obfuscated byte to the device.  The default mode is
           'wipesync', but note it can be expensive.
    
           CAUTION: shred assumes the file system and hardware overwrite data
           in place.  Although this is common, many platforms operate
           otherwise.  Also, backups and mirrors may contain unremovable
           copies that will let a shredded file be recovered later.  See the
           GNU coreutils manual for details.
    


* * *
# cksum

## NAME



           cksum - compute and verify file checksums
    


## SYNOPSIS



           **cksum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or verify checksums.  By default use the 32 bit CRC
           algorithm.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-a** , **--algorithm** =_TYPE_
                  select the digest type to use.  See DIGEST below
    
           **--base64**
                  emit base64-encoded digests, not hexadecimal
    
           **-c** , **--check**
                  read checksums from the FILEs and check them
    
           **-l** , **--length** =_BITS_
                  digest length in bits; must not exceed the max for the
                  blake2 algorithm and must be a multiple of 8
    
           **--raw** emit a raw binary digest, not hexadecimal
    
           **--tag** create a BSD-style checksum (the default)
    
           **--untagged**
                  create a reversed style checksum, without digest type
    
           **-z** , **--zero**
                  end each output line with NUL, not newline, and disable
                  file name escaping
    
       **The following five options are useful only when verifying checksums:**
           **--ignore-missing**
                  don't fail or report status for missing files
    
           **--quiet**
                  don't print OK for each successfully verified file
    
           **--status**
                  don't output anything, status code shows success
    
           **--strict**
                  exit non-zero for improperly formatted checksum lines
    
           **-w** , **--warn**
                  warn about improperly formatted checksum lines
    
           **--debug**
                  indicate which implementation used
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
       **DIGEST determines the digest algorithm and default output format:**
           sysv   (equivalent to sum **-s**)
    
           bsd    (equivalent to sum **-r**)
    
           crc    (equivalent to cksum)
    
           crc32b (only available through cksum)
    
           md5    (equivalent to md5sum)
    
           sha1   (equivalent to sha1sum)
    
           sha224 (equivalent to sha224sum)
    
           sha256 (equivalent to sha256sum)
    
           sha384 (equivalent to sha384sum)
    
           sha512 (equivalent to sha512sum)
    
           blake2b
                  (equivalent to b2sum)
    
           sm3    (only available through cksum)
    
           When checking, the input should be a former output of this
           program, or equivalent standalone program.
    


* * *
# pmpost

## NAME



           **pmpost** - append messages to the Performance Co-Pilot notice board
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmpost**[**-D** _debug_] _message_
    


## DESCRIPTION



           **pmpost** will append the text _message_ to the end of the Performance
           Co-Pilot (PCP) notice board file (**$PCP_LOG_DIR/NOTICES**) in an
           atomic manner that guards against corruption of the notice board
           file by concurrent invocations of **pmpost**.
    
           The PCP notice board is intended to be a persistent store and
           clearing house for important messages relating to the operation of
           the PCP and the notification of performance alerts from pmie(1)
           when other notification options are either unavailable or
           unsuitable.
    
           Before being written, messages are prefixed by the current time,
           and when the current day is different to the last time the notice
           board file was written, **pmpost** will prepend the message with the
           full date.
    
           If the notice board file does not exist, **pmpost** will create it.
           **pmpost** would usually run from long-running PCP daemons executing
           under the (typically unprivileged) **$PCP_USER** and **$PCP_GROUP**
           accounts.  The file should be owned and writable by the **$PCP_USER**
           user, and readable by others.
    


## FILES



           _$PCP_LOG_DIR/NOTICES_
                the PCP notice board file
    


## PCP ENVIRONMENT



           The file **/etc/pcp.conf** contains the local values for PCP_
           variables.
    


## DEBUGGING OPTIONS



           The **-D** or **--debug** option enables the output of additional
           diagnostics on _stderr_ to help triage problems, although the
           information is sometimes cryptic and primarily intended to provide
           guidance for developers rather end-users.  _debug_ is a comma
           separated list of debugging options; use pmdbg(1) with the **-l**
           option to obtain a list of the available debugging options and
           their meaning.
    


* * *
# dh_listpackages

## NAME



           dh_listpackages - list binary packages debhelper will act on
    


## SYNOPSIS



           **dh_listpackages**[_debhelper options_]
    


## DESCRIPTION



           **dh_listpackages** is a debhelper program that outputs a list of all
           binary packages debhelper commands will act on. If you pass it
           some options, it will change the list to match the packages other
           debhelper commands would act on if passed the same options.
    
           Packages are listed in the order they appear in _debian/control_.
    


* * *
# mariadb-fix-extensions

## NAME



           mariadb-fix-extensions - normalize table file name extensions
           (mariadb-fix-extensions is now a symlink to mariadb-fix-
           extensions)
    


## SYNOPSIS



    
           **mariadb-fix-extensions** _data_dir_
    


## DESCRIPTION



           This script is deprecated and will be removed in a later release.
    
           **mariadb-fix-extensions** converts the extensions for MyISAM (or
           ISAM) table files to their canonical forms. It looks for files
           with extensions matching any lettercase variant of .frm, .myd,
           .myi, .isd, and .ism and renames them to have extensions of .frm,
           .MYD, .MYI, .ISD, and .ISM, respectively. This can be useful after
           transferring the files from a system with case-insensitive file
           names (such as Windows) to a system with case-sensitive file
           names.
    
           Invoke **mariadb-fix-extensions** like this, where _data_dir_ is the
           path name to the MariaDB data directory.
    
               shell> **mariadb-fix-extensions** _data_dir_
    


* * *
# wsrep_sst_rsync_wan

## NAME



           wsrep_sst_rsync_wan - rsync_wan (rsync with delta transfers)-based
           state snapshot transfer
    


## DESCRIPTION



           Use: rsync_wan-based state snapshot transfer.
    
           For more information, please refer to the MariaDB Knowledge Base,
           available online at https://mariadb.com/kb/
    


* * *
# envsubst

## NAME



           envsubst - substitutes environment variables in shell format
           strings
    


## SYNOPSIS



           **envsubst**[_OPTION_] [_SHELL-FORMAT_]
    


## DESCRIPTION



           Substitutes the values of environment variables.
    
       **Operation mode:**
           **-v** , **--variables**
                  output the variables occurring in SHELL-FORMAT
    
       **Informative output:**
           **-h** , **--help**
                  display this help and exit
    
           **-V** , **--version**
                  output version information and exit
    
           In normal operation mode, standard input is copied to standard
           output, with references to environment variables of the form
           $VARIABLE or ${VARIABLE} being replaced with the corresponding
           values.  If a SHELL-FORMAT is given, only those environment
           variables that are referenced in SHELL-FORMAT are substituted;
           otherwise all environment variables references occurring in
           standard input are substituted.
    
           When **--variables** is used, standard input is ignored, and the
           output consists of the environment variables that are referenced
           in SHELL-FORMAT, one per line.
    


* * *
# pmerr

## NAME



           **pmerr** - translate Performance Co-Pilot error codes into error
           messages
    


## SYNOPSIS



           **pmerr**[**-?**]  _code_ ...
           **pmerr -l**
    


## DESCRIPTION



           **pmerr** accepts standard Performance Co-Pilot (PCP) error codes via
           the _code_ argument(s) and generates the corresponding error text.
    
           Each _code_ may be an integer, a hexadecimal value or a hexadecimal
           value prefixed by either ``0x'' or ``0X''.
    
           Error codes must be less than zero, so if _code_ is a positive
           number, a warning message is produced, and the negated value is
           used.
    


## OPTIONS



           The available command line options are:
    
           **-l** , **--list**
                This alternative invocation causes all known error codes to
                be listed, along with their symbolic names and error text.
    
           **-?** , **--help**
                Display usage message and exit.
    


## PCP ENVIRONMENT



           Environment variables with the prefix **PCP_** are used to
           parameterize the file and directory names used by PCP.  On each
           installation, the file _/etc/pcp.conf_ contains the local values for
           these variables.  The **$PCP_CONF** variable may be used to specify an
           alternative configuration file, as described in pcp.conf(5).
    


* * *
# ppdi

## NAME



           ppdi - import ppd files (deprecated)
    


## SYNOPSIS



           **ppdi**[ **-I** _include-directory_ ] [ **-o** _source-file_ ] _ppd-file_ [ ...
           _ppd-file_ ]
    


## DESCRIPTION



           **ppdi** imports one or more PPD files into a PPD compiler source
           file.  Multiple languages of the same PPD file are merged into a
           single printer definition to facilitate accurate changes for all
           localizations.  **This program is deprecated and will be removed in**
           **a future release of CUPS.**
    


## OPTIONS



           **ppdi** supports the following options:
    
           **-I** _include-directory_
                Specifies an alternate include directory.  Multiple _-I_
                options can be supplied to add additional directories.
    
           **-o** _source-file_
                Specifies the PPD source file to update.  If the source file
                does not exist, a new source file is created.  Otherwise the
                existing file is merged with the new PPD file(s) on the
                command-line.  If no source file is specified, the filename
                _ppdi.drv_ is used.
    


## NOTES



           PPD files 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).
    


* * *
# unexpand

## NAME



           unexpand - convert spaces to tabs
    


## SYNOPSIS



           **unexpand**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Convert blanks in each FILE to tabs, writing to standard output.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-a** , **--all**
                  convert all blanks, instead of just initial blanks
    
           **--first-only**
                  convert only leading sequences of blanks (overrides **-a**)
    
           **-t** , **--tabs** =_N_
                  have tabs N characters apart instead of 8 (enables **-a**)
    
           **-t** , **--tabs** =_LIST_
                  use comma separated list of tab positions.  The last
                  specified position can be prefixed with '/' to specify a
                  tab size to use after the last explicitly specified tab
                  stop.  Also a prefix of '+' can be used to align remaining
                  tab stops relative to the last specified tab stop instead
                  of the first column
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# rdma_server

## NAME



           rdma_server - simple RDMA CM connection and ping-pong test.
    


## SYNOPSIS



           _rdma_server_ [-p port]
    


## DESCRIPTION



           Uses synchronous librdmam calls to establish an RDMA connections
           between two nodes.  This example is intended to provide a very
           simple coding example of how to use RDMA.
    


## OPTIONS



           -s server_address
                  Specifies the address that the rdma_server listens on.  By
                  default the server listens on any address(0.0.0.0).
    
           -p port
                  Changes the port number that the server listens on.  By
                  default the server listens on port 7471.
    


## NOTES



           Basic usage is to start rdma_server, then connect to the server
           using the rdma_client program.
    
           Because this test maps RDMA resources to userspace, users must
           ensure that they have available system resources and permissions.
           See the libibverbs README file for additional details.
    


* * *
# ibv_uc_pingpong

## NAME



           ibv_uc_pingpong - simple InfiniBand UC transport test
    


## SYNOPSIS



           **ibv_uc_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index]
           **HOSTNAME**
    
           **ibv_uc_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index]
    


## DESCRIPTION



           Run a simple ping-pong test over InfiniBand via the unreliable
           connected (UC) transport.
    


## OPTIONS



           **-p** , **--port** =_PORT_
                  use TCP port _PORT_ for initial synchronization (default
                  18515)
    
           **-d** , **--ib-dev** =_DEVICE_
                  use IB device _DEVICE_ (default first device found)
    
           **-i** , **--ib-port** =_PORT_
                  use IB port _PORT_ (default port 1)
    
           **-s** , **--size** =_SIZE_
                  ping-pong messages of size _SIZE_ (default 4096)
    
           **-m** , **--mtu** =_SIZE_
                  path MTU _SIZE_ (default 1024)
    
           **-r** , **--rx-depth** =_DEPTH_
                  post _DEPTH_ receives at a time (default 1000)
    
           **-n** , **--iters** =_ITERS_
                  perform _ITERS_ message exchanges (default 1000)
    
           **-l** , **--sl** =_SL_
                  use _SL_ as the service level value of the QP (default 0)
    
           **-e** , **--events**
                  sleep while waiting for work completion events (default is
                  to poll for completions)
    
           **-g** , **--gid-idx** =_GIDINDEX_
                  local port _GIDINDEX_
    
           **-c** , **--chk**
                  validate received buffer
    


## BUGS



           The network synchronization between client and server instances is
           weak, and does not prevent incompatible options from being used on
           the two instances.  The method used for retrieving work
           completions is not strictly correct, and race conditions may cause
           failures on some systems.
    


* * *
# git-mktag

## NAME



           git-mktag - Creates a tag object with extra validation
    


## SYNOPSIS



           _git mktag_
    


## DESCRIPTION



           Reads a tag’s contents on standard input and creates a tag object.
           The output is the new tag’s <object> identifier.
    
           This command is mostly equivalent to git-hash-object(1) invoked
           with **-t tag -w --stdin**. I.e. both of these will create and write a
           tag found in **my-tag** :
    
               git mktag <my-tag
               git hash-object -t tag -w --stdin <my-tag
    
           The difference is that mktag will die before writing the tag if
           the tag doesn’t pass a git-fsck(1) check.
    
           The "fsck" check done by mktag is stricter than what git-fsck(1)
           would run by default in that all **fsck.**_< msg-id>_ messages are
           promoted from warnings to errors (so e.g. a missing "tagger" line
           is an error).
    
           Extra headers in the object are also an error under mktag, but
           ignored by git-fsck(1). This extra check can be turned off by
           setting the appropriate **fsck.**_< msg-id>_ variable:
    
               git -c fsck.extraHeaderEntry=ignore mktag <my-tag-with-headers
    


## OPTIONS



           --strict
               By default mktag turns on the equivalent of git-fsck(1)
               **--strict** mode. Use **--no-strict** to disable it.
    


## TAG FORMAT



           A tag signature file, to be fed to this command’s standard input,
           has a very simple fixed format: four lines of
    
               object <hash>
               type <typename>
               tag <tagname>
               tagger <tagger>
    
           followed by some _optional_ free-form message (some tags created by
           older Git may not have a **tagger** line). The message, when it
           exists, is separated by a blank line from the header. The message
           part may contain a signature that Git itself doesn’t care about,
           but that can be verified with gpg.
    


## GIT



           Part of the git(1) suite
    


* * *
# oomctl

## NAME



           oomctl - Analyze the state stored in **systemd-oomd**
    


## SYNOPSIS



    
           **oomctl**[OPTIONS...] {COMMAND}
    


## DESCRIPTION



           **oomctl** may be used to get information about the various contexts
           read in by the systemd(1) userspace out-of-memory (OOM) killer,
           systemd-oomd(8).
    


## COMMANDS



           The following commands are understood:
    
           **dump**
               Show the current state of the cgroups and system contexts
               stored by **systemd-oomd**.
    
               Added in version 247.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Print a short help text and exit.
    
           **--version**
               Print a short version string and exit.
    
           **--no-pager**
               Do not pipe output into a pager.
    


## EXIT STATUS



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


* * *
# stg-next

## NAME



           stg-next - Print the name of the next patch
    


## SYNOPSIS



           _stg next_ [OPTIONS]
    


## DESCRIPTION



           Print the name of the next patch.
    
           The next patch is the unapplied patch that follows the current,
           topmost patch. An error message will be printed if there are no
           unapplied patches.
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# lprm

## NAME



           lprm - cancel print jobs
    


## SYNOPSIS



           **lprm**[ **-h** _hostname_[**:**_port_] ] [ **-E**] [ **-U** _username_ ] [ **-P**
           _destination_[_/instance_] ] [ **-**] [ _job-id(s)_ ]
    


## DESCRIPTION



           **lprm** cancels print jobs that have been queued for printing.  If no
           arguments are supplied, the current job on the default destination
           is canceled.  You can specify one or more job ID numbers to cancel
           those jobs or use the _-_ option to cancel all jobs.
    


## OPTIONS



           The **lprm** command supports the following options:
    
           **-E** Forces encryption when connecting to the server.
    
           **-P** _destination_[_/instance_]
                Specifies the destination printer or class.
    
           **-U** _username_
                Specifies an alternate username.
    
           **-h** _server_[_:port_]
                Specifies an alternate server.  Note: This option must occur
                before all others.
    


## CONFORMING TO



           The CUPS version of **lprm** is compatible with the standard Berkeley
           command of the same name.
    


## EXAMPLES



           Cancel the current job on the default printer:
    
               lprm
    
           Cancel job 1234:
    
               lprm 1234
    
           Cancel all jobs:
    
               lprm -
    


* * *
# dh_clean

## NAME



           dh_clean - clean up package build directories
    


## SYNOPSIS



           **dh_clean**[_debhelper options_] [**-k**] [**-d**] [**-X** _item_] [_path_ ...]
    


## DESCRIPTION



           **dh_clean** is a debhelper program that is responsible for cleaning
           up.  It should be the last step of the **clean** target and other
           debhelper commands generally assume that **dh_clean** will clean up
           after them.
    
           It removes the package build directories, and removes some other
           files including _debian/files_ , and any detritus left behind by
           other debhelper commands. It also removes common files and
           directories that should not appear in a Debian diff:
             #*# *~ DEADJOE *.orig *.rej *.SUMS __pycache__ TAGS .deps/* *.P
           *-stamp
    
           It does not run "make clean" to clean up after the build process.
           Use dh_auto_clean(1) to do things like that.
    


## FILES



           _debian/clean_
               Can list other paths to be removed.
    
               Note that directories listed in this file **must** end with a
               trailing slash.  Any content in these directories will be
               removed as well.
    
               Supports substitution variables in compat 13 and later as
               documented in debhelper(7).
    


## OPTIONS



           **-k** , **--keep**
               This is deprecated, use dh_prep(1) instead.
    
               The option is removed in compat 12.
    
           **-d** , **--dirs-only**
               Only clean the package build directories, do not clean up any
               other files at all.
    
           **-X** _item_ **--exclude=**_item_
               Exclude files that contain _item_ anywhere in their filename
               from being deleted, even if they would normally be deleted.
               You may use this option multiple times to build up a list of
               things to exclude.
    
           _path_ ...
               Delete these _path_ s too.
    
               Note that directories passed as arguments **must** end with a
               trailing slash.  Any content in these directories will be
               removed as well.
    


* * *
# pcp-verify

## NAME



           **pcp-verify** - verify aspects of a PCP installation
    


## SYNOPSIS



           **pcp verify**[**-a** _archive_] [**-D** _debug_] [**-h** _host_] [**-csvV?**]
    


## DESCRIPTION



           **pcp-verify** inspects various aspects of a PCP collector
           installation and reports on whether it is configured correctly for
           certain modes of operation.
    
           By default, **pcp-verify** checks that PMCD is running and no agents
           are in a failed state.  These checks can be extended and refined
           using the command line options.
    


## OPTIONS



           The available command line options are:
    
           **-a** _archive_ , **--archive** =_archive_
                Use the _archive_ for verification.
    
           **-c** , **--containers**
                Verify the collector installation for monitoring containers.
    
           **-h** _host_ , **--host** =_host_
                Connect to the PMCD on _host_ for verification.
    
           **-s** , **--secure**
                Verify that the required components for encrypted
                communication are in place.
    
           **-v** , **--verbose**
                Increase the verbosity, and report on each check as it is
                made.  In the absence of any issues found, **pcp-verify**
                operates silently.
    
           **-V** , **--version**
                Display version number and exit.
    
           **-?** , **--help**
                Display usage message and exit.
    


## DIAGNOSTICS



           **pcp-verify** will exit with a non-zero status if it finds anything
           worth reporting, otherwise it is silent and returns zero.
    


## PCP ENVIRONMENT



           Environment variables with the prefix **PCP_** are used to
           parameterize the file and directory names used by PCP.  On each
           installation, the file _/etc/pcp.conf_ contains the local values for
           these variables.  The **$PCP_CONF** variable may be used to specify an
           alternative configuration file, as described in pcp.conf(5).
    
           For environment variables affecting PCP tools, see
           pmGetOptions(3).
    


## DEBUGGING OPTIONS



           The **-D** or **--debug** option enables the output of additional
           diagnostics on _stderr_ to help triage problems, although the
           information is sometimes cryptic and primarily intended to provide
           guidance for developers rather end-users.  _debug_ is a comma
           separated list of debugging options; use pmdbg(1) with the **-l**
           option to obtain a list of the available debugging options and
           their meaning.
    


* * *
# mariadb-secure-installation

## NAME



           mariadb-secure-installation - improve MariaDB installation
           security (mariadb-secure-installation is now a symlink to mariadb-
           secure-installation)
    


## SYNOPSIS



    
           **mariadb-secure-installation**
    


## DESCRIPTION



           This program enables you to improve the security of your MariaDB
           installation in the following ways:
    
           •   You can set a password for root accounts.
    
           •   You can remove root accounts that are accessible from outside
               the local host.
    
           •   You can remove anonymous-user accounts.
    
           •   You can remove the test database, which by default can be
               accessed by anonymous users.
    
           **mariadb-secure-installation** can be invoked without arguments:
    
               shell> **mariadb-secure-installation**
    
           The script will prompt you to determine which actions to perform.
    
           **mariadb-secure-installation** accepts some options:
    
           •   **--basedir=**_dir_name_
    
               Base directory.
    
           •   **--defaults-extra-file=**_file_name_
    
               Additional option file.
    
           •   **--defaults-file=**_file_name_
    
               Option file.
    
           •   **--no-defaults**
    
               Don't read any defaults file.
    
           Other unrecognized options will be passed on to the server.
    


* * *
# stg-float

## NAME



           stg-float - Push patches to the top, even if applied
    


## SYNOPSIS



           _stg float_ [OPTIONS] <patch>...
           _stg float_ [OPTIONS] <-S|--series> <file>
    


## DESCRIPTION



           Push patches to the top, even if applied.
    
           Float one or more patches to be the topmost applied patches. The
           patches to be floated may currently be either applied or
           unapplied. The necessary pop and push operations will be performed
           to float the named patches. Patches not specified will remain
           applied or unapplied as they were prior to the float operation.
    


## OPTIONS



           --noapply
               Reorder patches without reapplying any patches
    
           -S <file>, --series=<file>
               Rearrange according to a series <file>
    
           -k, --keep
               Keep the local changes
    
           --committer-date-is-author-date
               Instead of using the current time as the committer date, use
               the author date of the commit as the committer date.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# pinky

## NAME



           pinky - lightweight finger
    


## SYNOPSIS



           **pinky**[_OPTION_]... [_USER_]...
    


## DESCRIPTION



           **-l** produce long format output for the specified USERs
    
           **-b** omit the user's home directory and shell in long format
    
           **-h** omit the user's project file in long format
    
           **-p** omit the user's plan file in long format
    
           **-s** do short format output, this is the default
    
           **-f** omit the line of column headings in short format
    
           **-w** omit the user's full name in short format
    
           **-i** omit the user's full name and remote host in short format
    
           **-q** omit the user's full name, remote host and idle time in
                  short format
    
           **--lookup**
                  attempt to canonicalize hostnames via DNS
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           A lightweight 'finger' program;  print user information.  The utmp
           file will be _/var/run/utmp_.
    


* * *
# scmp_sys_resolver

## NAME



           scmp_sys_resolver - Resolve system calls
    


## SYNOPSIS



           **scmp_sys_resolver**[-h] [-a _ARCH_ ] [-t] _SYSCALL_NAME_ |
           _SYSCALL_NUMBER_
    


## DESCRIPTION



           This command resolves both system call names and numbers with
           respect to the given architecture supplied in the optional _ARCH_
           argument.  If the architecture is not supplied on the command line
           then the native architecture is used.  If the "-t" argument is
           specified along with a system call name, then the system call will
           be translated as necessary for the given architecture.  The "-t"
           argument has no effect if a system call number is specified.
    
           In some combinations of architecture and system call, a negative
           system call number will be displayed.  A negative system call
           number indicates that the system call is not defined for the given
           architecture and is treated in a special manner by libseccomp
           depending on the operation.
    
           **-a** _ARCH_
                  The architecture to use for resolving the system call.
                  Valid _ARCH_ values are "x86", "x86_64", "x32", "arm",
                  "aarch64", "loongarch64", "m68k", "mips", "mipsel",
                  "mips64", "mipsel64", "mips64n32", "mipsel64n32", "parisc",
                  "parisc64", "ppc", "ppc64", "ppc64le", "s390", "s390x",
                  "sheb" and "sh".
    
           **-t** If necessary, translate the system call name to the proper
                  system call number, even if the system call name is
                  different, e.g. socket(2) on x86.
    
           **-h** A simple one-line usage display.
    


## EXIT STATUS



           Returns zero on success, errno values on failure.
    


## NOTES



           The libseccomp project site, with more information and the source
           code repository, can be found at
           https://github.com/seccomp/libseccomp.  This tool, as well as the
           libseccomp library, is currently under development, please report
           any bugs at the project site or directly to the author.
    


* * *
# trace-cmd-clear

## NAME



           trace-cmd-clear - clear the Ftrace buffer.
    


## SYNOPSIS



           **trace-cmd clear**[_OPTIONS_]
    


## DESCRIPTION



           The **trace-cmd(1) clear** clears the content of the Ftrace ring
           buffer.
    


## OPTIONS



           **-B** _buffer-name_
               If the kernel supports multiple buffers, this will clear only
               the given buffer. It does not affect any other buffers. This
               may be used multiple times to specify different buffers. The
               top level buffer will not be clearded if this option is given.
    
           **-a**
               Clear all existing buffers, including the top level one.
    


## LICENSE



           trace-cmd is Free Software licensed under the terms of the GNU
           Public License (GPL).
    


## RESOURCES



           **https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/ **
    


## NOTES



            1. rostedt@goodmis.org
               mailto:rostedt@goodmis.org
    
            2. tz.stoyanov@gmail.com
               mailto:tz.stoyanov@gmail.com
    
            3. linux-trace-devel@vger.kernel.org
               mailto:linux-trace-devel@vger.kernel.org
    


* * *
# git-diagnose

## NAME



           git-diagnose - Generate a zip archive of diagnostic information
    


## SYNOPSIS



           _git diagnose_ [(-o | --output-directory) <path>] [(-s | --suffix) <format>]
                          [--mode=<mode>]
    


## DESCRIPTION



           Collects detailed information about the user’s machine, Git
           client, and repository state and packages that information into a
           zip archive. The generated archive can then, for example, be
           shared with the Git mailing list to help debug an issue or serve
           as a reference for independent debugging.
    
           By default, the following information is captured in the archive:
    
           •   _git version --build-options_
    
           •   The path to the repository root
    
           •   The available disk space on the filesystem
    
           •   The name and size of each packfile, including those in
               alternate object stores
    
           •   The total count of loose objects, as well as counts broken
               down by **.git/objects** subdirectory
    
           Additional information can be collected by selecting a different
           diagnostic mode using the **--mode** option.
    
           This tool differs from git-bugreport(1) in that it collects much
           more detailed information with a greater focus on reporting the
           size and data shape of repository contents.
    


## OPTIONS



           -o <path>, --output-directory <path>
               Place the resulting diagnostics archive in _< path>_ instead of
               the current directory.
    
           -s <format>, --suffix <format>
               Specify an alternate suffix for the diagnostics archive name,
               to create a file named _git-diagnostics- <formatted-suffix>_.
               This should take the form of a strftime(3) format string; the
               current local time will be used.
    
           --mode=(stats|all)
               Specify the type of diagnostics that should be collected. The
               default behavior of _git diagnose_ is equivalent to
               **--mode=stats**.
    
               The **--mode=all** option collects everything included in
               **--mode=stats** , as well as copies of **.git** , **.git/hooks** ,
               **.git/info** , **.git/logs** , and **.git/objects/info** directories. This
               additional information may be sensitive, as it can be used to
               reconstruct the full contents of the diagnosed repository.
               Users should exercise caution when sharing an archive
               generated with **--mode=all**.
    


## GIT



           Part of the git(1) suite
    


* * *
# zsoelim

## NAME



           zsoelim - satisfy .so requests in roff input
    


## SYNOPSIS



           **zsoelim**[**-CVh**] [_file_ ...]
    


## DESCRIPTION



           **zsoelim** parses _file_ arguments, or if none are specified, its
           standard input for lines of the form:
    
           **.so** <_filename_ >
    
           These requests are replaced by the contents of the _filename_
           specified.  If the request cannot be met, **zsoelim** looks for
           _filename.ext_ where _.ext_ can be one of **.gz** , **.Z** or **.z**.  Other
           extension types may be supported depending upon compile time
           options.  If the request can be met by a compressed file, this
           file is decompressed using an appropriate decompressor and its
           output is used to satisfy the request.
    
           Traditionally, **soelim** programs were used to allow roff
           preprocessors to be able to preprocess the files referred to by
           the requests.  This particular version was written to circumvent
           problems created by support for compressed manual pages.
    


## OPTIONS



           **-C** , **--compatible**
                  This flag is available for compatibility with other **soelim**
                  programs.  Its use is to enable .so requests followed by
                  something other than whitespace.  As this is already the
                  default behaviour, it is ignored.
    
           **-h** , **--help**
                  Print a help 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
    


* * *
# git-mailsplit

## NAME



           git-mailsplit - Simple UNIX mbox splitter program
    


## SYNOPSIS



           _git mailsplit_ [-b] [-f<nn>] [-d<prec>] [--keep-cr] [--mboxrd]
                           -o<directory> [--] [(<mbox>|<Maildir>)...]
    


## DESCRIPTION



           Splits a mbox file or a Maildir into a list of files: "0001"
           "0002" .. in the specified directory so you can process them
           further from there.
    
               **Important**
    
               Maildir splitting relies upon filenames being sorted to output
               patches in the correct order.
    


## OPTIONS



           <mbox>
               Mbox file to split. If not given, the mbox is read from the
               standard input.
    
           <Maildir>
               Root of the Maildir to split. This directory should contain
               the cur, tmp and new subdirectories.
    
           -o<directory>
               Directory in which to place the individual messages.
    
           -b
               If any file doesn’t begin with a From line, assume it is a
               single mail message instead of signaling an error.
    
           -d<prec>
               Instead of the default 4 digits with leading zeros, different
               precision can be specified for the generated filenames.
    
           -f<nn>
               Skip the first <nn> numbers, for example if -f3 is specified,
               start the numbering with 0004.
    
           --keep-cr
               Do not remove **\r** from lines ending with **\r\n**.
    
           --mboxrd
               Input is of the "mboxrd" format and "^>+From " line escaping
               is reversed.
    


## GIT



           Part of the git(1) suite
    


* * *
# flatpak-repair

## NAME



           flatpak-repair - Repair a flatpak installation
    


## SYNOPSIS



    
           **flatpak repair**[OPTION...]
    


## DESCRIPTION



           Repair a flatpak installation by pruning and reinstalling invalid
           objects. The repair command does all of the following:
    
           •   Scan all locally available refs, removing any that don't
               correspond to a deployed ref.
    
           •   Verify each commit they point to, removing any invalid objects
               and noting any missing objects.
    
           •   Remove any refs that had an invalid object, and any
               non-partial refs that had missing objects.
    
           •   Prune all objects not referenced by a ref, which gets rid of
               any possibly invalid non-scanned objects.
    
           •   Enumerate all deployed refs and re-install any that are not in
               the repo (or are partial for a non-subdir deploy).
    
           Note that **flatpak repair** has to be run with root privileges to
           operate on the system installation.
    
           An alternative command for repairing OSTree repositories is ostree
           fsck.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-u** , **--user**
               Repair per-user installation.
    
           **--system**
               Repair system-wide installation.
    
           **--installation=NAME**
               Repair the system-wide installation specified by NAME among
               those defined in /etc/flatpak/installations.d/. Using
               --installation=default is equivalent to using --system.
    
           **--dry-run**
               Only report inconsistencies, don't make any changes
    
           **--reinstall-all**
               Reinstall all refs, regardless of whether they were removed
               from the repo or not
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


## EXAMPLES



           **$ sudo flatpak repair**
    
           **$ flatpak repair --user**
    


* * *
# psfstriptable

## NAME



           psfstriptable - remove the embedded Unicode character table from a
           console font
    


## SYNOPSIS



           **psfstriptable** _fontfile outfile_
    


## DESCRIPTION



           **psfstriptable** reads a .psf format console font from _fontfile_ ,
           removes the embedded Unicode font table if there is one, and
           writes the result to _outfile_.  An input file name of "-" denotes
           standard input, and an output file name of "-" denotes standard
           output.
    


* * *
# repo-rss

## NAME



           repo-rss - generates an RSS feed from one or more Yum repositories
    


## SYNOPSIS



           **repo-rss**[options] repoid1 [repoid2...]
    


## DESCRIPTION



           **repo-rss** is a program for generating RSS feeds for one or more Yum
           repositories.
    


## GENERAL OPTIONS



           **-h, --help**
                  Help; display a help message and then quit.
    
           **-f <file>**
                  Specify the file to which the RSS will be written.  Default
                  is repo-rss.xml.
    
           **-l <link>**
                  Specify the URL to the RSS feed.  Default is
                  http://yum.baseurl.org/.
    
           **-t <title>**
                  Specify the title for the RSS feed.  Default is "RSS
                  Repository - Recent Packages".
    
           **-d <description>**
                  Specify the description of the RSS feed.  Default is "Most
                  recent packages in Repositories".
    
           **-r <days>**
                  Specify the number of days to consider most recent.
                  Default is 3.
    
           **--tempcache**
                  Enable the use of a temporary directory for the yum cache.
                  This is enabled by default for non-root users.
    


## EXAMPLES



           Generate an RSS for the updates-released repository and save it as
           updates-release.xml:
                  **repo-rss -f updates-released.xml updates-released**
    


## FILES



           As repo-rss uses YUM libraries for retrieving all the information,
           it relies on YUM configuration for its default values like which
           repositories to use. Consult YUM documentation for details:
    
           /etc/yum.conf
           /etc/yum/repos.d/
           /var/cache/yum/
    


## BUGS



           There are of course no bugs, but should you find any, you should
           first consult the FAQ section on http://yum.baseurl.org/wiki/Faq
           and if unsuccessful in finding a resolution contact the mailing
           list: yum-devel@lists.baseurl.org.  To file a bug use
           http://bugzilla.redhat.com for Fedora/RHEL/Centos related bugs and
           http://yum.baseurl.org/report for all other bugs.
    


* * *