tripathysagar/man_text huggingface dataset:
# rping

## NAME



           rping - RDMA CM connection and RDMA ping-pong test.
    


## SYNOPSIS



           _rping_ -s [-v] [-V] [-d] [-P] [-a address] [-p port]
                     [-C message_count] [-S message_size]
           _rping_ -c [-v] [-V] [-d] [-I address] -a address [-p port]
                     [-C message_count] [-S message_size]
    


## DESCRIPTION



           Establishes a reliable RDMA connection between two nodes using the
           librdmacm, optionally performs RDMA transfers between the nodes,
           then disconnects.
    


## OPTIONS



           -s     Run as the server.
    
           -c     Run as the client.
    
           -a address
                  On the server, specifies the network address to bind the
                  connection to.  To bind to any address with IPv6 use -a ::0
                  .  On the client, specifies the server address to connect
                  to.
    
           -I address
                  The address to bind to as the source IP address to use.
                  This is useful if you have multiple addresses on the same
                  network or complex routing.
    
           -p     Port number for listening server.
    
           -v     Display ping data.
    
           -V     Validate ping data.
    
           -d     Display debug information.
    
           -C message_count
                  The number of messages to transfer over each connection.
                  (default infinite)
    
           -S message_size
                  The size of each message transferred, in bytes.  (default
                  100)
    
           -P     Run the server in persistent mode.  This allows multiple
                  rping clients to connect to a single server instance. The
                  server will run until killed.
    
           -q     Control QP Creation/Modification directly from the
                  application, instead of rdma_cm.
    


## NOTES



           Because this test maps RDMA resources to userspace, users must
           ensure that they have available system resources and permissions.
           See the libibverbs README file for additional details.
    


* * *
# pmdafarm

## NAME



           **pmdafarm** - Seagate FARM Log PMDA
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/farm/pmdafarm**[**-D** _debug_]
    


## DESCRIPTION



           **pmdafarm** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values for Device Mapper on the local system.
    
           This PMDA collects its data through the **smartctl**(8) utility and
           requires that the program is installed in order to function.
    
           Further details on smartctl and smartmontools can be found at
           **https://smartmontools.org **.
    


## INSTALLATION



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


## FILES



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


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


* * *
# my_safe_process

## NAME



           my_safe_process - Utility program that encapsulates process
           creation, monitoring and bulletproof process cleanup
    


## DESCRIPTION



           Use: safe_process [options to safe_process] -- progname arg1 ...
           argn.
    
           For more information, please refer to the MariaDB Knowledge Base,
           available online at https://mariadb.com/kb/
    


* * *
# trace-cmd-stream

## NAME



           trace-cmd-stream - stream a trace to stdout as it is happening
    


## SYNOPSIS



           **trace-cmd stream [**_OPTIONS_**]**[_command_]
    


## DESCRIPTION



           The trace-cmd(1) stream will start tracing just like
           trace-cmd-record(1), except it will not record to a file and
           instead it will read the binary buffer as it is happening, convert
           it to a human readable format and write it to stdout.
    
           This is basically the same as trace-cmd-start(1) and then doing a
           trace-cmd-show(1) with the **-p** option. trace-cmd-stream is not as
           efficient as reading from the pipe file as most of the stream work
           is done in userspace. This is useful if it is needed to do the
           work mostly in userspace instead of the kernel, and stream also
           helps to debug trace-cmd-profile(1) which uses the stream code to
           perform the live data analysis for the profile.
    


## OPTIONS



               These are the same as trace-cmd-record(1), except that it does not take
               the *-o* option.
    


## RESOURCES



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


## COPYING



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


## NOTES



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


* * *
# man-recode

## NAME



           man-recode - convert manual pages to another encoding
    


## SYNOPSIS



           **man-recode -t** _to-code_ {**--suffix=**_suffix_ |**--in-place**} [**-dqhV**]
           [_filename_]
    


