tripathysagar/man_text huggingface dataset:
# sha256sum

## NAME



           sha256sum - compute and check SHA256 message digest
    


## SYNOPSIS



           **sha256sum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or check SHA256 (256-bit) checksums.
    
           With no FILE, or when FILE is -, read standard input.
    
           **-b** , **--binary**
                  read in binary mode
    
           **-c** , **--check**
                  read checksums from the FILEs and check them
    
           **--tag** create a BSD-style checksum
    
           **-t** , **--text**
                  read in text mode (default)
    
           **-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
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           The sums are computed as described in FIPS-180-2.  When checking,
           the input should be a former output of this program.  The default
           mode is to print a line with: checksum, a space, a character
           indicating input mode ('*' for binary, ' ' for text or where
           binary is insignificant), and name for each FILE.
    
           There is no difference between binary mode and text mode on GNU
           systems.
    


* * *
# stg-uncommit

## NAME



           stg-uncommit - Convert regular Git commits into StGit patches
    


## SYNOPSIS



           _stg uncommit_ <patchname-1> [<patchname-2> ...]
           _stg uncommit_ -n number [<patchname-prefix>]
           _stg uncommit_ -t <committish> [-x]
    


## DESCRIPTION



           Convert one or more Git commits from the base of the current stack
           into StGit patches. The original Git commits are not modified; the
           StGit stack extends to incorporate these commits as the bottommost
           applied patches. This is the opposite of stg-commit(1).
    
           By default, the number of patches to uncommit is determined by the
           number of patch names provided on the command line. The first
           provided name is used for the first patch to uncommit, i.e. for
           the newest patch.
    
           The -n/--number option specifies the number of patches to
           uncommit. In this case, at most one patch name may be specified.
           It is used as prefix to which the patch number is appended. If no
           patch names are provided on the command line, StGit automatically
           generates names based on the first lines of the commit messages.
    
           The -t/--to option specifies that all commits up to and including
           the given commit should be uncommitted. The -x/--exclusive option
           may be used to exclude the "to" commit.
    
           Only commits with exactly one parent can be uncommitted; in other
           words, merge commits may not be uncommitted.
    


## OPTIONS



           -n <number>, --number=<number>
               Uncommit the specified number of commits
    
           -t <committish>, --to=<committish>
               Uncommit to the specified committish
    
           -x, --exclusive
               Exclude the commit specified by the _--to_ option
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# show-changed-rco

## NAME



           show-changed-rco - show changes in an RPM package
    


## SYNOPSIS



           **show-changed-rco**[options]
    


## DESCRIPTION



           **show-changed-rco** gives a compact description of the changes to a
           packages Requires, Conflicts and Obsoletes data from the installed
           (or old) to a specified rpm file.
    


## OPTIONS



           **-h, --help**
                  show this help message and exit
    
           **-C, --cache**
                  Tells repoquery to run entirely from YUM cache - does not
                  download any metadata or update the cache. Queries in this
                  mode can fail or give partial/incorrect results if the
                  cache isn't fully populated beforehand with eg "yum
                  makecache".
    
           **-c <config file>, --config=<config file>**
                  Use alternative config file (default is /etc/yum.conf).
    
           **--repoid= <repo>**
                  Specify which repository to query. Using this option
                  disables all repositories not explicitly enabled with
                  --repoid option (can be used multiple times). By default
                  repoquery uses whatever repositories are enabled in YUM
                  configuration.
    
           **--enablerepo= <repo>**
                  In addition to the default set, query the given additional
                  repository, even if it is disabled in YUM configuration.
                  Can be used multiple times.
    
           **--disablerepo= <repo>**
                  Do not query the given repository, even if it is enabled in
                  YUM configuration.  Can be used multiple times.
    
           **--repofrompath= <repoid>,<path/url>**
                  Specify a path or url to a repository (same path as in a
                  baseurl) to add to the repositories for this query. This
                  option can be used multiple times. If you want to view only
                  the pkgs from this repository combine this with --repoid.
                  The repoid for the repository is specified by <repoid>.
    
           **--old-packages= <pkg>**
                  Explicitly list the valid old packages to match the new
                  packages against.
    
           **--ignore-arch**
                  Ignore arch. so you can compare foo-2.i686 to foo-1.x86_64.
    
           **--skip-new**
                  Only give output for packages which we've found an old
                  package for.
    


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


* * *
# icuexportdata

