tripathysagar/man_text huggingface dataset:
# perf-kmem

## NAME



           perf-kmem - Tool to trace/measure kernel memory properties
    


## SYNOPSIS



           _perf kmem_ [<options>] {record|stat}
    


## DESCRIPTION



           There are two variants of perf kmem:
    
               'perf kmem [<options>] record [<perf-record-options>] <command>' to
               record the kmem events of an arbitrary workload. Additional 'perf
               record' options may be specified after record, such as '-o' to
               change the output file name.
    
               'perf kmem [<options>] stat' to report kernel memory statistics.
    


## OPTIONS



           -i <file>, --input=<file>
               For stat, select the input file (default: perf.data unless
               stdin is a fifo)
    
           -f, --force
               Don’t do ownership validation
    
           -v, --verbose
               Be more verbose. (show symbol address, etc)
    
           --caller
               Show per-callsite statistics
    
           --alloc
               Show per-allocation statistics
    
           -s <key[,key2...]>, --sort=<key[,key2...]>
               Sort the output (default: _frag,hit,bytes_ for slab and
               _bytes,hit_ for page). Available sort keys are _ptr, callsite,_
               _bytes, hit, pingpong, frag_ for slab and _page, callsite, bytes,_
               _hit, order, migtype, gfp_ for page. This option should be
               preceded by one of the mode selection options - i.e. --slab,
               --page, --alloc and/or --caller.
    
           -l <num>, --line=<num>
               Print n lines only
    
           --raw-ip
               Print raw ip instead of symbol
    
           --slab
               Analyze SLAB allocator events.
    
           --page
               Analyze page allocator events
    
           --live
               Show live page stat. The perf kmem shows total allocation stat
               by default, but this option shows live (currently allocated)
               pages instead. (This option works with --page option only)
    
           --time=<start>,<stop>
               Only analyze samples within given time window: <start>,<stop>.
               Times have the format seconds.microseconds. If start is not
               given (i.e., time string is _,x.y_) then analysis starts at the
               beginning of the file. If stop time is not given (i.e, time
               string is _x.y,_) then analysis goes to end of file.
    


* * *
# pcp-geolocate

## NAME



           **pcp-geolocate** - discover collector system geographical labels
    


## SYNOPSIS



           **pcp geolocate**
    


## DESCRIPTION



           **pcp-geolocate** reports the latitude and longitude for the local
           Performance Co-Pilot collector host in JSON format.  This
           geolocation information is sourced from the cache file
           _$PCP_SYSCONF_DIR/labels/optional/geolocate_ if it exists, else an
           attempt is made to perform geolocation based on the host IP
           address, via several online sources (REST APIs).
    
           The output from this command is suited for storing as metric
           labels by saving it to the cache file mentioned above.
    
           The opt-in systemd(1) service unit file for this command provides
           an automated location discovery for PCP metric labels.
    


## METRIC LABELS



           The JSON output is the preferred format for storing geographical
           location as PCP metric labels.  Every PCP metric available from
           this host will be tagged with the labels for latitude and
           longitude, enabling tools that make use of this such as the
           Grafana geomap panel.
    
           For more information about metric labels refer to the pmcd(1),
           pminfo(1), pmlogger(1) and pmLookupLabels(3) manual entries.
    


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


* * *
# git-update-server-info

## NAME



           git-update-server-info - Update auxiliary info file to help dumb
           servers
    


## SYNOPSIS



           _git update-server-info_ [-f | --force]
    


## DESCRIPTION



           A dumb server that does not do on-the-fly pack generations must
           have some auxiliary information files in $GIT_DIR/info and
           $GIT_OBJECT_DIRECTORY/info directories to help clients discover
           what references and packs the server has. This command generates
           such auxiliary files.
    


## OPTIONS



           -f, --force
               Update the info files from scratch.
    


## OUTPUT



           Currently the command updates the following files. Please see
           gitrepository-layout(5) for a description of what they are for:
    
           •   objects/info/packs
    
           •   info/refs
    


## GIT



           Part of the git(1) suite
    


* * *
# pcap-config

## NAME



           pcap-config - write libpcap compiler and linker flags to standard
           output
    


## SYNOPSIS



           **pcap-config**[ **--help**] [ **--version**] [ **--cflags**]
                       [ **--libs** | **--additional-libs**]
                       [ **--static** | **--static-pcap-only**]
    


