tripathysagar/man_text huggingface dataset:
# oparchive

## NAME



           oparchive - produce archive of oprofile data for offline analysis
    


## SYNOPSIS



           **oparchive**[ _options_ ] [profile specification] **-o**[directory]
    


## DESCRIPTION



           The **oparchive** utility is commonly used for collecting profile data
           on a "target" system for future offline analysis on a different
           ("host") machine.  **oparchive** creates a directory populated with
           executables, libraries, debuginfo files, and oprofile sample
           files. This directory can be tar'ed up and moved to another
           machine to be analyzed without further use of the target machine.
           Using **opreport** and other post-profiling tools against archived
           data requires the use of the _archive: <archived-dir>_ specification.
           See oprofile(1) for how to write profile specifications.  A
           complete description of offline analysis can be found in the
           chapter titled _Analyzing profile data on another system_
           _(oparchive)_ of the OProfile user manual. (See the user manual URL
           in the "SEE ALSO" section below.)
    


## OPTIONS



           **--help / -? / --usage**
                  Show help message.
    
           **--version / -v**
                  Show version.
    
           **--verbose / -V [options]**
                  Give verbose debugging output.
    
           **--session-dir=**_dir_path_
                  Use sample database from the specified directory _dir_path_
                  instead of the default location. If _--session-dir_ is not
                  specified, then **oparchive** will search for samples in
                  <current_dir>/oprofile_data first. If that directory does
                  not exist, the standard session-dir of /var/lib/oprofile is
                  used.
    
           **--image-path / -p [paths]**
                  Comma-separated list of additional paths to search for
                  binaries.  This is needed to find modules in kernels 2.6
                  and upwards.
    
           **--root / -R [path]**
                  A path to a filesystem to search for additional binaries.
    
           **--output-directory / -o [directory]**
                  Output to the given directory. There is no default. This
                  must be specified.
    
           **--exclude-dependent / -x**
                  Do not include application-specific images for libraries,
                  kernel modules and the kernel. This option only makes sense
                  if the profile session used --separate.
    
           **--list-files / -l**
                  Only list the files that would be archived, don't copy
                  them.
    


## ENVIRONMENT



           No special environment variables are recognized by oparchive.
    


## FILES



           _< session_dir>/samples_
                  The location of the generated sample files.
    


## VERSION



           This man page is current for oprofile-1.5.0git.
    


* * *
# chvt

## NAME



           chvt - change foreground virtual terminal
    


## SYNOPSIS



           **chvt**[_option_...]  [_N_]
    


## DESCRIPTION



           The command **chvt** _N_ makes _/dev/ttyN_ the foreground terminal.  (The
           corresponding screen is created if it did not exist yet.  To get
           rid of unused VTs, use deallocvt(1).)  The key combination
           (Ctrl-)LeftAlt-F _N_ (with _N_ in the range 1-12) usually has a similar
           effect.
    


## OPTIONS



           **-C** , **--console** =_DEV_
                  the console device to be used.
    
           **-V** , **--version**
                  print version number.
    
           **-h** , **--help**
                  print this usage message.
    


* * *
# git-version

## NAME



           git-version - Display version information about Git
    


## SYNOPSIS



           _git version_ [--build-options]
    


## DESCRIPTION



           With no options given, the version of _git_ is printed on the
           standard output.
    
           Note that **git --version** is identical to **git version** because the
           former is internally converted into the latter.
    


## OPTIONS



           --build-options
               Include additional information about how git was built for
               diagnostic purposes.
    
               The libraries used to implement the SHA-1 and SHA-256
               algorithms are displayed in the form **SHA-1:**_< option>_ and
               **SHA-256:**_< option>_. Note that the SHA-1 options **SHA1_APPLE** ,
               **SHA1_OPENSSL** , and **SHA1_BLK** do not use a collision detection
               algorithm and thus may be vulnerable to known SHA-1 collision
               attacks. When a faster SHA-1 implementation without collision
               detection is used for only non-cryptographic purposes, the
               algorithm is displayed in the form
               **non-collision-detecting-SHA-1:**_< option>_.
    


