tripathysagar/man_text huggingface dataset:
# flatpak-permission-set

## NAME



           flatpak-permission-set - Set permissions
    


## SYNOPSIS



    
           **flatpak permission-set**[OPTION...] TABLE ID APP_ID [PERMISSION...]
    


## DESCRIPTION



           Set the permissions for an application in an entry in the
           permission store. The entry is identified by TABLE and ID, the
           application is identified by APP_ID. The PERMISSION strings must
           be in a format suitable for the table.
    
           The permission store is used by portals. Each portal generally has
           its own table in the permission store, and the format of the table
           entries is specific to each portal.
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **--data=DATA**
               Associate DATA with the entry. The data must be a serialized
               GVariant.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


## EXAMPLES



           **$ flatpak permission-set --data "{'always-ask': <true>}"**
           **desktop-used-apps text/plain org.mozilla.Firefox org.gnome.gedit 0**
           **3**
    


* * *
# sortman

## NAME



           sortman - sort manual-page path names
    


## SYNOPSIS



           **sortman**
    


## DESCRIPTION



           The **sortman** command sorts manual-page path names in the order that
           they should appear in the manual.
    
           The chapters and subchapters are first sorted.  Then, within each
           (sub)chapter, the first page is the corresponding **intro**(*) page,
           and the rest are sorted alphabetically (but treating specially
           some special characters).
    


* * *
# udaddy

## NAME



           udaddy - RDMA CM datagram setup and simple ping-pong test.
    


## SYNOPSIS



           _udaddy_ [-s server_address] [-b bind_address] [-c connections]
                     [-C message_count] [-S message_size] [-p port_space]
           _udaddy_ -s server_address [-b bind_address] [-c connections]
                     [-C message_count] [-S message_size] [-t tos] [-p port_space]
    


## DESCRIPTION



           Establishes a set of unreliable RDMA datagram communication paths
           between two nodes using the librdmacm, optionally transfers
           datagrams between the nodes, then tears down the communication.
    


## OPTIONS



           -s server_address
                  The network name or IP address of the server system
                  listening for communication.  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.  To bind to any
                  address with IPv6 use -b ::0 .
    
           -c connections
                  The number of communication paths to establish between the
                  client and server.  The test uses unreliable datagram
                  communication, so no actual connections are formed.
                  (default 1)
    
           -C message_count
                  The number of messages to transfer over each connection.
                  (default 10)
    
           -S message_size
                  The size of each message transferred, in bytes.  This value
                  must be smaller than the MTU of the underlying RDMA
                  transport, or an error will occur.  (default 100)
    
           -t tos Indicates the type of service used for the communication.
                  Type of service is implementation dependent based on subnet
                  configuration.
    
           -p port_space
                  The port space of the datagram communication.  May be
                  either the RDMA UDP (0x0111) or IPoIB (0x0002) port space.
                  (default RDMA_PS_UDP)
    


## NOTES



           Basic usage is to start udaddy on a server system, then run udaddy
           -s server_name on a client system.
    
           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.
    


* * *
# memusagestat

## NAME



           memusagestat - generate graphic from memory profiling data
    


## SYNOPSIS



           **memusagestat**[_option_ ...] _datafile_ [_outfile_]
    


## DESCRIPTION



           **memusagestat** creates a PNG file containing a graphical
           representation of the memory profiling data in the file _datafile_ ;
           that file is generated via the _-d_ (or _--data_) option of
           memusage(1).
    
           The red line in the graph shows the heap usage (allocated memory)
           and the green line shows the stack usage.  The x-scale is either
           the number of memory-handling function calls or (if the _-t_ option
           is specified) time.
    


## OPTIONS



           **-o** _file_
           **--output=**_file_
                  Name of the output file.
    
           **-s** _string_
           **--string=**_string_
                  Use _string_ as the title inside the output graph.
    
           **-t**
           **--time** Use time (rather than number of function calls) as the
                  scale for the X axis.
    
           **-T**
           **--total**
                  Also draw a graph of total memory consumption.
    
           **-x** _size_
           **--x-size=**_size_
                  Make the output graph _size_ pixels wide.
    
           **-y** _size_
           **--y-size=**_size_
                  Make the output graph _size_ pixels high.
    
           **-?**
           **--help** Print a help message and exit.
    
           **--usage**
                  Print a short usage message and exit.
    
           **-V**
           **--version**
                  Print version information and exit.
    


## BUGS



           To report bugs, see ⟨http://www.gnu.org/software/libc/bugs.html⟩
    


## EXAMPLES



           See memusage(1).
    