## DESCRIPTION



           _pcap-config_  writes  to  the  standard output various compiler and
           linker flags required to build a user program  with  libpcap.   By
           default,   it   writes  flags  appropriate  for  building  with  a
           dynamically-linked  version  of  libpcap;  see  below  for  static
           linking.   Depending  on  the manner of libpcap installation, some
           options or their combinations may produce empty output -  this  is
           by design.
    


## OPTIONS



           **--help** Produce a help message and exit.
    
           **--version**
                  Produce libpcap version and exit.  The version is the
                  contents of _VERSION_ file in libpcap source tree rather than
                  the result of **pcap_lib_version**(3PCAP).
    
           **--cflags**
                  Produce the **-I** compiler flag required to include libpcap's
                  header files.
    
           **--libs** Produce the **-L** and **-l** linker flags required to link with
                  libpcap, including **-l** flags for libraries required by
                  libpcap.
    
           **--additional-libs**
                  Produce the **-L** and **-l** linker flags for libraries required
                  by libpcap, but not the **-l** flag to link with libpcap
                  itself.
    
           **--static**
                  This option causes **--libs** and **--additional-libs** to produce
                  linker flags appropriate for static linking with libpcap.
    
           **--static-pcap-only**
                  This option causes **--libs** and **--additional-libs** to produce
                  linker flags appropriate for static linking with libpcap
                  and dynamic linking with all other libraries, including
                  libraries required by libpcap.
    


## EXIT STATUS



           _pcap-config_ exits with a non-zero status when invoked with an
           invalid command-line option, and with status 0 otherwise.
    


## BACKWARD COMPATIBILITY



           The **--version** flag became available in libpcap release 1.10.3.
    
           Before libpcap release 1.10.2 _pcap-config_ did not treat invalid
           command-line options as an error. The **--static-pcap-only** flag
           became available in libpcap release 1.10.2.
    
           The **--static** flag became available in libpcap release 1.1.0.
    


* * *
# git-upload-archive

## NAME



           git-upload-archive - Send archive back to git-archive
    


## SYNOPSIS



           _git upload-archive_ <repository>
    


## DESCRIPTION



           Invoked by _git archive --remote_ and sends a generated archive to
           the other end over the Git protocol.
    
           This command is usually not invoked directly by the end user. The
           UI for the protocol is on the _git archive_ side, and the program
           pair is meant to be used to get an archive from a remote
           repository.
    


## SECURITY



           In order to protect the privacy of objects that have been removed
           from history but may not yet have been pruned, **git-upload-archive**
           avoids serving archives for commits and trees that are not
           reachable from the repository’s refs. However, because calculating
           object reachability is computationally expensive,
           **git-upload-archive** implements a stricter but easier-to-check set
           of rules:
    
            1. Clients may request a commit or tree that is pointed to
               directly by a ref. E.g., **git archive --remote=origin v1.0**.
    
            2. Clients may request a sub-tree within a commit or tree using
               the **ref:path** syntax. E.g., **git archive --remote=origin**
               **v1.0:Documentation**.
    
            3. Clients may _not_ use other sha1 expressions, even if the end
               result is reachable. E.g., neither a relative commit like
               **master^** nor a literal sha1 like **abcd1234** is allowed, even if
               the result is reachable from the refs.
    
           Note that rule 3 disallows many cases that do not have any privacy
           implications. These rules are subject to change in future versions
           of git, and the server accessed by **git archive --remote** may or may
           not follow these exact rules.
    
           If the config option **uploadArchive.allowUnreachable** is true, these
           rules are ignored, and clients may use arbitrary sha1 expressions.
           This is useful if you do not care about the privacy of unreachable
           objects, or if your object database is already publicly available
           for access via non-smart-http.
    


## OPTIONS



           <repository>
               The repository to get a tar archive from.
    


## GIT



           Part of the git(1) suite
    


* * *
# pmdaslurm

## NAME



           **pmdaslurm** - SLURM statistics performance metrics domain agent
           (PMDA)
    


## DESCRIPTION



           **pmdaslurm** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values from the slurm perlapi interface to provide
           information on slurm jobs, nodes and users.
    


## INSTALLATION



           Install the slurm PMDA by using the Install script as root:
    
               **# cd $PCP_PMDAS_DIR/slurm**
               **# ./Install**
    
           To uninstall, do the following as root:
    
               **# cd $PCP_PMDAS_DIR/slurm**
               **# ./Remove**
    
           **pmdaslurm** is launched by pmcd(1) and should never be executed
           directly. The Install and Remove scripts notify pmcd(1) when the
           agent is installed or removed.
    