## GIT



           Part of the git(1) suite
    


* * *
# pmdaresctrl

## NAME



           **pmdaresctrl** - resctrl performance metrics domain agent (PMDA)
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/pmdaresctrl**[**-D** _debug_] [**-d** _domain_] [**-l** _logfile_]
    


## DESCRIPTION



           **pmdaresctrl** is a resctrl Performance Metrics Domain Agent (PMDA)
           which exposes performance metrics values from the /sys/fs/resctrl
           interface to provide information on the last level cache.
    
           Further details on linux support for last level cache metrics can
           be found at
           **https://github.com/torvalds/linux/tree/master/Documentation/arch/x86/resctrl.rst **.
    


## INSTALLATION



           If you want access to the names, help text and values for the
           resctrl performance metrics, do the following as root:
    
                # cd $PCP_PMDAS_DIR/resctrl
                # ./Install
    
           If you want to undo the installation (and remove both PMDAs), do
           the following as root:
    
                # cd $PCP_PMDAS_DIR/resctrl
                # ./Remove
    
           **pmdaresctrl** 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_PMCDCONF_PATH**
                  command line options used to launch **pmdaresctrl**
           **$PCP_PMDAS_DIR/resctrl/help**
                  default help text file for the resctrl metrics
           **$PCP_PMDAS_DIR/resctrl/Install**
                  installation script for the **pmdaresctrl** agent
           **$PCP_PMDAS_DIR/resctrl/Remove**
                  undo installation script for the **pmdaresctrl** agent
    


## 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).  In
           particular, the **$PCP_RESCTRL_DIR** may be set to change the default
           directory from **/sys/fs/resctrl**.
    


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


* * *
# mountpoint

## NAME



           mountpoint - see if a directory or file is a mountpoint
    


## SYNOPSIS



           **mountpoint**[**-d** |**-q**] _directory_ |_file_
    
           **mountpoint -x** _device_
    


## DESCRIPTION



           **mountpoint** checks whether the given _directory_ or _file_ is mentioned
           in the _/proc/self/mountinfo_ file.
    


## OPTIONS



           **-d** , **--fs-devno**
               Show the major/minor numbers of the device that is mounted on
               the given directory.
    
           **-q** , **--quiet**
               Be quiet - don’t print anything.
    
           **--nofollow**
               Do not follow symbolic link if it the last element of the
               _directory_ path.
    
           **-x** , **--devno**
               Show the major/minor numbers of the given blockdevice on
               standard output.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## EXIT STATUS



           **mountpoint** has the following exit status values:
    
           **0**
               success; the directory is a mountpoint, or device is block
               device on **--devno**
    
           **1**
               failure; incorrect invocation, permissions or system error
    
           **32**
               failure; the directory is not a mountpoint, or device is not a
               block device on **--devno**
    


## ENVIRONMENT



           **LIBMOUNT_DEBUG** =all
               enables libmount debug output.
    


## NOTES



           The util-linux **mountpoint** implementation was written from scratch
           for libmount. The original version for sysvinit suite was written
           by Miquel van Smoorenburg.
    


## AVAILABILITY



           The **mountpoint** 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-01-16                  _MOUNTPOINT_(1)
    


* * *
# git-merge-index

## NAME



           git-merge-index - Run a merge for files needing merging
    


## SYNOPSIS



           _git merge-index_ [-o] [-q] <merge-program> (-a | ( [--] <file>...) )
    


## DESCRIPTION



           This looks up the <file>(s) in the index and, if there are any
           merge entries, passes the SHA-1 hash for those files as arguments
           1, 2, 3 (empty argument if no file), and <file> as argument 4.
           File modes for the three files are passed as arguments 5, 6 and 7.
    