* * *
# stap-prep

## NAME



           stap-prep - prepare system for systemtap use
    


## SYNOPSIS



           **stap-prep**[ _KERNEL_VERSION_ ]
    


## DESCRIPTION



           The stap-prep executable prepares the system for systemtap use by
           installing kernel headers, debug symbols and build tools that
           match the currently running kernel or optionally the kernel
           version given by the user.
    
           If the debuginfod-find tool is installed and is able to fetch
           debuginfo for a kernel component, it is assumed to remain
           available later.  In this case, no debug symbols will be
           downloaded during stap-prep.
    
           The exact behavior of stap-prep may be customized by the
           distribution maintainers. It might for example only give
           suggestions and not actually install the required packages if that
           is difficult to automate.
    


## EXAMPLES



                  $ stap-prep
                  Please install linux-image-3.2.0-2-amd64-dbg
    


## BUGS



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


* * *
# gdb-add-index

## NAME



           gdb-add-index - Add index files to speed up GDB
    


## SYNOPSIS



           gdb-add-index [-dwarf-5] _filename_
    


## DESCRIPTION



           When GDB finds a symbol file, it scans the symbols in the file in
           order to construct an internal symbol table.  This lets most GDB
           operations work quickly--at the cost of a delay early on.  For
           large programs, this delay can be quite lengthy, so GDB provides a
           way to build an index, which speeds up startup.
    
           To determine whether a file contains such an index, use the
           command "readelf -S filename": the index is stored in a section
           named ".gdb_index" (pre-DWARF 5) or ".debug_names" and
           ".debug_str" (DWARF 5).  Indexes can only be produced on systems
           which use ELF binaries and DWARF debug information (i.e., sections
           named ".debug_*").
    
           By default **gdb-add-index** will add a pre-DWARF 5 ".gdb_index"
           section to _filename_.  With **-dwarf-5** DWARF 5 sections are added
           instead.
    
           _filename_ must be writable.
    
           **gdb-add-index** uses GDB, **objcopy** , and **readelf** found in the **PATH**
           environment variable.  If you want to use different versions of
           these programs, you can specify them through the appropriate
           environment variables (see below).
    
           **gdb-add-index** exits with status 0 if it succeeds in creating the
           index for _filename_ or greater than 0 if an error occurs.
    
           See more in the GDB manual in node "Index Files" -- shell command
           "info -f gdb -n "Index Files"".
    


## OPTIONS



           **-dwarf-5**
               Add DWARF 5 sections instead of previous ".debug_index"
               section.
    


## ENVIRONMENT



           **GDB** Full file name of the "gdb" program to use for index
               generation.  If not set, the **PATH** will be searched for a "gdb"
               program.
    
           **OBJCOPY**
               Full file name of the "objcopy" program to use to copy section
               information into the given file.  If not set, the **PATH** will be
               searched for a "objcopy" program.
    
           **READELF**
               Full file name of the "readelf" program to use to inspect
               properties of the given file.  If not set, the **PATH** will be
               searched for a "readelf" program.
    


* * *
# usb-devices

## NAME



           usb-devices - print USB device details
    


## SYNOPSIS



           **usb-devices**
    


## DESCRIPTION



           **usb-devices** is a shell script that can be used to display details
           of USB buses in the system and the devices connected to them.
    
           The output of the script is similar to the _usb/devices_ file
           available either under _/proc/bus_ (if usbfs is mounted), or under
           _/sys/kernel/debug_ (if debugfs is mounted there). The script is
           primarily intended to be used if the file is not available.
    
           In contrast to the _usb/devices_ file, this script only lists _active_
           interfaces (those marked with a "*" in the _usb/devices_ file) and
           their endpoints.
    
           Be advised that there can be differences in the way information is
           sorted, as well as in the format of the output.
    


## RETURN VALUE



           If sysfs is not mounted, a non-zero exit code is returned.
    


## FILES



           **/sys/bus/usb/devices/usb***
                  The part of the sysfs tree the script walks through to
                  assemble the printed information.
    
           **/proc/bus/usb/devices**
                  Location where the _usb/devices_ file can normally be found
                  for Linux kernels before 2.6.31, if usbfs is mounted.
    
           **/sys/kernel/debug/usb/devices**
                  Location where the _usb/devices_ file can normally be found
                  for Linux kernel 2.6.31 and later, if debugfs is mounted.
    


* * *
# mknod

## NAME



           mknod - make block or character special files
    


## SYNOPSIS



           **mknod**[_OPTION_]... _NAME TYPE_ [_MAJOR MINOR_]
    