## DESCRIPTION



           **man-recode** converts multiple manual pages from one encoding to
           another, guessing the appropriate input encoding for each one.  It
           is useful when permanently recoding pages written in legacy
           character sets, or in build systems that need to recode a set of
           pages to a single common encoding (usually UTF-8) for
           installation.  When converting many manual pages, this program is
           much faster than running **man --recode** or **manconv** on each page.
    
           If an encoding declaration is found on the first line of a manual
           page, then that declaration is used as the input encoding for that
           page.  Failing that, the input encoding is guessed based on the
           file name.
    
           Encoding declarations have the following form:
    
                  '\" -*- coding: UTF-8 -*-
    
           or (if manual page preprocessors are also to be declared):
    
                  '\" t -*- coding: ISO-8859-1 -*-
    


## OPTIONS



           **-t** _encoding_ , **--to-code=**_encoding_
                  Convert manual pages to _encoding_.
    
           **--suffix=**_suffix_
                  Form each output file name by appending _suffix_ to the input
                  file name, after removing any compression extension.
    
           **--in-place**
                  Overwrite each input file with the output, after removing
                  any compression extension.
    
           **-q** , **--quiet**
                  Do not issue error messages when the page cannot be
                  converted.
    
           **-d** , **--debug**
                  Print debugging information.
    
           **-h** , **--help**
                  Print a help message and exit.
    
           **-V** , **--version**
                  Display version information.
    


## BUGS



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


* * *
# pmdazswap

## NAME



           **pmdazswap** - zswap (compressed swap) PMDA
    


## DESCRIPTION



           **pmdazswap** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values about compressed swap operation, as tracked
           by the **zswap** Linux kernel module.
    
           Zswap is a lightweight compressed cache for swap pages.  It takes
           pages that are in the process of being swapped out and attempts to
           compress them into a dynamically allocated RAM-based memory pool.
           Zswap trades CPU cycles for potentially reduced swap I/O.  This
           tradeoff can also result in a performance improvement if reads
           from the compressed cache are faster than reads from a swap
           device.
    
           This PMDA exports metrics about pool size, number of pages stored,
           and various counters for the reasons pages are rejected.
    


## INSTALLATION



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


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


* * *
# openvt

## NAME



           openvt - start a program on a new virtual terminal (VT).
    


## SYNOPSIS



           **openvt**[-c vtnumber] [OPTIONS] [--] command
    


## DESCRIPTION



           **openvt** will find the first available VT, and run on it the given
           **command** with the given **command options ,** standard input, output
           and error are directed to that terminal. The current search path
           ($PATH) is used to find the requested command. If no command is
           specified then the environment variable $SHELL is used.
    
       **OPTIONS**
           **-c** , **--console** =_VTNUMBER_
                  Use the given VT number and not the first available. Note
                  you must have write access to the supplied VT for this to
                  work.
    
           **-f** , **--force**
                  Force opening a VT without checking whether it is already
                  in use.
    
           **-e** , **--exec**
                  Directly execute the given command, without forking.  This
                  option is meant for use in _/etc/inittab_.
    
           **-s** , **--switch**
                  Switch to the new VT when starting the command. The VT of
                  the new command will be made the new current VT.
    
           **-u** , **--user**
                  Figure out the owner of the current VT, and run login as
                  that user.  Suitable to be called by init. Shouldn't be
                  used with _-c_ or _-l_.
    
           **-l** , **--login**
                  Make the command a login shell. A - is prepended to the
                  name of the command to be executed.
    
           **-v** , **--verbose**
                  Be a bit more verbose.
    
           **-w** , **--wait**
                  wait for command to complete. If -w and -s are used
                  together then **openvt** will switch back to the controlling
                  terminal when the command completes.
    
           **-V** , **--version**
                  print program version and exit.
    
           **-h** , **--help**
                  show this text and exit.
    
           **--** end of options to **openvt**.
    


## NOTE



           If **openvt** is compiled with a getopt_long() and you wish to set
           options to the command to be run, then you must supply the end of
           options -- flag before the command.
    