## OPTIONS



           --
               Do not interpret any more arguments as options.
    
           -a
               Run merge against all files in the index that need merging.
    
           -o
               Instead of stopping at the first failed merge, do all of them
               in one shot - continue with merging even when previous merges
               returned errors, and only return the error code after all the
               merges.
    
           -q
               Do not complain about a failed merge program (a merge program
               failure usually indicates conflicts during the merge). This is
               for porcelains which might want to emit custom messages.
    
           If _git merge-index_ is called with multiple <file>s (or -a) then it
           processes them in turn only stopping if merge returns a non-zero
           exit code.
    
           Typically this is run with a script calling Git’s imitation of the
           _merge_ command from the RCS package.
    
           A sample script called _git merge-one-file_ is included in the
           distribution.
    
           ALERT ALERT ALERT! The Git "merge object order" is different from
           the RCS _merge_ program merge object order. In the above ordering,
           the original is first. But the argument order to the 3-way merge
           program _merge_ is to have the original in the middle. Don’t ask me
           why.
    
           Examples:
    
               torvalds@ppc970:~/merge-test> git merge-index cat MM
               This is MM from the original tree.              # original
               This is modified MM in the branch A.            # merge1
               This is modified MM in the branch B.            # merge2
               This is modified MM in the branch B.            # current contents
    
           or
    
               torvalds@ppc970:~/merge-test> git merge-index cat AA MM
               cat: : No such file or directory
               This is added AA in the branch A.
               This is added AA in the branch B.
               This is added AA in the branch B.
               fatal: merge program failed
    
           where the latter example shows how _git merge-index_ will stop
           trying to merge once anything has returned an error (i.e., **cat**
           returned an error for the AA file, because it didn’t exist in the
           original, and thus _git merge-index_ didn’t even try to merge the MM
           thing).
    


## GIT



           Part of the git(1) suite
    


* * *
# stg-repair

## NAME



           stg-repair - Repair stack after branch is modified with git
           commands
    


## SYNOPSIS



           _stg repair_ [OPTIONS]
    


## DESCRIPTION



           If a branch with a StGit stack is modified with certain git
           commands such as git-commit(1), git-pull(1), git-merge(1), or
           git-rebase(1), the StGit stack metadata will become inconsistent
           with the branch state. There are a few options for resolving this
           kind of situation:
    
            1. Use stg-undo(1) to undo the effect of the git commands. Or
               similarly use stg-reset(1) to reset the stack/branch to any
               previous stack state.
    
            2. Use **stg repair**. This will repair the StGit stack metadata to
               accommodate the modifications to the branch made by the git
               commands. Specifically, it will do the following:
    
               •   If regular git commits were made on top of the stack of
                   StGit patches (i.e. by using plain **git commit**), **stg repair**
                   will convert those commits to StGit patches, preserving
                   their content.
    
               •   However, merge commits cannot become patches. So if a
                   merge was committed on top of the stack, **stg repair** will
                   mark all patches below the merge commit as unapplied,
                   since they are no longer reachable. An alternative when
                   this is not the desired behavior is to use **stg undo** to
                   first get rid of the offending merge and then run **stg**
                   **repair** again.
    
               •   The applied patches are supposed to be precisely those
                   that are reachable from the branch head. If, for example,
                   git-reset(1) was used to move the head, some applied
                   patches may no longer be reachable and some unapplied
                   patches may have become reachable. In this case, **stg**
                   **repair** will correct the applied/unapplied state of such
                   patches.
    
           **stg repair** will repair these inconsistencies reliably, so there
           are valid workflows where git commands are used followed by **stg**
           **repair**. For example, new patches can be created by first making
           commits with a graphical commit tool and then running **stg repair**
           to convert those commits into patches.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# sg

## NAME



           sg - execute command as different group ID
    


## SYNOPSIS



    
           **sg**[-] [group [-c ] command]
    


## DESCRIPTION



           The **sg** command works similar to **newgrp** but accepts a command. The
           command will be executed with the /bin/sh shell. With most shells
           you may run **sg** from, you need to enclose multi-word commands in
           quotes. Another difference between **newgrp** and **sg** is that some
           shells treat **newgrp** specially, replacing themselves with a new
           instance of a shell that **newgrp** creates. This doesn't happen with
           **sg** , so upon exit from a **sg** command you are returned to your
           previous group ID.
    


## CONFIGURATION



           The following configuration variables in /etc/login.defs change
           the behavior of this tool:
    
           **SYSLOG_SG_ENAB**(boolean)
               Enable "syslog" logging of **sg** activity.
    