## DESCRIPTION



           Create the special file NAME of the given TYPE.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-m** , **--mode** =_MODE_
                  set file permission bits to MODE, not a=rw - umask
    
           **-Z** set the SELinux security context to default type
    
           **--context**[=_CTX_]
                  like **-Z** , or if CTX is specified then set the SELinux or
                  SMACK security context to CTX
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Both MAJOR and MINOR must be specified when TYPE is b, c, or u,
           and they must be omitted when TYPE is p.  If MAJOR or MINOR begins
           with 0x or 0X, it is interpreted as hexadecimal; otherwise, if it
           begins with 0, as octal; otherwise, as decimal.  TYPE may be:
    
           b      create a block (buffered) special file
    
           c, u   create a character (unbuffered) special file
    
           p      create a FIFO
    
           Your shell may have its own version of mknod, which usually
           supersedes the version described here.  Please refer to your
           shell's documentation for details about the options it supports.
    


* * *
# pmdamic

## NAME



           **pmdamic** - MIC card PMDA
    


## DESCRIPTION



           **pmdamic** is a Performance Metrics Domain Agent (PMDA) which exports
           metric values about Intel MIC cards using the **libmicmgmt**(7) python
           bindings.
    
           This provides information on core, memory and power utilization
    


## INSTALLATION



           Install the MIC PMDA by using the Install script as root:
    
                # cd $PCP_PMDAS_DIR/mic
                # ./Install
    
           If you want to undo the installation, do the following as root:
    
                # cd $PCP_PMDAS_DIR/mic
                # ./Remove
    
           **pmdamic** 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/mic/Install**
               installation script for the **pmdamic** agent
    
           **$PCP_PMDAS_DIR/mic/Remove**
               undo installation script for the **pmdamic** agent
    
           **$PCP_LOG_DIR/pmcd/mic.log**
               default log file for error messages from **pmdamic**
    


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


* * *
# realpath

## NAME



           realpath - print the resolved path
    


## SYNOPSIS



           **realpath**[_OPTION_]... _FILE_...
    


## DESCRIPTION



           Print the resolved absolute file name; all but the last component
           must exist
    
           **-e** , **--canonicalize-existing**
                  all components of the path must exist
    
           **-m** , **--canonicalize-missing**
                  no path components need exist or be a directory
    
           **-L** , **--logical**
                  resolve '..' components before symlinks
    
           **-P** , **--physical**
                  resolve symlinks as encountered (default)
    
           **-q** , **--quiet**
                  suppress most error messages
    
           **--relative-to** =_DIR_
                  print the resolved path relative to DIR
    
           **--relative-base** =_DIR_
                  print absolute paths unless paths below DIR
    
           **-s** , **--strip** , **--no-symlinks**
                  don't expand symlinks
    
           **-z** , **--zero**
                  end each output line with NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# stg-diff

## NAME



           stg-diff - Show a diff
    


## SYNOPSIS



           _stg diff_ [OPTIONS] [path]...
    


## DESCRIPTION



           Show the diff (default) or diffstat between the current working
           copy or a tree-ish object and another tree-ish object (defaulting
           to HEAD). File names can also be given to restrict the diff
           output. The tree-ish object has the format accepted by the
           stg-id(1) command.
    


## OPTIONS



           -r <revspec>, --range=<revspec>
               Show diff between specified revisions. Revisions ranges are
               specified as _rev1[..[rev2]]_. The revisions may be standard Git
               revision specifiers or patches.
    
           -s, --stat
               Show the stat instead of the diff
    
           -O <option>, --diff-opt=<option>
               Pass additional <option> to **git diff**.
    
               See the git-diff(1) man page. This option may be specified
               multiple times.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# expiry

## NAME



           expiry - check and enforce password expiration policy
    


## SYNOPSIS



    
           **expiry** _option_
    


## DESCRIPTION



           The **expiry** command checks (**-c**) the current password expiration and
           forces (**-f**) changes when required. It is callable as a normal user
           command.
    


## OPTIONS



           The options which apply to the **expiry** command are:
    
           **-c** , **--check**
               Check the password expiration of the current user.
    
           **-f** , **--force**
               Force a password change if the current user has an expired
               password.
    
           **-h** , **--help**
               Display help message and exit.
    


## FILES



           /etc/passwd
               User account information.
    
           /etc/shadow
               Secure user account information.
    


* * *
# stg-files

## NAME



           stg-files - Show files modified by a patch
    


## SYNOPSIS



           _stg files_ [OPTIONS] [revision]
    


