tripathysagar/man_text huggingface dataset:
# telnet-probe

## NAME



           **telnet-probe** - lightweight telnet-like port probe
    


## SYNOPSIS



           **$PCP_BINADM_DIR/telnet-probe**[**-cv?**]  _host port_
    


## DESCRIPTION



           **telnet-probe** allows the pmdashping(1) daemons to establish
           connections to arbitrary local and remote service-providing
           daemons so that response time and service availability information
           can be obtained.
    
           The required _host_ and _port_ number arguments have the same meaning
           as their **telnet**(1) equivalents.
    
           The **-c** option causes **telnet-probe** to perform a connect(2) only.
           This skips the read(2) and write(2) exercise that would otherwise
           be done after connecting (see below).
    
           Once the telnet connection has been established, **telnet-probe**
           reads from _stdin_ until end-of-file, and writes all the input data
           to the telnet connection.  Next, **telnet-probe** will read from the
           telnet connection until end-of-file, discarding whatever data it
           receives.  Then **telnet-probe** exits.
    
           To operate successfully, the input passed via **telnet-probe** to the
           remote service must be sufficient to cause the remote service to
           close the connection when the last line of input has been
           processed, e.g. ending with ``quit'' when probing SMTP on port 25.
    
           By default **telnet-probe** will not produce any output, unless there
           is an error in which case a diagnostic message can be displayed
           (in verbose mode only) and the exit status will be non-zero
           indicating a failure.
    


## OPTIONS



           The available command line options are:
    
           **-c** Connect only, do not read or write.
    
           **-v** Enable verbose mode.
    
           **-?** Display usage message and exit.
    


## DIAGNOSTICS



           If **telnet-probe** succeeds, then 0 will be returned.  If the attempt
           to establish a connection fails or is terminated, then a non-zero
           exit status is returned.
    


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


* * *
# iptables-xml

## NAME



           iptables-xml — Convert iptables-save format to XML
    


## SYNOPSIS



           **iptables-xml**[**-c**] [**-v**]
    


## DESCRIPTION



           **iptables-xml** is used to convert the output of iptables-save into
           an easily manipulatable XML format to STDOUT.  Use I/O-redirection
           provided by your shell to write to a file.
    
           **-c** , **--combine**
                  combine consecutive rules with the same matches but
                  different targets. iptables does not currently support more
                  than one target per match, so this simulates that by
                  collecting the targets from consecutive iptables rules into
                  one action tag, but only when the rule matches are
                  identical. Terminating actions like RETURN, DROP, ACCEPT
                  and QUEUE are not combined with subsequent targets.
    
           **-v** , **--verbose**
                  Output xml comments containing the iptables line from which
                  the XML is derived
    
           iptables-xml does a mechanistic conversion to a very expressive
           xml format; the only semantic considerations are for -g and -j
           targets in order to discriminate between <call> <goto> and <nane-
           of-target> as it helps xml processing scripts if they can tell the
           difference between a target like SNAT and another chain.
    
           Some sample output is:
    
           <iptables-rules>
             <table name="mangle">
               <chain name="PREROUTING" policy="ACCEPT" packet-count="63436"
           byte-count="7137573">
                 <rule>
                  <conditions>
                   <match>
                     <p>tcp</p>
                   </match>
                   <tcp>
                     <sport>8443</sport>
                   </tcp>
                  </conditions>
                  <actions>
                   <call>
                     <check_ip/>
                   </call>
                   <ACCEPT/>
                  </actions>
                 </rule>
               </chain>
             </table> </iptables-rules>
    
           Conversion from XML to iptables-save format may be done using the
           iptables.xslt script and xsltproc, or a custom program using
           libxsltproc or similar; in this fashion:
    
           xsltproc iptables.xslt my-iptables.xml | iptables-restore
    


## BUGS



           None known as of iptables-1.3.7 release
    


* * *
# kbdinfo

## NAME



           kbdinfo - read information about keyboard state
    


## SYNOPSIS



           **kbdinfo**[_options_] _getmode_ [_text|graphics_]
           **kbdinfo**[_options_] _gkbmode_ [_raw|xlate|mediumraw|unicode_]
           **kbdinfo**[_options_] _gkbmeta_ [_metabit|escprefix_]
           **kbdinfo**[_options_] _gkbled_  [_scrolllock|numlock|capslock_]
    