## FILES



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


* * *
# lxc-wait

## NAME



           lxc-wait - wait for a specific container state
    


## SYNOPSIS



           **lxc-wait**{-n _name_} {-s _states_}
    


## DESCRIPTION



           **lxc-wait** waits for a specific container state before exiting, this
           is useful for scripting.
    


## OPTIONS



           **-s, --state** _states_
                  Specify the container state(s) to wait for. The container
                  states can be ORed to specify several states.
    
           **-t, --timeout** _timeout_
                  Wait timeout seconds for desired state to be reached.
    


## COMMON OPTIONS



           These options are common to most of lxc commands.
    
           **-?, -h, --help**
                  Print a longer usage message than normal.
    
           **--usage**
                  Give the usage message
    
           **-q, --quiet**
                  mute on
    
           **-P, --lxcpath=**_PATH_
                  Use an alternate container path. The default is
                  /var/lib/lxc.
    
           **-o, --logfile=**_FILE_
                  Output to an alternate log _FILE_. The default is no log.
    
           **-l, --logpriority=**_LEVEL_
                  Set log priority to _LEVEL_. The default log priority is ER‐
                  ROR. Possible values are : FATAL, ALERT, CRIT, WARN, ERROR,
                  NOTICE, INFO, DEBUG, TRACE.
    
                  Note that this option is setting the priority of the events
                  log in the alternate log file. It do not have effect on the
                  ERROR events log on stderr.
    
           **-n, --name=**_NAME_
                  Use container identifier _NAME_.  The container identifier
                  format is an alphanumeric string.
    
           **--rcfile=**_FILE_
                  Specify the configuration file to configure the virtualiza‐
                  tion and isolation functionalities for the container.
    
                  This configuration file if present will be used even if
                  there is already a configuration file present in the previ‐
                  ously created container (via lxc-create).
    
           **--version**
                  Show the version number.
    


## EXAMPLES



           lxc-wait -n foo -s RUNNING
                  exits when 'RUNNING' is reached.
    
           lxc-wait -n foo -s 'RUNNING|STOPPED'
                  exits when 'RUNNING' or 'STOPPED' state is reached.
    


## DIAGNOSTIC



           The container was not found
                  The specified container was not created before with the
                  **lxc-create** command.
    


* * *
# wrudf

## NAME



           **wrudf** - Maintain a UDF filesystem.
    


## SYNOPSIS



           **wrudf** _device_
           **wrudf --help** | **-help** | **-h**
    


## DESCRIPTION



           **wrudf** provides an interactive shell with operations on existing
           UDF filesystem: cp, rm, mkdir, rmdir, ls, cd.
    
       **COMMANDS**
           **cp** copy
    
           **rm** remove
    
           **mkdir** make directory
    
           **rmdir** remove directory
    
           **lsc** list files (Compact disc version)
    
           **lsh** list files (Hard disc version)
    
           **cdc** change working directory (Compact disc)
    
           **cdh** change working directory (Hard disc)
    
           **quit** quit **wrudf**
    
           **exit** quit **wrudf**
    


## AVAILABILITY



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


* * *
# pmdarabbitmq

## NAME



           **pmdarabbitmq** - Rabbit Message Queue subsystem PMDA
    


## DESCRIPTION



           **pmdarabbitmq** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values for each RabbitMQ queue configured on the
           local system.
    


## INSTALLATION



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


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


* * *
# readlink

## NAME



           readlink - print resolved symbolic links or canonical file names
    


## SYNOPSIS



           **readlink**[_OPTION_]... _FILE_...
    


## DESCRIPTION



           realpath(1) is a better command for canonicalization
           functionality.
    
           Print value of a symbolic link or canonical file name
    
           **-f** , **--canonicalize**
                  canonicalize by following every symlink in every component
                  of the given name recursively; all but the last component
                  must exist
    
           **-e** , **--canonicalize-existing**
                  canonicalize by following every symlink in every component
                  of the given name recursively, all components must exist
    
           **-m** , **--canonicalize-missing**
                  canonicalize by following every symlink in every component
                  of the given name recursively, without requirements on
                  components existence
    
           **-n** , **--no-newline**
                  do not output the trailing delimiter
    
           **-q** , **--quiet**
    
           **-s** , **--silent**
                  suppress most error messages (on by default)
    
           **-v** , **--verbose**
                  report error messages
    
           **-z** , **--zero**
                  end each output line with NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# pmdanetfilter