## DESCRIPTION



           Show the files modified by a patch. The files of the topmost patch
           are shown by default. Passing the _--stat_ option shows the diff
           statistics for the given patch. Note that this command does not
           show the files modified in the working tree and not yet included
           in the patch by a _refresh_ command. Use the _diff_ or _status_ commands
           to show these files.
    


## OPTIONS



           -s, --stat
               Show patch’s diffstat
    
           --bare
               Print bare file names. This is useful for scripting.
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# dh_installxfonts

## NAME



           dh_installxfonts - register X fonts
    


## SYNOPSIS



           **dh_installxfonts**[_debhelper options_]
    


## DESCRIPTION



           **dh_installxfonts** is a debhelper program that is responsible for
           registering X fonts, so their corresponding _fonts.dir_ ,
           _fonts.alias_ , and _fonts.scale_ be rebuilt properly at install time.
    
           Before calling this program, you should have installed any X fonts
           provided by your package into the appropriate location in the
           package build directory, and if you have _fonts.alias_ or
           _fonts.scale_ files, you should install them into the correct
           location under _etc/X11/fonts_ in your package build directory.
    
           Your package should depend on **xfonts-utils** so that the
           **update-fonts-**_*_ commands are available. (This program adds that
           dependency to **${misc:Depends}**.)
    
           This program automatically generates the _postinst_ and _postrm_
           commands needed to register X fonts. These commands are inserted
           into the maintainer scripts by **dh_installdeb**. See dh_installdeb(1)
           for an explanation of how this works.
    


## NOTES



           See **update-fonts-alias**(8), **update-fonts-scale**(8), and
           **update-fonts-dir**(8) for more information about X font
           installation.
    
           See Debian policy, section 11.8.5. for details about doing fonts
           the Debian way.
    


* * *
# pmdarocestat

## NAME



           **pmdarocestat** - Performance Metrics Domain Agent (PMDA) for RoCE
           devices
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/rocestat/pmdarocestat**
    


## DESCRIPTION



           The **Rocestat PMDA**(Performance Metrics Domain Agent) is a
           Performance Co-Pilot (PCP) module that collects and exports
           performance statistics for RDMA over Converged Ethernet (RoCE)
           devices. It provides insights into network performance, error
           conditions, and congestion events, aiding in the diagnosis and
           monitoring of RoCE-based communication.
    
           This PMDA reports software-aggregated InfiniBand port statistics,
           including received/transmitted bytes and packets, link errors, and
           congestion-related drops, helping to identify potential
           bottlenecks and failures.  Additionally, it includes hardware-
           level counters, which track low-level transmission metrics,
           duplicate requests, NAKs, and physical/constraint errors, offering
           a deeper view into the underlying transport reliability and
           efficiency.
    
           Furthermore, Rocestat PMDA collects priority-based lane metrics
           from ethtool -S <interface>, filtering statistics related to
           priority lanes in RoCE traffic. These metrics provide visibility
           into traffic distribution across lanes, helping diagnose
           congestion hotspots and optimize workload balancing across
           different lanes
    
           By integrating Rocestat PMDA into a PCP monitoring environment,
           users can efficiently analyze RoCE network behavior, detect
           performance anomalies, and optimize high-speed RDMA workloads in
           data center and HPC environments.
    


## INSTALLATION



           To install the Rocestat PMDA, follow these steps:
                  # cd $PCP_PMDAS_DIR/rocestat
                  # ./Install
    
           To verify that the PMDA is running:
                  $ pminfo -t rocestat
    


## USAGE



           To query Rocestat metrics, use the following command:
                  $ pminfo rocestat
           To retrieve specific metric values:
                  $ pmval rocestat.hw.rcv.port_rcv_packets
    


## FILES



           _$PCP_PMDAS_DIR/rocestat/Install_
                  Installation script for Rocestat PMDA.
    
           _$PCP_PMDAS_DIR/rocestat/Remove_
                  Uninstallation script.
    
           _$PCP_LOG_DIR/pmcd/rocestat.log_
                  Log file for Rocestat PMDA events and errors.
    


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


* * *
# true

## NAME



           true - do nothing, successfully
    


## SYNOPSIS



           **true**[_ignored command line arguments_]
           **true** _OPTION_
    


## DESCRIPTION



           Exit with a status code indicating success.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Your shell may have its own version of true, which usually
           supersedes the version described here.  Please refer to your
           shell's documentation for details about the options it supports.
    


* * *
# ncurses6-config

## NAME



           ncurses6-config - helper script for ncurses libraries
    


