tripathysagar/man_text huggingface dataset:
# tsort

## NAME



           tsort - perform topological sort
    


## SYNOPSIS



           **tsort**[_OPTION_] [_FILE_]
    


## DESCRIPTION



           Write totally ordered list consistent with the partial ordering in
           FILE.
    
           With no FILE, or when FILE is -, read standard input.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# git-hook

## NAME



           git-hook - Run git hooks
    


## SYNOPSIS



           _git hook_ run [--ignore-missing] [--to-stdin=<path>] <hook-name> [-- <hook-args>]
    


## DESCRIPTION



           A command interface for running git hooks (see githooks(5)), for
           use by other scripted git commands.
    


## SUBCOMMANDS



           run
               Run the _< hook-name>_ hook. See githooks(5) for supported hook
               names.
    
               Any positional arguments to the hook should be passed after a
               mandatory **--**(or **--end-of-options** , see gitcli(7)). See
               githooks(5) for arguments hooks might expect (if any).
    


## OPTIONS



           --to-stdin
               For "run"; specify a file which will be streamed into the
               hook’s stdin. The hook will receive the entire file from
               beginning to EOF.
    
           --ignore-missing
               Ignore any missing hook by quietly returning zero. Used for
               tools that want to do a blind one-shot run of a hook that may
               or may not be present.
    


## GIT



           Part of the git(1) suite
    


* * *
# replace

## NAME



           replace - a string-replacement utility
    


## SYNOPSIS



    
           **replace** _arguments_
    


## DESCRIPTION



           The **replace** utility program changes strings in place in files or
           on the standard input.
    
           Invoke **replace** in one of the following ways:
    
               shell> **replace** _from to_ **[**_from to_**] ... --**_file_name_ **[**_file_name_**] ...**
               shell> **replace** _from to_ **[**_from to_**] ... < **_file_name_
    
           _from_ represents a string to look for and _to_ represents its
           replacement. There can be one or more pairs of strings.
    
           Use the **--** option to indicate where the string-replacement list
           ends and the file names begin. In this case, any file named on the
           command line is modified in place, so you may want to make a copy
           of the original before converting it.  _replace_ prints a message
           indicating which of the input files it actually modifies.
    
           If the **--** option is not given, **replace** reads the standard input
           and writes to the standard output.
    
           **replace** uses a finite state machine to match longer strings first.
           It can be used to swap strings. For example, the following command
           swaps a and b in the given files, file1 and file2:
    
               shell> **replace a b b a -- file1 file2 ...**
    
           The **replace** program is used by **msql2mysql**. See msql2mysql(1).
    
           **replace** supports the following options.
    
           •   **-?** , **-I**
    
               Display a help message and exit.
    
           •   **-#**_debug_options_
    
               Enable debugging.
    
           •   **-s**
    
               Silent mode. Print less information what the program does.
    
           •   **-v**
    
               Verbose mode. Print more information about what the program
               does.
    
           •   **-V**
    
               Display version information and exit.
    


* * *
# dh_installsystemduser

## NAME



           dh_installsystemduser - install systemd unit files
    


## SYNOPSIS



           **dh_installsystemduser**[_debhelper options_] [**--no-enable**]
           [**--name=**_name_] [_unit file_ ...]
    


## DESCRIPTION



           **dh_installsystemduser** finds the systemd user instance service
           files installed by a package and generates _preinst_ , _postinst_ , and
           _prerm_ code blocks for enabling, disabling, starting, stopping, and
           restarting the corresponding systemd user instance services, when
           the package is installed, updated, or removed. These snippets are
           added to the maintainer scripts by dh_installdeb(1).
    
           **deb-systemd-helper**(1) is used to enable and disable the systemd
           units, thus it is not necessary that the machine actually runs
           systemd during package installation time, enabling happens on all
           machines.
    
           **dh_installsystemduser** operates on all user instance unit files
           installed by a package. For only generating blocks for specific
           unit files, pass them as arguments. Specific unit files can be
           excluded from processing using the **-X** common **debhelper**(1) option.
    