## NAME



           **icuexportdata** - Writes text files with Unicode properties data
           from ICU.
    


* * *
# yum-changelog

## NAME



           **yum-changelog**
    


## SYNOPSIS



           The **yum-changelog** package
    


## DESCRIPTION



           yum-changelog(1) is a Yum plugin for viewing package changelogs
           before/after updating.  yum will invoke yum-changelog(1) plugin if
           the **--changelog** option or the **changelog** command is used with yum.
    


## OPTIONS



           --changelog
                  Show changelog delta of updated packages
    


## COMMANDS



           changelog
                  Show changelog data of packages listed (same format as the
                  list command).  The first argument is required and is
                  either "all" for all the changelog entries, a date for the
                  changelog entries since a specified point in time or a
                  number for a given number of changelog entries.
    


## FILES



           _/etc/yum/pluginconf.d/changelog.conf_
                  The system wide configuration file. See
                  yum-changelog.conf(5) for more information.
    


## EXAMPLES



           # yum **changelog** 2008-Jan yum\*
           Listing changelogs since: 2008-01-18
           yum-versionlock-1.1.11-1.fc8.noarch      installed
           * Wed Jan 30 17:00:00 2008 Tim Lauridsen
           <timlau@fedoraproject.org>
           - mark as 1.1.11
           changelog stats. 33 pkgs, 12 source pkgs, 1 changelog
           # yum update ktechlab **--changelog**
           Loading "changelog" plugin
           Setting up Update Process
           Setting up repositories
           [..]
           Resolving Dependencies
           --> Populating transaction set with selected packages. Please
           wait.
           ---> Package ktechlab.i386 0:0.3-6 set to be updated
           --> Running transaction check
    
           Changes in packages about to be updated:
    
           ktechlab - 0.3-6.i386
           * Wed Nov 22 23:00:00 2006 Chitlesh Goorah - 0.3-6
           - Rebuilt due to new gpsim-devel release
    


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


## AVAILABILITY



           yum-changelog is available via:
           # yum install yum-changelog
    


* * *
# chsh

## NAME



           chsh - change your login shell
    


## SYNOPSIS



           **chsh**[**-s** _shell_] [**-l**] [**-h**] [**-V**] [_username_]
    


## DESCRIPTION



           **chsh** is used to change your login shell. If a shell is not given
           on the command line, **chsh** prompts for one.
    
           **chsh** supports non-local entries (kerberos, LDAP, etc.) if linked
           with libuser, otherwise use **ypchsh**(1), **lchsh**(1) or any other
           implementation for non-local entries.
    


## OPTIONS



           **-s** , **--shell** _shell_
               Specify your login shell.
    
           **-l** , **--list-shells**
               Print the list of shells listed in _/etc/shells_ and exit.
    
           **-h** , **--help**
               Display help text and exit. (Short option **-h** is used since
               version 2.30; older versions used the now-deprecated **-u**).
    
           **-V** , **--version**
               Display version and exit. (Short option **-V** is used since
               version 2.39; older versions used the now-deprecated **-v**).
    


## VALID SHELLS



           **chsh** will accept the full pathname of any executable file on the
           system.
    
           The default behavior for non-root users is to accept only shells
           listed in the _/etc/shells_ file, and issue a warning for root user.
           It can also be configured at compile-time to only issue a warning
           for all users.
    


## EXIT STATUS



           Returns 0 if operation was successful, 1 if operation failed or
           command syntax was not valid.
    


## AVAILABILITY



           The **chsh** command is part of the util-linux package which can be
           downloaded from Linux Kernel Archive
           <https://www.kernel.org/pub/linux/utils/util-linux/>. This page is
           part of the _util-linux_ (a random collection of Linux utilities)
           project. Information about the project can be found at 
           ⟨https://www.kernel.org/pub/linux/utils/util-linux/⟩. If you have a
           bug report for this manual page, send it to
           util-linux@vger.kernel.org. This page was obtained from the
           project's upstream Git repository
           ⟨git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git⟩ on
           2025-08-11. (At that time, the date of the most recent commit that
           was found in the repository was 2025-08-05.) If you discover any
           rendering problems in this HTML version of the page, or you
           believe there is a better or more up-to-date source for the page,
           or you have corrections or improvements to the information in this
           COLOPHON (which is _not_ part of the original manual page), send a
           mail to man-pages@man7.org
    
    util-linux 2.42-start-521-ec46  2025-08-09                        _CHSH_(1)
    


* * *
# mansect