## SYNOPSIS



           **ncurses6-config**[_options_]
    


## DESCRIPTION



           This is a shell script which simplifies configuring applications
           against a particular set of ncurses libraries.
    


## OPTIONS



           **--prefix**
                  echos the package-prefix of ncurses
    
           **--exec-prefix**
                  echos the executable-prefix of ncurses
    
           **--cflags**
                  echos the C compiler flags needed to compile with ncurses
    
           **--libs** echos the libraries needed to link with ncurses
    
           **--version**
                  echos the release+patchdate version of ncurses
    
           **--abi-version**
                  echos the ABI version of ncurses
    
           **--mouse-version**
                  echos the mouse-interface version of ncurses
    
           **--bindir**
                  echos the directory containing ncurses programs
    
           **--datadir**
                  echos the directory containing ncurses data
    
           **--includedir**
                  echos the directory containing ncurses header files
    
           **--libdir**
                  echos the directory containing ncurses libraries
    
           **--mandir**
                  echos the directory containing ncurses manpages
    
           **--terminfo**
                  echos the $TERMINFO terminfo database path, e.g.,
                  /usr/share/terminfo
    
           **--terminfo-dirs**
                  echos the $TERMINFO_DIRS directory list, e.g.,
                  /usr/share/terminfo
    
           **--termpath**
                  echos the $TERMPATH termcap list, if support for termcap is
                  configured.
    
           **--help** prints this message
    


* * *
# git-backfill

## NAME



           git-backfill - Download missing objects in a partial clone
    


## SYNOPSIS



           **git backfill**[**--min-batch-size=**_< n>_] [**--**[**no-**]**sparse**]
    


## DESCRIPTION



           Blobless partial clones are created using **git clone**
           **--filter=blob:none** and then configure the local repository such
           that the Git client avoids downloading blob objects unless they
           are required for a local operation. This initially means that the
           clone and later fetches download reachable commits and trees but
           no blobs. Later operations that change the **HEAD** pointer, such as
           **git checkout** or **git merge** , may need to download missing blobs in
           order to complete their operation.
    
           In the worst cases, commands that compute blob diffs, such as **git**
           **blame** , become very slow as they download the missing blobs in
           single-blob requests to satisfy the missing object as the Git
           command needs it. This leads to multiple download requests and no
           ability for the Git server to provide delta compression across
           those objects.
    
           The **git backfill** command provides a way for the user to request
           that Git downloads the missing blobs (with optional filters) such
           that the missing blobs representing historical versions of files
           can be downloaded in batches. The **backfill** command attempts to
           optimize the request by grouping blobs that appear at the same
           path, hopefully leading to good delta compression in the packfile
           sent by the server.
    
           In this way, **git backfill** provides a mechanism to break a large
           clone into smaller chunks. Starting with a blobless partial clone
           with **git clone --filter=blob:none** and then running **git backfill** in
           the local repository provides a way to download all reachable
           objects in several smaller network calls than downloading the
           entire repository at clone time.
    
           By default, **git backfill** downloads all blobs reachable from the
           **HEAD** commit. This set can be restricted or expanded using various
           options.
    
           THIS COMMAND IS EXPERIMENTAL. ITS BEHAVIOR MAY CHANGE IN THE
           FUTURE.
    


## OPTIONS



           **--min-batch-size=**_< n>_
               Specify a minimum size for a batch of missing objects to
               request from the server. This size may be exceeded by the last
               set of blobs seen at a given path. The default minimum batch
               size is 50,000.
    
           **--**[**no-**]**sparse**
               Only download objects if they appear at a path that matches
               the current sparse-checkout. If the sparse-checkout feature is
               enabled, then **--sparse** is assumed and can be disabled with
               **--no-sparse**.
    


## GIT



           Part of the git(1) suite
    


* * *
# stg-pull

## NAME



           stg-pull - Pull changes from a remote repository
    


## SYNOPSIS



           _stg pull_ [OPTIONS] [repository]
    


## DESCRIPTION



           Pull the latest changes from a remote repository.
    
           The remote repository may be specified on the command line, but
           defaults to branch.<name>.remote from the git configuration, or
           "origin" if not configured.
    
           This command works by popping all currently applied patches from
           the stack, pulling the changes from the remote repository,
           updating the stack base to the new remote HEAD, and finally
           pushing all formerly applied patches back onto the stack. Merge
           conflicts may occur during the final push step. Those conflicts
           need to be resolved manually.
    
           See git-fetch(1) for the format of remote repository argument.
    