## EXAMPLES



           **openvt** can be used to start a shell on the next free VT, by using
           the command:
    
           _openvt bash_
    
           To start the shell as a login shell, use:
    
           _openvt -l bash_
    
           To get a long listing you must supply the -- separator:
    
           _openvt -- ls -l_
    


* * *
# paste

## NAME



           paste - merge lines of files
    


## SYNOPSIS



           **paste**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Write lines consisting of the sequentially corresponding lines
           from each FILE, separated by TABs, to standard output.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-d** , **--delimiters** =_LIST_
                  reuse characters from LIST instead of TABs
    
           **-s** , **--serial**
                  paste one file at a time instead of in parallel
    
           **-z** , **--zero-terminated**
                  line delimiter is NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# pmlogger_merge

## NAME



           **pmlogger_merge** - helper script to merge Performance Co-Pilot
           archives
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmlogger_merge**[**-fNVE?**]  [_input-basename_ ...
           _output-name_]
    


## DESCRIPTION



           **pmlogger_merge** is a helper script that is used by
           pmlogger_daily(1) when merging all of the Performance Co-Pilot
           (PCP) archives for a single host on a single day into a combined
           PCP archive.
    
           **pmlogger_merge** is a wrapper script for pmlogextract(1) that merges
           all of the archives matching the _input-basename_ arguments and
           creates a new archive using _output-name_ as the base name for the
           physical files that constitute an archive.  The _input-basename_
           arguments may contain meta characters in the style of **sh**(1).
    
           If any of the files that are components of the _input-basename_
           archives has been compressed then on success **pmlogger_merge** will
           compress _output-name_ using pmlogcompress(1).
    


## OPTIONS



           The available command line options are:
    
           **-f** , **--force**
                This option causes all of the input files to be removed once
                the output archive has been created.
    
           **-N** , **--showme**
                Runs **pmlogger_merge** in a ``show me'' or ``dry run'' mode
                where the tasks that would be performed are reported, but no
                changes are made.  This is typically used for debugging in
                combination with one (verbose) or two (very verbose) **-V**
                options.
    
           **-V** , **--verbose**
                Increase verbosity in the output progress report.
    
           **-E** , **--expunge**
                When metric metadata differences are encountered between
                archives to be merged, the default behaviour is for
                **pmlogger_merge** to fail with a fatal error and the _output-name_
                archive is not created.  The **-E** flag instead issues a warning
                and excludes the affected metrics from the merged output
                archive.  This is intended for automated daily archive
                rotation where it is highly desirable for unattended daily
                archive merging, rewriting and compression to succeed.  See
                also pmlogger_daily(1) and the **-x** flag to pmlogextract(1).
    
           **-?** , **--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).
    


* * *
# pcp-kube-pods

## NAME



           **pcp-kube-pods** - list Kubernetes pods to scan for running PCP
           services
    


## SYNOPSIS



           **$PCP_BINADM_DIR/discover/pcp-kube-pods**
    


## DESCRIPTION



           **pcp-kube-pods** uses **kubectl**(1) to provide a list of IP addresses
           for PODs running in a local Kubenetes cluster, that may be running
           PCP services like pmcd(1) and pmproxy(1).
    
           It is used by the pmfind(1) command and the pmDiscoverServices(3)
           API as a ``shell'' command.
    
           The script invokes the **kubectl get pod** command line (see
           **kubectl-get**(1)) to discover IP addresses for pods.  The
           **.status.podIP** output field is extracted from the Kubernetes pod
           object(s).  Additional options can be specified via configuration
           file, such as _-l service=database_ to restrict the results using
           Kubernetes pod labels.  The default configuration file is
           **$PCP_SYSCONF_DIR/discover/pcp-kube-pods.conf**.
    
           If no local **kubectl** command is found, nothing is reported and an
           exit code indicating success is returned.
    


## DIAGNOSTICS



           All diagnostics produced are provided by the **kubectl** command.
    
           The **kubectl** exit status is propagated unchanged.
    