## NAME



           **pmdanetfilter** - Linux netfilter IP connection tracking performance
           metrics domain agent (PMDA)
    


## DESCRIPTION



           **pmdanetfilter** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values from the IP connection tracking module in
           the Linux kernel.
    


## INSTALLATION



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


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


* * *
# timeout

## NAME



           timeout - run a command with a time limit
    


## SYNOPSIS



           **timeout**[_OPTION_] _DURATION COMMAND_ [_ARG_]...
           **timeout**[_OPTION_]
    


## DESCRIPTION



           Start COMMAND, and kill it if still running after DURATION.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-f** , **--foreground**
    
                  when not running timeout directly from a shell prompt,
                  allow COMMAND to read from the TTY and get TTY signals; in
                  this mode, children of COMMAND will not be timed out
    
           **-k** , **--kill-after** =_DURATION_
    
                  also send a KILL signal if COMMAND is still running this
                  long after the initial signal was sent
    
           **-p** , **--preserve-status**
    
                  exit with the same status as COMMAND, even when the command
                  times out
    
           **-s** , **--signal** =_SIGNAL_
    
                  specify the signal to be sent on timeout; SIGNAL may be a
                  name like 'HUP' or a number; see 'kill **-l** ' for a list of
                  signals
    
           **-v** , **--verbose**
                  diagnose to stderr any signal sent upon timeout
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           DURATION is a floating point number with an optional suffix: 's'
           for seconds (the default), 'm' for minutes, 'h' for hours or 'd'
           for days.  A duration of 0 disables the associated timeout.
    
           Upon timeout, send the TERM signal to COMMAND, if no other SIGNAL
           specified.  The TERM signal kills any process that does not block
           or catch that signal.  It may be necessary to use the KILL signal,
           since this signal can't be caught.
    
       **Exit status:**
           124    if COMMAND times out, and **--preserve-status** is not
                  specified
    
           125    if the timeout command itself fails
    
           126    if COMMAND is found but cannot be invoked
    
           127    if COMMAND cannot be found
    
           137    if COMMAND (or timeout itself) is sent the KILL (9) signal
                  (128+9)
    
           -      the exit status of COMMAND otherwise
    


## BUGS



           Some platforms don't currently support timeouts beyond the year
           2038.
    


* * *
# pdfmom

## Name



           pdfmom - produce PDF documents using the _mom_ macro package for
           _groff_
    


## Synopsis



           **pdfmom**[**--roff**] [**-Tpdf**] [_groff-options_] [_file_ ...]
    
           **pdfmom**[**--roff**] **-Tps**[_pdfroff-options_] [_groff-options_] [_file_ ...]
    
           **pdfmom -v**
    
           **pdfmom --version**
    


## Description



           _pdfmom_ is a wrapper around _groff_(1) that facilitates the
           production of PDF documents from files formatted with the _mom_
           macros.
    
           If the **--roff** option is used, the wrapper can be used with macro
           packages other than _groff_mom_(7).  This is also true if the
           wrapper is renamed or linked as a pseudonym; for example, creating
           a _pdfms_ link pointing to the _pdfmom_ executable makes a wrapper for
           producing PDFs with the _ms_ package.
    
           _pdfmom_ prints to the standard output, so output must usually be
           redirected to a destination file.  The size of the final PDF can
           be reduced by piping the output through _ps2pdf_(1).
    
           If called with the **-Tpdf** option (which is the default), _pdfmom_
           processes files using _groff_ 's native PDF driver, _gropdf_(1).  If
           **-Tps** is given, processing is passed over to _pdfroff_ , which uses
           _groff_ 's PostScript driver.  In either case, multiple runs of the
           source file are performed in order to satisfy any forward
           references in the document.
    
           _pdfmom_ accepts all the same options as _groff_.  If **-Tps** is given,
           the options associated with _pdfroff_ are accepted as well.  When
           _pdfmom_ calls _pdfroff_ , the options “**-mpdfmark -mom --no-toc** ”
           options are implied and should not be given on the command line.
           Equally, it is not necessary to supply the **-mom** or **-m mom** options
           when **-Tps** is absent.
    
           PDF integration with the _mom_ macros is discussed in full in the
           manual “Producing PDFs with _groff_ and _mom_ ”, which was itself
           produced with _pdfmom_.
    
           If called with the **-v** or **--version** options, _pdfmom_ displays its
           version information and exits.  Using the **--help** option displays a
           usage message and exits.
    