## NAME



           mansect - print the source code of sections of manual pages
    


## SYNOPSIS



           **mansect** _section_ [_file_ ...]
    


## DESCRIPTION



           The **mansect** command prints the source code of the _section_ of the
           given manual-page files.  If no files are specified, the standard
           input is used.
    
           _section_ is a PCRE2 regular expression.
    
           The **TH** line is unconditionally printed.
    
           The output of this program is suitable for piping to the groff(1)
           pipeline.
    


## EXAMPLES



           $ **man -w strtol strtoul | xargs mansect 'NAME|SEE ALSO'** ;
           .lf 1 /usr/local/man/man3/strtol.3
           .TH strtol 3 2024-07-23 "Linux man-pages 6.9.1"
           .SH NAME
           strtol, strtoll, strtoq - convert a string to a long integer
           .SH SEE ALSO
           .BR atof (3),
           .BR atoi (3),
           .BR atol (3),
           .BR strtod (3),
           .BR strtoimax (3),
           .BR strtoul (3)
           .lf 1 /usr/local/man/man3/strtoul.3
           .TH strtoul 3 2024-07-23 "Linux man-pages 6.9.1"
           .SH NAME
           strtoul, strtoull, strtouq - convert a string to an unsigned long integer
           .SH SEE ALSO
           .BR a64l (3),
           .BR atof (3),
           .BR atoi (3),
           .BR atol (3),
           .BR strtod (3),
           .BR strtol (3),
           .BR strtoumax (3)
    


* * *
# pmlogger_rewrite

## NAME



           **pmlogger_rewrite** - helper script to rewrite Performance Co-Pilot
           archives
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmlogger_rewrite**[**-dNsVvw?**]  [**-c** _config_] _archive_
           ...
    


## DESCRIPTION



           **pmlogger_rewrite** is a helper script that is used by
           pmlogger_daily(1) when rewriting Performance Co-Pilot (PCP)
           archives.  Rewriting is usually required to accommodate
           evolutionary changes in metadata so old archives can be updated
           and then merged with current archives.
    
           **pmlogger_rewrite** is a wrapper script for pmlogrewrite(1) that will
           potentially rewrite all of the archives matching the _archive_
           arguments.  Each _archive_ argument may be a PCP archive file name,
           the basename for the files in a PCP archive, or a directory (in
           which case all subordinate PCP archives are found by recursive
           descent).
    
           **pmlogrewrite** is run with the **-i** option so rewriting is done ``in
           place''.  The **-q** option is also used, so if no rewriting is
           required then no changes are made to the archive files.
    


## OPTIONS



           The following options are passed through to **pmlogrewrite** : **-c**(or
           **--config**), **-d**(or **--desperate**), **-s**(or **--scale**), **-v**(or **--verbose)**
           and **-w**(or **--warnings**).  Refer to pmlogrewrite(1) for the meaning
           of these options.
    
           The remaining options are:
    
           **-N** , **--showme**
                Runs **pmlogger_rewrite** in a ``show me'' or ``dry run'' mode
                where the tasks that would be performed are reported, but no
                changes are made.  This is typically used for debugging in
                combination with one (verbose) or two (very verbose) **-V** op‐
                tions.
    
           **-V** , **--verbose**
                Increase script output verbosity.
    
           **-?** , **--help**
                Display usage message and exit.
    


## PCP ENVIRONMENT



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


* * *
# dh_installlogcheck

## NAME



           dh_installlogcheck - install logcheck rulefiles into etc/logcheck/
    


## SYNOPSIS



           **dh_installlogcheck**[_debhelper options_]
    


## DESCRIPTION



           **dh_installlogcheck** is a debhelper program that is responsible for
           installing logcheck rule files.
    


## FILES



           debian/_package_.logcheck.cracking
           debian/_package_.logcheck.violations
           debian/_package_.logcheck.violations.ignore
           debian/_package_.logcheck.ignore.workstation
           debian/_package_.logcheck.ignore.server
           debian/_package_.logcheck.ignore.paranoid
               Each of these files, if present, are installed into
               corresponding subdirectories of _etc/logcheck/_ in package build
               directories.
    


## OPTIONS



           **--name=**_name_
               Look for files named _debian/package.name.logcheck.*_ and
               install them into the corresponding subdirectories of
               _etc/logcheck/_ , but use the specified name instead of that of
               the package.
    


* * *
# colon