## FILES



           _$PCP_BINADM_DIR/discover_
                default path to address discovery commands like **pcp-kube-pods**
    
           _$PCP_SYSCONF_DIR/discover/pcp-kube-pods.conf_
                configuration file containing command line options passed to
                **kubectl-get**
    
           _$PCP_SYSCONF_DIR/discover/pcp-kube-pods.disabled_
                existence of this file causes the script to report nothing
    


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


* * *
# dh_installtmpfiles

## NAME



           dh_installtmpfiles - install tmpfiles.d configuration files
    


## SYNOPSIS



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


## DESCRIPTION



           **dh_installtmpfiles** is a debhelper program that is responsible for
           installing package maintainer supplied tmpfiles.d configuration
           files (e.g. for systemd-tmpfiles).
    
           It also finds the tmpfiles.d configuration files installed by a
           package and generates _postinst_ code blocks for activating the
           tmpfiles.d configuration when the package is installed. These
           snippets are added to the maintainer scripts by dh_installdeb(1).
    
           In compat 14+, tmpfiles.d files are copied into the _postrm_ script,
           and they are used with systemd-tmpfiles --remove after the package
           is removed and --purge when the package is purged. This allows one
           to use the tmpfiles.d mechanism to clean up files that are no
           longer needed after a package has been removed/purged.
    


## OPTIONS



           **--name=**_name_
               This option controls both a prefix used for looking up
               maintainer provided tmpfiles.d configuration files (those
               mentioned in the "FILES" section) and also the base name used
               for the installed version of the file.
    


## FILES



           debian/_package_.tmpfiles
               If this exists, it is installed into _usr/lib/tmpfiles.d/_ in
               the package build directory. Note that the "tmpfiles.d"
               mechanism is currently only used by systemd.
    
           debian/_package_.tmpfile
               Deprecated name for debian/_package_.tmpfiles.
    


## NOTES



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


* * *
# runcon

## NAME



           runcon - run command with specified security context
    


## SYNOPSIS



           **runcon** _CONTEXT COMMAND_ [_args_]
           **runcon**[ _-c_ ] [_-u USER_] [_-r ROLE_] [_-t TYPE_] [_-l RANGE_] _COMMAND_
           [_args_]
    


## DESCRIPTION



           Run COMMAND with completely-specified CONTEXT, or with current or
           transitioned security context modified by one or more of LEVEL,
           ROLE, TYPE, and USER.
    
           If none of _-c_ , _-t_ , _-u_ , _-r_ , or _-l_ , is specified, the first argument
           is used as the complete context.  Any additional arguments after
           _COMMAND_ are interpreted as arguments to the command.
    
           Only carefully-chosen contexts are likely to run successfully.
    
           Run a program in a different SELinux security context.  With
           neither CONTEXT nor COMMAND, print the current security context.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           CONTEXT
                  Complete security context
    
           **-c** , **--compute**
                  compute process transition context before modifying
    
           **-t** , **--type** =_TYPE_
                  type (for same role as parent)
    
           **-u** , **--user** =_USER_
                  user identity
    
           **-r** , **--role** =_ROLE_
                  role
    
           **-l** , **--range** =_RANGE_
                  levelrange
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
       **Exit status:**
           125    if the runcon command itself fails
    
           126    if COMMAND is found but cannot be invoked
    
           127    if COMMAND cannot be found
    
           -      the exit status of COMMAND otherwise
    


* * *
# ppdmerge

## NAME



           ppdmerge - merge ppd files (deprecated)
    


## SYNOPSIS



           **ppdmerge**[ **-o** _output-ppd-file_ ] _ppd-file ppd-file_ [ ...  _ppd-file_
           ]
    


## DESCRIPTION



           **ppdmerge** merges two or more PPD files into a single, multi-
           language PPD file.  **This program is deprecated and will be removed**
           **in a future release of CUPS.**
    


## OPTIONS



           **ppdmerge** supports the following options:
    
           **-o** _output-ppd-file_
                  Specifies the PPD file to create.  If not specified, the
                  merged PPD file is written to the standard output.  If the
                  output file already exists, it is silently overwritten.
    


## NOTES



           PPD files are deprecated and will no longer be supported in a
           future feature release of CUPS.  Printers that do not support IPP
           can be supported using applications such as ippeveprinter(1).
    
           **ppdmerge** does not check whether the merged PPD files are for the
           same device.  Merging of different device PPDs will yield
           unpredictable results.
    


* * *
# pmconfig

## NAME



           **pmconfig** - Performance Co-Pilot configuration parameters
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmconfig**[**-alLs?**]  [_name ..._]
    


## DESCRIPTION



           **pmconfig** displays the values for some or all configuration
           parameters of the local Performance Co-Pilot toolkit installation.
    


## OPTIONS



           The available command line options are:
    
           **-a** , **--all**
                Reports all configuration parameters in the default format.
    
           **-l** , **--list**
                Synonym for the **-a** option, reports the same (default) format.
    
           **-L** , **--library**
                This option changes the default reporting mode so that the
                capabilities of the PCP library are reported, rather than the
                PCP environment.
    
           **-s** , **--shell**
                An output format suitable for sourcing in shell scripts which
                ensures configuration information is quoted and preceded by
                an export statement.  When not reporting the library
                capabilities, this mode will produce a statement that does
                not override an existing setting in the environment for PCP
                configuration variables.
    
           **-?** , **--help**
                Display usage message and exit.
    
           In the default operating mode, **pmconfig** is often used in
           conjunction with the **$PCP_DIR** environment variable to setup
           scripts running under the Windows operating system, where the
           filesystem hierarchy differs greatly to the of Linux/UNIX-based
           operating systems.
    


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


* * *
# tload

## NAME



           tload - graphic representation of system load average
    


## SYNOPSIS



           **tload**[_option_ ...] [_tty_]
    


## DESCRIPTION



           **tload** prints a graph of the current system load average to the
           specified _tty_ (or the tty of the **tload** process if none is
           specified).
    


## OPTIONS



           **-s** , **--scale** _number_
                  The scale option allows a vertical scale to be specified
                  for the display (in characters between graph ticks); thus,
                  a smaller value represents a larger scale, and vice versa.
    
           **-d** , **--delay** _seconds_
                  The delay sets the delay between graph updates in _seconds_.
    
           **-h** , **--help**
                  Display this help text.
    
           **-V** , **--version**
                  Display version information and exit.
    


## FILES



           _/proc/loadavg_ load average information
    


## BUGS



           The **-d** _delay_ option sets the time argument for an alarm(2); if -d
           0 is specified, the alarm is set to 0, which will never send the
           **SIGALRM** and update the display.
    


* * *
# dh_dwz

## NAME



           dh_dwz - optimize DWARF debug information in ELF binaries via dwz
    


## SYNOPSIS



           **dh_dwz**[_debhelper options_] [**-X** _item_] [**--**_params_]
    


## DESCRIPTION



           **dh_dwz** is a debhelper program that will optimize the
           (uncompressed) size of the DWARF debug information in ELF
           binaries.  It does so by running **dwz**(1) on all the ELF binaries in
           the package.
    


## OPTIONS



           **--dwz-multifile** , **--no-dwz-multifile**
               Whether **dwz**(1) should generate a _multifile_ from the ELF
               binaries in the same package.  When enabled, if a package
               ships at least 2 ELF binaries, **dh_dwz** will instruct **dwz**(1) to
               generate a multifile for the package.
    
               By default, **dh_dwz** will attempt to create a multifile but will
               continue without if **dwz**(1) does not create one (but succeeds
               anyway).  This commonly happens when the debug files do not
               contain debug symbols (e.g. a missing -g to the compiler) or
               when the debug symbols are compressed (see Debian bug
               #931891).  If **--dwz-multifile** is passed, then **dh_dwz** will
               abort with an error if **dwz**(1) does not create a multifile.
    
               Note this options may not work if a package contains more ELF
               binaries than can fit on a single command line.  If this
               becomes a problem, please pass **--no-dwz-multifile** to work
               around the issue.
    
               The generated multifile will be compressed with **objcopy**
               **--compress-debug-sections**.
    
               Note for **udeb** packages: **dh_dwz** will never generate multifiles
               for **udeb** packages.  It will still use **dwz** to reduce the file
               size of debug files if it finds any.
    
           **-X** _item_ , **--exclude=**_item_
               Exclude files that contain _item_ anywhere in their filename
               from being stripped. You may use this option multiple times to
               build up a list of things to exclude.
    
           **--**_params_
               Pass _params_ to **dwz**(1) when it processes ELF binaries.  This is
               mostly useful for setting memory related parameters (e.g. -l
               and -L).
    


## NOTES



           If the **DEB_BUILD_OPTIONS** environment variable contains **nostrip** ,
           nothing will be stripped, in accordance with Debian policy
           (section 10.1 "Binaries").
    
           While this tool technically does not remove debug information from
           binaries, it is still skipped when the **DEB_BUILD_OPTIONS**
           environment variable contains **nostrip**.  This is because **nostrip** is
           often used to optimize build times (e.g. for "build and
           test"-cycles) rather than optimizing for size.
    


* * *
# cg_annotate

## NAME



           cg_annotate - post-processing tool for Cachegrind
    


## SYNOPSIS



    
           **cg_annotate**[_options_] _cachegrind-out-file_ [_source-files_...]
    


## DESCRIPTION



           **cg_annotate** takes one or more Cachegrind output files and prints
           data about the profiled program in an easy-to-read form.
    


## OPTIONS



           **-h --help**
               Show the help message.
    
           **--version**
               Show the version number.
    
           **--diff**
               Diff two Cachegrind output files.
    
           **--mod-filename <regex> [default: none]**
               Specifies an **s/old/new/** search-and-replace expression that is
               applied to all filenames. Useful when differencing, for
               removing minor differences in paths between two different
               versions of a program that are sitting in different
               directories. An **i** suffix makes the regex case-insensitive, and
               a **g** suffix makes it match multiple times.
    
           **--mod-funcname <regex> [default: none]**
               Like **--mod-filename** , but for filenames. Useful for removing
               minor differences in randomized names of auto-generated
               functions generated by some compilers.
    
           **--show=A,B,C [default: all, using order in the Cachegrind output**
           **file]**
               Specifies which events to show (and the column order). Default
               is to use all present in the Cachegrind output file (and use
               the order in the file). Best used in conjunction with **--sort**.
    
           **--sort=A,B,C [default: order in the Cachegrind output file]**
               Specifies the events upon which the sorting of the
               file:function and function:file entries will be based.
    
           **--threshold=X [default: 0.1%]**
               Sets the significance threshold for the file:function and
               function:files sections. A file or function is shown if it
               accounts for more than X% of the counts for the primary sort
               event. If annotating source files, this also affects which
               files are annotated.
    
           **--show-percs, --no-show-percs, --show-percs= <no|yes> [default:**
           **yes]**
               When enabled, a percentage is printed next to all event
               counts. This helps gauge the relative importance of each
               function and line.
    
           **--annotate, --no-annotate, --auto= <no|yes> [default: yes]**
               Enables or disables source file annotation.
    
           **--context=N [default: 8]**
               The number of lines of context to show before and after each
               annotated line. Use a large number (e.g. 100000) to show all
               source lines.
    


* * *
# rmdir

## NAME



           rmdir - remove empty directories
    


## SYNOPSIS



           **rmdir**[_OPTION_]... _DIRECTORY_...
    


## DESCRIPTION



           Remove the DIRECTORY(ies), if they are empty.
    
           **--ignore-fail-on-non-empty**
                  ignore each failure to remove a non-empty directory
    
           **-p** , **--parents**
                  remove DIRECTORY and its ancestors; e.g., 'rmdir **-p** a/b' is
                  similar to 'rmdir a/b a'
    
           **-v** , **--verbose**
                  output a diagnostic for every directory processed
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# pmdate

## NAME



           **pmdate** - display an offset date
    


## SYNOPSIS



           **pmdate**[_offset_ ...]  _format_
    


## DESCRIPTION



           **pmdate** displays the current date and/or time, with an optional
           offset.
    
           An _offset_ is specified with a leading sign (``+'' or ``-''),
           followed by an integer value, followed by one of the following
           ``scale'' specifiers;
    
           S      seconds
           M      minutes
           H      hours
           d      days
           m      months
           y      years
    
           The output _format_ follows the same rules as for date(1) and
           strftime(3).
    
           For example, the following will display the date a week ago as
           DDMMYYYY;
                   pmdate -7d %d%m%Y
    


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


* * *
# repotrack

## NAME



           repotrack - track a package and its dependencies and download them
    


## SYNOPSIS



           **repotrack**[options] package1 [package2...]
    


## DESCRIPTION



           **repotrack** is a program for keeping track of a particular package
           and its dependencies. It will download one or more packages and
           all dependencies.
    


## OPTIONS



           **-h, --help**
                  Display a help message, and then quit.
    
           **-c CONFIG, --config=CONFIG**
                  Config file to use (defaults to /etc/yum.conf).
    
           **-a ARCH, --arch=ARCH**
                  Act as if running the specified arch (default: current
                  arch).
    
           **-r REPOID, --repoid=REPOID**
                  Specify repo ids to query, can be specified multiple times
                  (default is all enabled).
    
           **--repofrompath= <repoid>,<path/url>**
                  Specify repoid & paths of additional repositories - unique
                  repoid and complete path required, can be specified
                  multiple times.  Example:
                  --repofrompath=myrepo,/path/to/repo
    
           **-t, --tempcache**
                  Use a temp dir for storing/accessing yum-cache.
    
           **-p DESTDIR, --download_path=DESTDIR**
                  Path to download packages to.
    
           **-u, --urls**
                  Instead of downloading RPMs, list the URLs that would be
                  downloaded.
    
           **-n, --newest**
                  Toggle downloading only the newest packages (defaults to
                  newest-only).
    
           **-q, --quiet**
                  Output as little information as possible.
    


* * *
# perror

## NAME



           perror - explain error codes
    


## SYNOPSIS



    
           **perror [**_options_**]**_errorcode_ **...**
    


## DESCRIPTION



           For most system errors, MariaDB displays, in addition to an
           internal text message, the system error code in one of the
           following styles:
    
               message ... (errno: #)
               message ... (Errcode: #)
    
           You can find out what the error code means by examining the
           documentation for your system or by using the **perror** utility.
    
           **perror** prints a description for a system error code or for a
           storage engine (table handler) error code.
    
           Invoke **perror** like this:
    
               shell> **perror [**_options_**]**_errorcode_ **...**
    
           Example:
    
               shell> **perror 13 64**
               OS error code  13:  Permission denied
               OS error code  64:  Machine is not on the network
    
           Note that the meaning of system error messages may be dependent on
           your operating system. A given error code may mean different
           things on different operating systems.
    
           **perror** supports the following options.
    
           •   **--help** , **--info** , **-I** , **-?**
    
               Display a help message and exit.
    
           •   **--silent** , **-s**
    
               Silent mode. Print only the error message.
    
           •   **--verbose** , **-v**
    
               Verbose mode. Print error code and message. This is the
               default behavior.
    
           •   **--version** , **-V**
    
               Display version information and exit.
    


* * *
# pmdads389log

## NAME



           **pmdads389log** - 389 Directory Server Log PMDA
    


## DESCRIPTION



           **pmdads389log** is a Performance Metrics Domain Agent (PMDA) which
           extracts statistics from 389 Directory Server access log using the
           **logconv.pl**(1) utility.
    


## INSTALLATION



           **pmdads389log** reads configuration file
    
               • $PCP_PMDAS_DIR _/ds389log/ds389log.conf_
    
           This file can contain overridden values (Perl code) for the
           settings listed at the start of _pmdads389log.pl_ , namely:
    
               • **logconv.pl** parameters
               • minimal query interval
               • 389 DS access log to use
               • 389 DS log directory to use (used if no file specified)
               • non-root user having read access to the access log file
    
           Once this is setup, you can access the names and values for the
           389 DS performance metrics by doing the following as root:
    
               **# cd $PCP_PMDAS_DIR/ds389log**
               **# ./Install**
    
           To uninstall, do the following as root:
    
               **# cd $PCP_PMDAS_DIR/ds389log**
               **# ./Remove**
    
           **pmdads389log** 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 _/ds389log/ds389log.conf_
                  configuration file for the **pmdads389log** agent
    
           $PCP_PMDAS_DIR _/ds389log/Install_
                  installation script for the **pmdads389log** agent
    
           $PCP_PMDAS_DIR _/ds389log/Remove_
                  undo installation script for the **pmdads389log** agent
    
           $PCP_LOG_DIR _/pmcd/ds389log.log_
                  default log file for error messages from **pmdads389log**
    
           _/var/log/dirsrv/slapd-.../access_
                  389 Directory Server access log parsed by **logconv.pl**
    


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


* * *
# return

## PROLOG



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


## NAME



           return — return from a function or dot script
    


## SYNOPSIS



           return **[**_n_**]**
    


## DESCRIPTION



           The _return_ utility shall cause the shell to stop executing the
           current function or _dot_ script. If the shell is not currently
           executing a function or _dot_ script, the results are unspecified.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           The value of the special parameter **'?'** shall be set to _n_ , an
           unsigned decimal integer, or to the exit status of the last
           command executed if _n_ is not specified. If _n_ is not an unsigned
           decimal integer, or is greater than 255, the results are
           unspecified. When _return_ is executed in a _trap_ action, the last
           command is considered to be the command that executed immediately
           preceding the _trap_ action.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           None.
    


## RATIONALE



           The behavior of _return_ when not in a function or _dot_ script
           differs between the System V shell and the KornShell. In the
           System V shell this is an error, whereas in the KornShell, the
           effect is the same as _exit_.
    
           The results of returning a number greater than 255 are undefined
           because of differing practices in the various historical
           implementations. Some shells AND out all but the low-order 8 bits;
           others allow larger values, but not of unlimited size.
    
           See the discussion of appropriate exit status values under
           exit(1p).
    


## FUTURE DIRECTIONS



           None.
    


* * *
# dh_installcron

## NAME



           dh_installcron - install cron scripts into etc/cron.*
    


## SYNOPSIS



           **dh_installcron**[**debhelper options**] [**--name=**_name_]
    


## DESCRIPTION



           **dh_installcron** is a debhelper program that is responsible for
           installing cron scripts.
    


## FILES



           debian/_package_.cron.daily
           debian/_package_.cron.weekly
           debian/_package_.cron.monthly
           debian/_package_.cron.yearly
           debian/_package_.cron.hourly
           debian/_package_.cron.d
               Installed into the appropriate _etc/cron.*/_ directory in the
               package build directory.
    


## OPTIONS



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


* * *
# perf-data

## NAME



           perf-data - Data file related processing
    


## SYNOPSIS



           _perf data_ [<common options>] <command> [<options>]",
    


## DESCRIPTION



           Data file related processing.
    


## COMMANDS



           convert
               Converts perf data file into another format. It’s possible to
               set data-convert debug variable to get debug messages from
               conversion, like: perf --debug data-convert data convert ...
    


## OPTIONS FOR CONVERT



           --to-ctf
               Triggers the CTF conversion, specify the path of CTF data
               directory.
    
           --to-json
               Triggers JSON conversion. Specify the JSON filename to output.
    
           --tod
               Convert time to wall clock time.
    
           -i
               Specify input perf data file path.
    
           -f, --force
               Don’t complain, do it.
    
           -v, --verbose
               Be more verbose (show counter open errors, etc).
    
           --all
               Convert all events, including non-sample events (comm, fork,
               ...), to output. Default is off, only convert samples.
    


* * *