## OPTIONS



           -n, --nopush
               Do not push back patches after pulling
    
           -m, --merged
               Check for patches that may have been merged upstream.
    
               When pushing-back patches, each patch is checked to see if its
               changes already exist in the just-pulled upstream changes. If
               a patch’s changes have already been merged upstream, the patch
               will still exist in the stack, but become empty after the pull
               operation.
    
           --conflicts[=<policy>]
               Either "allow" or "disallow" pushing a patch with conflicts.
    
               Using **--conflicts=allow**(or just **--conflicts**) allows pushing a
               patch that may result in unresolved merge conflicts. The patch
               will be pushed and files with conflicts will be left with
               conflict markers to be resolved manually; or the operation
               undone with **stg undo --hard**. This is the default behavior and
               also corresponds to the "stgit.push.allow-conflicts" variable
               being set to "true".
    
               Using **--conflicts=disallow** disallows pushing any patch that
               would result in merge conflicts. The operation will stop on
               the last patch that can be pushed without conflicts. This
               behavior can be configured by setting
               "stgit.push.allow-conflicts" to "false".
    


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# guards

## NAME



           guards - select from a list of files guarded by conditions
    


## SYNOPSIS



           _guards_ [--prefix=_dir_] [--path=_dir1:dir2:..._] [--default=<0|1>]
           [--check|--list] [--invert-match] [--with-guards]
           [--config=<file>] _symbol_ ...
    


## DESCRIPTION



           The script reads a configuration file that may contain so-called
           guards, file names, and comments, and writes those file names that
           satisfy all guards to standard output. The script takes a list of
           symbols as its arguments. Each line in the configuration file is
           processed separately. Lines may start with a number of guards. The
           following guards are defined:
    
               +_xxx_ Include the file(s) on this line if the symbol _xxx_ is
               defined.
    
               -_xxx_ Exclude the file(s) on this line if the symbol _xxx_ is
               defined.
    
               +!_xxx_ Include the file(s) on this line if the symbol _xxx_ is
               not defined.
    
               -!_xxx_ Exclude the file(s) on this line if the symbol _xxx_ is
               not defined.
    
               - Exclude this file. Used to avoid spurious _--check_ messages.
    
           The guards are processed left to right. The last guard that
           matches determines if the file is included. If no guard is
           specified, the _--default_ setting determines if the file is
           included.
    
           If no configuration file is specified, the script reads from
           standard input.
    
           The _--check_ option is used to compare the specification file
           against the file system. If files are referenced in the
           specification that do not exist, or if files are not enlisted in
           the specification file warnings are printed. The _--path_ option can
           be used to specify which directory or directories to scan.
           Multiple directories are separated by a colon (":") character. The
           _--prefix_ option specifies the location of the files.
           Alternatively, the _--path=@ <file>_ syntax can be used to specify a
           file from which the file names will be read.
    
           Use _--list_ to list all files independent of any rules. Use
           _--invert-match_ to list only the excluded patches. Use
           _--with-guards_ to also include all inclusion and exclusion rules.
    


* * *
# genbrk

## NAME



           **genbrk** - Compiles ICU break iteration rules source files into
           binary data files
    


## SYNOPSIS



           **genbrk**[ **-h** , **-?** , **--help**] [ **-V** , **--version**] [ **-c** , **--copyright**] [
           **-v** , **--verbose**] [ **-d** , **--destdir** _destination_ ] [ **-i** , **--icudatadir**
           _directory_ ] **-r** , **--rules** _rule-file_ **-o** , **--out** _output-file_
    


## DESCRIPTION



           **genbrk** reads the break (boundary) rule source code from _rule-file_
           and creates a break iteration data file. Normally this data file
           has the **.brk** extension.
    
           The details of the rule syntax can be found in ICU's User Guide.
    


## OPTIONS



           **-h** , **-?** , **--help**
                  Print help about usage and exit.
    
           **-V** , **--version**
                  Print the version of **genbrk** and exit.
    
           **-c** , **--copyright**
                  Embeds the standard ICU copyright into the _output-file_.
    
           **-v** , **--verbose**
                  Display extra informative messages during execution.
    
           **-d** , **--destdir** _destination_
                  Set the destination directory of the _output-file_ to
                  _destination_.
    
           **-i** , **--icudatadir** _directory_
                  Look for any necessary ICU data files in _directory_.  For
                  example, the file **pnames.icu** must be located when ICU's
                  data is not built as a shared library.  The default ICU
                  data directory is specified by the environment variable
                  **ICU_DATA**.  Most configurations of ICU do not require this
                  argument.
    
           **-r** , **--rules** _rule-file_
                  The source file to read.
    
           **-o** , **--out** _output-file_
                  The output data file to write.
    