## PROLOG



           This manual page is part of the POSIX Programmer's Manual.  The
           Linux implementation of this interface may differ (consult the
           corresponding Linux manual page for details of Linux behavior), or
           the interface may not be implemented on Linux.
    


## NAME



           colon — null utility
    


## SYNOPSIS



           : **[**_argument_...**]**
    


## DESCRIPTION



           This utility shall only expand command _argument_ s.  It is used when
           a command is needed, as in the **then** condition of an **if** command,
           but nothing is to be done by the command.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           Zero.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           : ${X=abc}
           if     false
           then   :
           else   echo $X
           fi
           **abc**
    
           As with any of the special built-ins, the null utility can also
           have variable assignments and redirections associated with it,
           such as:
    
               x=y : > z
    
           which sets variable _x_ to the value _y_ (so that it persists after
           the null utility completes) and creates or truncates file **z**.
    


## RATIONALE



           None.
    


## FUTURE DIRECTIONS



           None.
    


* * *
# opimport

## NAME



           opimport - converts sample database files
    


## SYNOPSIS



           **opimport**[ _options_ ] input_file
    


## DESCRIPTION



           **opimport** converts sample database files from a foreign binary
           format (abi) to the native format.
    


## OPTIONS



           **--abi / -a**
                  Input abi file description location.
    
           **--force / -f**
                  Force conversion even if the input and output abi are
                  identical.
    
           **--output / -o filename**
                  Specify the output filename. If the output file already
                  exists it is not overwritten but data are accumulated in.
                  Sample filename are informative for post profile tools and
                  must be kept identical, in other word the pathname from the
                  first path component containing a '{' must be kept as it in
                  the output filename.
    
           **--help / -? / --usage**
                  Show help message.
    
           **--verbose / -V**
                  Give verbose debugging output.
    
           **--version / -v**
                  Show version.
    


## ENVIRONMENT



           No special environment variables are recognized by opimport
    


## FILES



           _< session_dir>/abi_
                  The abi file description of the sample database files
    


## VERSION



           This man page is current for oprofile-1.5.0git.
    


* * *
# kbd_mode

## NAME



           kbd_mode - report or set the keyboard mode
    


## SYNOPSIS



           **kbd_mode**[ _-a | -u | -k | -s | -d_ ] [ _-f_ ] [ _-C CONSOLE_ ]
    


## DESCRIPTION



           Without argument, **kbd_mode** prints the current keyboard mode (RAW,
           MEDIUMRAW or XLATE). Using the options it is possible to switch
           the keyboard mode of the current console or the specified console.
    


## OPTIONS



           **-a, --ascii**
                  set ASCII mode (XLATE).
    
           **-k, --keycode**
                  set keycode mode (MEDIUMRAW).
    
           **-s, --scancode**
                  set scancode mode (RAW).
    
           **-u, --unicode**
                  set UTF-8 mode (UNICODE).
    
           **-d, --disable**
                  set Disable mode (OFF).
    
           **-f, --force**
                  switch the mode even if it makes the keyboard unusable.
    
           **-C, --console=DEV**
                  the console device to be used.
    
           Of course the "-a" is only traditional, and the code used can be
           any 8-bit character set.  With "-u" a 16-bit character set is
           expected, and these chars are transmitted to the kernel as 1, 2,
           or 3 bytes (following the UTF-8 coding).  In these latter two
           modes the key mapping defined by loadkeys(1) is used.
    
           The Didable mode for the virtual console keyboard OFF to
           compliment RAW in which all key events are ignored. The mode
           prevents vt input buffers from overflowing when a program opens
           but doesn't read from a tty, like Xorg using only evdev for input.
    
           kbd_mode operates on the console specified by the "-C" option; if
           there is none, the console associated with stdin is used.
    
           Warning: changing the keyboard mode, other than between ASCII and
           Unicode, will probably make your keyboard unusable. Set the "-f"
           option to force such changes.  This command is only meant for use
           (say via remote login) when some program left your keyboard in the
           wrong state.  Note that in some obsolete versions of this program
           the "-u" option was a synonym for "-s" and older versions of this
           program may not recognize the "-f" option.
    


* * *
# valgrind-listener

## NAME



           valgrind-listener - listens on a socket for Valgrind commentary
    


## SYNOPSIS



    
           **valgrind-listener**[_options_]
    


## DESCRIPTION



           **valgrind-listener** accepts (multiple) connections from **valgrind**
           processes that use the **--log-socket** option on the specified port
           and copies the commentary it is sent to stdout.
    