## DESCRIPTION



           The utility allows you to read and check various parameters of the
           keyboard and virtual console.
    
           **getmode** Get or check virtual console mode.
    
           **gkbmode** Gets current keyboard mode.
    
                  **raw** Raw (scancode) mode. These are the raw codes
                         generated by the keyboard.
    
                  **mediumraw**
                         Medium raw (scancode) mode. This is extended medium
                         raw mode, with keys above 127 encoded as 0, high 7
                         bits, low 7 bits, with the 0 bearing the 'up' flag
                         if needed. 0 is reserved, so this shouldn't
                         interfere with anything else. The two bytes after 0
                         will always have the up flag set not to interfere
                         with older applications. This allows for 16384
                         different keycodes, which should be enough.
    
                  **xlate** Translate keycodes using keymap. These are the codes
                         generated via the current keysym mapping.
    
                  **unicode**
                         Unicode mode.
    
           **gkbmeta** Gets meta key handling mode.
    
                  **escprefix**
                         Specifies if pressing the meta (alt) key generates
                         an ESC (\033) prefix followed by the keysym.
    
                  **metabit**
                         The keysym marked with the high bit set.
    
           **gkbled** Get keyboard flags CapsLock, NumLock, ScrollLock (not
                    lights).
    
                  **scrolllock**
                         The scroll lock is down.
    
                  **numlock**
                         The num lock is down.
    
                  **capslock**
                         The caps lock is down.
    


## OPTIONS



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


* * *
# trace-cmd-hist

## NAME



           trace-cmd-hist - show histogram of events in trace.dat file
    


## SYNOPSIS



           **trace-cmd hist**[_OPTIONS_][_input-file_]
    


## DESCRIPTION



           The trace-cmd(1) hist displays a histogram form from the trace.dat
           file. Instead of showing the events as they were ordered, it
           creates a histogram that can be displayed per task or for all
           tasks where the most common events appear first. It uses the
           function tracer and call stacks that it finds to try to put
           together a call graph of the events.
    


## OPTIONS



           **-i** _input-file_
               By default, trace-cmd hist will read the file _trace.dat_. But
               the **-i** option open up the given _input-file_ instead. Note, the
               input file may also be specified as the last item on the
               command line.
    
           **-P**
               To compact all events and show the call graphs by ignoring
               tasks and different PIDs, add the **-P** to do so. Instead of
               showing the task name, it will group all chains together and
               show "<all pids>".
    


## RESOURCES



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


## COPYING



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


## NOTES



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


* * *
# flatpak-permissions

## NAME



           flatpak-permissions - List permissions
    


## SYNOPSIS



    
           **flatpak permissions**[OPTION...] [TABLE] [ID]
    


## DESCRIPTION



           Lists dynamic permissions which are stored in the Flatpak
           permission store.
    
           When called without arguments, lists all the entries in all
           permission store tables. When called with one argument, lists all
           the entries in the named table. When called with two arguments,
           lists the entry in the named table for the given object ID.
    
           The permission store is used by portals. Each portal generally has
           its own table in the permission store, and the format of the table
           entries is specific to each portal.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


* * *
# bno_plot

## NAME



           bno_plot - generate interactive 3D plot of IO blocks and sizes
    


## SYNOPSIS



           **bno_plot**[ -h | --help ]
                    [ -v | --verbose ]
                    [ -K | --keys-below ]
                    [ <file...> ]
    


## DESCRIPTION



           bno_plot is a visualization tool for the block layer IO tracing
           tool called blktrace(8).  As noted in its documentation, blktrace
           is a block layer IO tracing mechanism which provides detailed
           information about request queue operations up to user space.
    
           bno_plot utilizes gnuplot to generate a 3D plot of the block
           number output from btt.  If no _< files>_ are specified, it will
           utilize all files generated after btt was run with _-B blknos_
           (meaning: all files of the form _blknos*[rw].dat_).
    
           The _-K_ option forces bno_plot to put the keys below the graph.  If
           it is not specified, all keys for input files are put in the upper
           right corner of the graph. If the number of devices exceed 10,
           then bno_plot will automatically push the keys under the graph.
    
           To use this utility, the gnuplot package needs to be installed.
    
           To exit the plotter, enter 'quit' or ^D at the 'gnuplot> ' prompt.
    


* * *
# rdma_xclient

## NAME



           rdma_xclient - RDMA CM communication client test program
    


## SYNOPSIS



           _rdma_xclient_ [-s server_address] [-p server_port] [-c comm_type]
    


## DESCRIPTION



           Uses synchronous librdmam calls to establish an RDMA connection
           between two nodes.  This example is intended to provide a very
           simple coding example of how to use RDMA.
    


## OPTIONS



           -s server_address
                  Specifies the address of the system that the rdma_server is
                  running on.  By default, the client will attempt to connect
                  to the server using 127.0.0.1.
    
           -p server_port
                  Specifies the port number that the server listens on.  By
                  default the server listens on port 7471.
    
           -c communication type
                  Specifies the type of communication established with the
                  server program.  'r' results in using a reliable-connected
                  QP (the default).  'x' uses extended reliable-connected XRC
                  QPs.
    


## NOTES



           Basic usage is to start rdma_xserver, then connect to the server
           using the rdma_client program.
    
           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.
    


* * *
# needs-restarting

## NAME



           needs-restarting - report running processes that have been updated
    


## SYNOPSIS



           **needs-restarting**[options]
    


## DESCRIPTION



           **needs-restarting** is a program that reports a list of process ids
           that started running before they or some component that they use
           were updated.
    


## OPTIONS



           **-h, --help**
                  Display a help message, and then quit.
    
           **-u, --useronly**
                  Show processes for my userid only.
    
           **-r, --reboothint**
                  Only report whether a full reboot is required (exit code 1)
                  or not (exit code 0).
    
           **-s, --services**
                  List the affected systemd services only.
    


* * *
# mrtg2pcp

## NAME



           **mrtg2pcp** - import MRTG data and create a PCP archive
    


## SYNOPSIS



           **mrtg2pcp** _hostname devname timezone infile outfile_
    


## DESCRIPTION



           **mrtg2pcp** is intended to read an MRTG log file as created by
           **mrtg**(1) and translate this into a Performance Co-Pilot (PCP)
           archive with the basename _outfile_.  The _hostname_ , _devname_ , and
           _timezone_ arguments specify information about the system for which
           the statistics were gathered.
    
           The resultant PCP archive may be used with all PCP client tools to
           graph subsets of the data using pmchart(1), perform data reduction
           and reporting, filter with the PCP inference engine pmie(1), etc.
    
           A series of physical files will be created with the prefix
           _outfile_.  These are _outfile_**.0**(the performance data), _outfile_**.meta**
           (the metadata that describes the performance data) and
           _outfile_**.index**(a temporal index to improve efficiency of replay
           operations for the archive).  If any of these files exists
           already, then **mrtg2pcp** will **not** overwrite them and will exit with
           an error message of the form
    
           __pmLogNewFile: ``blah.0'' already exists, not over-written
    
           **mrtg2pcp** is a Perl script that uses the PCP::LogImport Perl
           wrapper around the PCP _libpcp_import_ library, and as such could be
           used as an example to develop new tools to import other types of
           performance data and create PCP archives.
    


## PCP ENVIRONMENT



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


* * *
# git-remote-fd

## NAME



           git-remote-fd - Reflect smart transport stream back to caller
    


## SYNOPSIS



           "fd::<infd>[,<outfd>][/<anything>]" (as URL)
    


## DESCRIPTION



           This helper uses specified file descriptors to connect to a remote
           Git server. This is not meant for end users but for programs and
           scripts calling git fetch, push, or archive.
    
           If only <infd> is given, it is assumed to be a bidirectional
           socket connected to a remote Git server (git-upload-pack,
           git-receive-pack, or git-upload-archive). If both <infd> and
           <outfd> are given, they are assumed to be pipes connected to a
           remote Git server (<infd> being the inbound pipe and <outfd> being
           the outbound pipe).
    
           It is assumed that any handshaking procedures have already been
           completed (such as sending service request for git://) before this
           helper is started.
    
           <anything> can be any string. It is ignored. It is meant for
           providing information to the user in the URL in case that URL is
           displayed in some context.
    


## ENVIRONMENT VARIABLES



           GIT_TRANSLOOP_DEBUG
               If set, prints debugging information about various
               reads/writes.
    


## EXAMPLES



           **git fetch fd::17 master**
               Fetch master, using file descriptor #17 to communicate with
               git-upload-pack.
    
           **git fetch fd::17/foo master**
               Same as above.
    
           **git push fd::7** ,8 **master**(**as URL**)
               Push master, using file descriptor #7 to read data from
               git-receive-pack and file descriptor #8 to write data to the
               same service.
    
           **git push fd::7** ,8/bar **master**
               Same as above.
    


## GIT



           Part of the git(1) suite
    


* * *
# setleds

## NAME



           setleds - set the keyboard leds
    


## SYNOPSIS



           **setleds**[_-v_] [_-L_] [_-D_] [_-F_] [_{+|-}num_] [_{+|-}caps_] [_{+|-}scroll_]
    


## DESCRIPTION



           **Setleds** reports and changes the led flag settings of a VT (namely
           NumLock, CapsLock and ScrollLock).  Without arguments, **setleds**
           prints the current settings.  With arguments, it sets or clears
           the indicated flags (and leaves the others unchanged). The
           settings before and after the change are reported if the -v flag
           is given.
    
           The led flag settings are specific for each VT (and the VT
           corresponding to stdin is used).
    
           By default (or with option -F), **setleds** will only change the VT
           flags (and their setting may be reflected by the keyboard leds).
    
           With option -D, **setleds** will change both the VT flags and their
           default settings (so that a subsequent reset will not undo the
           change).  This might be useful for people who always want to have
           numlock set.
    
           With option -L, **setleds** will not touch the VT flags, but only
           change the leds.  From this moment on, the leds will no longer
           reflect the VT flags (but display whatever is put into them). The
           command **setleds -L**(without further arguments) will restore the
           situation in which the leds reflect the VT flags.
    
           One might use **setleds** in /etc/rc to define the initial and default
           state of NumLock, e.g. by
                INITTY=/dev/tty[1-8]
                for tty in $INITTY; do
                     setleds -D +num < $tty
                done
    


## OPTIONS



           -num +num
                  Clear or set NumLock.  (At present, the NumLock setting
                  influences the interpretation of keypad keys.  Pressing the
                  NumLock key complements the NumLock setting.)
    
           -caps +caps
                  Clear or set CapsLock.  (At present, the CapsLock setting
                  complements the Shift key when applied to letters.
                  Pressing the CapsLock key complements the CapsLock
                  setting.)
    
           -scroll +scroll
                  Clear or set ScrollLock.  (At present, pressing the
                  ScrollLock key (or ^S/^Q) stops/starts console output.)
    


## BUGS



           In keyboard application mode the NumLock key does not influence
           the NumLock flag setting.
    


* * *
# diff3

## NAME



           diff3 - compare three files line by line
    


## SYNOPSIS



           **diff3**[_OPTION_]... _MYFILE OLDFILE YOURFILE_
    


## DESCRIPTION



           Compare three files line by line.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-A** , **--show-all**
                  output all changes, bracketing conflicts
    
           **-e** , **--ed**
                  output ed script incorporating changes from OLDFILE to
                  YOURFILE into MYFILE
    
           **-E** , **--show-overlap**
                  like **-e** , but bracket conflicts
    
           **-3** , **--easy-only**
                  like **-e** , but incorporate only nonoverlapping changes
    
           **-x** , **--overlap-only**
                  like **-e** , but incorporate only overlapping changes
    
           **-X** like **-x** , but bracket conflicts
    
           **-i** append 'w' and 'q' commands to ed scripts
    
           **-m** , **--merge**
                  output actual merged file, according to **-A** if no other
                  options are given
    
           **-a** , **--text**
                  treat all files as text
    
           **--strip-trailing-cr**
                  strip trailing carriage return on input
    
           **-T** , **--initial-tab**
                  make tabs line up by prepending a tab
    
           **--diff-program** =_PROGRAM_
                  use PROGRAM to compare files
    
           **-L** , **--label** =_LABEL_
                  use LABEL instead of file name (can be repeated up to three
                  times)
    
           **--help** display this help and exit
    
           **-v** , **--version**
                  output version information and exit
    
           The default output format is a somewhat human-readable
           representation of the changes.
    
           The **-e** , **-E** , **-x** , **-X**(and corresponding long) options cause an ed
           script to be output instead of the default.
    
           Finally, the **-m**(**--merge**) option causes diff3 to do the merge
           internally and output the actual merged file.  For unusual input,
           this is more robust than using ed.
    
           If a FILE is '-', read standard input.  Exit status is 0 if
           successful, 1 if conflicts, 2 if trouble.
    


* * *
# yum-fs-snapshot

## NAME



           **yum-fs-snapshot**
    


## SYNOPSIS



           The **yum-fs-snapshot** package
    


## DESCRIPTION



           yum-fs-snapshot(1) is a Yum plugin for taking snapshots of your
           filesystems before running a yum transaction.  By default it will
           take a snapshot of any filesystem that can be snapshotted, which
           currently is limited to BTRFS filesystems.  However, all
           filesystems built on LVM logical volumes may be snapshotted at the
           block level using LVM snapshots.  LVM snapshot support is provided
           for the purpose of system rollback.  As such LVM snapshots will
           only be created if the kernel supports the "snapshot-merge" DM
           target.
    


## FILES



           **yum-fs-snapshot** uses a configuration file for its specific
           actions: _/etc/yum/pluginconf.d/fs-snapshot.conf_
    


* * *
# ascii-xfr

## NAME



           ascii-xfr - upload/download files using the ASCII protocol
    


## SYNOPSIS



           **ascii-xfr -s|-r**[**-ednv**] [**-l** _linedelay_] [**-c** _characterdelay_]
           _filename_
    


## DESCRIPTION



           **Ascii-xfr** Transfers files in ASCII mode. This means no flow
           control, no checksumming and no file-name negotiation. It should
           _only_ be used if the remote system doesn't understand anything
           else.
    
           The ASCII protocol transfers files line-by-line. The EOL (End-Of-
           Line) character is transmitted as CRLF. When receiving, the CR
           character is stripped from the incoming file.  The Control-Z
           (ASCII 26) character signals End-Of-File, if option -e is
           specified (unless you change it to Control-D (ASCII 4) with -d).
    
           **Ascii-xfr** reads from _stdin_ when receiving, and sends data on
           _stdout_ when sending. Some form of input or output redirection to
           the modem device is thus needed when downloading or uploading,
           respectively.
    


## OPTIONS



           **-s** Send a file.
    
           **-r** Receive a file. One of **-s** or **-r** _must_ be present.
    
           **-e** Send the End-Of-File character (Control-Z, ASCII 26 by
                  default) when uploading has finished.
    
           **-d** Use the Control-D (ASCII 4) as End-Of-File character.
    
           **-n** Do not translate CR to CRLF and vice versa.
    
           **-v** Verbose: show transfer statistics on the stderr output.
    
           **-l** _milliseconds_
                  When transmitting, pause for this delay after each line.
    
           **-c** _milliseconds_
                  When transmitting, pause for this delay after each
                  character.
    
           _file_   Name of the file to send or receive. When receiving, any
                  existing file by this name will be truncated.
    


## USAGE WITH MINICOM



           If you want to call this program from minicom(1), start minicom
           and go to the **O** ptions menu. Select _File transfer protocols_.  Add
           the following lines, for example as protocols **I** and **J**.
    
           I  Ascii    /usr/bin/ascii-xfr -sv   Y   U   N   Y
           J  Ascii    /usr/bin/ascii-xfr -rv   Y   D   N   Y
    


* * *
# cg_diff

## NAME



           cg_diff - (deprecated) diffs two Cachegrind output files
    


## SYNOPSIS



    
           **cg_diff**[_options_] _cachegrind-out-file1 cachegrind-out-file2_
    


## DESCRIPTION



           **cg_diff** diffs two Cachegrind output files into a single Cachegrind
           output file. It is deprecated because **cg_annotate** can now do much
           the same thing, but better.
    


## OPTIONS



           **-h --help**
               Show the help message.
    
           **--version**
               Show the version number.
    
           **--mod-filename= <expr> [default: none]**
               Specifies an **s/old/new/** search-and-replace expression that is
               applied to all filenames.
    
           **--mod-funcname= <expr> [default: none]**
               Like **--mod-filename** , but for filenames.
    


* * *
# deallocvt

## NAME



           deallocvt - deallocate unused virtual consoles
    


## SYNOPSIS



           **deallocvt**[_option_...]  [_N_ ...]
    


## DESCRIPTION



           The command **deallocvt** deallocates kernel memory and data
           structures for all unused virtual consoles.  If one or more
           arguments _N_ ...  are given, only the corresponding consoles
           _/dev/ttyN_ are deallocated.
    
           A virtual console is unused if it is not the foreground console,
           and no process has it open for reading or writing, and no text has
           been selected on its screen.
    


## OPTIONS



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


* * *
# psfgettable

## NAME



           psfgettable - extract the embedded Unicode character table from a
           console font
    


## SYNOPSIS



           **psfgettable** _fontfile_ [_outfile_]
    


## DESCRIPTION



           **psfgettable** extracts the embedded Unicode character table from a
           .psf format console font into a human readable ASCII file of the
           format used by psfaddtable(1).  If the font file name is a single
           dash (-), the font is read from standard input.
    


* * *
# ibv_devices

## NAME



           ibv_devices - list RDMA devices
    


## SYNOPSIS



           **ibv_devices**
    


## DESCRIPTION



           List RDMA devices available for use from userspace.
    


* * *
# dpkg-realpath

## NAME



           dpkg-realpath - print the resolved pathname with DPKG_ROOT support
    


## SYNOPSIS



           **dpkg-realpath**[_option_...] _pathname_
    


## DESCRIPTION



           **dpkg-realpath** is a tool (since dpkg 1.20.1) to resolve a pathname,
           that takes the dpkg(1) root directory into account, either
           implicitly from the **DPKG_ROOT** environment variable or from the
           command-line **--root** or **--instdir** options, and returns an absolute
           _pathname_ relative to the root directory.  The root directory must
           not be prefixed to the _pathname_ to be resolved.
    
           This is intended to be used by other **dpkg** helpers, or by
           maintainer scripts instead of using realpath(1) or readlink(1) to
           canonicalize pathnames, as these latter commands do not support
           canonicalization relative to a different root than _/_.
    
           This program was introduced in dpkg 1.20.1.
    


## OPTIONS



           **-z** , **--zero**
               Use a NUL byte to end output lines instead of a new line
               character (since dpkg 1.20.6).
    
           **--instdir** _directory_
           **--root** _directory_
               Set the root directory to _directory_ , which is the base
               directory that pathnames get canonicalized against.  Defaults
               to «**/** » if **DPKG_ROOT** has not been set.
    
           **-?** , **--help**
               Show the usage message and exit.
    
           **--version**
               Show the version and exit.
    


## ENVIRONMENT



           **DPKG_ROOT**
               If set and the **--instdir** or **--root** options have not been
               specified, it will be used as the filesystem root directory.
    
           **DPKG_COLORS**
               Sets the color mode.  The currently accepted values are: **auto**
               (default), **always** and **never**.
    
           **DPKG_NLS**
               If set, it will be used to decide whether to activate Native
               Language Support, also known as internationalization (or i18n)
               support (since dpkg 1.22.7).  The accepted values are: **0** and **1**
               (default).
    


* * *
# resolve_stack_dump

## NAME



           resolve_stack_dump - resolve numeric stack trace dump to symbols
    


## SYNOPSIS



    
           **resolve_stack_dump [**_options_**]**_symbols_file_ **[**_numeric_dump_file_**]**
    


## DESCRIPTION



           **resolve_stack_dump** resolves a numeric stack dump to symbols.
    
           Invoke **resolve_stack_dump** like this:
    
               shell> **resolve_stack_dump [**_options_**]**_symbols_file_ **[**_numeric_dump_file_**]**
    
           The symbols file should include the output from the **nm**
           **--numeric-sort mariadbd** command. The numeric dump file should
           contain a numeric stack track from **mariadbd**. If no numeric dump
           file is named on the command line, the stack trace is read from
           the standard input.
    
           **resolve_stack_dump** supports the following options.
    
           •   **--help** , **-h**
    
               Display a help message and exit.
    
           •   **--numeric-dump-file=**_file_name_ , **-n** _file_name_
    
               Read the stack trace from the given file.
    
           •   **--symbols-file=**_file_name_ , **-s** _file_name_
    
               Use the given symbols file.
    
           •   **--version** , **-V**
    
               Display version information and exit.
    


* * *
# fusermount3

## NAME



           **fusermount3** - mount and unmount FUSE filesystems
    


## SYNOPSIS



           **fusermount3**[_OPTIONS_] _MOUNTPOINT_
    


## DESCRIPTION



           Filesystem in Userspace (FUSE) is a simple interface for userspace
           programs to export a virtual filesystem to the Linux kernel. It
           also aims to provide a secure method for non privileged users to
           create and mount their own filesystem implementations.
    
           **fusermount3** is a program to mount and unmount FUSE filesystems. It
           should be called directly only for unmounting FUSE file systems.
           To allow mounting and unmounting by unprivileged users,
           **fusermount3** needs to be installed set-uid root.
    


## OPTIONS



           -h  print help.
    
           -V  print version.
    
           -o _OPTION_[,_OPTION_...]
               mount options.
    
           -u  unmount.
    
           -q  quiet.
    
           -z  lazy unmount.
    


## HOMEPAGE



           More information about fusermount3 and the FUSE project can be
           found at <_http://fuse.sourceforge.net/ _>.
    


* * *
# stg-undo

## NAME



           stg-undo - Undo the last command
    


## SYNOPSIS



           _stg undo_ [OPTIONS]
    


## DESCRIPTION



           Reset the patch stack to the state before the last operation.
           Consecutive undos will go back to yet older stack states.
    


## OPTIONS



           -n <n>, --number=<n>
               Undo the last <n> commands
    
           --hard
               Discard changes in the index and worktree
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# dh_installifupdown

## NAME



           dh_installifupdown - install if-up and if-down hooks
    


## SYNOPSIS



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


## DESCRIPTION



           **dh_installifupdown** is a debhelper program that is responsible for
           installing _if-up_ , _if-down_ , _if-pre-up_ , and _if-post-down_ hook
           scripts into package build directories.
    


## FILES



           debian/_package_.if-up
           debian/_package_.if-down
           debian/_package_.if-pre-up
           debian/_package_.if-post-down
               These files are installed into etc/network/if-*.d/_package_ in
               the package build directory.
    


## OPTIONS



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


* * *
# pmdalio

## NAME



           **pmdalio** - Linux LIO subsystem PMDA
    


## DESCRIPTION



           **pmdalio** is a Performance Metrics Domain Agent (PMDA) which exports
           metric values about the Linux I/O target subsystem, which provides
           for protocols like iSCSI, FCP, FCoE.  These allow storage
           available on one host to be exported and consumed by other hosts
           using industry standard protocols.
    
           This PMDA exports summary metrics which are performance value
           aggregations and configuration per LIO target instance.
           Additionally, it provides per LUN performance metrics including
           IOPS, and READ and WRITE throughput.
    
           The LIO configuration is maintained within the kernel's **configfs**
           virtual filesystem.  The _python-rtslib_ module provides an
           interface to **configfs** , allowing tools like **pmdalio** to interact
           with the settings and metadata held in **configfs**.
    


## INSTALLATION



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


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


* * *
# pslog

## NAME



           pslog - report current logs path of a process
    


## SYNOPSIS



           **pslog** _pid_ ...
           **pslog -V**
    


## DESCRIPTION



           The **pslog** command reports the current working logs of a process.
    


## OPTIONS



           **-V** Display version information.
    


* * *
# stg-redo

## NAME



           stg-redo - Undo the last undo operation
    


## SYNOPSIS



           _stg redo_ [OPTIONS]
    


## DESCRIPTION



           If the last command was an undo, the patch stack state will be
           reset to its state before the undo. Consecutive redos will undo
           the effects of consecutive invocations of stg-undo(1).
    
           It is an error to redo if the last stack-modifying command was not
           an undo.
    


## OPTIONS



           -n <n>, --number=<n>
               Undo the last <n> undos
    
           --hard
               Discard changes in the index and worktree
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# trace-cmd-list

## NAME



           trace-cmd-list - list available plugins, events or options for
           Ftrace.
    


## SYNOPSIS



           **trace-cmd list**[_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) list displays the available plugins, events or
           Ftrace options that are configured on the current machine. If no
           option is given, then it lists all plugins, event systems, events
           and Ftrace options to standard output.
    


## OPTIONS



           **-e**[_regex_]
               This option will list the available events that are enabled on
               the local system.
    
                   It takes an optional argument that uses 'regcomp(3)' expressions to seach.
    
                   trace-cmd list -e '^sys.*'
    
           **-F**
               Used with **-e** _regex_ to show the fields of the event.
    
           **--full**
               Used with **-F** which will show the "print fmt" of the event
               along with the fields.
    
           **-l**
               Used with **-e** _regex_ to show those events filters.
    
           **-R**
               Used with **-e** _regex_ to show those events triggers.
    
           **-s**
               This option will list the available event systems.
    
           **-t**
               This option will list the available tracers that are enabled
               on the local system.
    
           **-p**
               Same as **-t** and only for legacy purposes.
    
           **-o**
               This option will list the available Ftrace options that are
               configured on the local system.
    
           **-f**[_regex_]
               This option will list the available filter functions. These
               are the list of functions on the system that you can trace, or
               filter on. It takes an optional argument that uses regcomp(3)
               expressions to seach.
    
                   trace-cmd list -f '^sched.*'
    
           **-P**
               List the plugin files that get loaded on trace-cmd report.
    
           **-O**
               List plugin options that can be used by trace-cmd report **-O**
               option.
    
           **-B**
               List defined buffer instances (sub buffers).
    
           **-C**
               List defined clocks that can be used with trace-cmd record -C.
               The one in brackets ([]) is the active clock.
    
           **-c**
               List the available trace file compression algorithms.
    


## RESOURCES



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


## COPYING



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


## NOTES



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


* * *
# perf-buildid-list

## NAME



           perf-buildid-list - List the buildids in a perf.data file
    


## SYNOPSIS



           _perf buildid-list <options>_
    


## DESCRIPTION



           This command displays the buildids found in a perf.data file, so
           that other tools can be used to fetch packages with matching
           symbol tables for use by perf report.
    
           It can also be used to show the build id of the running kernel or
           in an ELF file using -i/--input.
    


## OPTIONS



           -H, --with-hits
               Show only DSOs with hits.
    
           -i, --input=
               Input file name. (default: perf.data unless stdin is a fifo)
    
           -f, --force
               Don’t do ownership validation.
    
           -k, --kernel
               Show running kernel build id.
    
           -m, --kernel-maps
               Show buildid, start/end text address, and path of running
               kernel and its modules.
    
           -v, --verbose
               Be more verbose.
    


* * *
# cancel

## NAME



           cancel - cancel jobs
    


## SYNOPSIS



           **cancel**[ **-h** _hostname[:port]_ ] [ **-E**] [ **-U** _username_ ] [ **-a**] [ **-u**
           _username_ ] [ **-x**] [ _id_ ] [ _destination_ ] [ _destination-id_ ]
    


## DESCRIPTION



           The **cancel** command cancels print jobs.  If no _destination_ or _id_ is
           specified, the currently printing job on the default destination
           is canceled.
    


## OPTIONS



           The following options are recognized by **cancel** :
    
           **-a** Cancel all jobs on the named destination, or all jobs on all
                destinations if none is provided.
    
           **-E** Forces encryption when connecting to the server.
    
           **-h** _hostname_[_:port_]
                Specifies an alternate server.  Note: This option must occur
                before all others.
    
           **-U** _username_
                Specifies the username to use when connecting to the server.
    
           **-u** _username_
                Cancels jobs owned by _username_.
    
           **-x** Deletes job data files in addition to canceling.
    


## CONFORMING TO



           Unlike the System V printing system, CUPS allows printer names to
           contain any printable character except SPACE, TAB, "/", or "#".
           Also, printer and class names are _not_ case-sensitive.
    


## EXAMPLES



           Cancel the current print job:
    
               cancel
    
           Cancel job "myprinter-42":
    
               cancel myprinter-42
    
           Cancel all jobs:
    
               cancel -a
    


## NOTES



           The **-a** and **-u** _username_ options require administrative access.
           These restrictions are part of the operation policies defined in
           the cupsd.conf(5) file for the "Cancel-Jobs" and "Cancel-My-Jobs"
           operations, respectively.
    


* * *
# pmdakvm

## NAME



           **pmdakvm** - Linux virtualization performance metrics domain agent
           (PMDA)
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/kvm/pmdakvm**[**-D** _debug_]
    


## DESCRIPTION



           **pmdakvm** is a Performance Metrics Domain Agent (PMDA) which exports
           metric values from the Linux KVM (Kernel Virtual Machine)
           virtualization subsystem.
    
           Per-processor KVM trace metrics from the kernel events enumerated
           below _/sys/kernel/debug/tracing/events/kvm_ can be configured
           statically using the **pmdakvm** configuration file,
           _/etc/pcp/kvm/kvm.conf_.
    


## INSTALLATION



           Optionally configure trace points in the configuration file, then
           install the KVM PMDA by using the Install script as root:
    
               **# cd $PCP_PMDAS_DIR/kvm**
               **# ./Install**
    
           To uninstall, do the following as root:
    
               **# cd $PCP_PMDAS_DIR/kvm**
               **# ./Remove**
    
           **pmdakvm** 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.
    


## CAVEATS



           When **pmdakvm** is running, it holds references to kernel resources
           within the KVM device driver.  It is thus not possible to unload
           or reload the device driver module while the PMDA is running.  The
           ideal procedure to follow in order to reload the kernel module is
           the reverse of that described in the ``INSTALLATION'' section
           above - i.e. first run **./Remove** , then reload the kernel module,
           then run **./Install**.
    


## FILES



           **$PCP_SYSCONF_DIR/kvm/kvm.conf**
               configuration file for the **pmdakvm** agent
    
           **$PCP_PMDAS_DIR/kvm/Install**
               installation script for the **pmdakvm** agent
    
           **$PCP_PMDAS_DIR/kvm/Remove**
               undo installation script for the **pmdakvm** agent
    
           **$PCP_LOG_DIR/pmcd/kvm.log**
               default log file for error messages from **pmdakvm**
    


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


* * *