## FILES



           debian/_package_.user.path, debian/_package_ @.user.path,
           debian/_package_.user.service, debian/_package_ @.user.service,
           debian/_package_.user.socket, debian/_package_ @.user.socket,
           debian/_package_.user.target, debian/_package_ @.user.target,
           debian/_package_.user.timer, debian/_package_ @.user.timer
               If any of those files exists, they are installed into
               _usr/lib/systemd/user/_ in the package build directory removing
               the _.user_ file name part.
    


## OPTIONS



           **--name=**_name_
               Install the service file as _name.service_ instead of the
               default filename _package.service_. When this parameter is used,
               **dh_installsystemd** looks for and installs files named
               _debian/package.name.user.service_ instead of the usual
               _debian/package.user.service_.  Moreover, maintainer scripts are
               only generated for units that match the given _name_.
    
           **--no-enable**
               Disable the service(s) on purge, but do not enable them on
               install.
    


## NOTES



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


* * *
# dh_installpam

## NAME



           dh_installpam - install pam support files
    


## SYNOPSIS



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


## DESCRIPTION



           **dh_installpam** is a debhelper program that is responsible for
           installing files used by PAM into package build directories.
    


## FILES



           debian/_package_.pam
               Installed into usr/lib/pam.d/_package_ in the package build
               directory.
    
               Until compatibility level 14 this file was installed under
               etc/pam.d/_package_. Please consider using the "rm_conffile"
               feature from dh_installdeb(1) to ensure the proper removal of
               previous PAM files.
    


## OPTIONS



           **--name=**_name_
               Look for files named debian/_package_._name_.pam and install them
               as usr/lib/pam.d/_name_ , instead of using the usual files and
               installing them using the package name.
    


* * *
# stg-sink

## NAME



           stg-sink - Move patches deeper in the stack
    


## SYNOPSIS



           _stg sink_ [OPTIONS] [patch]...
    


## DESCRIPTION



           Move the specified patches down the stack.
    
           If no patch is specified on the command line, the current
           (topmost) patch is sunk. By default, patches are sunk to the
           bottom of the stack, but the _--above_ or _--below_ (alias _--to_)
           options may be used to place them above or below any applied
           patch.
    
           Internally, sinking involves popping all patches to the bottom (or
           to the target patch if _--above_ or _--below_ is used), then pushing
           the patches to sink, and then, unless _--nopush_ is specified,
           pushing back any other formerly applied patches.
    
           Sinking may be useful, for example, to group stable patches at the
           bottom of the stack where they less likely to be impacted by the
           push of another patch, and from where they can be more easily
           committed or pushed to another repository.
    


## OPTIONS



           -n, --nopush
               Do not push any formerly applied patches after sinking. Only
               the patches to sink are pushed.
    
           -t <target>, --below=<target>, --to=<target>
               Sink patches below <target> patch.
    
               Specified patches are placed below <target> instead of at the
               bottom of the stack.
    
           -T <target>, --above=<target>
               Sink patches above <target> patch.
    
               Specified patches are placed above <target> instead of at the
               bottom of the stack.
    
           -k, --keep
               Keep the local changes
    
           --committer-date-is-author-date
               Instead of using the current time as the committer date, use
               the author date of the commit as the committer date.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# ngettext

## NAME



           ngettext - translate message and choose plural form
    


## SYNOPSIS



           **ngettext**[_OPTION_] [_TEXTDOMAIN_] _MSGID MSGID-PLURAL COUNT_
    


## DESCRIPTION



           The **ngettext** program translates a natural language message into
           the user's language, by looking up the translation in a message
           catalog, and chooses the appropriate plural form, which depends on
           the number _COUNT_ and the language of the message catalog where the
           translation was found.
    
           Display native language translation of a textual message whose
           grammatical form depends on a number.
    
       **Options and arguments:**
           **-d** , **--domain** =_TEXTDOMAIN_
                  retrieve translated message from TEXTDOMAIN
    
           **-c** , **--context** =_CONTEXT_
                  specify context for MSGID
    
           **-e** enable expansion of some escape sequences
    
           **-E**(ignored for compatibility)
    
           [TEXTDOMAIN]
                  retrieve translated message from TEXTDOMAIN
    
           MSGID MSGID-PLURAL
                  translate MSGID (singular) / MSGID-PLURAL (plural)
    
           COUNT  choose singular/plural form based on this value
    
       **Informative output:**
           **-h** , **--help**
                  display this help and exit
    
           **-V** , **--version**
                  display version information and exit
    
           If the TEXTDOMAIN parameter is not given, the domain is determined
           from the environment variable TEXTDOMAIN.  If the message catalog
           is not found in the regular directory, another location can be
           specified with the environment variable TEXTDOMAINDIR.  Standard
           search directory: /usr/local/share/locale
    