## Authors



           _pdfmom_ was written by Deri James ⟨deri@chuzzlewit.myzen.co.uk⟩ and
           Peter Schaffter ⟨peter@schaffter.ca⟩, and is maintained by James.
    


## See also



           _/usr/local/share/doc/groff-1.23.0/pdf/mom-pdf.pdf_
                  “Producing PDFs with _groff_ and _mom_ ”, by Deri James and
                  Peter Schaffter.  This file, together with its source,
                  _mom-pdf.mom_ , is part of the _groff_ distribution.
    
           _groff_(1), _gropdf_(1), _pdfroff_(1), _ps2pdf_(1)
    


* * *
# recode-sr-latin

## NAME



           recode-sr-latin - convert Serbian text from Cyrillic to Latin
           script
    


## SYNOPSIS



           **recode-sr-latin**[_OPTION_]
    


## DESCRIPTION



           Recode Serbian text from Cyrillic to Latin script.  The input text
           is read from standard input.  The converted text is output to
           standard output.
    
       **Informative output:**
           **-h** , **--help**
                  display this help and exit
    
           **-V** , **--version**
                  output version information and exit
    


* * *
# git-sh-i18n--envsubst

## NAME



           git-sh-i18n--envsubst - Git's own envsubst(1) for i18n fallbacks
    


## SYNOPSIS



           eval_gettext () {
                   printf "%s" "$1" | (
                           export PATH $(_git sh-i18n--envsubst_ --variables "$1");
                           _git sh-i18n--envsubst_ "$1"
                   )
           }
    


## DESCRIPTION



           This is not a command the end user would want to run. Ever. This
           documentation is meant for people who are studying the plumbing
           scripts and/or are writing new ones.
    
           _git sh-i18n--envsubst_ is Git’s stripped-down copy of the GNU
           **envsubst**(**1**) program that comes with the GNU gettext package. It’s
           used internally by git-sh-i18n(1) to interpolate the variables
           passed to the **eval_gettext** function.
    
           No promises are made about the interface, or that this program
           won’t disappear without warning in the next version of Git. Don’t
           use it.
    


## GIT



           Part of the git(1) suite
    


* * *
# link

## NAME



           link - call the link function to create a link to a file
    


## SYNOPSIS



           **link** _FILE1 FILE2_
           **link** _OPTION_
    


## DESCRIPTION



           Call the link function to create a link named FILE2 to an existing
           FILE1.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# pcp-shping

## NAME



           **pcp-shping** - report on shell service availability and response
    


## SYNOPSIS



           **pcp**[_pcp options_] **shping**[**-cl?**]  _tag_ ...
    