## OPTIONS



           **-e --exit-at-zero**
               When the number of connected processes falls back to zero,
               exit. Without this, it will run forever, that is, until you
               send it Control-C.
    
           **--max-connect=INTEGER**
               By default, the listener can connect to up to 50 processes.
               Occasionally, that number is too small. Use this option to
               provide a different limit. E.g.  --max-connect=100.
    
           **portnumber**
               Changes the port it listens on from the default (1500). The
               specified port must be in the range 1024 to 65535. The same
               restriction applies to port numbers specified by a
               **--log-socket** to Valgrind itself.
    


* * *
# flatpak-document-info

## NAME



           flatpak-document-info - Show information about exported files
    


## SYNOPSIS



    
           **flatpak document-info**[OPTION...] FILE
    


## DESCRIPTION



           Shows information about an exported file, such as the document id,
           the fuse path, the original location in the filesystem, and the
           per-application permissions.
    
           FILE can either be a file in the fuse filesystem at
           /run/user/$UID/doc/, or a file anywhere else.
    


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


## EXAMPLES



           **$ flatpak document-info ~/Sources/gtk/gail-3.0.pc**
    
               id: dd32c34a
               path: /run/user/1000/doc/dd32c34a/gail-3.0.pc
               origin: /home/mclasen/Sources/gtk/gail-3.0.pc
               permissions:
                       org.gnome.gedit read, write
    


* * *
# trace-cmd-options

## NAME



           trace-cmd-options - list available options from trace-cmd plugins
    


## SYNOPSIS



           **trace-cmd options**
    


## DESCRIPTION



           The trace-cmd(1) options command will examine all the trace-cmd
           plugins that are used by **trace-cmd report(1)** and list them.
    


## RESOURCES



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


## COPYING



           Copyright (C) 2011 Red Hat, Inc. Free use of this software is
           granted under the terms of the GNU Public License (GPL).
    


## NOTES



            1. rostedt@goodmis.org
               mailto:rostedt@goodmis.org
    


* * *
# trace-cmd-snapshot

## NAME



           trace-cmd-snapshot - take, reset, free, or show a Ftrace kernel
           snapshot
    


## SYNOPSIS



           **trace-cmd snapshot**[_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) snapshot controls or displays the Ftrace Linux
           kernel snapshot feature (if the kernel supports it). This is
           useful to "freeze" an instance of a live trace but without
           stopping the trace.
    
                trace-cmd start -p function
                trace-cmd snapshot -s
                trace-cmd snapshot
               [ dumps the content of buffer at 'trace-cmd snapshot -s' ]
                trace-cmd snapshot -s
                trace-cmd snapshot
               [ dumps the new content of the buffer at the last -s operation ]
    


## OPTIONS



           **-s**
               Take a snapshot of the currently running buffer.
    
           **-r**
               Clear out the buffer.
    
           **-f**
               Free the snapshot buffer. The buffer takes up memory inside
               the kernel. It is best to free it when not in use. The first
               -s operation will allocate it if it is not already allocated.
    
           **-c** _cpu_
               Operate on a per cpu snapshot (may not be fully supported by
               all kernels)
    
           **-B** _buf_
               If a buffer instance was created, then the **-B** option will
               operate on the snapshot within the buffer.
    


## RESOURCES



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


## COPYING



           Copyright (C) 2010 Red Hat, Inc. Free use of this software is
           granted under the terms of the GNU Public License (GPL).
    


## NOTES



            1. rostedt@goodmis.org
               mailto:rostedt@goodmis.org
    


* * *
# lsattr

## NAME



           lsattr - list ext2/ext3/ext4 file attributes
    


## SYNOPSIS



           **lsattr**[ **-RVadlpv**] [ _files..._  ]
    


## DESCRIPTION



           **lsattr** lists the file attributes on an ext2/ext3/ext4 file system.
           See chattr(1) for a description of the attributes and what they
           mean.
    