## CAVEATS



           When the _rule-file_ contains a byte order mark (BOM) at the
           beginning of the file, which is the Unicode character **U+FEFF,** then
           the _rule-file_ is interpreted as Unicode. Without the BOM, the file
           is interpreted in the current operating system default codepage.
           In order to eliminate any ambiguity of the encoding for how the
           _rule-file_ was written, it is recommended that you write this file
           in UTF-8 with the BOM.
    


## ENVIRONMENT



           **ICU_DATA**
                  Specifies the directory containing ICU data. Defaults to
                  **${prefix}/share/icu/76.0.1/**.  Some tools in ICU depend on
                  the presence of the trailing slash. It is thus important to
                  make sure that it is present if **ICU_DATA** is set.
    


## VERSION



           1.0
    


* * *
# aria_ftdump

## NAME



           aria_ftdump - display full-text index information
    


## DESCRIPTION



           Use: aria_ft_dump <table_name> <index_num>
    
           **-?** , **-h** , **--help**
                  Display help and exit.
    
           **-c** , **--count**
                  Calculate per-word stats (counts and global weights).
    
           **-d** , **--dump**
                  Dump index (incl. data offsets and word weights).
    
           **-l** , **--length**
                  Report length distribution.
    
           **-s** , **--stats**
                  Report global stats.
    
           **-v** , **--verbose**
                  Be verbose.
    


* * *
# verify_blkparse

## NAME



           verify_blkparse - verifies an output file produced by blkparse
    


## SYNOPSIS



           **verify_blkparse <**_filename_ >
    


## DESCRIPTION



           Verifies an output file from blkparse. All it does is check if the
           events in the file are correctly time ordered. If an entry is
           found that isn't ordered, it's dumped to stdout.
    


* * *
# flatpak-enter

## NAME



           flatpak-enter - Enter an application or runtime's sandbox
    


## SYNOPSIS



    
           **flatpak enter**[OPTION...] INSTANCE COMMAND [ARG...]
    


## DESCRIPTION



           Enter a running sandbox.
    
           INSTANCE must be either the pid of a process running in a flatpak
           sandbox, or the ID of a running application, or the instance ID of
           a running sandbox. You can use **flatpak ps** to find the instance IDs
           of running flatpaks.
    
           COMMAND is the command to run in the sandbox. Extra arguments are
           passed on to the command.
    
           This creates a new process within the running sandbox, with the
           same environment. This is useful when you want to debug a problem
           with a running application.
    
           This command works as a regular user if the system support
           unprivileged user namespace. If that is not available you need to
           run run it like: **sudo -E flatpak enter**.
    


## OPTIONS



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


## EXAMPLES



           **$ flatpak enter 15345 sh**
    


* * *
# stg-prev

## NAME



           stg-prev - Print the name of the previous patch
    


## SYNOPSIS



           _stg prev_ [OPTIONS]
    


## DESCRIPTION



           Print the name of the previous patch.
    
           The previous patch is the applied patch preceding the current,
           topmost patch. An error message will be printed if not enough
           patches are applied.
    


## OPTIONS



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


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# id

## NAME



           id - print real and effective user and group IDs
    


## SYNOPSIS



           **id**[_OPTION_]... [_USER_]...
    


## DESCRIPTION



           Print user and group information for each specified USER, or (when
           USER omitted) for the current process.
    
           **-a** ignore, for compatibility with other versions
    
           **-Z** , **--context**
                  print only the security context of the process
    
           **-g** , **--group**
                  print only the effective group ID
    
           **-G** , **--groups**
                  print all group IDs
    
           **-n** , **--name**
                  print a name instead of a number, for **-u** ,-g,-G
    
           **-r** , **--real**
                  print the real ID instead of the effective ID, with
                  **-u** ,-g,-G
    
           **-u** , **--user**
                  print only the effective user ID
    
           **-z** , **--zero**
                  delimit entries with NUL characters, not whitespace; not
                  permitted in default format
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Without any OPTION, print some useful set of identified
           information.
    


* * *
# yum-debug-restore

## NAME



           yum-debug-restore - replay Yum transactions captured in a debug-
           dump file
    


## SYNOPSIS



           **yum-debug-restore**
    


## DESCRIPTION



           **yum-debug-restore** is a program which takes a gzipped file created
           by **yum-debug-dump** and acts on the information about installed
           packages contained within.
    


## GENERAL OPTIONS



           **--output**
                  Output the commands that would be run to stdout.
    
           **--shell= <file>**
                  Output the commands that would be run to a file.
    
           **--install-latest**
                  Ask yum to install the latest version of the given
                  packages, instead of the version that was installed in the
                  debug-dump file.
    
           **--ignore-arch**
                  Ignore the architecture of the packages, so you can
                  "restore" an i386 debug-dump on an x86_64 machine.
    
           **--filter-types=[install,remove,update,downgrade]**
                  Only perform the given types of commands, so you can filter
                  to just upgrades and installs.
    


## FILES



           As yum-debug-restore uses YUM libraries for retrieving all the
           information, it relies on YUM configuration for its default values
           like which repositories to use. Consult YUM documentation for
           details:
    
           /etc/yum.conf
           /etc/yum/repos.d/
           /var/cache/yum/
    


## BUGS



           There are of course no bugs, but should you find any, you should
           first consult the FAQ section on http://yum.baseurl.org/wiki/Faq
           and if unsuccessful in finding a resolution contact the mailing
           list: yum-devel@lists.baseurl.org.  To file a bug use
           http://bugzilla.redhat.com for Fedora/RHEL/Centos related bugs and
           http://yum.baseurl.org/report for all other bugs.
    


* * *
# git-patch-id

## NAME



           git-patch-id - Compute unique ID for a patch
    


## SYNOPSIS



           _git patch-id_ [--stable | --unstable | --verbatim]
    


## DESCRIPTION



           Read a patch from the standard input and compute the patch ID for
           it.
    
           A "patch ID" is nothing but a sum of SHA-1 of the file diffs
           associated with a patch, with line numbers ignored. As such, it’s
           "reasonably stable", but at the same time also reasonably unique,
           i.e., two patches that have the same "patch ID" are almost
           guaranteed to be the same thing.
    
           The main usecase for this command is to look for likely duplicate
           commits.
    
           When dealing with _git diff-tree_ output, it takes advantage of the
           fact that the patch is prefixed with the object name of the
           commit, and outputs two 40-byte hexadecimal strings. The first
           string is the patch ID, and the second string is the commit ID.
           This can be used to make a mapping from patch ID to commit ID.
    


## OPTIONS



           --verbatim
               Calculate the patch-id of the input as it is given, do not
               strip any whitespace.
    
                   This is the default if patchid.verbatim is true.
    
           --stable
               Use a "stable" sum of hashes as the patch ID. With this
               option:
    
               •   Reordering file diffs that make up a patch does not affect
                   the ID. In particular, two patches produced by comparing
                   the same two trees with two different settings for
                   "-O<orderfile>" result in the same patch ID signature,
                   thereby allowing the computed result to be used as a key
                   to index some meta-information about the change between
                   the two trees;
    
               •   Result is different from the value produced by git 1.9 and
                   older or produced when an "unstable" hash (see --unstable
                   below) is configured - even when used on a diff output
                   taken without any use of "-O<orderfile>", thereby making
                   existing databases storing such "unstable" or historical
                   patch-ids unusable.
    
               •   All whitespace within the patch is ignored and does not
                   affect the id.
    
                       This is the default if patchid.stable is set to true.
    
           --unstable
               Use an "unstable" hash as the patch ID. With this option, the
               result produced is compatible with the patch-id value produced
               by git 1.9 and older and whitespace is ignored. Users with
               pre-existing databases storing patch-ids produced by git 1.9
               and older (who do not deal with reordered patches) may want to
               use this option.
    
                   This is the default.
    


## GIT



           Part of the git(1) suite
    


* * *
# pcp-ipcs

## NAME



           **pcp-ipcs** - provide information on IPC facilities
    


## SYNOPSIS



           **pcp**[_pcp options_] **ipcs**[**-luV?**] [_output-format_]
    


## DESCRIPTION



           **pcp-ipcs** provides information on the inter-process communication
           facilities for which the calling process has read access.
    


## OPTIONS



           When invoked via the pcp(1) command, the **-h** /**--host** , **-a** /**--archive** ,
           **-O** /**--origin** , **-Z** /**--timezone** and several other _pcp options_ become
           indirectly available; refer to PCPIntro(1) for a complete
           description of these options.
    
           The additional command line options available for **pcp-ipcs** are:
    
           **-V** , **--version**
                  Display version information and exit.
    
           **-?** , **--help**
                  Display the usage message and exit.
    
       **Output formats**
           **-l** , **--limits**
                  Show resource limits.
    
           **-u** , **--summary**
                  Show status summary.
    


## PCP ENVIRONMENT



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


* * *