## DESCRIPTION



           **pcp-shping** samples and reports on the shell-ping service metrics
           exported by the pmdashping(1) agent.
    
           The default report from **pcp-shping** shows two columns for each
           service _tag_ , the first showing service status (zero indicating
           success) and the second service response time, for the last
           **pmdashping** command refresh cycle.
    
           When invoked via the pcp(1) command, the **-h** /**--host** , **-a** /**--archive** ,
           **-O** /**--origin** , **-s** /**--samples** , **-t** /**--interval** , **-Z** /**--timezone** and
           several other **pcp** _options_ become indirectly available, see
           PCPIntro(1) for their descriptions.
    


## OPTIONS



           The available command line options are:
    
           **-c** , **--status**
                Display a summary of the current shell-ping collector,
                including information about service refresh interval, the
                current command timeout setting, count of refreshes, and the
                full command line associated with each _tag_.
    
           **-l** , **--tags**
                Displays the valid _tag_ s.
    
           **-?** , **--help**
                Display usage message and exit.
    


## PCP ENVIRONMENT



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


* * *
# psfxtable

## NAME



           psfxtable - handle Unicode character tables for console fonts
    


## SYNOPSIS



           **psfxtable**[**-i** _infont_] [**-o** _outfont_] [**-it** _intable_] [**-ot** _outtable_]
           [**-nt**]
    


## DESCRIPTION



           **psfxtable** handles the embedded Unicode character table for .psf
           format console fonts. It reads a font and possibly a table and
           writes a font and/or a table.  psfaddtable(1), psfgettable(1) and
           psfstriptable(1) are links to it.
    
           Each of the filenames _infont_ , _outfont_ , _intable_ , and _outtable_ may
           be replaced by a single dash (-), in which case standard input or
           standard output is used.  If no _-i_ option is given, the font is
           read from standard input.  If no _-it_ or _-o_ or _-ot_ option is given,
           no input table is read or no output font or output table is
           written.
    
           By default the output font (if any) will have a Unicode table when
           either the input font has one, or an explicit table (which
           overrides an input font table) has been provided.  The option _-nt_
           causes output of a font without table.  When _outfont_ is requested
           it will get a psf1 header when infont has a psf1 header and
           _intable_ does not have sequences and a psf2 header otherwise.
    


* * *
# wsrep_sst_mariabackup

## NAME



           wsrep_sst_mariabackup - mariabackup-based state snapshot transfer
    


## DESCRIPTION



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


* * *
# hostid

## NAME



           hostid - print the numeric identifier for the current host
    


## SYNOPSIS



           **hostid**[_OPTION_]
    


## DESCRIPTION



           Print the numeric identifier (in hexadecimal) for the current
           host.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# git-citool

## NAME



           git-citool - Graphical alternative to git-commit
    


## SYNOPSIS



           _git citool_
    


## DESCRIPTION



           A Tcl/Tk based graphical interface to review modified files, stage
           them into the index, enter a commit message and record the new
           commit onto the current branch. This interface is an alternative
           to the less interactive _git commit_ program.
    
           _git citool_ is actually a standard alias for **git gui citool**. See
           git-gui(1) for more details.
    


## GIT



           Part of the git(1) suite
    


* * *
# tty

## NAME



           tty - print the file name of the terminal connected to standard
           input
    


## SYNOPSIS



           **tty**[_OPTION_]...
    


## DESCRIPTION



           Print the file name of the terminal connected to standard input.
    
           **-s** , **--silent** , **--quiet**
                  print nothing, only return an exit status
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# sha512sum

## NAME



           sha512sum - compute and check SHA512 message digest
    


## SYNOPSIS



           **sha512sum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or check SHA512 (512-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.
    


* * *
# git-verify-commit

## NAME



           git-verify-commit - Check the GPG signature of commits
    


## SYNOPSIS



           **git verify-commit**[**-v** | **--verbose**] [**--raw**] _< commit>_...
    


## DESCRIPTION



           Validates the GPG signature created by **git commit -S** on the commit
           objects given on the command line.
    


## OPTIONS



           **--raw**
               Print the raw gpg status output to standard error instead of
               the normal human-readable output.
    
           **-v** , **--verbose**
               Print the contents of the commit object before validating it.
    


## GIT



           Part of the git(1) suite
    


* * *
# ptx

## NAME



           ptx - produce a permuted index of file contents
    


## SYNOPSIS



           **ptx**[_OPTION_]... [_INPUT_]...   _(without -G)_
           **ptx** _-G_ [_OPTION_]... [_INPUT_ [_OUTPUT_]]
    


## DESCRIPTION



           Output a permuted index, including context, of the words in the
           input files.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-A** , **--auto-reference**
                  output automatically generated references
    
           **-G** , **--traditional**
                  behave more like System V 'ptx'
    
           **-F** , **--flag-truncation** =_STRING_
                  use STRING for flagging line truncations.  The default is
                  '/'
    
           **-M** , **--macro-name** =_STRING_
                  macro name to use instead of 'xx'
    
           **-O** , **--format** =_roff_
                  generate output as roff directives
    
           **-R** , **--right-side-refs**
                  put references at right, not counted in **-w**
    
           **-S** , **--sentence-regexp** =_REGEXP_
                  for end of lines or end of sentences
    
           **-T** , **--format** =_tex_
                  generate output as TeX directives
    
           **-W** , **--word-regexp** =_REGEXP_
                  use REGEXP to match each keyword
    
           **-b** , **--break-file** =_FILE_
                  word break characters in this FILE
    
           **-f** , **--ignore-case**
                  fold lower case to upper case for sorting
    
           **-g** , **--gap-size** =_NUMBER_
                  gap size in columns between output fields
    
           **-i** , **--ignore-file** =_FILE_
                  read ignore word list from FILE
    
           **-o** , **--only-file** =_FILE_
                  read only word list from this FILE
    
           **-r** , **--references**
                  first field of each line is a reference
    
           **-t** , **--typeset-mode** - not implemented -
    
           **-w** , **--width** =_NUMBER_
                  output width in columns, reference excluded
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# msginit

## NAME



           msginit - initialize a message catalog
    


## SYNOPSIS



           **msginit**[_OPTION_]
    


## DESCRIPTION



           Creates a new PO file, initializing the meta information with
           values from the user's environment.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
       **Input file location:**
           **-i** , **--input** =_INPUTFILE_
                  input POT file
    
           If no input file is given, the current directory is searched for
           the POT file.  If it is -, standard input is read.
    
       **Output file location:**
           **-o** , **--output-file** =_FILE_
                  write output to specified PO file
    
           If no output file is given, it depends on the **--locale** option or
           the user's locale setting.  If it is -, the results are written to
           standard output.
    
       **Input file syntax:**
           **-P** , **--properties-input**
                  input file is in Java .properties syntax
    
           **--stringtable-input**
                  input file is in NeXTstep/GNUstep .strings syntax
    
       **Output details:**
           **-l** , **--locale** =_LL_CC[_.ENCODING]
                  set target locale
    
           **--no-translator**
                  assume the PO file is automatically generated
    
           **--color**
                  use colors and other text attributes always
    
           **--color** =_WHEN_
                  use colors and other text attributes if WHEN.  WHEN may be
                  'always', 'never', 'auto', or 'html'.
    
           **--style** =_STYLEFILE_
                  specify CSS style rule file for **--color**
    
           **-p** , **--properties-output**
                  write out a Java .properties file
    
           **--stringtable-output**
                  write out a NeXTstep/GNUstep .strings file
    
           **-w** , **--width** =_NUMBER_
                  set output page width
    
           **--no-wrap**
                  do not break long message lines, longer than the output
                  page width, into several lines
    
       **Informative output:**
           **-h** , **--help**
                  display this help and exit
    
           **-V** , **--version**
                  output version information and exit
    


* * *
# dh_installmenu

## NAME



           dh_installmenu - install Debian menu files into package build
           directories
    


## SYNOPSIS



           **dh_installmenu**[**debhelper options**] [**-n**]
    


## DESCRIPTION



           **dh_installmenu** is a debhelper program that is responsible for
           installing files used by the Debian **menu** package into package
           build directories.
    
           It also automatically generates the _postinst_ and _postrm_ commands
           needed to interface with the Debian **menu** package. These commands
           are inserted into the maintainer scripts by dh_installdeb(1).
    


## FILES



           debian/_package_.menu
               Debian menu files, installed into usr/share/menu/_package_ in
               the package build directory. See **menufile**(5) for its format.
    
           debian/_package_.menu-method
               Debian menu method files, installed into
               etc/menu-methods/_package_ in the package build directory.
    


## OPTIONS



           **-n** , **--no-scripts**
               Do not modify _postinst_ /_postrm_ scripts.
    


* * *