* * *
# git-count-objects

## NAME



           git-count-objects - Count unpacked number of objects and their
           disk consumption
    


## SYNOPSIS



           _git count-objects_ [-v] [-H | --human-readable]
    


## DESCRIPTION



           Counts the number of unpacked object files and disk space consumed
           by them, to help you decide when it is a good time to repack.
    


## OPTIONS



           -v, --verbose
               Provide more detailed reports:
    
               count: the number of loose objects
    
               size: disk space consumed by loose objects, in KiB (unless -H
               is specified)
    
               in-pack: the number of in-pack objects
    
               size-pack: disk space consumed by the packs, in KiB (unless -H
               is specified)
    
               prune-packable: the number of loose objects that are also
               present in the packs. These objects could be pruned using **git**
               **prune-packed**.
    
               garbage: the number of files in the object database that are
               neither valid loose objects nor valid packs
    
               size-garbage: disk space consumed by garbage files, in KiB
               (unless -H is specified)
    
               alternate: absolute path of alternate object databases; may
               appear multiple times, one line per path. Note that if the
               path contains non-printable characters, it may be surrounded
               by double-quotes and contain C-style backslashed escape
               sequences.
    
           -H, --human-readable
               Print sizes in human readable format
    


## GIT



           Part of the git(1) suite
    


* * *
# lxc-cgroup

## NAME



           lxc-cgroup - manage the control group associated with a container
    


## SYNOPSIS



           **lxc-cgroup**{-n _name_} {_state-object_} [value]
    


## DESCRIPTION



           **lxc-cgroup** gets  or  sets  the  value  of  a  _state-object_ (e.g.,
           'cpuset.cpus') in the container's  cgroup  for  the  corresponding
           subsystem  (e.g.,  'cpuset'). If no [value] is specified, the cur‐
           rent value of the _state-object_ is displayed; otherwise it is set.
    
           Note that **lxc-cgroup** does not check that the _state-object_ is valid
           for the running kernel, or that  the  corresponding  subsystem  is
           contained in any mounted cgroup hierarchy.
    


## OPTIONS



           _state-object_
                  Specify the state object name.
    
           **[value]**
                  Specify the value to assign to the state object.
    


## COMMON OPTIONS



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


## EXAMPLES



           lxc-cgroup -n foo devices.list
                  display the allowed devices to be used.
    
           lxc-cgroup -n foo cpuset.cpus "0,3"
                  assign the processors 0 and 3 to the container.
    


## DIAGNOSTIC



           The container was not found
                  The container is not running.
    


* * *
# git-sh-i18n

## NAME



           git-sh-i18n - Git's i18n setup code for shell scripts
    


## SYNOPSIS



           _. "$(git --exec-path)/git-sh-i18n"_
    


## DESCRIPTION



           This is not a command the end user would want to run. Ever. This
           documentation is meant for people who are studying the
           Porcelain-ish scripts and/or are writing new ones.
    
           The 'git sh-i18n scriptlet is designed to be sourced (using .) by
           Git’s porcelain programs implemented in shell script. It provides
           wrappers for the GNU **gettext** and **eval_gettext** functions accessible
           through the **gettext.sh** script, and provides pass-through fallbacks
           on systems without GNU gettext.
    


## FUNCTIONS



           gettext
               Currently a dummy fall-through function implemented as a
               wrapper around **printf**(**1**). Will be replaced by a real gettext
               implementation in a later version.
    
           eval_gettext
               Currently a dummy fall-through function implemented as a
               wrapper around **printf**(**1**) with variables expanded by the
               git-sh-i18n--envsubst(1) helper. Will be replaced by a real
               gettext implementation in a later version.
    


## GIT



           Part of the git(1) suite
    


* * *
# groups

## NAME



           groups - print the groups a user is in
    


## SYNOPSIS



           **groups**[_OPTION_]... [_USERNAME_]...
    


