tripathysagar/man_text huggingface dataset:
# idl2wrs

## NAME



           idl2wrs - CORBA IDL to Wireshark Plugin Generator
    


## SYNOPSIS



           **idl2wrs** <filename>
    


## DESCRIPTION



           **idl2wrs** is a program that takes a user specified **CORBA IDL** file
           and generates **"C"** source code for a **Wireshark** "plugin".
    
           This resulting file can be compiled as a **Wireshark** plugin, and
           used to monitor **GIOP/IIOP** traffic that is using this IDL.
    
           **idl2wrs** is actually a shell script wrapper for two **Python**
           programs. These programs are:
    
           •   **wireshark_be.py** Contains the main IDL Visitor Class
    
           •   **wireshark_gen.py** Contains the Source Code Generator Class
    
           **idl2wrs** supports heuristic dissection of GIOP/IIOP traffic, and
           some experimental code for explicit dissection, based on Object
           Key <→ Repository Id mapping. However, code for heuristic based
           plugins is generated by default, and users should consider this
           the preferred method unless you have some namespace collisions.
    


## OPTIONS



           Currently there are no options. **idl2wrs** can be invoked as follows.
    
            1. To write the C code to stdout.
    
                   idl2wrs  <your_file.idl>
    
                   eg: idl2wrs echo.idl
    
            2. To write to a file, just redirect the output.
    
                   idl2wrs echo.idl > packet-test.c
    