## OPTIONS



           **-R** Recursively list attributes of directories and their
                  contents.
    
           **-V** Display the program version.
    
           **-a** List all files in directories, including files that start
                  with `.'.
    
           **-d** List directories like other files, rather than listing
                  their contents.
    
           **-l** Print the options using long names instead of single
                  character abbreviations.
    
           **-p** List the file's project number.
    
           **-v** List the file's version/generation number.
    


## BUGS



           There are none :-).
    


## AVAILABILITY



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


* * *
# dh_builddeb

## NAME



           dh_builddeb - build Debian binary packages
    


## SYNOPSIS



           **dh_builddeb**[_debhelper options_] [**--destdir=**_directory_]
           [**--filename=**_name_] [**--**_params_]
    


## DESCRIPTION



           **dh_builddeb** simply calls dpkg-deb(1) to build a Debian package or
           packages.  It will also build dbgsym packages when dh_strip(1) and
           dh_gencontrol(1) have prepared them.
    
           It supports building multiple binary packages in parallel, when
           enabled by DEB_BUILD_OPTIONS.
    
           When the _Rules-Requires-Root_ field is not (effectively) _binary-_
           _targets_ , **dh_builddeb** will pass **--root-owner-group** to dpkg-deb(1).
    


## OPTIONS



           **--destdir=**_directory_
               Use this if you want the generated _.deb_ files to be put in a
               directory other than the default of "_.._ ".
    
           **--filename=**_name_
               Use this if you want to force the generated .deb file to have
               a particular file name. Does not work well if more than one
               .deb is generated!
    
           **--**_params_
               Pass _params_ to dpkg-deb(1) when it is used to build the
               package.
    
           **-u** _params_
               This is another way to pass _params_ to dpkg-deb(1).  It is
               deprecated; use **--** instead.
    


* * *
# gcov-dump

## NAME



           gcov-dump - offline gcda and gcno profile dump tool
    


## SYNOPSIS



           gcov-dump [**-v** |**--version**]
                [**-h** |**--help**]
                [**-l** |**--long**]
                [**-p** |**--positions**]
                _gcovfiles_
    


## DESCRIPTION



           **gcov-dump** is a tool you can use in conjunction with GCC to dump
           content of gcda and gcno profile files offline.
    


## OPTIONS



           **-h**
           **--help**
               Display help about using **gcov-dump**(on the standard output),
               and exit without doing any further processing.
    
           **-l**
           **--long**
               Dump content of records.
    
           **-p**
           **--positions**
               Dump positions of records.
    
           **-v**
           **--version**
               Display the **gcov-dump** version number (on the standard output),
               and exit without doing any further processing.
    


* * *
# repoclosure

## NAME



           repoclosure - display a list of unresolved dependencies for a yum
           repository
    


## SYNOPSIS



           **repoclosure**[options]
    


## DESCRIPTION



           **repoclosure** is a program that reads package metadata from one or
           more yum repositories, checks all dependencies, and displays a
           list of packages with unresolved dependencies.
    


## OPTIONS



           **-h, --help**
                  Display a help message, and then quit.
    
           **-c CONFIG, --config=CONFIG**
                  Config file to use (defaults to /etc/yum.conf).
    
           **-a ARCH, --arch=ARCH**
                  Check packages of the given archs, can be specified
                  multiple times (default: current arch).
    
           **--basearch=BASEARCH**
                  Set the basearch for yum to run as.
    
           **-b, --builddeps**
                  Check build dependencies only (needs source repos enabled).
    
           **-l LOOKASIDE, --lookaside=LOOKASIDE**
                  Specify a lookaside repo id to query, can be specified
                  multiple times.
    
           **-r REPOID, --repoid=REPOID**
                  Specify repo ids to query, can be specified multiple times
                  (default is all enabled).
    
           **-t, --tempcache**
                  Use a temp dir for storing/accessing yum-cache.
    
           **-q, --quiet**
                  Run quietly: no warnings printed to stderr.
    
           **-n, --newest**
                  Check only the newest packages in the repos.
    
           **--repofrompath=REPOID,PATH/URL**
                  Specify a path or url to a repository (same path as in a
                  baseurl) to add to the repositories for this query. This
                  option can be used multiple times. If you want to view only
                  the pkgs from this repository combine this with --repoid.
                  The repoid for the repository is specified by REPOID.
    
           **-p PKG, --pkg=PKG**
                  Check closure for this package only
    
           **-g GROUP, --group=GROUP**
                  Check closure for packages in this group only
    


* * *
# pmdaopenvswitch

## NAME



           **pmdaopenvswitch** - OpenvSwitch PMDA
    


## DESCRIPTION



           **pmdaopenvswitch** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values for each openvswitch virtual switch
           configured on the local system.
    


## INSTALLATION



           Install the openvswitch PMDA by using the Install script as root:
    
               **# cd $PCP_PMDAS_DIR/openvswitch**
               **# ./Install**
    
           To uninstall, do the following as root:
    
               **# cd $PCP_PMDAS_DIR/openvswitch**
               **# ./Remove**
    
           **pmdaopenvswitch** 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/openvswitch/Install**
               installation script for the **pmdaopenvswitch** agent
    
           **$PCP_PMDAS_DIR/openvswitch/Remove**
               undo installation script for the **pmdaopenvswitch** agent
    
           **$PCP_LOG_DIR/pmcd/openvswitch.log**
               default log file for error messages from **pmdaopenvswitch**
    


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


* * *
# lxc-checkconfig

## NAME



           lxc-checkconfig - check the current kernel for lxc support
    


## SYNOPSIS



           **lxc-checkconfig**
    


## DESCRIPTION



           **lxc-checkconfig** check the current kernel for lxc support
    


## EXAMPLES



           lxc-checkconfig
                  check the current kernel.  CONFIG can be set in the envi‐
                  ronment to an alternate location.
    


* * *
# dh_auto_test

## NAME



           dh_auto_test - automatically runs a package's test suites
    


## SYNOPSIS



           **dh_auto_test**[_build system options_] [_debhelper options_]
           [**--**_params_]
    


## DESCRIPTION



           **dh_auto_test** is a debhelper program that tries to automatically
           run a package's test suite. It does so by running the appropriate
           command for the build system it detects the package uses. For
           example, if there's a Makefile and it contains a **test** or **check**
           target, then this is done by running **make**(or **MAKE** , if the
           environment variable is set). If the test suite fails, the command
           will exit nonzero. If there's no test suite, it will exit zero
           without doing anything.
    
           This is intended to work for about 90% of packages with a test
           suite. If it doesn't work, you're encouraged to skip using
           **dh_auto_test** at all, and just run the test suite manually.
    


## OPTIONS



           See "**BUILD SYSTEM OPTIONS** " in debhelper(7) for a list of common
           build system selection and control options.
    
           **--**_params_
               Pass _params_ to the program that is run, after the parameters
               that **dh_auto_test** usually passes.
    


## NOTES



           If the **DEB_BUILD_OPTIONS** environment variable contains **nocheck** , no
           tests will be performed.
    


* * *
# stg-reset

## NAME



           stg-reset - Reset the patch stack to an earlier state
    


## SYNOPSIS



           _stg reset_ [--hard] [<committish> [<patchname>...]]
           _stg reset_ --hard
    


## DESCRIPTION



           Reset the patch stack to an earlier state. If no state is
           specified, reset only the changes in the worktree.
    
           The state is specified with a commit id from the stack log, which
           may be viewed with stg-log(1). Patch name arguments may optionally
           be provided to limit which patches are reset.
    


## OPTIONS



           --hard
               Discard changes in the index and worktree
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# dh_installinfo

## NAME



           dh_installinfo - install info files
    


## SYNOPSIS



           **dh_installinfo**[_debhelper options_] [**-A**] [_file_ ...]
    


## DESCRIPTION



           **dh_installinfo** is a debhelper program that is responsible for
           installing info files into _usr/share/info_ in the package build
           directory.
    
           From debhelper compatibility level 11 on, **dh_install** will fall
           back to looking in _debian/tmp_ for files, if it does not find them
           in the current directory (or wherever you've told it to look using
           **--sourcedir**).
    


## FILES



           debian/_package_.info
               List info files to be installed.
    
               Supports substitution variables in compat 13 and later as
               documented in debhelper(7).
    


## OPTIONS



           **-A** , **--all**
               Install all files specified by command line parameters in ALL
               packages acted on.
    
           **--sourcedir=**_dir_
               Look in the specified directory for files to be installed.
               This option requires compat 11 or later (it is silently
               ignored in compat 10 or earlier).
    
               Note that this is not the same as the **--sourcedirectory** option
               used by the **dh_auto_**_*_ commands. You rarely need to use this
               option, since **dh_installinfo** automatically looks for files in
               _debian/tmp_ in debhelper compatibility level 11 and above.
    
           _file_ ...
               Install these info files into the first package acted on. (Or
               in all packages if **-A** is specified).
    


* * *
# printenv

## NAME



           printenv - print all or part of environment
    


## SYNOPSIS



           **printenv**[_OPTION_]... [_VARIABLE_]...
    


## DESCRIPTION



           Print the values of the specified environment VARIABLE(s).  If no
           VARIABLE is specified, print name and value pairs for them all.
    
           **-0** , **--null**
                  end each output line with NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Your shell may have its own version of printenv, which usually
           supersedes the version described here.  Please refer to your
           shell's documentation for details about the options it supports.
    


* * *
# yum-debug-dump

## NAME



           yum-debug-dump - write system RPM configuration to a debug-dump
           file
    


## SYNOPSIS



           **yum-debug-dump**
    


## DESCRIPTION



           **yum-debug-dump** is a program which creates a gzipped file
           containing a lot of information useful to developers trying to
           debug a problem.
    
           By default it will output a file to the current working directory
           named yum_debug_dump-<hostname>-<time>.txt.gz. This file contains
           no private information but does contain a complete list of all
           packages you have installed, all packages available in any
           repository, important configuration and system information.  You
           can view this file using the 'zless' command.
    
           You can use the coresponding program **yum-debug-restore** to act on
           this file and restore a set of packages (much like dump/restore).
    


## FILES



           As yum-debug-dump 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.
    


* * *
# mktemp

## NAME



           mktemp - create a temporary file or directory
    


## SYNOPSIS



           **mktemp**[_OPTION_]... [_TEMPLATE_]
    


## DESCRIPTION



           Create a temporary file or directory, safely, and print its name.
           TEMPLATE must contain at least 3 consecutive 'X's in last
           component.  If TEMPLATE is not specified, use tmp.XXXXXXXXXX, and
           **--tmpdir** is implied.  Files are created u+rw, and directories
           u+rwx, minus umask restrictions.
    
           **-d** , **--directory**
                  create a directory, not a file
    
           **-u** , **--dry-run**
                  do not create anything; merely print a name (unsafe)
    
           **-q** , **--quiet**
                  suppress diagnostics about file/dir-creation failure
    
           **--suffix** =_SUFF_
                  append SUFF to TEMPLATE; SUFF must not contain a slash.
                  This option is implied if TEMPLATE does not end in X
    
           **-p** DIR, **--tmpdir**[=_DIR_]
                  interpret TEMPLATE relative to DIR; if DIR is not
                  specified, use $TMPDIR if set, else _/tmp_.  With this
                  option, TEMPLATE must not be an absolute name; unlike with
                  **-t** , TEMPLATE may contain slashes, but mktemp creates only
                  the final component
    
           **-t** interpret TEMPLATE as a single file name component,
                  relative to a directory: $TMPDIR, if set; else the
                  directory specified via **-p** ; else _/tmp_ [deprecated]
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# arch

## NAME



           arch - print machine hardware name (same as uname -m)
    


## SYNOPSIS



           **arch**[_OPTION_]...
    


## DESCRIPTION



           Print machine architecture.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# autopoint

## NAME



           autopoint - copies standard gettext infrastructure
    


## SYNOPSIS



           **autopoint**[_OPTION_]...
    


## DESCRIPTION



           Copies standard gettext infrastructure files into a source
           package.
    


## OPTIONS



           **--help** print this help and exit
    
           **--version**
                  print version information and exit
    
           **-f** , **--force**
                  force overwriting of files that already exist
    
           **-n** , **--dry-run**
                  print modifications but don't perform them
    


* * *
# usbreset

## NAME



           usbreset - send a USB port reset to a USB device
    


## SYNOPSIS



           **usbreset**[ _device_ ]
    


## DESCRIPTION



           **usbreset** is a utility that performs resets on USB devices.  It is
           particularly useful for situations where a USB device is
           unresponsive or exhibits erratic behavior.  The USB _device_ to be
           reset can be specified in one of three formats:
    
           **VVVV:PPPP**
                  Reset by vendor and product IDs
    
           **BBB/DDD**
                  Reset by bus and device number
    
           **SN:SERIAL**
                  Reset by serial number
    
           **Product**
                  Reset by product name
    
           When run without any arguments, **usbreset** provides usage
           information and a list of connected USB devices, including their
           vendor and product IDs, bus and device numbers, and product names.
    


## RETURN VALUE



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


## EXAMPLES



           Reset device with vendor ID 1234 and product ID 5678:
                  **usbreset 1234:5678**
    
           Reset device 002 on bus 001:
                  **usbreset 001/002**
    
           Reset device with serial number ABCDEF0
                  **usbreset SN:ABCDEF0**
    
           Reset device named USB2.0 Hub:
                  **usbreset "USB2.0 Hub"**
    


* * *