## DESCRIPTION



           Print group memberships for each USERNAME or, if no USERNAME is
           specified, for the current process (which may differ if the groups
           database has changed).
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# dh_fixperms

## NAME



           dh_fixperms - fix permissions of files in package build
           directories
    


## SYNOPSIS



           **dh_fixperms**[_debhelper options_] [**-X** _item_]
    


## DESCRIPTION



           **dh_fixperms** is a debhelper program that is responsible for setting
           the permissions of files and directories in package build
           directories to a sane state -- a state that complies with Debian
           policy.
    
           **dh_fixperms** makes all files in _usr/share/doc_ in the package build
           directory (excluding files in the _examples/_ directory) be mode
           644. It also changes the permissions of all man pages to mode 644.
           It removes group and other write permission from all files. It
           removes execute permissions from any libraries, headers, Perl
           modules, or desktop files that have it set. It makes all files in
           the standard _bin_ and _sbin_ directories, _usr/games/_ and _etc/init.d_
           executable (since v4). Finally, it removes the setuid and setgid
           bits from all files in the package.
    
           When the _Rules-Requires-Root_ field has the (effective) value of
           _binary-targets_ , **dh_fixperms** will also reset the ownership of all
           paths to "root:root".
    


## OPTIONS



           **-X** _item_ , **--exclude** _item_
               Exclude files that contain _item_ anywhere in their filename
               from having their permissions changed. You may use this option
               multiple times to build up a list of things to exclude.
    


* * *
# comp_err

## NAME



           comp_err - compile MariaDB error message file
    


## SYNOPSIS



    
           **comp_err [**_options_**]**
    


## DESCRIPTION



           **comp_err** creates the errmsg.sys file that is used by **mariadbd** to
           determine the error messages to display for different error codes.
           **comp_err** normally is run automatically when MariaDB is built. It
           compiles the errmsg.sys file from the plaintext file located at
           sql/share/errmsg.txt in MariaDB source distributions.
    
           **comp_err** also generates mysqld_error.h, mysqld_ername.h, and
           sql_state.h header files.
    
           For more information about how error messages are defined, see the
           MariaDB Manual.
    
           Invoke **comp_err** like this:
    
               shell> **comp_err [**_options_**]**
    
           **comp_err** supports the following options.
    
           •   **--help** , **-?**
    
               Display a help message and exit.
    
           •   **--charset=**_path_ , **-C** _path_
    
               The character set directory. The default is
               ../sql/share/charsets.
    
           •   **--debug=**_debug_options_ , **-#**_debug_options_
    
               Write a debugging log. A typical _debug_options_ string is
               ´d:t:O,_file_name_ ´. The default is ´d:t:O,/tmp/comp_err.trace´.
    
           •   **--debug-info** , **-T**
    
               Print some debugging information when the program exits.
    
           •   **--header_file=**_file_name_ , **-H** _file_name_
    
               The name of the error header file. The default is
               mariadbd_error.h.
    
           •   **--in_file=**_file_name_ , **-F** _file_name_
    
               The name of the input file. The default is
               ../sql/share/errmsg.txt.
    
           •   **--name_file=**_file_name_ , **-N** _file_name_
    
               The name of the error name file. The default is
               mysqld_ername.h.
    
           •   **--out_dir=**_path_ , **-D** _path_
    
               The name of the output base directory. The default is
               ../sql/share/.
    
           •   **--out_file=**_file_name_ , **-O** _file_name_
    
               The name of the output file. The default is errmsg.sys.
    
           •   **--statefile=**_file_name_ , **-S** _file_name_
    
               The name for the SQLSTATE header file. The default is
               sql_state.h.
    
           •   **--version** , **-V**
    
               Display version information and exit.
    


* * *
# pmlogpaste

## NAME



           **pmlogpaste** - paste text into a metric in a PCP archive
    


## SYNOPSIS



           **pmlogpaste**[**-?**]  [**-f** _file_] [**-h** _hostname_] [**-l** _label_] [**-m** _metric_]
           [**-o** _outfile_] [**-t** _timezone_]
    


## DESCRIPTION



           **pmlogpaste** takes input text from a file or the command line, and
           writes it as a metric value in a new PCP archive.  This metric
           value is timestamped with the current time, and is stored as a
           string type metric.
    
           The main purpose of this tool is to take captured output and
           preserve this in a PCP archive.  This allows, for example, the
           output of a benchmark run to be stored along with performance
           metrics captured during that run, in a single archive.  Archives
           can be merged using the pmlogextract(1) utility.
    
           **pmlogpaste** uses the LOGIMPORT(3) library interfaces internally,
           which support the creation of archives from external sources of
           performance data.
    


## OPTIONS



           The available command line options are:
    
           **-f** _file_ , **--file** =_file_
                File with input text to be archived, or ``-'' for standard
                input.
    
           **-h** _hostname_ , **--hostname** =_hostname_
                Source host name for the archive.  The default value is the
                local host name, or ``localhost'' if that cannot be obtained.
    
           **-l** _label_ , **--label** =_label_
                Add context labels to the generated archive.  This option can
                be presented multiple times to produce multiple labels in the
                archive.  The _label_ should be in the form _name:value_.
    
           **-m** _metric_ , **--metric** =_metric_
                Metric name for the archive.  The default metric name is
                _paste.value_.
    
           **-o** _outfile_ , **--outfile** =_outfile_
                Archive output file.  The default archive name is _paste_.
    
           **-t** _timezone_ , **--timezone** =_timezone_
                Source timezone for the archive archive.  The default value
                is the local timezone.
    
           **-?** , **--help**
                Display usage message and exit.
    


## PCP ENVIRONMENT



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


* * *
# ibv_rc_pingpong

## NAME



           ibv_rc_pingpong - simple InfiniBand RC transport test
    


## SYNOPSIS



           **ibv_rc_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o]
           [-P] [-t] [-j] [-N] **HOSTNAME**
    
           **ibv_rc_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid index] [-o]
           [-P] [-t] [-j] [-N]
    


## DESCRIPTION



           Run a simple ping-pong test over InfiniBand via the reliable
           connected (RC) transport.
    


## OPTIONS



           **-p** , **--port** =_PORT_
                  use TCP port _PORT_ for initial synchronization (default
                  18515)
    
           **-d** , **--ib-dev** =_DEVICE_
                  use IB device _DEVICE_ (default first device found)
    
           **-i** , **--ib-port** =_PORT_
                  use IB port _PORT_ (default port 1)
    
           **-s** , **--size** =_SIZE_
                  ping-pong messages of size _SIZE_ (default 4096)
    
           **-m** , **--mtu** =_SIZE_
                  path MTU _SIZE_ (default 1024)
    
           **-r** , **--rx-depth** =_DEPTH_
                  post _DEPTH_ receives at a time (default 1000)
    
           **-n** , **--iters** =_ITERS_
                  perform _ITERS_ message exchanges (default 1000)
    
           **-l** , **--sl** =_SL_
                  use _SL_ as the service level value of the QP (default 0)
    
           **-e** , **--events**
                  sleep while waiting for work completion events (default is
                  to poll for completions)
    
           **-g** , **--gid-idx** =_GIDINDEX_
                  local port _GIDINDEX_
    
           **-o** , **--odp**
                  use on demand paging
    
           **-P** , **--prefetch=**
                  prefetch an ODP MR
    
           **-t** , **--ts**
                  get CQE with timestamp
    
           **-c** , **--chk**
                  validate received buffer
    
           **-j** , **--dm**
                  use device memory
    
           **-N** , **--new_send**
                  use new post send WR API
    


## BUGS



           The network synchronization between client and server instances is
           weak, and does not prevent incompatible options from being used on
           the two instances.  The method used for retrieving work
           completions is not strictly correct, and race conditions may cause
           failures on some systems.
    


* * *
# trace-cmd-listen

## NAME



           trace-cmd-listen - listen for incoming connection to record
           tracing.
    


## SYNOPSIS



           **trace-cmd listen** -p _port_ [_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) listen sets up a port to listen to waiting for
           connections from other hosts that run trace-cmd-record(1) with the
           **-N** option. When a connection is made, and the remote host sends
           data, it will create a file called _trace.HOST:PORT.dat_. Where HOST
           is the name of the remote host, and PORT is the port that the
           remote host used to connect with.
    


## OPTIONS



           **-p** _port_
               This option will specify the port to listen to.
    
           **-D**
               This options causes trace-cmd listen to go into a daemon mode
               and run in the background.
    
           **-V**
               Listen on a vsocket instead. This is useful for tracing
               between host and guest VMs.
    
           **-d** _dir_
               This option specifies a directory to write the data files
               into.
    
           **-o** _filename_
               This option overrides the default _trace_ in the
               _trace.HOST:PORT.dat_ that is created when a remote host
               connects.
    
           **-l** _filename_
               This option writes the output messages to a log file instead
               of standard output.
    
           **--verbose**[=_level_]
               Set the log level. Supported log levels are "none",
               "critical", "error", "warning", "info", "debug", "all" or
               their identifiers "0", "1", "2", "3", "4", "5", "6". Setting
               the log level to specific value enables all logs from that and
               all previous levels. The level will default to "info" if one
               is not specified.
    
                   Example: enable all critical, error and warning logs
    
                   trace-cmd listen --verbose=warning
    


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


* * *
# dot

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



           dot — execute commands in the current environment
    


## SYNOPSIS



           . _file_
    


## DESCRIPTION



           The shell shall execute commands from the _file_ in the current
           environment.
    
           If _file_ does not contain a <slash>, the shell shall use the search
           path specified by _PATH_ to find the directory containing _file_.
           Unlike normal command search, however, the file searched for by
           the _dot_ utility need not be executable. If no readable file is
           found, a non-interactive shell shall abort; an interactive shell
           shall write a diagnostic message to standard error, but this
           condition shall not be considered a syntax error.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           See the DESCRIPTION.
    


## ENVIRONMENT VARIABLES



           See the DESCRIPTION.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           If no readable file was found or if the commands in the file could
           not be parsed, and the shell is interactive (and therefore does
           not abort; see _Section 2.8.1_ , _Consequences of Shell Errors_), the
           exit status shall be non-zero. Otherwise, return the value of the
           last command executed, or a zero exit status if no command is
           executed.
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           None.
    


## EXAMPLES



           cat foobar
           **foo=hello bar=world**
           . ./foobar
           echo $foo $bar
           **hello world**
    


## RATIONALE



           Some older implementations searched the current directory for the
           _file_ , even if the value of _PATH_ disallowed it. This behavior was
           omitted from this volume of POSIX.1‐2017 due to concerns about
           introducing the susceptibility to trojan horses that the user
           might be trying to avoid by leaving **dot** out of _PATH_.
    
           The KornShell version of _dot_ takes optional arguments that are set
           to the positional parameters.  This is a valid extension that
           allows a _dot_ script to behave identically to a function.
    


## FUTURE DIRECTIONS



           None.
    


* * *
# pmdads389

## NAME



           **pmdads389** - 389 Directory Server PMDA
    


## DESCRIPTION



           **pmdads389** is a Performance Metrics Domain Agent (PMDA) which
           extracts live performance data from a running 389 Directory Server
           instance.
    
           See the Red Hat Directory Server Administration Guide for
           description for each metric.
    


## INSTALLATION



           **pmdads389** reads an optional configuration file
    
               • $PCP_PMDAS_DIR _/ds389/ds389.conf_
    
           This file can contain overridden values (Perl code) for the
           settings listed at the start of _pmdads389.pl_ , namely:
    
               • LDAP server
               • bind DN
               • bind password
               • default search scope
               • default search base
               • default search filter
               • query interval
               • List of sources
               • List of attributes to display for each source
    
           Please use the provided ds389.conf.example as a starting point.
           Once this is setup, you can access the names and values for the
           389 DS performance metrics by doing the following as root:
    
               **# cd $PCP_PMDAS_DIR/ds389**
               **# ./Install**
    
           To uninstall, do the following as root:
    
               **# cd $PCP_PMDAS_DIR/ds389**
               **# ./Remove**
    
           **pmdads389** 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 _/ds389/ds389.conf.example_
                  example configuration file for the **pmdads389** agent
    
           $PCP_PMDAS_DIR _/ds389/ds389.conf_
                  configuration file for the **pmdads389** agent
    
           $PCP_PMDAS_DIR _/ds389/Install_
                  installation script for the **pmdads389** agent
    
           $PCP_PMDAS_DIR _/ds389/Remove_
                  undo installation script for the **pmdads389** agent
    
           $PCP_LOG_DIR _/pmcd/ds389.log_
                  default log file for error messages from **pmdads389**
    


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


* * *
# cg_merge

## NAME



           cg_merge - (deprecated) merges multiple Cachegrind output files
           into one
    


## SYNOPSIS



    
           **cg_merge**[_options_] [_cachegrind-out-files_...]
    


## DESCRIPTION



           **cg_merge** sums together multiple 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



           **-o outfile**
               Write the output to to outfile instead of standard output.
    


* * *
# flatpak-info

## NAME



           flatpak-info - Show information about an installed application or
           runtime
    


## SYNOPSIS



    
           **flatpak info**[OPTION...] NAME [BRANCH]
    


## DESCRIPTION



           Show info about an installed application or runtime.
    
           By default, the output is formatted in a friendly format. If you
           specify any of the **--show-...** or **--file-access** options, the
           output is instead formatted in a machine-readable format.
    
           By default, both per-user and system-wide installations are
           queried. Use the **--user** , **--system** or **--installation** options to
           change this.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **-u** , **--user**
               Query per-user installations.
    
           **--system**
               Query the default system-wide installation.
    
           **--installation=NAME**
               Query a system-wide installation by NAME among those defined
               in /etc/flatpak/installations.d/. Using **--installation=default**
               is equivalent to using **--system**.
    
           **--arch=ARCH**
               Query for this architecture. See **flatpak --supported-arches**
               for architectures supported by the host.
    
           **-r** , **--show-ref**
               Show the installed ref.
    
           **-o** , **--show-origin**
               Show the remote the ref is installed from.
    
           **-c** , **--show-commit**
               Show the installed commit id.
    
           **-s** , **--show-size**
               Show the installed size.
    
           **-m** , **--show-metadata**
               Show the metadata.
    
           **--show-runtime**
               Show the runtime.
    
           **--show-sdk**
               Show the SDK.
    
           **-M** , **--show-permissions**
               Show the permissions.
    
           **--file-access=PATH**
               Show the level of access to the given path.
    
           **-e** , **--show-extensions**
               Show the matching extensions.
    
           **-l** , **--show-location**
               Show the on-disk location of the app or runtime. See the
               examples below.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


## EXAMPLES



           **$ flatpak info org.gnome.Builder//master**
    
           **$ tree `flatpak info -l org.gnome.Builder//master`/files**
    


* * *
# stg-rename

## NAME



           stg-rename - Rename a patch
    


## SYNOPSIS



           _stg rename_ [OPTIONS] [old-patch] <new-patch>
    


## DESCRIPTION



           Rename [old-patch] to <new-patch>. If [old-patch] is not given,
           the topmost patch will be renamed.
    


## OPTIONS



           -b <branch>, --branch=<branch>
               Use <branch> instead of current branch
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# perf-evlist

## NAME



           perf-evlist - List the event names in a perf.data file
    


## SYNOPSIS



           _perf evlist <options>_
    


## DESCRIPTION



           This command displays the names of events sampled in a perf.data
           file.
    


## OPTIONS



           -i, --input=
               Input file name. (default: perf.data unless stdin is a fifo)
    
           -f, --force
               Don’t complain, do it.
    
           -F, --freq=
               Show just the sample frequency used for each event.
    
           -v, --verbose
               Show all fields.
    
           -g, --group
               Show event group information.
    
           --trace-fields
               Show tracepoint field names.
    


* * *
# git-write-tree

## NAME



           git-write-tree - Create a tree object from the current index
    


## SYNOPSIS



           **git write-tree**[**--missing-ok**] [**--prefix=**_< prefix>_**/**]
    


## DESCRIPTION



           Creates a tree object using the current index. The name of the new
           tree object is printed to standard output.
    
           The index must be in a fully merged state.
    
           Conceptually, **git write-tree** sync()s the current index contents
           into a set of tree files. In order to have that match what is
           actually in your directory right now, you need to have done a **git**
           **update-index** phase before you did the **git write-tree**.
    


## OPTIONS



           **--missing-ok**
               Normally **git write-tree** ensures that the objects referenced by
               the directory exist in the object database. This option
               disables this check.
    
           **--prefix=**_< prefix>_**/**
               Writes a tree object that represents a subdirectory _< prefix>_.
               This can be used to write the tree object for a subproject
               that is in the named subdirectory.
    


## GIT



           Part of the git(1) suite
    


* * *
# gendiff

## NAME



           gendiff - utility to aid in error-free diff file generation
    


## SYNOPSIS



           **gendiff** <directory> <diff-extension>
    


## DESCRIPTION



           **gendiff** is a rather simple script which aids in generating a diff
           file from a single directory.  It takes a directory name and a
           "diff-extension" as its only arguments.  The diff extension should
           be a unique sequence of characters added to the end of all
           original, unmodified files.  The output of the program is a diff
           file which may be applied with the **patch** program to recreate the
           changes.
    
           The usual sequence of events for creating a diff is to create two
           identical directories, make changes in one directory, and then use
           the **diff** utility to create a list of differences between the two.
           Using gendiff eliminates the need for the extra, original and
           unmodified directory copy.  Instead, only the individual files
           that are modified need to be saved.
    
           Before editing a file, copy the file, appending the extension you
           have chosen to the filename.  I.e.  if you were going to edit
           somefile.cpp and have chosen the extension "fix", copy it to
           somefile.cpp.fix before editing it.  Then edit the first copy
           (somefile.cpp).
    
           After editing all the files you need to edit in this fashion,
           enter the directory one level above where your source code
           resides, and then type
    
                      $ gendiff somedirectory .fix > mydiff-fix.patch
    
           You should redirect the output to a file (as illustrated) unless
           you want to see the results on stdout.
    


* * *
# pmlock

## NAME



           **pmlock** - simple file-based mutex
    


## SYNOPSIS



           **$PCP_BINADM_DIR/pmlock**[**-i** _ident_] [**-v**] _file_
    


## DESCRIPTION



           **pmlock** attempts to acquire an exclusive lock by creating a zero-
           sized _file_ with a mode of 0.
    
           The _-i_ option changes the behaviour to write _ident_ into _file_ ,
           followed by a newline and the file mode is 0444.  _ident_ is an
           arbitrary string, but by convention it is the process id of the
           locker followed by the name or identification of the locker
           command or script.
    
           The exit status is 0 for success, 1 for failure.
    
           To release the lock, remove _file_ with rm(1) or unlink(2).
    
           In the event of a failure, the **-v** option produces an explanatory
           message on _stderr_.
    


* * *
# newuidmap

## NAME



           newuidmap - set the uid mapping of a user namespace
    


## SYNOPSIS



    
           **newuidmap** _pid uid loweruid count_ [_uid loweruid count_ [ _..._ ]]
    


## DESCRIPTION



           The **newuidmap** sets /proc/[pid]/uid_map based on its command line
           arguments and the uids allowed. Subuid delegation can either be
           managed via /etc/subuid or through the configured NSS subid
           module. These options are mutually exclusive.
    
           Note that the root user is not exempted from the requirement for a
           valid /etc/subuid entry.
    
           After the pid argument, **newuidmap** expects sets of 3 integers:
    
           uid
               Beginning of the range of UIDs inside the user namespace.
    
           loweruid
               Beginning of the range of UIDs outside the user namespace.
    
           count
               Length of the ranges (both inside and outside the user
               namespace).
    
           **newuidmap** verifies that the caller is the owner of the process
           indicated by **pid** and that for each of the above sets, each of the
           UIDs in the range [loweruid, loweruid+count) is allowed to the
           caller according to /etc/subuid before setting
           /proc/[pid]/uid_map.
    
           Note that newuidmap may be used only once for a given process.
    
           Instead of an integer process id, the first argument may be
           specified as _fd:N_ , where the integer N is the file descriptor
           number for the calling process's opened file descriptor for the
           directory /proc/[pid]. In this case, **newuidmap** will use openat(2)
           to open the uid_map file under that directory, avoiding a TOCTTOU
           in case the process exits and the pid is immediately reused.
    


## OPTIONS



           There currently are no options to the **newuidmap** command.
    


## FILES



           /etc/subuid
               List of user's subordinate user IDs.
    
           /proc/[pid]/uid_map
               Mapping of uids from one between user namespaces.
    


* * *