## ENVIRONMENT



           **idl2wrs** will look for **wireshark_be.py** and **wireshark_gen.py** in
           **$PYTHONPATH/site-packages/** and if not found, will try the current
           directory **./**
    
           The **-p** option passed to omniidl (inside **idl2wrs**) indicates where
           **wireshark_be.py** and **wireshark_gen.py** will be searched. This may
           need tweaking if you place these files somewhere else.
    
           If it complains about being unable to find some modules (eg
           tempfile.py), you may want to check if PYTHONPATH is set
           correctly.
    
           eg:  PYTHONPATH=/usr/lib/python3/
    


## NOTES



           **idl2wrs**(including **wireshark_be.py** and **wireshark_gen.py**) are part
           of the **Wireshark** distribution. The latest version of **Wireshark** can
           be found at https://www.wireshark.org.
    
           **idl2wrs** uses **omniidl** , an IDL parser, and can be found at
           http://omniorb.sourceforge.net/
    


## TODO



           Some of the more important things to do are:
    
           •   Improve Explicit dissection code.
    
           •   Improve command line options.
    
           •   Improve decode algorithm when we have operation name
               collision.
    


* * *
# stdbuf

## NAME



           stdbuf - Run COMMAND, with modified buffering operations for its
           standard streams.
    


## SYNOPSIS



           **stdbuf** _OPTION_... _COMMAND_
    


## DESCRIPTION



           Run COMMAND, with modified buffering operations for its standard
           streams.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-i** , **--input** =_MODE_
                  adjust standard input stream buffering
    
           **-o** , **--output** =_MODE_
                  adjust standard output stream buffering
    
           **-e** , **--error** =_MODE_
                  adjust standard error stream buffering
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           If MODE is 'L' the corresponding stream will be line buffered.
           This option is invalid with standard input.
    
           If MODE is '0' the corresponding stream will be unbuffered.
    
           Otherwise MODE is a number which may be followed by one of the
           following: KB 1000, K 1024, MB 1000*1000, M 1024*1024, and so on
           for G,T,P,E,Z,Y,R,Q.  Binary prefixes can be used, too: KiB=K,
           MiB=M, and so on.  In this case the corresponding stream will be
           fully buffered with the buffer size set to MODE bytes.
    
           NOTE: If COMMAND adjusts the buffering of its standard streams
           ('tee' does for example) then that will override corresponding
           changes by 'stdbuf'.  Also some filters (like 'dd' and 'cat' etc.)
           don't use streams for I/O, and are thus unaffected by 'stdbuf'
           settings.
    
       **Exit status:**
           125    if the stdbuf command itself fails
    
           126    if COMMAND is found but cannot be invoked
    
           127    if COMMAND cannot be found
    
           -      the exit status of COMMAND otherwise
    


## EXAMPLES



           **tail -f access.log | stdbuf -oL cut -d ' ' -f1 | uniq**
           This will immediately display unique entries from access.log
    


## BUGS



           On GLIBC platforms, specifying a buffer size, i.e., using fully
           buffered mode will result in undefined operation.
    


* * *
# dh_md5sums

## NAME



           dh_md5sums - generate DEBIAN/md5sums file
    


## SYNOPSIS



           **dh_md5sums**[_debhelper options_] [**-x**] [**-X** _item_] [**--include-conffiles**]
    


## DESCRIPTION



           **dh_md5sums** is a debhelper program that is responsible for
           generating a _DEBIAN/md5sums_ file, which lists the md5sums of each
           file in the package.  These files are used by **dpkg --verify** or the
           **debsums**(1) program.
    
           All files in _DEBIAN/_ are omitted from the _md5sums_ file, as are all
           conffiles (unless you use the **--include-conffiles** switch).
    
           The md5sums file is installed with proper permissions and
           ownerships.
    


## OPTIONS



           **-x** , **--include-conffiles**
               Include conffiles in the md5sums list. Note that this
               information is redundant since it is included in
               _/var/lib/dpkg/status_ in Debian packages.
    
           **-X** _item_ , **--exclude=**_item_
               Exclude files that contain _item_ anywhere in their filename
               from being listed in the md5sums file.
    


* * *
# xminicom

## NAME



           xminicom - friendly serial communication program
    


## SYNOPSIS



           **xminicom** _minicom-options_
    


## DESCRIPTION



           **Xminicom** is a script wrapper around _minicom._  It tries to find a
           color capable xterm or rxvt on your system, and then runs minicom
           with the -c (color) flag in a terminal session.
    


## OPTIONS



           See _minicom_ (1).
    


* * *
# tee

## NAME



           tee - read from standard input and write to standard output and
           files
    


## SYNOPSIS



           **tee**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Copy standard input to each FILE, and also to standard output.
    
           **-a** , **--append**
                  append to the given FILEs, do not overwrite
    
           **-i** , **--ignore-interrupts**
                  ignore interrupt signals
    
           **-p** operate in a more appropriate MODE with pipes
    
           **--output-error**[=_MODE_]
                  set behavior on write error.  See MODE below
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
       **MODE determines behavior with write errors on the outputs:**
           warn   diagnose errors writing to any output
    
           warn-nopipe
                  diagnose errors writing to any output not a pipe
    
           exit   exit on error writing to any output
    
           exit-nopipe
                  exit on error writing to any output not a pipe
    
           The default MODE for the **-p** option is 'warn-nopipe'.  With
           "nopipe" MODEs, exit immediately if all outputs become broken
           pipes.  The default operation when **--output-error** is not
           specified, is to exit immediately on error writing to a pipe, and
           diagnose errors writing to non pipe outputs.
    


* * *
# dh_testroot

## NAME



           dh_testroot - ensure that a package is built with necessary level
           of root permissions
    


## SYNOPSIS



           **dh_testroot**[_debhelper options_]
    


## DESCRIPTION



           **dh_testroot** is used to determine if the target is being run with
           suffient access to root(-like) features.
    
           The definition of sufficient access depends on whether the builder
           (the tool invoking the _debian/rules_ target) supports the _Rules-_
           _Requires-Root_ (R³) field.  If the builder supports R³, then it
           will set the environment variable _DEB_RULES_REQUIRES_ROOT_ and
           **dh_testroot** will validate that the builder followed the minimum
           requirements for the given value of _DEB_RULES_REQUIRES_ROOT_.
    
           If the builder does not support _Rules-Requires-Root_ , then it will
           not set the _DEB_RULES_REQUIRES_ROOT_ environment variable.  This
           will in turn make **dh_testroot**(and the rest of debhelper) fall
           back to assuming that (fake)root is implied.
    
           The following is a summary of how **dh_testroot** behaves based on the
           _DEB_RULES_REQUIRES_ROOT_ environment variable (leading and trailing
           whitespace in the variable is ignored).
    
           -   If unset, or set to "binary-targets", then **dh_testroot** asserts
               that it is run as root or under **fakeroot**(1).
    
           -   If set to "no", then **dh_testroot** returns successfully (without
               performing any additional checks).
    
           -   If set to any other value than the above, then **dh_testroot**
               asserts that it is either run as root (or under **fakeroot**(1))
               or the builder has provided the **DEB_GAIN_ROOT_CMD** environment
               variable (e.g. via dpkg-buildpackage -r).
    
           Please note that **dh_testroot** does _not_ read the _Rules-Requires-Root_
           field.  Which implies that **dh_testroot** may produce incorrect
           result if the builder lies in _DEB_RULES_REQUIRES_ROOT_.  On the
           flip side, it also enables things like testing for what will
           happen when _DEB_RULES_REQUIRES_ROOT_ is set to a given value.
    


* * *
# gcore

## NAME



           gcore - Generate a core file of a running program
    


## SYNOPSIS



           gcore [-a] [-o _prefix_] [-d _directory_] _pid1_ [_pid2_..._pidN_]
    


## DESCRIPTION



           Generate core dumps of one or more running programs with process
           IDs _pid1_ , _pid2_ , etc.  A core file produced by **gcore** is equivalent
           to one produced by the kernel when the process crashes (and when
           "ulimit -c" was used to set up an appropriate core dump limit).
           However, unlike after a crash, after **gcore** finishes its job the
           program remains running without any change.
    


## OPTIONS



           **-a** Dump all memory mappings.  The actual effect of this option
               depends on the Operating System.  On GNU/Linux, it will
               disable "use-coredump-filter" and enable
               "dump-excluded-mappings".
    
           **-o** _prefix_
               The optional argument _prefix_ specifies the prefix to be used
               when composing the file names of the core dumps.  The file
               name is composed as _prefix.pid_ , where _pid_ is the process ID of
               the running program being analyzed by **gcore**.  If not
               specified, _prefix_ defaults to _gcore_.
    
           **-d** _directory_
               Use _directory_ as the data directory when invoking GDB for
               running the gcore command. This argument is optional.
    


## ENVIRONMENT



    


* * *
# lxc-unfreeze

## NAME



           lxc-unfreeze - thaw all the container's processes
    


## SYNOPSIS



           **lxc-unfreeze**{-n _name_}
    


## DESCRIPTION



           **lxc-unfreeze** will thaw all the processes previously frozen by the
           **lxc-freeze** command.
    


## COMMON OPTIONS



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


## DIAGNOSTIC



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


* * *
# lsinitrd

## NAME



           lsinitrd - tool to show the contents of an initramfs image
    


## SYNOPSIS



           **lsinitrd**[_OPTION..._] [<image> [<filename> [<filename> [...] ]]]
    
           **lsinitrd**[_OPTION..._] -k <kernel version>
    


## DESCRIPTION



           lsinitrd shows the contents of an initramfs image. if <image> is
           omitted, then lsinitrd determines the default location based on
           the local configuration or Linux distribution policy.
    


## OPTIONS



           **-h, --help**
               print a help message and exit.
    
           **-s, --size**
               sort the contents of the initramfs by size.
    
           **-f, --file** _< filename>_
               print the contents of <filename>.
    
           **-k, --kver** _< kernel version>_
               inspect the initramfs of <kernel version>.
    
           **-m, --mod**
               list dracut modules included of the initramfs image.
    
           **--unpack**
               unpack the initramfs to the current directory, instead of
               displaying the contents. If optional filenames are given, will
               only unpack specified files, else the whole image will be
               unpacked. Won’t unpack anything from early cpio part.
    
           **--unpackearly**
               unpack the early microcode initramfs to the current directory,
               instead of displaying the contents. Same as --unpack, but only
               unpack files from early cpio part.
    
           **-v, --verbose**
               unpack verbosely
    


## AVAILABILITY



           The lsinitrd command is part of the dracut package and is
           available from **https://github.com/dracut-ng/dracut-ng **
    


* * *
# dircolors

## NAME



           dircolors - color setup for ls
    


## SYNOPSIS



           **dircolors**[_OPTION_]... [_FILE_]
    


## DESCRIPTION



           Output commands to set the LS_COLORS environment variable.
    
       **Determine format of output:**
           **-b** , **--sh** , **--bourne-shell**
                  output Bourne shell code to set LS_COLORS
    
           **-c** , **--csh** , **--c-shell**
                  output C shell code to set LS_COLORS
    
           **-p** , **--print-database**
                  output defaults
    
           **--print-ls-colors**
                  output fully escaped colors for display
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           If FILE is specified, read it to determine which colors to use for
           which file types and extensions.  Otherwise, a precompiled
           database is used.  For details on the format of these files, run
           'dircolors **--print-database** '.
    


* * *
# chroot

## NAME



           chroot - run command or interactive shell with special root
           directory
    


## SYNOPSIS



           **chroot**[_OPTION_] _NEWROOT_ [_COMMAND_ [_ARG_]...]
           **chroot** _OPTION_
    


## DESCRIPTION



           Run COMMAND with root directory set to NEWROOT.
    
           **--groups** =_G_LIST_
                  specify supplementary groups as g1,g2,..,gN
    
           **--userspec** =_USER_ :GROUP
                  specify user and group (ID or name) to use
    
           **--skip-chdir**
                  do not change working directory to '/'
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           If no command is given, run '"$SHELL" **-i** ' (default: '/bin/sh **-i** ').
    
       **Exit status:**
           125    if the chroot command itself fails
    
           126    if COMMAND is found but cannot be invoked
    
           127    if COMMAND cannot be found
    
           -      the exit status of COMMAND otherwise
    


* * *
# systemd-ac-power

## NAME



           systemd-ac-power - Report whether we are connected to an external
           power source
    


## SYNOPSIS



    
           **systemd-ac-power**[OPTIONS...]
    


## DESCRIPTION



           **systemd-ac-power** may be used to check whether the system is
           running on AC power or not. By default, it will simply return
           success (if we can detect that we are running on AC power) or
           failure, with no output. This can be useful for example to debug
           _ConditionACPower=_ (see systemd.unit(5)).
    


## OPTIONS



           The following options are understood:
    
           **-v** , **--verbose**
               Show result as text instead of just returning success or
               failure.
    
               Added in version 253.
    
           **--low**
               Instead of showing AC power state, show low battery state. In
               this case, will return zero if all batteries are currently
               discharging and below 5% of maximum charge. Returns non-zero
               otherwise.
    
               Added in version 254.
    
           **-h** , **--help**
               Print a short help text and exit.
    
           **--version**
               Print a short version string and exit.
    


## EXIT STATUS



           On success (running on AC power), 0 is returned, a non-zero
           failure code otherwise.
    


* * *
# pmdazfs

## NAME



           **pmdazfs** - ZFS filesystem performance metrics domain agent (PMDA)
           for Linux
    


## SYNOPSIS



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


## DESCRIPTION



           **pmdazfs** is a Performance Metrics Domain Agent (PMDA) which
           extracts performance metrics describing the state of the ZFS
           filesystem from the stats files located in /proc.
    
           The **zfs** PMDA exports metrics that measure information about
           caching (ARC, L2ARC, ZIL, VDEV), buffering, RAIDZ, dnode
           operations and pools IO.
    
           A brief description of the **pmdazfs** command line options follows:
    
           **-d** The performance metrics _domain_ number must be set to a unique
                value.
    
           **-l** Location of the log file.  By default, a log file named
                _zfs.log_ is written in the current directory of pmcd(1) when
                **pmdazfs** is started, i.e.  **$PCP_LOG_DIR/pmcd**.  If the log file
                cannot be created or is not writable, output is written to
                the standard error instead.
    


## INSTALLATION



           OpenZFS is not included in PCP, and has to be installed on the
           system from the available packages or source.  Once OpenZFS is
           installed and configured, the stats files should appear in /proc
           and PMDA can be added to PMCD using the Install script:
    
                # cd $PCP_PMDAS_DIR/zfs
                # ./Install
    
           To remove PMDA use the Remove script:
    
                # cd $PCP_PMDAS_DIR/zfs
                # ./Remove
    


## DEBUGGING OPTIONS



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


* * *
# dh_testdir

## NAME



           dh_testdir - test directory before building Debian package
    


## SYNOPSIS



           **dh_testdir**[_debhelper options_] [_file_ ...]
    


## DESCRIPTION



           **dh_testdir** tries to make sure that you are in the correct
           directory when building a Debian package. It makes sure that the
           file _debian/control_ exists, as well as any other files you
           specify. If not, it exits with an error.
    


## OPTIONS



           _file_ ...
               Test for the existence of these files too.
    


* * *
# lxc-config

## NAME



           lxc-config - query LXC system configuration
    


## SYNOPSIS



           **lxc-config**[-l] [_item_]
    


## DESCRIPTION



           **lxc-config** queries the lxc system configuration and lets you list
           all valid keys or query individual keys for their value.
    


## OPTIONS



           **-l** List all supported keys.
    
           **item** Query the value of the specified key.
    


* * *
# pcp-python

## NAME



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


## SYNOPSIS



           **pcp python**[_SCRIPT_ [_ARG_] ...]
    


## DESCRIPTION



           **pcp-python** has been replaced by pmpython(1) which is preferred,
           however **pcp-python** is still installed to provided backwards
           compatibility.
    
           **pcp-python** provides a way to run python scripts using a
           customisable python binary, rather than embedding any particular
           version of python into each script.
    
           This can be useful as it allows version-independent python code to
           be run anywhere.  All python modules shipped with PCP support
           versions 2.6 and later (in the python2 series), and 3.3 and later
           (in the python3 release series).
    
           Due to python monitoring and collecting scripts being relatively
           simple in PCP (not requiring new modules, language features, etc),
           it has been possible to ensure they work for all of the above
           python versions.  Thus, it is common for PCP python scripts to use
           a "shebang" line that invokes **pcp-python** as follows:
    
              _#!/usr/bin/pcp python_
    
           This allows the custom setting to be injected instead of a hard-
           coded python version, while still allowing the user to override
           the python version as follows:
    
              **$ PCP_PYTHON_PROG=python3 /usr/bin/pcp python --version**
              Python 3.3.2
              **$ PCP_PYTHON_PROG=python2 /usr/bin/pcp python --version**
              Python 2.7.5
    
           This is convenient for shipping identical scripts on multiple
           platforms, and for testing different python versions with the one
           script (e.g. in the case where multiple versions of python are
           installed, PCP_PYTHON_PROG can be set in the local environment to
           override the global setting).
    
           By default, the value of PCP_PYTHON_PROG from _/etc/pcp.conf_ will
           be used.  The default value of this configuration parameter is set
           depending on some heuristics about the target build platform.
           These heuristics favour the use of _python3_ in all recent releases
           of PCP, for those platforms that support it.
    


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


* * *
# mmdbresolve

## NAME



           mmdbresolve - Read IPv4 and IPv6 addresses and print their IP
           geolocation information.
    


## SYNOPSIS



           **mmdbresolve**[ **-v**]
    
           **mmdbresolve**[ **-h**]
    
           **mmdbresolve -f <dbfile> **[ **-f <dbfile> **] _..._
    


## DESCRIPTION



           **mmdbresolve** reads IPv4 and IPv6 addresses on stdin and prints
           their IP geolocation information on stdout. Each input line must
           contain exactly one address. Output is in INI format, with a
           section delimiter named after the query address followed by a set
           of "key: value" pairs. A comment beginning with "# End" is
           appended to each section.
    
           At startup an "[init]" section is printed that shows the status of
           each database and of mmdbresolve itself.
    


## OPTIONS



           -v
               Print version information and exit.
    
           -h
               Print help information and exit.
    
           -f
               Path to a MaxMind Database file. Multiple databases may be
               specified.
    


## EXAMPLES



           To resolve a single address:
    
               echo 4.4.4.4 | mmdbresolve -f /usr/share/GeoIP/GeoLite2-City.mmdb
    
           **Example output**
    
               [init]
               db.0.path: /usr/share/GeoIP/GeoLite2-City.mmdb
               db.0.status: OK
               mmdbresolve.status: true
               # End init
               [4.4.4.4]
               # GeoLite2-City
               country.iso_code: US
               country.names.en: United States
               location.latitude: 37.751000
               location.longitude: -97.822000
               # End 4.4.4.4
    


## NOTES



           **mmdbresolve** is part of the **Wireshark** distribution. The latest
           version of **Wireshark** can be found at https://www.wireshark.org.
    
           HTML versions of the Wireshark project man pages are available at
           https://www.wireshark.org/docs/man-pages.
    


* * *
# stap-merge

## NAME



           stap-merge - systemtap per-cpu binary merger
    


## SYNOPSIS



           **stap-merge**[ _OPTIONS_ ] [ _INPUT FILENAMES_ ]
    


## DESCRIPTION



           The stap-merge executable applies when the -b option has been used
           while running a _stap_ script.  The -b option will generate files
           per-cpu, based on the timestamp field. Then stap-merge will merge
           and sort through the per-cpu files based on the timestamp field.
    


## OPTIONS



           The systemtap merge executable supports the following options.
    
           **-v** Verbose mode, displays three extra fields per set of
                  collected data.
    
                  **[cpu** number,**sequence** number**of** data,**the** length**of** the**data** set]
    
           **-o** _OUTPUT_FILENAME_
    
                  Specify the name of the file you would like the output to
                  be redirected into.  If this option is not specified than
                  the output will be pushed to standard out.
    


## EXAMPLES



                  $ stap -v -b -e 'probe syscall.open { printf("%s(%d) open\n",
                  execname(), pid()) }'
    
           This should result in several _stpd_cpu_ files (each labled with a
           number representing which cpu the file was produced from).
    
                  $ stap-merge -v stpd_cpu0 stpd_cpu1
    
           Running the stap-merge program in the same directory as the stap
           script earlier in the example, will produce an ordered sequence of
           packets with the three part label for each set of data.  This re‐
           sult will be pushed through the standard output.  An output file
           could have been specified using the "-o" option.
    


## FILES



           Important files and their corresponding paths can be located in
           the
                  stappaths (7) manual page.
    


## BUGS



           Use the Bugzilla link of the project web page or our mailing list.
           **http://sourceware.org/systemtap/ **,**< systemtap@sourceware.org>**.
    


* * *
# mariadb-tzinfo-to-sql

## NAME



           mariadb-tzinfo-to-sql - load the time zone tables (mariadb-tzinfo-
           to-sql is now a symlink to mariadb-tzinfo-to-sql)
    


## SYNOPSIS



    
           **mariadb-tzinfo-to-sql** _arguments_
    


## DESCRIPTION



           The **mariadb-tzinfo-to-sql** program loads the time zone tables in
           the mysql database. It is used on systems that have a zoneinfo
           database (the set of files describing time zones). Examples of
           such systems are Linux, FreeBSD, Solaris, and Mac OS X. One likely
           location for these files is the /usr/share/zoneinfo directory
           (/usr/share/lib/zoneinfo on Solaris).
    
           **mariadb-tzinfo-to-sql** can be invoked several ways:
    
               shell> **mariadb-tzinfo-to-sql** _tz_dir_
               shell> **mariadb-tzinfo-to-sql** _tz_file tz_name_
               shell> **mariadb-tzinfo-to-sql --leap** _tz_file_
               shell> **mariadb-tzinfo-to-sql --skip-write-binlog** _tz_dir_
    
           For the first invocation syntax, pass the zoneinfo directory path
           name to **mariadb-tzinfo-to-sql** and send the output into the **mariadb**
           program. For example:
    
               shell> **mariadb-tzinfo-to-sql /usr/share/zoneinfo | mariadb -u root mysql**
    
           **mariadb-tzinfo-to-sql** reads your system's time zone files and
           generates SQL statements from them.  **mariadb** processes those
           statements to load the time zone tables.
    
           The second syntax causes **mariadb-tzinfo-to-sql** to load a single
           time zone file _tz_file_ that corresponds to a time zone name
           _tz_name_ :
    
               shell> **mariadb-tzinfo-to-sql** _tz_file tz_name_ **| mariadb -u root mysql**
    
           If your time zone needs to account for leap seconds, invoke
           **mariadb-tzinfo-to-sql** using the third syntax, which initializes
           the leap second information.  _tz_file_ is the name of your time
           zone file:
    
               shell> **mariadb-tzinfo-to-sql --leap** _tz_file_ **| mariadb -u root mysql**
    
           Using the --skip-write-binlog option prevents writing of changes
           to the binary log or to other Galera cluster members. This can be
           used with any form of running **mariadb-tzinfo-to-sql**.
    
           After running **mariadb-tzinfo-to-sql** , it is best to restart the
           server so that it does not continue to use any previously cached
           time zone data.
    


* * *
# false

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



           false — return false value
    


## SYNOPSIS



           false
    


## DESCRIPTION



           The _false_ utility shall return with a non-zero exit code.
    


## OPTIONS



           None.
    


## OPERANDS



           None.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           Not used.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           The _false_ utility shall always exit with a value other than zero.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           None.
    


## RATIONALE



           None.
    


## FUTURE DIRECTIONS



           None.
    


* * *
# comm

## NAME



           comm - compare two sorted files line by line
    


## SYNOPSIS



           **comm**[_OPTION_]... _FILE1 FILE2_
    


## DESCRIPTION



           Compare sorted files FILE1 and FILE2 line by line.
    
           When FILE1 or FILE2 (not both) is -, read standard input.
    
           With no options, produce three-column output.  Column one contains
           lines unique to FILE1, column two contains lines unique to FILE2,
           and column three contains lines common to both files.
    
           **-1** suppress column 1 (lines unique to FILE1)
    
           **-2** suppress column 2 (lines unique to FILE2)
    
           **-3** suppress column 3 (lines that appear in both files)
    
           **--check-order**
                  check that the input is correctly sorted, even if all input
                  lines are pairable
    
           **--nocheck-order**
                  do not check that the input is correctly sorted
    
           **--output-delimiter** =_STR_
                  separate columns with STR
    
           **--total**
                  output a summary
    
           **-z** , **--zero-terminated**
                  line delimiter is NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Comparisons honor the rules specified by 'LC_COLLATE'.
    


## EXAMPLES



           comm -12 file1 file2
                  Print only lines present in both file1 and file2.
    
           comm -3 file1 file2
                  Print lines in file1 not in file2, and vice versa.
    


* * *
# riostream

## NAME



           riostream - zero-copy streaming over RDMA ping-pong test.
    


## SYNOPSIS



           _riostream_ [-s server_address] [-b bind_address] [-B buffer_size]
                          [-I iterations] [-C transfer_count]
                          [-S transfer_size] [-p server_port] [-T test_option]
    


## DESCRIPTION



           Uses the streaming over RDMA protocol (rsocket) to connect and
           exchange data between a client and server application.
    


## OPTIONS



           -s server_address
                  The network name or IP address of the server system
                  listening for connections.  The used name or address must
                  route over an RDMA device.  This option must be specified
                  by the client.
    
           -b bind_address
                  The local network address to bind to.
    
           -B buffer_size
                  Indicates the size of the send and receive network buffers.
    
           -I iterations
                  The number of times that the specified number of messages
                  will be exchanged between the client and server.  (default
                  1000)
    
           -C transfer_count
                  The number of messages to transfer from the client to the
                  server and back again on each iteration.  (default 1)
    
           -S transfer_size
                  The size of each send transfer, in bytes.  (default 1000)
                  If 'all' is specified, rstream will run a series of tests
                  of various sizes.
    
           -p server_port
                  The server's port number.
    
           -T test_option
                  Specifies test parameters.  Available options are:
    
           a | async - uses asynchronous operation (e.g. select / poll)
    
           b | blocking - uses blocking calls
    
           n | nonblocking - uses non-blocking calls
    
           v | verify - verifies data transfers
    


## NOTES



           Basic usage is to start riostream on a server system, then run
           riostream -s server_name on a client system.  By default,
           riostream will run a series of latency and bandwidth performance
           tests.  Specifying a different iterations, transfer_count, or
           transfer_size will run a user customized test using default values
           where none have been specified.
    
           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.
    


* * *
# fadvise

## NAME



           fadvise - utility to use the posix_fadvise system call
    


## SYNOPSIS



           **fadvise**[**-a** _advice_] [**-o** _offset_] [**-l** _length_] _filename_
    
           **fadvise**[**-a** _advice_] [**-o** _offset_] [**-l** _length_] -d _file-descriptor_
    


## DESCRIPTION



           **fadvise** is a simple command wrapping posix_fadvise(2) system call
           that is for predeclaring an access pattern for file data.
    


## OPTIONS



           **-d** , **--fd** _file-descriptor_
               Apply the advice to the file specified with the file
               descriptor instead of open a file specified with a file name.
    
           **-a** , **--advice** _advice_
               See the command output with **--help** option for available values
               for advice. If this option is omitted, "dontneed" is used as
               default advice.
    
           **-o** , **--offset** _offset_
               Specifies the beginning offset of the range, in bytes. If this
               option is omitted, 0 is used as default advice.
    
           **-l** , **--length** _length_
               Specifies the length of the range, in bytes. If this option is
               omitted, 0 is used as default advice.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## EXIT STATUS



           **fadvise** has the following exit status values:
    
           **0**
               success
    
           **1**
               unspecified failure
    


## AVAILABILITY



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


* * *
# rcopy

## NAME



           rcopy - simple file copy over RDMA.
    


## SYNOPSIS



           _rcopy_ source server[:destination] [-p port]
           _rcopy_ [-p port]
    


## DESCRIPTION



           Uses sockets over RDMA interface to copy a source file to the
           specified destination.
    


## OPTIONS



           source The name and path of the source file to copy.
    
           server The name or address of the destination server.
    
           :destination
                  An optional destination filename and path.  If not given,
                  the destination filename will match that of the source.
    
           -p server_port
                  The server's port number.
    


## NOTES



                  Basic usage is to start rcopy on a server system, then run
                  rcopy sourcefile servername.  The server application will
                  continue to run after copying the file, but is currently
                  single-threaded.
    
           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.
    


* * *
# times

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



           times — write process times
    


## SYNOPSIS



           times
    


## DESCRIPTION



           The _times_ utility shall write the accumulated user and system
           times for the shell and for all of its child processes, in the
           following POSIX locale format:
    
               "%dm%fs %dm%fs\n%dm%fs %dm%fs\n", <_shell user minutes_ >,
                   <_shell user seconds_ >, <_shell system minutes_ >,
                   <_shell system seconds_ >, <_children user minutes_ >,
                   <_children user seconds_ >, <_children system minutes_ >,
                   <_children system seconds_ >
    
           The four pairs of times shall correspond to the members of the
           _< sys/times.h>_ **tms** structure (defined in the Base Definitions
           volume of POSIX.1‐2017, _Chapter 13_ , _Headers_) as returned by
           _times_(): _tms_utime_ , _tms_stime_ , _tms_cutime_ , and _tms_cstime_ ,
           respectively.
    


## OPTIONS



           None.
    


## OPERANDS



           None.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           See the DESCRIPTION.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



            0    Successful completion.
    
           >0    An error occurred.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           **$** times
           **0m0.43s 0m1.11s**
           **8m44.18s 1m43.23s**
    


## RATIONALE



           The _times_ special built-in from the Single UNIX Specification is
           now required for all conforming shells.
    


## FUTURE DIRECTIONS



           None.
    


* * *
# stg-fold

## NAME



           stg-fold - Fold diff file into the current patch
    


## SYNOPSIS



           _stg fold_ [OPTIONS] [file]
    


## DESCRIPTION



           Fold diff file into the current patch. The given GNU diff file (or
           standard input) is applied onto the current patch.
    
           With the _--threeway_ option, the diff is applied onto the bottom of
           the current patch and a three-way merge is performed with the
           current top. With the _--base_ option, the diff is applied onto the
           specified base and a three-way merge is performed with the current
           top.
    


## OPTIONS



           -t, --threeway
               Perform a three-way merge with the current patch
    
           -b <committish>, --base=<committish>
               Use <committish> instead of HEAD when applying the patch
    
           -p <n>, --strip=<n>
               Remove <n> leading components from diff paths (default 1)
    
           -C <n>
               Ensure <n> lines of matching context for each change
    
           --reject
               Leave rejected hunks in ".rej" files
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# git-pack-redundant

## NAME



           git-pack-redundant - Find redundant pack files
    


## SYNOPSIS



           _git pack-redundant_ [--verbose] [--alt-odb] (--all | <pack-filename>...)
    


## WARNING



           **git pack-redundant** has been deprecated and is scheduled for
           removal in a future version of Git. Because it can only remove
           entire duplicate packs and not individual duplicate objects, it is
           generally not a useful tool for reducing repository size. You are
           better off using **git gc** to do so, which will put objects into a
           new pack, removing duplicates.
    
           Running **pack-redundant** without the **--i-still-use-this** flag will
           fail in this release. If you believe you have a use case for which
           **pack-redundant** is better suited and oppose this removal, please
           contact the Git mailing list at **git@vger.kernel.org******[1]. More
           information about the list is available at**https://git-scm.com/community ******.


## DESCRIPTION



           This program computes which packs in your repository are
           redundant. The output is suitable for piping to **xargs rm** if you
           are in the root of the repository.
    
           _git pack-redundant_ accepts a list of objects on standard input.
           Any objects given will be ignored when checking which packs are
           required. This makes the following command useful when wanting to
           remove packs which contain unreachable objects.
    
           git fsck --full --unreachable | cut -d ' ' -f3 | \ git
           pack-redundant --all | xargs rm
    


## OPTIONS



           --all
               Processes all packs. Any filenames on the command line are
               ignored.
    
           --alt-odb
               Don’t require objects present in packs from alternate object
               database (odb) directories to be present in local packs.
    
           --verbose
               Outputs some statistics to stderr. Has a small performance
               penalty.
    


## GIT



           Part of the git(1) suite
    


## NOTES



            1. git@vger.kernel.org
               mailto:git@vger.kernel.org
    


* * *