## FILES



           **$PCP_PMDAS_DIR/slurm/Install**
               installation script for the **pmdaslurm** agent
    
           **$PCP_PMDAS_DIR/slurm/Remove**
               undo installation script for the **pmdaslurm** agent
    
           **$PCP_LOG_DIR/pmcd/slurm.log**
               default log file for error messages from **pmdaslurm**
    


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


* * *
# git-stripspace

## NAME



           git-stripspace - Remove unnecessary whitespace
    


## SYNOPSIS



           _git stripspace_ [-s | --strip-comments]
           _git stripspace_ [-c | --comment-lines]
    


## DESCRIPTION



           Read text, such as commit messages, notes, tags and branch
           descriptions, from the standard input and clean it in the manner
           used by Git.
    
           With no arguments, this will:
    
           •   remove trailing whitespace from all lines
    
           •   collapse multiple consecutive empty lines into one empty line
    
           •   remove empty lines from the beginning and end of the input
    
           •   add a missing _\n_ to the last line if necessary.
    
           In the case where the input consists entirely of whitespace
           characters, no output will be produced.
    
           **NOTE** : This is intended for cleaning metadata. Prefer the
           **--whitespace=fix** mode of git-apply(1) for correcting whitespace of
           patches or files in the repository.
    


## OPTIONS



           -s, --strip-comments
               Skip and remove all lines starting with a comment character
               (**core.commentChar** , default #).
    
           -c, --comment-lines
               Prepend the comment character and a blank space to each line.
               Lines will automatically be terminated with a newline. On
               empty lines, only the comment character will be prepended.
    


## EXAMPLES



           Given the following noisy input with _$_ indicating the end of a
           line:
    
               |A brief introduction   $
               |   $
               |$
               |A new paragraph$
               |# with a commented-out line    $
               |explaining lots of stuff.$
               |$
               |# An old paragraph, also commented-out. $
               |      $
               |The end.$
               |  $
    
           Use _git stripspace_ with no arguments to obtain:
    
               |A brief introduction$
               |$
               |A new paragraph$
               |# with a commented-out line$
               |explaining lots of stuff.$
               |$
               |# An old paragraph, also commented-out.$
               |$
               |The end.$
    
           Use _git stripspace --strip-comments_ to obtain:
    
               |A brief introduction$
               |$
               |A new paragraph$
               |explaining lots of stuff.$
               |$
               |The end.$
    


## GIT



           Part of the git(1) suite
    


* * *
# git-show-index

## NAME



           git-show-index - Show packed archive index
    


## SYNOPSIS



           _git show-index_ [--object-format=<hash-algorithm>] < <pack-idx-file>
    


## DESCRIPTION



           Read the **.idx** file for a Git packfile (created with
           git-pack-objects(1) or git-index-pack(1)) from the standard input,
           and dump its contents. The output consists of one object per line,
           with each line containing two or three space-separated columns:
    
           •   the first column is the offset in bytes of the object within
               the corresponding packfile
    
           •   the second column is the object id of the object
    
           •   if the index version is 2 or higher, the third column contains
               the CRC32 of the object data
    
           The objects are output in the order in which they are found in the
           index file, which should be (in a correctly constructed file)
           sorted by object id.
    
           Note that you can get more information on a packfile by calling
           git-verify-pack(1). However, as this command considers only the
           index file itself, it’s both faster and more flexible.
    


## OPTIONS



           --object-format=<hash-algorithm>
               Specify the given object format (hash algorithm) for the index
               file. The valid values are _sha1_ and (if enabled) _sha256_. The
               default is the algorithm for the current repository (set by
               **extensions.objectFormat**), or _sha1_ if no value is set or
               outside a repository..
    
               Note: At present, there is no interoperability between SHA-256
               repositories and SHA-1 repositories.
    
           Historically, we warned that SHA-256 repositories may later need
           backward incompatible changes when we introduce such
           interoperability features. Today, we only expect compatible
           changes. Furthermore, if such changes prove to be necessary, it
           can be expected that SHA-256 repositories created with today’s Git
           will be usable by future versions of Git without data loss.
    


## GIT



           Part of the git(1) suite
    


* * *
# dh_computeautosubstvars

## NAME



           dh_gencontrol - generate and install control file
    


## SYNOPSIS



           **dh_computeautosubstvars**[_debhelper options_] [**--**_params_]
    


## DESCRIPTION



           **dh_computeautosubstvars** is a debhelper program that is responsible
           for computing substvars relevant to most packages. It needs to be
           run before **dh_gencontrol** but after all the content has been added
           into the package staging directory (**debian/_package_ /**).
    
           Note that this command generally assumes compat 14 or later where
           **dh_gencontrol** will apply relationship substvars automatically. It
           can be used in older compat levels but the substvars will not be
           used automatically in that case.
    


## OPTIONS



           This helper only accepts standard **debhelper** options. Please refer
           to debhelper(7) for these.
    


* * *
# flatpak-build-import-bundle

## NAME



           flatpak-build-import-bundle - Import a file bundle into a local
           repository
    


## SYNOPSIS



    
           **flatpak build-import-bundle**[OPTION...] LOCATION FILENAME
    


## DESCRIPTION



           Imports a bundle from a file named FILENAME into the repository at
           LOCATION.
    
           The format of the bundle file is that generated by build-bundle.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    
           **--ref=REF**
               Override the ref specified in the bundle.
    
           **--oci**
               Import an OCI image instead of a Flatpak bundle.
    
           **--update-appstream**
               Update the appstream branch after the build.
    
           **--no-update-summary**
               Don't update the summary file after the new commit is added.
               This means the repository will not be useful for serving over
               http until build-update-repo has been run. This is useful is
               you want to do multiple repo operations before finally
               updating the summary.
    
           **--gpg-sign=KEYID**
               Sign the commit with this GPG key. This option can be used
               multiple times.
    
           **--gpg-homedir=PATH**
               GPG Homedir to use when looking for keyrings
    


* * *
# perf-help

## NAME



           perf-help - display help information about perf
    


## SYNOPSIS



           _perf help_ [-a|--all] [COMMAND]
    


## DESCRIPTION



           With no options and no COMMAND given, the synopsis of the _perf_
           command and a list of the most commonly used perf commands are
           printed on the standard output.
    
           If the option _--all_ or _-a_ is given, then all available commands
           are printed on the standard output.
    
           If a perf command is named, a manual page for that command is
           brought up. The _man_ program is used by default for this purpose,
           but this can be overridden by other options or configuration
           variables.
    
           Note that perf --help ... is identical to perf help ... because
           the former is internally converted into the latter.
    


## OPTIONS



           -a, --all
               Prints all the available commands on the standard output. This
               option supersedes any other option.
    


## PERF



           Part of the perf(1) suite
    


* * *
# wsrep_sst_common

## NAME



           wsrep_sst_common - common command line parser to be sourced by
           other SST scripts
    


## DESCRIPTION



           Use: Common command line parser to be sourced by other SST
           scripts.
    
           For more information, please refer to the MariaDB Knowledge Base,
           available online at https://mariadb.com/kb/
    


* * *
# nl

## NAME



           nl - number lines of files
    


## SYNOPSIS



           **nl**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Write each FILE to standard output, with line numbers added.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-b** , **--body-numbering** =_STYLE_
                  use STYLE for numbering body lines
    
           **-d** , **--section-delimiter** =_CC_
                  use CC for logical page delimiters
    
           **-f** , **--footer-numbering** =_STYLE_
                  use STYLE for numbering footer lines
    
           **-h** , **--header-numbering** =_STYLE_
                  use STYLE for numbering header lines
    
           **-i** , **--line-increment** =_NUMBER_
                  line number increment at each line
    
           **-l** , **--join-blank-lines** =_NUMBER_
                  group of NUMBER empty lines counted as one
    
           **-n** , **--number-format** =_FORMAT_
                  insert line numbers according to FORMAT
    
           **-p** , **--no-renumber**
                  do not reset line numbers for each section
    
           **-s** , **--number-separator** =_STRING_
                  add STRING after (possible) line number
    
           **-v** , **--starting-line-number** =_NUMBER_
                  first line number for each section
    
           **-w** , **--number-width** =_NUMBER_
                  use NUMBER columns for line numbers
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Default options are: **-bt -d** '\:' **-fn -hn -i1 -l1 -n** 'rn' **-s** <TAB> **-v1**
           **-w6**
    
           CC are two delimiter characters used to construct logical page
           delimiters; a missing second character implies ':'.  As a GNU
           extension one can specify more than two characters, and also
           specifying the empty string (**-d** '') disables section matching.
    
           STYLE is one of:
    
           a      number all lines
    
           t      number only nonempty lines
    
           n      number no lines
    
           pBRE   number only lines that contain a match for the basic
                  regular expression, BRE
    
           FORMAT is one of:
    
           ln     left justified, no leading zeros
    
           rn     right justified, no leading zeros
    
           rz     right justified, leading zeros
    


* * *
# pmdacifs

## NAME



           **pmdacifs** - Common Internet Filesystem (CIFS) PMDA
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/cifs/pmdacifs**[**-D** _debug_]
    


## DESCRIPTION



           **pmdacifs** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values about mounted CIFS shares from the
           /proc/fs/cifs directory. This PMDA requires at least the CIFS
           kernel module to be loaded to return some metric values and at
           least one mounted CIFS share in order to provide data for all
           metrics.
    


## INSTALLATION



           Install the CIFS PMDA by using the Install script as root:
    
               **# cd $PCP_PMDAS_DIR/cifs**
               **# ./Install**
    
           To uninstall, the following must be done as root:
    
               **# cd $PCP_PMDAS_DIR/cifs**
               **# ./Remove**
    
           **pmdacifs** is launched by pmcd(1) and should never be executed
           directly.  The Install and Remove scripts notify **pmcd** when the
           agent is installed or removed.
    


## FILES



           **$PCP_PMDAS_DIR/cifs/help**
               default help text file for the CIFS metrics
    
           **$PCP_PMDAS_DIR/cifs/Install**
               installation script for the **pmdacifs** agent
    
           **$PCP_PMDAS_DIR/cifs/Remove**
               undo installation script for the **pmdacifs** agent
    
           **$PCP_LOG_DIR/pmcd/cifs.log**
               default log file for error messages from **pmdacifs**
    


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


## 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_installlogrotate

## NAME



           dh_installlogrotate - install logrotate config files
    


## SYNOPSIS



           **dh_installlogrotate**[_debhelper options_] [**--name=**_name_]
    


## DESCRIPTION



           **dh_installlogrotate** is a debhelper program that is responsible for
           installing logrotate config files into _etc/logrotate.d_ in package
           build directories.  Files named _debian/package.logrotate_ are
           installed.
    


## OPTIONS



           **--name=**_name_
               Look for files named _debian/package.name.logrotate_ and install
               them as _etc/logrotate.d/name_ , instead of using the usual files
               and installing them as the package name.
    


* * *
# nfsvis

## NAME



           **nfsvis** - visualize performance of NFS statistics
    


## SYNOPSIS



           **nfsvis**[**-V**] [**-c** _version_] [**-m** _maxrate_] [**-s** _version_] [_pmview_
           _options_]
    


## DESCRIPTION



           **nfsvis** displays a three dimensional bar chart of NFS request
           statistics.  The display is updated with new values retrieved from
           the target _host_ or _archive_ every _interval_ seconds (default is 2
           seconds).
    
           Two blocks of statistics are displayed - one for the NFS server
           and one for the NFS client requests.  The height of the bars is
           proportional to the rate at which the various request types are
           processed.
    
           **nfsvis** generates a pmview(1) configuration file, and passes most
           command line options to pmview(1).  Therefore, the command line
           options **-A** , **-a** , **-C** , **-h** , **-n** , **-O** , **-p** , **-S** , **-t** , **-T** , **-Z** and **-z** , and the
           user interface are described in the pmview(1) man page.
    


## COMMAND LINE OPTIONS



           The **nfsvis** specific options are:
    
           **-c** Monitor NFS _version_ 2 or 3 client metrics.  The default is
                  version 2.
    
           **-m** Use _maxrate_ as the maximum NFS request rate over all
                  classes of request, from which the height of the bars is
                  computed.  This effectively specifies the height at which
                  bars will be clipped.
    
           **-s** Monitor NFS _version_ 2 or 3 server metrics.  The default is
                  version 2.
    
           **-V** Verbose mode - output the generated pmview(1) configuration
                  file.
    


## FILES



           **$PCP_VAR_DIR/config/pmlogger/config.nfsvis**
                  A pmlogger(1) configuration file for **nfsvis** metrics.
           **$PCP_SHARE_DIR/lib/pmview-args**
                  Shell procedures for parsing pmview(1) command line
                  options.
    


## 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**(4).
    


* * *
# dpkg-buildtree

## NAME



           dpkg-buildtree - helper for build tree operations during package
           builds
    


## SYNOPSIS



           **dpkg-buildtree**[_option_...] [_command_]
    


## DESCRIPTION



           **dpkg-buildtree** is a tool to perform common operations on the build
           tree for a source package.
    
           This program was introduced in dpkg 1.22.3.
    


## COMMANDS



           **clean**
               Removes all artifacts generated during a build by the various
               dpkg tools, and pathnames used or controlled by dpkg tools
               that are safe to clean.  These files are used to track state
               between package build runs, and are in many cases internal
               implementation details the packager should not be concerned
               about, or are staging directories containing build artifacts.
    
           **is-rootless**
               Checks whether the build tree can be built with no root
               privileges (since dpkg 1.22.12).
    
               This command can be used safely even with versions where the
               command was not yet available as the default will then be the
               historic one where root was required.
    
           **--help**
               Show the usage message and exit.
    
           **--version**
               Show the version and exit.
    


## ENVIRONMENT



           **DPKG_COLORS**
               Sets the color mode.  The currently accepted values are: **auto**
               (default), **always** and **never**.
    
           **DPKG_NLS**
               If set, it will be used to decide whether to activate Native
               Language Support, also known as internationalization (or i18n)
               support.  The accepted values are: **0** and **1**(default).
    


## FILES



       **Cleaned files**
           _debian/files_
           _debian/files.new_
               Files generated by dpkg-distaddfile(1).
    
           _debian/substvars_
           _debian/substvars.new_
               Files generated by dpkg-shlibdeps(1).
    
           _debian/tmp_
               Staging directory containing the contents to be used when
               creating a package.  Both dpkg-gencontrol(1) and
               dpkg-gensymbols(1) generate files within.
    


## EXAMPLES



       **Usage in debian/rules**
           You can call **dpkg-buildtree clean** from the _debian/rules_ **clean**
           target, after having performed other necessary cleanups.
    
           For example for an autoconf-like build system:
    
             clean:
                   [ ! -f Makefile ] || $(MAKE) distclean
                   dpkg-buildtree clean
    


* * *
# unicode_start

## NAME



           unicode_start - put keyboard and console in unicode mode
    


## SYNOPSIS



           **unicode_start**[_font_ [_umap_]]
    


## DESCRIPTION



           The **unicode_start** command will put the keyboard and console into
           Unicode (UTF-8) mode.
    
           For the keyboard this means that one can attach 16-bit U+xxxx
           values to keyboard keys using loadkeys(1), and have these appear
           as UTF-8 input to user programs.  Also, that one can type
           hexadecimal Alt-xxxx using the numeric keypad, and again produce
           UTF-8.
    
           For the console this means that the kernel expects UTF-8 output
           from user programs, and displays the output accordingly.
    
           The parameter _font_ is a font that is loaded. It should have a
           built-in Unicode map, or, if it hasn't, such a map can be given
           explicitly as second parameter.  When no font was specified, the
           current font is kept.
    


## NOTE



           Unicode mode is a parameter with a value per virtual console.
           However, usually the font and keymap is common to all consoles.
    


* * *
# pmdadbping

## NAME



           **pmdadbping** - database response time and availability PMDA
    


## DESCRIPTION



           **pmdadbping** is a database response time measurement PMDA.
    
           **pmdadbping** runs dbprobe(1), and exports the performance
           measurements it makes available as PCP metrics.
    
           dbprobe(1) should be configured to use the type of DBI appropriate
           for the local database, which includes: RDBMS flavour,
           user/password, delay between "ping" requests, and the SQL
           statement to use.
    


## INSTALLATION



           Configure dbprobe(1) - it uses a configuration file from (in this
           order):
    
           •   /etc/pcpdbi.conf
    
           •   $PCP_PMDAS_DIR/dbping/dbprobe.conf
    
           This file can contain overridden values (Perl code) for the
           settings listed at the start of _dbprobe.pl_ , namely:
    
           •   database name (see **DBI**(3) for details)
    
           •   database user name
    
           •   database pass word
    
           •   SQL statement to measure (probe)
    
           •   delay between probes
    
           Once this is setup, you can access the names and values for the
           dbping performance metrics by doing the following as root:
    
               **# cd $PCP_PMDAS_DIR/dbping**
               **# ./Install**
    
           To uninstall, the following must be done as root:
    
               **# cd $PCP_PMDAS_DIR/dbping**
               **# ./Remove**
    
           **pmdadbping** is launched by pmcd(1) and should never be executed
           directly. The Install and Remove scripts notify pmcd(1) when the
           agent is installed or removed.
    


## FILES



           **$PCP_PMDAS_DIR/dbping/dbprobe.conf**
               probe configuration file for _dbprobe_(1), used indirectly by
               **pmdadbping**
    
           **$PCP_PMDAS_DIR/dbping/Install**
               installation script for the **pmdadbping** agent
    
           **$PCP_PMDAS_DIR/dbping/Remove**
               undo installation script for the **pmdadbping** agent
    
           **$PCP_LOG_DIR/pmcd/dbping.log**
               default log file for error messages from **pmdadbping**
    


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


* * *
# git-credential-cache--daemon

## NAME



           git-credential-cache--daemon - Temporarily store user credentials
           in memory
    


## SYNOPSIS



           _git credential-cache--daemon_ [--debug] <socket-path>
    


## DESCRIPTION



               **Note**
    
               You probably don’t want to invoke this command yourself; it is
               started automatically when you use git-credential-cache(1).
    
           This command listens on the Unix domain socket specified by
           _< socket-path>_ for **git-credential-cache** clients. Clients may store
           and retrieve credentials. Each credential is held for a timeout
           specified by the client; once no credentials are held, the daemon
           exits.
    
           If the **--debug** option is specified, the daemon does not close its
           stderr stream, and may output extra diagnostics to it even after
           it has begun listening for clients.
    


## GIT



           Part of the git(1) suite
    


* * *
# dbprobe

## NAME



           **dbprobe** - database response time and availability information
    


## SYNOPSIS



           **dbprobe.pl**[_delay_]
    


## DESCRIPTION



           The **dbprobe** utility is used by pmdadbping(1) to measure response
           time from a database.  A given query is executed on the database
           at the requested interval (_delay_ , which defaults to 60 seconds).
           This response time measure can be exported via the Performance Co-
           Pilot framework for live and historical monitoring using
           _pmdadbping_(1).
    


* * *
# lsusb.py

## NAME



           lsusb.py - list USB devices
    


## SYNOPSIS



           **lsusb.py**[ _options_ ]
    


## DESCRIPTION



           **lsusb.py** is a utility for displaying information about USB buses
           in the system and the devices connected to them. It uses the
           **usb.ids** file to associate a human-readable name to the vendor and
           product IDs.
    
           In comparison with lsusb(8), this program can display additional
           information such as the interface speed of a device, and details
           of a device's interfaces including the driver bound to them and
           Linux devices provided by the driver, and the details of device
           and interface endpoints.
    


## OPTIONS



           **-h** , **--help**
                  Displays options supported by **lsusb**(1).
    
           **-i** , **--interfaces**
                  Display information about the interfaces of each device,
                  excluding hubs.
    
           **-I** , **--hub-interfaces**
                  Display information about the interfaces of each device,
                  including hubs., excluding hubs.
    
           **-u** , **--hide-empty-hubs**
                  Suppress information about hubs that have no devices
                  connected.
    
           **-U** , **--hide-hubs**
                  Suppress information about hubs, even if they have devices
                  connected.
    
           **-c** , **--color**
                  Use color
    
           **-C** , **--no-color**
                  Don't use color
    
           **-e** , **--endpoints**
                  Include information about device (and interface, with **-i**)
                  endpoints.
    
           **-f** , **--usbids-path**
                  Overrides the path of the **usb.ids** file.
    


* * *
# nohup

## NAME



           nohup - run a command immune to hangups, with output to a non-tty
    


## SYNOPSIS



           **nohup** _COMMAND_ [_ARG_]...
           **nohup** _OPTION_
    


## DESCRIPTION



           Run COMMAND, ignoring hangup signals.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           If standard input is a terminal, redirect it from an unreadable
           file.  If standard output is a terminal, append output to
           'nohup.out' if possible, '$HOME/nohup.out' otherwise.  If standard
           error is a terminal, redirect it to standard output.  To save
           output to FILE, use 'nohup COMMAND > FILE'.
    
           Your shell may have its own version of nohup, which usually
           supersedes the version described here.  Please refer to your
           shell's documentation for details about the options it supports.
    
       **Exit status:**
           125    if the nohup command itself fails
    
           126    if COMMAND is found but cannot be invoked
    
           127    if COMMAND cannot be found
    
           -      the exit status of COMMAND otherwise
    


* * *
# debuginfo-install

## NAME



           debuginfo-install - install debuginfo packages and their
           dependencies
    


## SYNOPSIS



           **debuginfo-install** package
    


## DESCRIPTION



           **debuginfo-install** is a program which installs the RPMs needed to
           debug the specified package.  The package argument can be a
           wildcard, but will only match installed packages.  **debuginfo-**
           **install** will then enable any debuginfo repositories, and install
           the relevant debuginfo rpm.
    


## EXAMPLES



           Download and install all the RPMs needed to debug the kernel RPM:
                  **debuginfo-install** kernel
    


## WARNING MESSAGES



           Could not find debuginfo for:
                  You may sometimes see warning messages about certain
                  packages not being found if you run debuginfo-install for a
                  wildcard or glob. Debuginfo packages are not necessary for
                  "noarch" RPMs; these will generate a warning message.
                  Additionally, On 64-bit systems, no multilib debuginfo
                  packages are published, so if you have 32-bit packages
                  installed, these will also generate warning messages.
    


## FILES



           As debuginfo-install 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.
    


* * *
# wsrep_sst_mysqldump

## NAME



           wsrep_sst_mysqldump - mysqldump-based state snapshot transfer
    


## DESCRIPTION



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


* * *
# pathchk

## NAME



           pathchk - check whether file names are valid or portable
    


## SYNOPSIS



           **pathchk**[_OPTION_]... _NAME_...
    


## DESCRIPTION



           Diagnose invalid or non-portable file names.
    
           **-p** check for most POSIX systems
    
           **-P** check for empty names and leading "-"
    
           **--portability**
                  check for all POSIX systems (equivalent to **-p -P**)
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# dh_perl

## NAME



           dh_perl - calculates Perl dependencies and cleans up after
           MakeMaker
    


## SYNOPSIS



           **dh_perl**[_debhelper options_] [**-d**] [_library dirs_ ...]
    


## DESCRIPTION



           **dh_perl** is a debhelper program that is responsible for generating
           the **${perl:Depends}** substitutions and adding them to substvars
           files.
    
           The program will look at Perl scripts and modules in your package,
           and will use this information to generate a dependency on **perl** or
           **perlapi**. The dependency will be substituted into your package's
           _control_ file wherever you place the token **${perl:Depends}**.
    
           **dh_perl** also cleans up empty directories that MakeMaker can
           generate when installing Perl modules.
    


## OPTIONS



           **-d** In some specific cases you may want to depend on **perl-base**
               rather than the full **perl** package. If so, you can pass the -d
               option to make **dh_perl** generate a dependency on the correct
               base package. This is only necessary for some packages that
               are included in the base system.
    
               Note that this flag may cause no dependency on **perl-base** to be
               generated at all. **perl-base** is Essential, so its dependency
               can be left out, unless a versioned dependency is needed.
    
           **-V** By default, scripts and architecture independent modules don't
               depend on any specific version of **perl**. The **-V** option causes
               the current version of the **perl**(or **perl-base** with **-d**) package
               to be specified.
    
           _library dirs_
               If your package installs Perl modules in non-standard
               directories, you can make **dh_perl** check those directories by
               passing their names on the command line. It will only check
               the _vendorlib_ and _vendorarch_ directories by default.
    


## CONFORMS TO



           Debian policy, version 3.8.3
    
           Perl policy, version 1.20
    


* * *
# manconv

## NAME



           manconv - convert manual page from one encoding to another
    


## SYNOPSIS



           **manconv -f**[_from-code_[:_from-code_...]] **-t** _to-code_ [**-dqhV**]
           [_filename_]
    


## DESCRIPTION



           **manconv** converts a manual page from one encoding to another, like
           **iconv**.  Unlike **iconv** , it can try multiple possible input encodings
           in sequence.  This is useful for manual pages installed in
           directories without an explicit encoding declaration, since they
           may be in UTF-8 or in a legacy character set.
    
           If an encoding declaration is found on the first line of the
           manual page, that declaration overrides any input encodings
           specified on **manconv** 's command line.  Encoding declarations have
           the following form:
    
                  '\" -*- coding: UTF-8 -*-
    
           or (if manual page preprocessors are also to be declared):
    
                  '\" t -*- coding: ISO-8859-1 -*-
    


## OPTIONS



           **-f** _encodings_ , **--from-code** _encodings_
                  Try each of _encodings_ (a colon-separated list) in sequence
                  as the input encoding.  The default is to guess likely
                  input encodings based on the file name.
    
           **-t** _encoding_ , **--to-code** _encoding_
                  Convert the manual page to _encoding_.
    
           **-q** , **--quiet**
                  Do not issue error messages when the page cannot be
                  converted.
    
           **-d** , **--debug**
                  Print debugging information.
    
           **-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
    


* * *
# yes

## NAME



           yes - output a string repeatedly until killed
    


## SYNOPSIS



           **yes**[_STRING_]...
           **yes** _OPTION_
    


## DESCRIPTION



           Repeatedly output a line with all specified STRING(s), or 'y'.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *