tripathysagar/man_text huggingface dataset:
# dh_bugfiles

## NAME



           dh_bugfiles - install bug reporting customization files into
           package build directories
    


## SYNOPSIS



           **dh_bugfiles**[**-A**] [_debhelper options_]
    


## DESCRIPTION



           **dh_bugfiles** is a debhelper program that is responsible for
           installing bug reporting customization files (bug scripts and/or
           bug control files and/or presubj files) into package build
           directories.
    


## FILES



           debian/_package_.bug-script
               This is the script to be run by the bug reporting program for
               generating a bug report template. This file is installed as
               _usr/share/bug/package_ in the package build directory if no
               other types of bug reporting customization files are going to
               be installed for the package in question. Otherwise, this file
               is installed as _usr/share/bug/package/script_. Finally, the
               installed script is given execute permissions.
    
           debian/_package_.bug-control
               It is the bug control file containing some directions for the
               bug reporting tool. This file is installed as
               _usr/share/bug/package/control_ in the package build directory.
    
           debian/_package_.bug-presubj
               The contents of this file are displayed to the user by the bug
               reporting tool before allowing the user to write a bug report
               on the package to the Debian Bug Tracking System. This file is
               installed as _usr/share/bug/package/presubj_ in the package
               build directory.
    


## OPTIONS



           **-A** , **--all**
               Install _debian/bug-*_ files to ALL packages acted on when
               respective _debian/package.bug-*_ files do not exist. Normally,
               _debian/bug-*_ will be installed to the first package only.
    


* * *
# msql2mysql

## NAME



           msql2mysql - convert mSQL programs for use with MariaDB
    


## SYNOPSIS



    
           **msql2mysql** _C-source-file_ **...**
    


## DESCRIPTION



           Initially, the MySQL C API was developed to be very similar to
           that for the mSQL database system. Because of this, mSQL programs
           often can be converted relatively easily for use with MariaDB by
           changing the names of the C API functions.
    
           The **msql2mysql** utility performs the conversion of mSQL C API
           function calls to their MariaDB equivalents.  **msql2mysql** converts
           the input file in place, so make a copy of the original before
           converting it. For example, use **msql2mysql** like this:
    
               shell> **cp client-prog.c client-prog.c.orig**
               shell> **msql2mysql client-prog.c**
               client-prog.c converted
    
           Then examine client-prog.c and make any post-conversion revisions
           that may be necessary.
    
           **msql2mysql** uses the **replace** utility to make the function name
           substitutions. See replace(1).
    


* * *
# lttng-crash

## NAME



           lttng-crash - Recover and view LTTng 2 trace buffers in the event
           of a crash
    


## SYNOPSIS



           **lttng-crash**[**--extract** =_PATH_ | **--viewer** =_VIEWER_] [**-v** | **-vv** | **-vvv**]
    


## DESCRIPTION



           The _Linux Trace Toolkit: next generation_ <https://lttng.org/> is
           an open source software package used for correlated tracing of the
           Linux kernel, user applications, and user libraries.
    
           LTTng consists of Linux kernel modules (for Linux kernel tracing)
           and dynamically loaded libraries (for user application and library
           tracing).
    
           The **lttng-crash** command-line tool is used to recover and view
           LTTng trace buffers in the event of a system crash.
    


## OPTIONS



           **-x** _PATH_ , **--extract** =_PATH_
               Extract recovered traces to path _PATH_ ; do not execute the
               trace viewer.
    
           **-v** , **--verbose**
               Increase verbosity.
    
               Three levels of verbosity are available, which are triggered
               by appending additional **v** letters to the option (that is, **-vv**
               and **-vvv**).
    
           **-e** _VIEWER_ , **--viewer** =_VIEWER_
               Use trace viewer _VIEWER_ to view the trace buffers.  _VIEWER_ is
               the absolute path to the viewer command to use, and it can
               contain command arguments as well. The trace directory paths
               are passed to the _VIEWER_ command as its last arguments.
    
               Default: **babeltrace**.
    
       **Program information**
           **-h** , **--help**
               Show help.
    
           **-V** , **--version**
               Show version.
    


## EXIT STATUS



           **0**
               Success
    
           **1**
               Error
    
           **3**
               Fatal error
    


## BUGS



           If you encounter any issue or usability problem, please report it
           on the LTTng bug tracker <https://bugs.lttng.org/projects/lttng-
           tools>.
    


## RESOURCES



           •   LTTng project website <https://lttng.org>
    
           •   LTTng documentation <https://lttng.org/docs>
    
           •   Git repositories <http://git.lttng.org>
    
           •   GitHub organization <http://github.com/lttng>
    
           •   Continuous integration <http://ci.lttng.org/>
    
           •   Mailing list <http://lists.lttng.org> for support and
               development: **lttng-dev@lists.lttng.org**
    
           •   IRC channel <irc://irc.oftc.net/lttng>: **#lttng** on **irc.oftc.net**
    


## THANKS



           Special thanks to Michel Dagenais and the DORSAL laboratory
           <http://www.dorsal.polymtl.ca/> at École Polytechnique de Montréal
           for the LTTng journey.
    
           Also thanks to the Ericsson teams working on tracing which helped
           us greatly with detailed bug reports and unusual test cases.
    


* * *
# pmpython

## NAME



           **pmpython** - run a python script using a preferred python variant
    


## SYNOPSIS



           **pmpython**[_python-args-and-script_]
    


## DESCRIPTION



           **pmpython** provides a way to run python scripts using a customisable
           python interpreter, rather than embedding the name of a particular
           version of python into each script.
    
           This can be useful as it allows version-independent python code to
           be run anywhere.  All python modules shipped with PCP support
           versions 2.6 and later (in the python2 series), and 3.3 and later
           (in the python3 release series).
    
           Due to python monitoring and collecting scripts being relatively
           simple in PCP (not requiring new modules, language features, etc),
           it has been possible to ensure they work for all of the above
           python versions.
    
           However, the name of the python interpreter is not always the
           same, thus, it is common for PCP python scripts to use a “shebang”
           line that launches the **python** interpreter indirectly as follows:
    
              #!/usr/bin/env pmpython
    
           env(1) is used to find the correct path for the **pmpython**
           executable from the user's **$PATH**.
    
           By default the name of the python interpreter is found from the
           the value of **$PCP_PYTHON_PROG** from the environment (if set) else
           from _/etc/pcp.conf_.  The latter is the more typical case where
           this value is based on some heuristics about the platform at the
           time the PCP packages were build and favour the use of _python3_ in
           all recent releases of PCP (for those platforms that support it).
    
           This allows an appropriate name to be used for the python
           interpreter instead of a hard-coded python version name, while
           still allowing the user to override the python interpreter as
           follows:
    
              $ PCP_PYTHON_PROG=python3 pmpython --version
              Python 3.4.2
              $ PCP_PYTHON_PROG=python2 pmpython --version
              Python 2.7.9
    
           This is convenient for shipping identical scripts on multiple
           platforms, and for testing different python versions with the one
           script (e.g. in the case where multiple versions of python are
           installed, PCP_PYTHON_PROG can be set in the local environment to
           override the global setting).
    
           **pmpython** is a replacement for an earlier tool with similar
           function, namely pcp-python(1).
    


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


* * *
# flatpak-mask

## NAME



           flatpak-mask - Mask out updates and automatic installation
    


## SYNOPSIS



    
           **flatpak mask**[OPTION...] PATTERN...
    


## DESCRIPTION



           Flatpak maintains a list of patterns that define which refs are
           masked. A masked ref will never be updated or automatically
           installed (for example a masked extension marked auto-download
           will not be downloaded). You can still manually install such refs,
           but once they are installed the version will be pinned.
    
           The patterns are just a partial ref, with the * character matching
           anything within that part of the ref. Here are some example
           patterns:
    
               org.some.App
               org.some.App//unstable
               app/org.domain.*
               org.some.App/arm
    
           To list the current set of masks, run this command without any
           patterns.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **--remove**
               Instead of adding the patterns, remove matching patterns.
    
           **-u** , **--user**
               Mask refs in a per-user installation.
    
           **--system**
               Mask refs in the default system-wide installation.
    
           **--installation=NAME**
               Mask refs in a system-wide installation specified by NAME
               among those defined in /etc/flatpak/installations.d/. Using
               **--installation=default** is equivalent to using **--system**.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    


## EXAMPLES



           **$ flatpak mask**
    
           **$ flatpak mask org.broken.App**
    
           **$ flatpak mask --remove org.broken.App**
    


* * *
# runaspcp

## NAME



           **runaspcp** - execute a shell command as the user ``pcp''
    


## SYNOPSIS



           **$PCP_BINADM_DIR/runaspcp**[**-D** _debug_] [**-s** _shell_] command
    


## DESCRIPTION



           **runaspcp** runs the single argument _command_ as the user **$PCP_USER**
           and group **$PCP_GROUP**(both from _/etc/pcp.conf_).
    
           The _command_ is run by **sh**(1) by default, else _shell_ from the **-s**(or
           **--shell)** command line argument.
    
           Normally **runaspcp** is used from the PCP ``init'' scripts that are
           launched as ``root'' but need to downgrade their privileges when
           running some PCP daemons as the ``pcp'' user.
    
           The **-?** , **--help** option displays a usage message.
    


## DIAGNOSTICS



           The exit status is 1 if **runaspcp** cannot change user or group, or
           cannot execute the shell, else the exit status of _command_.
    


## PCP ENVIRONMENT



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


## DEBUGGING OPTIONS



           The **-D** or **--debug** option enables the output of additional
           diagnostics on _stderr_ to help triage problems, although the
           information is sometimes cryptic and primarily intended to provide
           guidance for developers rather end-users.  _debug_ is a comma
           separated list of debugging options; use pmdbg(1) with the **-l**
           option to obtain a list of the available debugging options and
           their meaning.
    
           Debugging options specific to **runaspcp** are as follows:
           ┌────────┬─────────────────────┐
           │ **Option** │ **Description** │
           ├────────┼─────────────────────┤
           │ **appl0** │ verbose diagnostics │
           └────────┴─────────────────────┘
    


* * *
# flatpak-document-export

## NAME



           flatpak-document-export - Export a file to a sandboxed application
    


## SYNOPSIS



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


## DESCRIPTION



           Creates a document id for a local file that can be exposed to
           sandboxed applications, allowing them access to files that they
           would not otherwise see. The exported files are exposed in a fuse
           filesystem at /run/user/$UID/doc/.
    
           This command also lets you modify the per-application permissions
           of the documents, granting or revoking access to the file on a
           per-application basis.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-u** , **--unique**
               Don't reuse an existing document id for the file. This makes
               it safe to later remove the document when you're finished with
               it.
    
           **-t** , **--transient**
               The document will only exist for the length of the session.
               This is useful for temporary grants.
    
           **-n** , **--noexist**
               Don't require the file to exist already.
    
           **-a** , **--app=APPID**
               Grant read access to the specified application. The **--allow**
               and **--forbid** options can be used to grant or remove additional
               privileges. This option can be used multiple times.
    
           **-r** , **--allow-read**
               Grant read access to the applications specified with **--app**.
               This defaults to TRUE.
    
           **--forbid-read**
               Revoke read access for the applications specified with **--app**.
    
           **-w** , **--allow-write**
               Grant write access to the applications specified with **--app**.
    
           **--forbid-write**
               Revoke write access for the applications specified with **--app**.
    
           **-d** , **--allow-delete**
               Grant the ability to remove the document from the document
               portal to the applications specified with **--app**.
    
           **--forbid-delete**
               Revoke the ability to remove the document from the document
               portal from the applications specified with **--app**.
    
           **-g** , **--allow-grant-permission**
               Grant the ability to grant further permissions to the
               applications specified with **--app**.
    
           **--forbid-grant-permission**
               Revoke the ability to grant further permissions for the
               applications specified with **--app**.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


## EXAMPLES



           **$ flatpak document-export --app=org.gnome.gedit ~/test.txt**
    
               /run/user/1000/doc/e52f9c6a/test.txt
    


* * *
# git-refs

## NAME



           git-refs - Low-level access to refs
    


## SYNOPSIS



           **git refs migrate --ref-format=**_< format>_ [**--no-reflog**] [**--dry-run**]
           **git refs verify**[**--strict**] [**--verbose**]
    


## DESCRIPTION



           This command provides low-level access to refs.
    


## COMMANDS



           migrate
               Migrate ref store between different formats.
    
           verify
               Verify reference database consistency.
    


## OPTIONS



           The following options are specific to _git refs migrate_ :
    
           --ref-format=<format>
               The ref format to migrate the ref store to. Can be one of:
    
               •   **files** for loose files with packed-refs. This is the
                   default.
    
               •   **reftable** for the reftable format. This format is
                   experimental and its internals are subject to change.
    
           --dry-run
               Perform the migration, but do not modify the repository. The
               migrated refs will be written into a separate directory that
               can be inspected separately. The name of the directory will be
               reported on stdout. This can be used to double check that the
               migration works as expected before performing the actual
               migration.
    
           --reflog, --no-reflog
               Choose between migrating the reflog data to the new backend,
               and discarding them. The default is "--reflog", to migrate.
    
           The following options are specific to _git refs verify_ :
    
           --strict
               Enable stricter error checking. This will cause warnings to be
               reported as errors. See git-fsck(1).
    
           --verbose
               When verifying the reference database consistency, be chatty.
    


## KNOWN LIMITATIONS



           The ref format migration has several known limitations in its
           current form:
    
           •   It is not possible to migrate repositories that have
               worktrees.
    
           •   There is no way to block concurrent writes to the repository
               during an ongoing migration. Concurrent writes can lead to an
               inconsistent migrated state. Users are expected to block
               writes on a higher level. If your repository is registered for
               scheduled maintenance, it is recommended to unregister it
               first with git-maintenance(1).
    
           These limitations may eventually be lifted.
    


## GIT



           Part of the git(1) suite
    


* * *
# aria_pack

## NAME



           aria_pack - generate compressed, read-only Aria tables
    


## SYNOPSIS



           **aria_pack**[_OPTIONS_] _filename_...
    


## DESCRIPTION



           Pack a Aria-table to take much less space.  Keys are not updated,
           you must run **aria_chk -rq** on the index (.MAI) file afterwards to
           update the keys.  You should give the .MAI file as the filename
           argument.  To unpack a packed table, run **aria_chk -u** on the table
    
           **-b** , **--backup**
                  Make a backup of the table as table_name.OLD.
    
           **--character-sets-dir** =_name_
                  Directory where character sets are.
    
           **-#** , **--debug**[=_name_]
                  Output debug log. Often this is 'd:t:o,filename'.
    
           **-f** , **--force**
                  Force packing of table even if it gets bigger or if
                  tempfile exists.
    
           **-j** , **--join** =_name_
                  Join all given tables into 'new_table_name'. All tables
                  MUST have identical layouts.
    
           **-?** , **--help**
                  Display this help and exit.
    
           **-s** , **--silent**
                  Be more silent.
    
           **-T** , **--tmpdir** =_name_
                  Use temporary directory to store temporary table.
    
           **-t** , **--test**
                  Don't pack table, only test packing it.
    
           **-v** , **--verbose**
                  Write info about progress and packing result. Use many **-v**
                  for more verbosity!
    
           **-V** , **--version**
                  Output version information and exit.
    
           **-w** , **--wait**
                  Wait and retry if table is in use.
    
           Default options are read from the following files in the given
           order: **/etc/my.cnf /etc/mysql/my.cnf ~/.my.cnf**
    
           The following groups are read: **ariapack**
    
           The following options may be given as the first argument:
    
           **--print-defaults**
                  Print the program argument list and exit.
    
           **--no-defaults**
                  Don't read default options from any option file.
    
           **--defaults-file=** #
                  Only read default options from the given file #.
    
           **--defaults-extra-file=** #
                  Read this file after the global files are read.
    


* * *
# pcp-netstat

## NAME



           **pcp-netstat** - Report statistics for different network protocols
           and network interfaces.
    


## SYNOPSIS



           **pcp**[_pcp options_] **netstat**[**--statistics**] [**-p** _[TCP|IP|UDP|ICMP]_]
           [**-i**] [**-s** _samples_] [**-a** _archive_] [**-S** _start_time_] [**-T** _end_time_]
    


## DESCRIPTION



           The **pcp-netstat** command is used for viewing the different kinds of
           statistics related to the network protocols and the network
           interfaces. This tool is useful for checking the status of your
           network interfaces, network connections and for troubleshooting
           network issues.  This tool can also be used to analyze network
           statistics for all available protocols, including TCP, UDP, ICMP,
           and IP protocols.
    
           By default **pcp-netstat** reports live data for the local host. It
           has the capabilities to analyze the data on the archives as well.
    


## OPTIONS



           **--statistics**
                  shows output similar to netstat -s, which displays summary
                  statistics for each protocol
    
           **-i** shows output similar to netstat -i -a -n, which displays a
                  table of all network interfaces
    
           **-p** , **--TCP|IP|UDP|ICMP**
                  filter network statistics specific to a protocol
    
           **-a** _file_ , **--archive** =_file_
                  Fetch /proc/netstat for a specified archive _file_
    
           **-s** _count_ , **--samples** =_count_
                  Get the network statistics for specified number of samples
                  _count_
    
           **-S** , **--start** =_time_
                  Filter the samples from the archive from the given _time_
    
           **-T** , **--finish=time**
                  Filter the samples from the archive until the given _time_
    
           **-V** , **--version**
                  Display version number and exit.
    
           **-?** , **--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).
    
           For environment variables affecting PCP tools, see
           pmGetOptions(3).
    


* * *
# asn2deb

## NAME



           asn2deb - Create a Debian package for BER monitoring from ASN.1
    


## SYNOPSIS



           **asn2deb**[ **-a** <ASN.1 file> ] [ **--asn** =<ASN.1 file> ] [ **-d** <opts> ] [
           **--dbopts** =<opts> ] [ **-e** <address> ] [ **--email** =<address> ] [ **-h**] [
           **--help**] [ **-n** <name> ] [ **--name** =<name> ] [ **-p**] [ **--preserve**] [
           **-v**] [ **--version**]
    


## DESCRIPTION



           This manual page documents briefly the **asn2deb** command. **asn2deb**
           takes an ASN.1 file as input and creates a Debian package from it.
           The package contains a loadable type table file for the Wireshark
           network analyzer. The type table is generated by the ASN.1
           compiler **esnacc**.
    


## OPTIONS



           -a <ASN.1 file> --asn=<ASN.1 file>
               ASN.1 file to use (mandatory).
    
           -d <opts> --dbopts=<opts>
               options for dpkg-buildpackage.
    
           -e <address> --email=<address>
               use e-mail address.
    
           -h --help
               print help and exit.
    
           -n <name> --name=<name>
               use user name.
    
           -p --preserve
               do not overwrite files.
    
           -v --version
               print version and exit.
    


## EXAMPLES



           /usr/bin/asn2deb -e me@foo.net -a bar.asn1 \-n "My Name" -d
           "-rfakeroot -uc -us"-d "-rfakeroot -uc -us"
    


## COPYING



           This manual page was written by W. Borgert debacle@debian.org for
           Debian GNU/Linux (but may be used by others). Permission is
           granted to copy, distribute and/or modify this document under the
           terms of the GNU General Public License, Version 2 or any later
           version published by the Free Software Foundation.
    


* * *
# lpq

## NAME



           lpq - show printer queue status
    


## SYNOPSIS



           **lpq**[ **-h** _server_[**:**_port_] ] [ **-E**] [ **-U** _username_ ] [ **-P**
           _destination_[**/**_instance_] ] [ **-a**] [ **-l**] [ **+**_interval_ ]
    


## DESCRIPTION



           **lpq** shows the current print queue status on the named printer.
           Jobs queued on the default destination will be shown if no printer
           or class is specified on the command-line.
    
           The _+interval_ option allows you to continuously report the jobs in
           the queue until the queue is empty; the list of jobs is shown once
           every _interval_ seconds.
    


## OPTIONS



           **lpq** supports the following options:
    
           **-E** Forces encryption when connecting to the server.
    
           **-P** _destination_[**/**_instance_]
                Specifies an alternate printer or class name.
    
           **-U** _username_
                Specifies an alternate username.
    
           **-a** Reports jobs on all printers.
    
           **-h** _server_[**:**_port_]
                Specifies an alternate server.  Note: This option must occur
                before all others.
    
           **-l** Requests a more verbose (long) reporting format.
    


* * *
# pmiestatus

## NAME



           **pmiestatus** - display information from pmie stats file
    


## SYNOPSIS



           **pmiestatus** _statsfile_ [...]
    


## DESCRIPTION



           **pmiestatus** displays information used to identify a running pmie(1)
           process.  It is mostly used by pmie_check(1) and pmie_daily(1)
           when they hunt for instances of **pmie** to check against the control
           file.
    


## FILES



           _$PCP_TMP_DIR/pmie/*_
                pmie stats files
    


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


* * *
# perf-archive

## NAME



           perf-archive - Create archive with object files with build-ids
           found in perf.data file
    


## SYNOPSIS



           _perf archive_ [file]
    


## DESCRIPTION



           This command runs perf-buildid-list --with-hits, and collects the
           files with the buildids found so that analysis of perf.data
           contents can be possible on another machine.
    


* * *
# yum-utils

## NAME



           yum-utils - tools for manipulating repositories and extended
           package management
    


## SYNOPSIS



           **debuginfo-install** - install debuginfo packages and their dependencies
           **find-repos-of-install** - report which repository the package was installed from
           **needs-restarting** - report process ids that started running before they or some component they use were updated
           **package-cleanup** - manage package cleanup, duplicates, orphaned packages and outstanding dependency problems
           **repo-graph** - outputs a full package dependency list in dot format
           **repo-rss** - generates an RSS feed from one or more repositories
           **repoclosure** - reads metadata of repositories, checks dependencies and displays list of unresolved dependencies
           **repodiff** - takes two or more repositories, returns a list of added, removed or changed packages
           **repomanage** - manages a directory of rpm packages, returns a list of newest or oldest packages in a directory
           **repoquery** - query yum repositories and get additional information on the them
           **reposync** - synchronize a remote yum repository to a local directory using yum to retrieve packages
           **repotrack** - track packages and its dependencies and downloads them
           **show-changed-rco** - list of changes to a package Requires, Conflicts and Obsoletes data from installed to a specified rpm file
           **show-installed** - gives a compact description of packages installed and makes use of comps groups in repositories
           **verifytree** - verify that a local yum repository is consistent
           **yum-builddep** - installs missing dependencies to build a specified package
           **yum-complete-transaction** - finds incomplete or aborted yum transactions and attempts to complete them
           **yum-config-manager** - toggle yum repositories, add new repositories and set main yum configuration options
           **yum-debug-dump** - creates gzipped file containing information for debugging problems
           **yum-debug-restore** - replays any transactions captured in gzipped file in yum shell
           **yum-groups-manager** - create and edit yum's group metadata
           **yumdb** - query or alter the yum database
           **yumdownloader** - downloads packages from yum repositories including source RPMs
    


## DESCRIPTION



           **yum-utils** is a collection of tools and programs for managing yum
           repositories, installing debug packages, source packages, extended
           information from repositories and administration.
    


## NOTES



           See respective tools for additional help for commands without a
           manual page
    


* * *
# manpath

## NAME



           manpath - determine search path for manual pages
    


## SYNOPSIS



           **manpath**[**-qgdc?V**] [**-m** _system_[,...]] [**-C** _file_]
    


## DESCRIPTION



           If $**MANPATH** is set, **manpath** will simply display its contents and
           issue a warning.  If not, **manpath** will determine a suitable manual
           page hierarchy search path and display the results.
    
           The colon-delimited path is determined using information gained
           from the man-db configuration file – (_/usr/local/etc/man_db.conf_)
           and the user's environment.
    


## OPTIONS



           **-q** , **--quiet**
                  Do not issue warnings.
    
           **-d** , **--debug**
                  Print debugging information.
    
           **-c** , **--catpath**
                  Produce a catpath as opposed to a manpath.  Once the
                  manpath is determined, each path element is converted to
                  its relative catpath.
    
           **-g** , **--global**
                  Produce a manpath consisting of all paths named as "global"
                  within the man-db configuration file.
    
           **-m** _system_[,...], **--systems=**_system_[,...]
                  If this system has access to other operating systems'
                  manual hierarchies, this option can be used to include them
                  in the output of **manpath**.  To include NewOS's manual page
                  hierarchies use the option **-m NewOS**.
    
                  The _system_ specified can be a combination of comma
                  delimited operating system names.  To include the native
                  operating system's manual page hierarchies, the system name
                  **man** must be included in the argument string.  This option
                  will override the $**SYSTEM** environment variable.
    
           **-C** _file_ , **--config-file=**_file_
                  Use this user configuration file rather than the default of
                  _~/.manpath_.
    
           **-?** , **--help**
                  Print a help message and exit.
    
           **--usage**
                  Print a short usage message and exit.
    
           **-V** , **--version**
                  Display version information.
    


## ENVIRONMENT



           **MANPATH**
                  If $**MANPATH** is set, **manpath** displays its value rather than
                  determining it on the fly.
    
                  See the **SEARCH PATH** section of manpath(5) for the default
                  behaviour and details of how this environment variable is
                  handled.
    
           **SYSTEM** If $**SYSTEM** is set, it will have the same effect as if it
                  had been specified as the argument to the **-m** option.
    


## FILES



           _/usr/local/etc/man_db.conf_
                  man-db configuration file.
    


## BUGS



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


* * *
# ovs-pcap

## NAME



           ovs-pcap - print packets from a pcap file as hex
    


## SYNOPSIS



           **ovs-pcap** _file_
    
           Common options:
                  [**-h** | **--help**] [**-V** | **--version**]
    


## DESCRIPTION



           The **ovs-pcap** program reads the pcap _file_ named on the command line
           and prints each packet's contents as a sequence of hex digits on a
           line of its own.  This format is suitable for use with the
           **ofproto/trace** command supported by ovs-vswitchd(8).
    


## OPTIONS



           **-h**
           **--help** Prints a brief help message to the console.
    
           **-V**
           **--version**
                  Prints version information to the console.
    


* * *
# autofsd-probe

## NAME



           **autofsd-probe** - probe AutoFS mount/unmount daemon
    


## SYNOPSIS



           **$PCP_BINADM_DIR/autofsd-probe**[**-h** _host_] [**-t** _timeout_]
    


## DESCRIPTION



           **autofsd-probe** will check the status of the **autofsd**(1) daemon on
           the specified _host_.
    
           Unless directed to another _host_ by the **-h** option, **autofsd-probe**
           will contact the **AutoFS** daemon on the local host.
    
           The **AutoFS** file system is built on the Remote Procedure Call
           (RPC(3)) library routines.  The **-t** option allows the total timeout
           and retry timeout intervals to be set for all remote procedure
           call operations used with **autofsd-probe**.  This option accepts an
           interval argument in the form described in the PCPIntro(1) manual
           page.
    
           **autofsd-probe** is typically used in an automated fashion from
           within pmdashping(1) and in conjunction with pmie(1), for
           monitoring response time and service failure.
    
           By default **autofsd-probe** will not produce any output, unless there
           is an error in which case a diagnostic message will be displayed
           and the exit status will indicate the reason for failure.
    


## DIAGNOSTICS



           If **autofsd-probe** succeeds, then 0 will be returned.  If the
           attempt to establish a connection with **autofsd** fails, then 2 is
           returned.  If the subsequent attempt to invoke an **autofsd** response
           fails, then 1 will be returned.
    
           In the case of a syntactical command line error, 4 is returned and
           the usage message is displayed.
    


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


* * *
# eqn2graph

## Name



           eqn2graph - convert an _eqn_ equation into a cropped image
    


## Synopsis



           **eqn2graph**[**-format** _output-format_] [_convert-argument_ ...]
    
           **eqn2graph --help**
    
           **eqn2graph -v**
    
           **eqn2graph --version**
    


## Description



           _eqn2graph_ reads a one-line _eqn_(1) equation from the standard input
           and writes an image file, by default in Portable Network Graphics
           (PNG) format, to the standard output.
    
           The input EQN code should _not_ be preceded by the **.EQ** macro that
           normally precedes it within _groff_(1) macros; nor do you need to
           have dollar-sign or other delimiters around the equation.
    
           Arguments not recognized by _eqn2graph_ are passed to the
           ImageMagick or GraphicsMagick program _convert_(1).  By specifying
           these, you can give your image a border, set the image's pixel
           density, or perform other useful transformations.
    
           The output image is clipped using _convert_ 's **-trim** option to the
           smallest possible bounding box that contains all the black pixels.
    


## Options



           **--help** displays a usage message, while **-v** and **--version** show
           version information; all exit afterward.
    
           **-format** _output-format_
                  Write the image in _output-format_ , which must be understood
                  by _convert_ ; the default is PNG.
    


## Environment



           _GROFF_TMPDIR_
           _TMPDIR_
           _TMP_
           _TEMP_   These environment variables are searched in the order shown
                  to determine the directory where temporary files will be
                  created.  If none are set, _/tmp_ is used.
    


## Authors



           _eqn2graph_ was written by Eric S. Raymond ⟨esr@thyrsus.com⟩, based
           on a recipe for _pic2graph_(1), by W. Richard Stevens.
    


## See also



           _pic2graph_(1), _grap2graph_(1), _eqn_(1), _groff_(1), _convert_(1)
    


* * *
# quotasync

## NAME



           quotasync - synchronize in-kernel file system usage and limits to
           disk format
    


## SYNOPSIS



           **quotasync**[ **-ugP**] _mount-point_...
           **quotasync**[ **-ugP**] **-a**
           **quotasync -h** | **-V**
    


## DESCRIPTION



           **quotasync** flushes file system usage and limits from kernel memory
           to quota files stored in the file system. By default only the user
           quotas are synchronized.
    
           This tool can be useful if you want to display accurate quotas by
           tools that parse quota files, like repquota(8).
    


## OPTIONS



           **-u, --user**
                  Synchronize user usage and limits.
    
           **-g, --group**
                  Synchronize group usage and limits.
    
           **-P, --project**
                  Synchronize project usage and limits.
    
           **-a, --all**
                  Synchronize usage and limits on all file systems. You have
                  to specify this option or to specify desired file systems.
    
           **-V, --version**
                  Show program version information and exit.
    
           **-h, --help**
                  Show program usage and exit.
    


## DIAGNOSTICS



           If requested synchronization fails, or invalid option is given,
           **quotasync** will terminate with non-zero exit code. Otherwise it
           will return zero.
    


## FILES



           **aquota.user  or  aquota.group**
                  Quota file at the file system root (version 2 quota, non-
                  XFS/GFS2 file systems).
           **quota.user  or  quota.group**
                  Quota file at the file system root (version 1 quota, non-
                  XFS/GFS2 file systems).
           **/etc/mtab**
                  List of mounted file systems maintained by user space.
           **/proc/mounts**
                  List of mounted file systems maintained by kernel.
    


* * *
# dh_installmodules

## NAME



           dh_installmodules - register kernel modules
    


## SYNOPSIS



           **dh_installmodules**[_debhelper options_] [**-n**] [**--name=**_name_]
    


## DESCRIPTION



           **dh_installmodules** is a debhelper program that is responsible for
           registering kernel modules.
    
           Kernel modules are searched for in the package build directory and
           if found, _preinst_ , _postinst_ and _postrm_ commands are automatically
           generated to run **depmod** and register the modules when the package
           is installed.  These commands are inserted into the maintainer
           scripts by dh_installdeb(1).
    


## FILES



           debian/_package_.modprobe
               Installed to usr/lib/modprobe.d/_package_.conf in the package
               build directory.  Before compat version 14, files get
               installed under etc/modprobe.d instead.
    


## OPTIONS



           **-n** , **--no-scripts**
               Do not modify _preinst_ /_postinst_ /_postrm_ scripts.
    
           **--name=**_name_
               When this parameter is used, **dh_installmodules** looks for and
               installs files named debian/_package_._name_.modprobe instead of
               the usual debian/_package_.modprobe
    


## NOTES



           Note that this command is not idempotent. dh_prep(1) should be
           called between invocations of this command. Otherwise, it may
           cause multiple instances of the same text to be added to
           maintainer scripts.
    


* * *
# dh_ucf

## NAME



           dh_ucf - register configuration files with ucf
    


## SYNOPSIS



           **dh_ucf**[_debhelper options_] [**-A**] [**-n**] [_file_ ...]
    


## DESCRIPTION



           **dh_ucf** is a debhelper program that is responsible for generating
           the _postinst_ and _postrm_ commands that register files with **ucf**(1)
           and **ucfr**(1).
    


## FILES



           debian/_package_.ucf
               List pairs of source and destination files to register with
               ucf. Each pair should be put on its own line, with the source
               and destination separated by whitespace. Both source and
               destination must be absolute paths. The source should be a
               file that is provided by your package, typically in
               /usr/share/, while the destination is typically a file in
               /etc/.
    
               A dependency on ucf will be generated in **${misc:Depends}**.
    
               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.
    
           **-n** , **--no-scripts**
               Do not modify _postinst_ /_postrm_ scripts. Turns this command into
               a no-op.
    
           _file_ ...
               Install these info files into the first package acted on. (Or
               in all packages if **-A** is specified).
    


## NOTES



           Note that this command is not idempotent. dh_prep(1) should be
           called between invocations of this command. Otherwise, it may
           cause multiple instances of the same text to be added to
           maintainer scripts.
    


* * *
# idl2deb

## NAME



           idl2deb - Create a Debian package for CORBA monitoring from IDL
    


## SYNOPSIS



           **idl2deb**[ **-d** <opts> ] [ **--dbopts** =<opts> ] [ **-e** <address> ] [
           **--email** =<address> ] [ **-h**] [ **--help**] [ **-i** <idlfile> ] [
           **--idl** =<idlfile> ] [ **-n** <name> ] [ **--name** =<name> ] [ **-p**] [
           **--preserve**] [ **-v**] [ **--version**]
    


## DESCRIPTION



           This manual page documents briefly the **idl2deb** command. **idl2deb**
           takes an CORBA IDL file as input and creates a Debian package from
           it. The package contains a loadable module for the Wireshark
           network analyzer.
    


## OPTIONS



           -d <opts> --dbopts=<opts>
               options for dpkg-buildpackage.
    
           -e <address> --email=<address>
               use e-mail address.
    
           -h --help
               print help and exit.
    
           -i <idlfile> --idl=<idlfile>
               IDL file to use (mandatory)
    
           -n <name> --name=<name>
               use user name.
    
           -p --preserve
               do not overwrite files.
    
           -v --version
               print version and exit.
    


## EXAMPLES



           /usr/bin/idl2deb -e me@foo.net -i bar.idl \-n "My Name" -d
           "-rfakeroot -uc -us"-d "-rfakeroot -uc -us"
    


## COPYING



           This manual page was written by W. Borgert debacle@debian.org for
           Debian GNU/Linux (but may be used by others). Permission is
           granted to copy, distribute and/or modify this document under the
           terms of the GNU General Public License, Version 2 or any later
           version published by the Free Software Foundation.
    


* * *