tripathysagar/man_text huggingface dataset:
# sha1sum

## NAME



           sha1sum - compute and check SHA1 message digest
    


## SYNOPSIS



           **sha1sum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or check SHA1 (160-bit) checksums.
    
           With no FILE, or when FILE is -, read standard input.
    
           **-b** , **--binary**
                  read in binary mode
    
           **-c** , **--check**
                  read checksums from the FILEs and check them
    
           **--tag** create a BSD-style checksum
    
           **-t** , **--text**
                  read in text mode (default)
    
           **-z** , **--zero**
                  end each output line with NUL, not newline, and disable
                  file name escaping
    
       **The following five options are useful only when verifying checksums:**
           **--ignore-missing**
                  don't fail or report status for missing files
    
           **--quiet**
                  don't print OK for each successfully verified file
    
           **--status**
                  don't output anything, status code shows success
    
           **--strict**
                  exit non-zero for improperly formatted checksum lines
    
           **-w** , **--warn**
                  warn about improperly formatted checksum lines
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           The sums are computed as described in FIPS-180-1.  When checking,
           the input should be a former output of this program.  The default
           mode is to print a line with: checksum, a space, a character
           indicating input mode ('*' for binary, ' ' for text or where
           binary is insignificant), and name for each FILE.
    
           There is no difference between binary mode and text mode on GNU
           systems.
    


## BUGS



           Do not use the SHA-1 algorithm for security related purposes.
           Instead, use an SHA-2 algorithm, implemented in the programs
           sha224sum(1), sha256sum(1), sha384sum(1), sha512sum(1), or the
           BLAKE2 algorithm, implemented in b2sum(1)
    


* * *
# git-symbolic-ref

## NAME



           git-symbolic-ref - Read, modify and delete symbolic refs
    


## SYNOPSIS



           _git symbolic-ref_ [-m <reason>] <name> <ref>
           _git symbolic-ref_ [-q] [--short] [--no-recurse] <name>
           _git symbolic-ref_ --delete [-q] <name>
    


## DESCRIPTION



           Given one argument, reads which branch head the given symbolic ref
           refers to and outputs its path, relative to the **.git/** directory.
           Typically you would give **HEAD** as the <name> argument to see which
           branch your working tree is on.
    
           Given two arguments, creates or updates a symbolic ref <name> to
           point at the given branch <ref>.
    
           Given **--delete** and an additional argument, deletes the given
           symbolic ref.
    
           A symbolic ref is a regular file that stores a string that begins
           with **ref: refs/**. For example, your **.git/HEAD** is a regular file
           whose content is **ref: refs/heads/master**.
    


## OPTIONS



           -d, --delete
               Delete the symbolic ref <name>.
    
           -q, --quiet
               Do not issue an error message if the <name> is not a symbolic
               ref but a detached HEAD; instead exit with non-zero status
               silently.
    
           --short
               When showing the value of <name> as a symbolic ref, try to
               shorten the value, e.g. from **refs/heads/master** to **master**.
    
           --recurse, --no-recurse
               When showing the value of <name> as a symbolic ref, if <name>
               refers to another symbolic ref, follow such a chain of
               symbolic refs until the result no longer points at a symbolic
               ref (**--recurse** , which is the default).  **--no-recurse** stops
               after dereferencing only a single level of symbolic ref.
    
           -m
               Update the reflog for <name> with <reason>. This is valid only
               when creating or updating a symbolic ref.
    


## NOTES



           In the past, **.git/HEAD** was a symbolic link pointing at
           **refs/heads/master**. When we wanted to switch to another branch, we
           did **ln -sf refs/heads/newbranch .git/HEAD** , and when we wanted to
           find out which branch we are on, we did **readlink .git/HEAD**. But
           symbolic links are not entirely portable, so they are now
           deprecated and symbolic refs (as described above) are used by
           default.
    
           _git symbolic-ref_ will exit with status 0 if the contents of the
           symbolic ref were printed correctly, with status 1 if the
           requested name is not a symbolic ref, or 128 if another error
           occurs.
    


## GIT



           Part of the git(1) suite
    


* * *
# ibv_ud_pingpong

## NAME



           ibv_ud_pingpong - simple InfiniBand UD transport test
    


## SYNOPSIS



           **ibv_ud_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-r
           rx depth] [-n iters] [-l sl] [-e] [-g gid index] **HOSTNAME**
    
           **ibv_ud_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-r
           rx depth] [-n iters] [-l sl] [-e] [-g gid index]
    


## DESCRIPTION



           Run a simple ping-pong test over InfiniBand via the unreliable
           datagram (UD) 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 2048)
    
           **-r** , **--rx-depth** =_DEPTH_
                  post _DEPTH_ receives at a time (default 500)
    
           **-n** , **--iters** =_ITERS_
                  perform _ITERS_ message exchanges (default 1000)
    
           **-l** , **--sl** =_SL_
                  send messages with service level _SL_ (default 0)
    
           **-e** , **--events**
                  sleep while waiting for work completion events (default is
                  to poll for completions)
    
           **-g** , **--gid-idx** =_GIDINDEX_
                  local port _GIDINDEX_
    
           **-c** , **--chk**
                  validate received buffer
    


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


* * *
# ibv_srq_pingpong

## NAME



           ibv_srq_pingpong - simple InfiniBand shared receive queue test
    


## SYNOPSIS



           **ibv_srq_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid
           index] **HOSTNAME**
    
           **ibv_srq_pingpong**[-p port] [-d device] [-i ib port] [-s size] [-m
           size] [-q num QPs] [-r rx depth] [-n iters] [-l sl] [-e] [-g gid
           index]
    


## DESCRIPTION



           Run a simple ping-pong test over InfiniBand via the reliable
           connected (RC) transport, using multiple queue pairs (QPs) and a
           single shared receive queue (SRQ).
    


## 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)
    
           **-q** , **--num-qp** =_NUM_
                  use _NUM_ queue pairs for test (default 16)
    
           **-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 QPs (default 0)
    
           **-e** , **--events**
                  sleep while waiting for work completion events (default is
                  to poll for completions)
    
           **-g** , **--gid-idx** =_GIDINDEX_
                  local port _GIDINDEX_
    
           **-c** , **--chk**
                  validate received buffer
    


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


* * *
# yum-torrent

## NAME



           yum-torrent - download packages via http and peer-to-peer
    


## DESCRIPTION



           **yum-torrent** extends the behaviour of yum by downloading then
           seeding packages via BitTorrent.  Once installed and configured,
           the plugin works transparently.
    


## FILES



           **yum-torrent** makes extensive use of cache files. The BitTorrent
           client's cwd is set to the root of the cache by default.  All
           generated .torrent files are guaranteed to contain files in
           subdirectories.  Once a torrent download is complete the files are
           hard or soft linked to the path in **/var/cache/yum** where yum will
           look before starting it's own downloads, bypassing it.
    
           **yum-torrent** will automatically clean up unused files and
           directories left over from previous runs.
    
                  /var/cache/yum_torrent/_torrenthash_.torrent
                  /var/cache/yum_torrent/_torrenthash_.torrent.log
                  /var/cache/yum_torrent/_path/to/package_.rpm
                  /var/cache/yum/_repo_ /packages/_package_.rpm
    


* * *
# dh_installdirs

## NAME



           dh_installdirs - create subdirectories in package build
           directories
    


## SYNOPSIS



           **dh_installdirs**[_debhelper options_] [**-A**] [**--sourcedir=**_dir_]
           [**--create-in-sourcedir**] [_dir_ ...]
    


## DESCRIPTION



           **dh_installdirs** is a debhelper program that is responsible for
           creating subdirectories in package build directories.
    
           Many packages can get away with omitting the call to
           **dh_installdirs** completely.  Notably, other **dh_*** commands are
           expected to create directories as needed.
    


## FILES



           debian/_package_.dirs
               Lists directories to be created in _package_.
    
               Generally, there is no need to list directories created by the
               upstream build system or directories needed by other **debhelper**
               commands.
    
               Supports substitution variables in compat 13 and later as
               documented in debhelper(7).
    


## OPTIONS



           **-A** , **--all**
               Create any directories specified by command line parameters in
               ALL packages acted on, not just the first.
    
           **--create-in-sourcedir** , **--no-create-in-sourcedir**
               Whether to create the specified directories in the source
               directory (usually _debian/tmp_) _in addition to_ in the package
               build directory (usually _debian/package_).
    
               The default is **--no-create-in-sourcedir**.
    
           **--sourcedir=**_dir_
               Consider _dir_ the source directory for the packages acted on
               instead of the default (which is usually _debian/tmp_).
    
               Please note that this option is dependent on the
               **--create-in-sourcedir** option (when **--no-create-in-sourcedir** is
               in effect, this option does nothing in **dh_installdirs**).
    
           _dir_ ...
               Create these directories in the package build directory of the
               first package acted on. (Or in all packages if **-A** is
               specified.)
    


* * *
# pmdalmsensors

## NAME



           **pmdalmsensors** - Linux hardware monitoring performance metrics
           domain agent (PMDA)
    


## SYNOPSIS



           **$PCP_PMDAS_DIR/lmsensors/pmdalmsensors**[**debug**]
    


## DESCRIPTION



           **pmdalmsensors** is a Performance Metrics Domain Agent (PMDA) which
           extracts performance metrics describing the state of hardware
           using the lm-sensors software on compatible motherboards.
    
           The **lmsensors** PMDA exports metrics that measure fan speeds and
           core temperatures.
    


## INSTALLATION



           If you want access to the names, help text and values for the
           lmsensors performance metrics, do the following as root:
    
                # cd $PCP_PMDAS_DIR/lmsensors
                # ./Install
    
           If you want to undo the installation, do the following as root:
    
                # cd $PCP_PMDAS_DIR/lmsensors
                # ./Remove
    
           pmdalmsensors.python is usually launched by pmcd (1), and not
           executed directly. Direct execution is mostly used for debugging
           purposes.
    
           The Install and Remove scripts notify pmcd (1) when the agent is
           installed or removed.
    


## OPTIONS



           pmdalmsensors.python supports the following options.
    
           **-i** , **--inject**
                  inject data from file instead of using sensors
    
           **-d** , **--debug**
                  debug level: 0 (default), 1 or 2
    
           **-h** , **--help**
                  show a help message
    
                  To use options while pmdalmsensors.python is run from PMCD,
                  you might want to use 'args' in the 'Install' stript, for
                  example
    
                  args="-i /path/static_sensors_output.txt"
    


## FILES



           **$PCP_PMCDCONF_PATH**
                  command line options used to launch **pmdalmsensors**
           **$PCP_PMDAS_DIR/lmsensors/help**
                  default help text file for the lmsensors metrics
           **$PCP_PMDAS_DIR/lmsensors/Install**
                  installation script for the **pmdalmsensors** agent
           **$PCP_PMDAS_DIR/lmsensors/Remove**
                  undo installation script for the **pmdalmsensors** agent
    


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


* * *
# unsetfiles

## NAME



           unsetfiles - Remove SELinux file security contexts.
    


## SYNOPSIS



           **unsetfiles**[**-hnrvx**] _pathname_ ...
    


## DESCRIPTION



           This program removes the SELinux file security contexts of files.
           It can help cleaning extended file attributes after disabling
           SELinux.
    
           **unsetfiles** will only work on SELinux disabled systems, since
           removing file security contexts is not supported by SELinux.
    


## OPTIONS



           **-h** Show usage information and exit.
    
           **-n** Do not actually remove any SELinux file security contexts.
    
           **-r** Remove SELinux file security contexts recursive.
    
           **-v** Be verbose about performed actions.
    
           **-x** Do not cross filesystem boundaries.
    


## ARGUMENTS



           _pathname_ ...
                  One or more path names to operate on.
    


* * *
# ppdhtml

## NAME



           ppdhtml - cups html summary generator (deprecated)
    


## SYNOPSIS



           **ppdhtml**[ **-D** _name_[**=**_value_] ] [ **-I** _include-directory_ ] _source-file_
    


## DESCRIPTION



           **ppdhtml** reads a driver information file and produces a HTML
           summary page that lists all of the drivers in a file and the
           supported options.  **This program is deprecated and will be removed**
           **in a future release of CUPS.**
    


## OPTIONS



           **ppdhtml** supports the following options:
    
           **-D** _name_[**=**_value_]
                Sets the named variable for use in the source file.  It is
                equivalent to using the _#define_ directive in the source file.
    
           **-I** _include-directory_
                Specifies an alternate include directory.  Multiple _-I_
                options can be supplied to add additional directories.
    


## NOTES



           PPD files are deprecated and will no longer be supported in a
           future feature release of CUPS.  Printers that do not support IPP
           can be supported using applications such as ippeveprinter(1).
    


* * *
# flatpak-search

## NAME



           flatpak-search - Search for applications and runtimes
    


## SYNOPSIS



    
           **flatpak search** TEXT
    


## DESCRIPTION



           Searches for applications and runtimes matching TEXT. Note that
           this uses appstream data that can be updated with the **flatpak**
           **update** command. The appstream data is updated automatically only
           if it's at least a day old.
    


## OPTIONS



           The following options are understood:
    
           **-u** , **--user**
               Only search through remotes in the per-user installation.
    
           **--system**
               Only search through remotes in the default system-wide
               installation.
    
           **--installation=NAME**
               Show a system-wide installation by NAME among those defined in
               /etc/flatpak/installations.d/. Using **--installation=default** is
               equivalent to using **--system**.
    
           **-h** , **--help**
               Show help options and exit.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    
           **--columns=FIELD,...**
               Specify what information to show about each result. You can
               list multiple fields, or use this option multiple times.
    
               Append :s[tart], :m[iddle], :e[nd] or :f[ull] to column names
               to change ellipsization.
    


## FIELDS



           The following fields are understood by the **--columns** option:
    
           name
               Show the name
    
           description
               Show the description
    
           application
               Show the application ID
    
           version
               Show the version
    
           branch
               Show the branch
    
           remotes
               Show the remotes
    
           all
               Show all columns
    
           help
               Show the list of available columns
    
           Note that field names can be abbreviated to a unique prefix.
    


* * *
# pcp-slabinfo

## NAME



           **pcp-slabinfo** - Report statistics for kernel slab allocator
    


## SYNOPSIS



           **pcp**[_pcp options_] **slabinfo**[**-a** _archive_] [**-s** _samples_] [**-Z** _timezone_]
    


## DESCRIPTION



           The **pcp-slabinfo** command is used for viewing different stats
           related to slab.  It helps users analyze useful information
           related to the slab allocator.  The information includes the total
           number of objects that are currently active, allocated objects,
           pages per slab, etc.  By default, **pcp-slabinfo** reports live data
           for the local host.
    
           The statistics shown are as follows:
           **HEADER         DESCRIPTION**
           ───────────────────────────────────────────────────────────────────
           active_objs    The number of objects that are currently active
                          (i.e., in use)
           num_objs       The total number of allocated objects (i.e. objects
                          that are both in use and not in use).
           objsize        The size of objects in this slab, in bytes.
           objperslab     The number of objects stored in each slab.
           pagesperslab   The number of pages allocated for each slab
           active_slabs   The number of active slabs.
           num_slabs      The total number of slabs.
    


## OPTIONS



           **-a** _file_ , **--archive** =_file_
                  Fetch /proc/slabinfo for a specified archive _file_
    
           **-s** _count_ , **--samples** =_count_
                  Get the slabinfo statistics for specified number of samples
                  _count_
    
           **-V** , **--version**
                  Display version number and exit.
    
           **-z** , **--hostzone**
                  Use the local timezone of the host that is the source of
                  the performance metrics, as identified by either the **-h** or
                  the **-a** options.  The default is to use the timezone of the
                  local host.
    
           **-Z** _timezone_ , **--timezone** =_timezone_
                  Use _timezone_ for the date and time.  _Timezone_ is in the
                  format of the environment variable **TZ** as described in
                  environ(7).
    
           **-?** , **--help**
                  Display usage message and exit.
    


## NOTES



           **pcp-slabinfo** collects information from _/proc/slabinfo_.
    


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


* * *
# op-check-perfevents

## NAME



           op-check-perfevents - checks for kernel perf pmu support
    


## SYNOPSIS



           **op-check-perfevents**[ _options_ ]
    


## DESCRIPTION



           The small helper program **op-check-perfevents** determines whether
           the kernel supports the perf interface and returns a zero exit
           status if the perf pmu support is available.
    


## OPTIONS



           **--help / -h**
                  Show usage help message.
    
           **--verbose / -v**
                  Print string describing the error number of perf_event_open
                  syscall
    


## ENVIRONMENT



           No special environment variables are recognised by op-check-
           perfevents.
    


## VERSION



           This man page is current for oprofile-1.5.0git.
    


* * *
# uptime

## NAME



           uptime - Tell how long the system has been running.
    


## SYNOPSIS



           **uptime**[_option_ ...]
    


## DESCRIPTION



           **uptime** gives a one line display of the following information.  The
           current time, how long the system has been running, how many users
           are currently logged on, and the system load averages for the past
           1, 5, and 15 minutes.
    
           This is the same information contained in the header line
           displayed by w(1).
    
           System load averages is the average number of processes that are
           either in a runnable or uninterruptable state.  A process in a
           runnable state is either using the CPU or waiting to use the CPU.
           A process in uninterruptable state is waiting for some I/O access,
           eg waiting for disk.  The averages are taken over the three time
           intervals.  Load averages are not normalized for the number of
           CPUs in a system, so a load average of 1 means a single CPU system
           is loaded all the time while on a 4 CPU system it means it was
           idle 75% of the time.
    


## OPTIONS



           **-c** , **--container**
                  show the container uptime instead of system uptime.
    
           **-p** , **--pretty**
                  show uptime in pretty format
    
           **-h** , **--help**
                  display this help text
    
           **-r** , **--raw**
                  Display values in a raw format. Current time and uptime are
                  displayed in seconds.
    
           **-s** , **--since**
                  system up since, in yyyy-mm-dd HH:MM:SS format
    
           **-V** , **--version**
                  display version information and exit
    


## ENVIRONMENT



           **PROCPS_CONTAINER**
                  If $**PROCPS_CONTAINER** is set, then **uptime** behaves as if the
                  **--container** option has been given.
    


## FILES



           _/var/run/utmp_
                  information about who is currently logged on
    
           _/proc_  process information
    


* * *
# gstack

## NAME



           gstack - Print a stack trace of a running program
    


## SYNOPSIS



           gstack [-h | --help] [-v | --version] _pid_
    


## DESCRIPTION



           Print a stack trace of a running program with process ID _pid_.  If
           the process is multi-threaded, **gstack** outputs backtraces for every
           thread which exists in the process.
    
           The script invokes GDB, attaches to the given process ID, prints
           the stack trace, and detaches from the process.
    
           **gstack** exits with non-zero status if "gdb" was unable to attach to
           the given process ID for any reason, such as a non-existent
           process ID or insufficient privileges to attach to the process.
    


## OPTIONS



           **--help**
           **-h** List all options, with brief explanations.
    
           **--version**
           **-v** Print version information and then exit.
    


## ENVIRONMENT



           **AWK** Full file name for an Awk interpreter to use.  If not set,
               **PATH** will be searched for an "awk" program.
    
           **GDB** Full file name for a GDB executable to use to generate stack
               backtraces.  If not set, **PATH** will be searched for a "gdb"
               program.
    
           **GDBARGS**
               Optional arguments to be passed to the "gdb" program.
    


* * *
# peekfd

## NAME



           peekfd - peek at file descriptors of running processes
    


## SYNOPSIS



           **peekfd**[**-8** ,**--eight-bit-clean**] [**-n** ,**--no-headers**] [**-c** ,**--follow**]
           [**-d** ,**--duplicates-removed**] [**-V** ,**--version**] [**-h** ,**--help**] _pid_ [_fd_] [_fd_]
           ...
    


## DESCRIPTION



           **peekfd** attaches to a running process and intercepts all reads and
           writes to file descriptors.  You can specify the desired file
           descriptor numbers or dump all of them.
    


## OPTIONS



           -8     Do no post-processing on the bytes being read or written.
    
           -n     Do not display headers indicating the source of the bytes
                  dumped.
    
           -c     Also dump the requested file descriptor activity in any new
                  child processes that are created.
    
           -d     Remove duplicate read/writes from the output.  If you're
                  looking at a tty with echo, you might want this.
    
           -v     Display a version string.
    
           -h     Display a help message.
    


## FILES



           **/proc/**_*_ **/fd**
                  Not used but useful for the user to look at to get good
                  file descriptor numbers.
    


## ENVIRONMENT



           None.
    


## DIAGNOSTICS



           The following diagnostics may be issued on stderr:
    
           **Error attaching to pid** _< PID>_
                  An unknown error occurred while attempted to attach to a
                  process, you may need to be root.
    


## BUGS



           Probably lots.  Don't be surprised if the process you are
           monitoring dies.
    


* * *
# fuse2fs

## NAME



           fuse2fs - FUSE file system client for ext2/ext3/ext4 file systems
    


## SYNOPSIS



           **fuse2fs**[ **device/image**] [ **mountpoint**] [ _options_ ]
    


## DESCRIPTION



           **fuse2fs** is a FUSE file system client that supports reading and
           writing from devices or image files containing ext2, ext3, and
           ext4 file systems.
    


## OPTIONS



       **general options:**
           **-o** opt,[opt...]
                  mount options
    
           **-h   --help**
                  print help
    
           **-V   --version**
                  print version
    
       **fuse2fs options:**
           **-o** ro  read-only mount
    
           **-o** errors=panic
                  dump core on error
    
           **-o** minixdf
                  minix-style df
    
           **-o** fakeroot
                  pretend to be root for permission checks
    
           **-o** no_default_opts
                  do not include default fuse options
    
           **-o** norecovery
                  do not replay the journal and mount the file system read-
                  only
    
           **-o** fuse2fs_debug
                  enable fuse2fs debugging
    
           **-o** kernel
                  Behave more like the kernel ext4 driver in the following
                  ways: Allows processes owned by other users to access the
                  filesystem.  Uses the kernel's permissions checking logic
                  instead of fuse2fs's.  Enables setuid and device files.
                  Note that these options can still be overridden (e.g.
                  _nosuid_ ) later.
    
           **-o** direct
                  Use O_DIRECT to access the block device.
    
           **-o** cache_size
                  Set the disk cache size to this quantity.  The quantity may
                  contain the suffixes k, m, or g.  By default, the size is
                  32MB.  The size may not be larger than 2GB.
    
       **FUSE options:**
           **-d -o** debug
                  enable debug output (implies -f)
    
           **-f** foreground operation
    
           **-s** disable multi-threaded operation
    
           For other FUSE options please see **mount.fuse**(8) or see the output
           of _fuse2fs --helpfull_
    


## AVAILABILITY



           **fuse2fs** is part of the e2fsprogs package and is available from
           http://e2fsprogs.sourceforge.net.
    


* * *
# callgrind_annotate

## NAME



           callgrind_annotate - post-processing tool for the Callgrind
    


## SYNOPSIS



    
           **callgrind_annotate**[_options_]
                              [_callgrind-out-file_ [_source-files_...]]
    


## DESCRIPTION



           **callgrind_annotate** takes an output file produced by the Valgrind
           tool Callgrind and prints the information in an easy-to-read form.
    


## OPTIONS



           **-h --help**
               Show summary of options.
    
           **--version**
               Show version of callgrind_annotate.
    
           **--show=A,B,C [default: all]**
               Only show figures for events A,B,C.
    
           **--threshold= <0--100> [default: 99%]**
               Percentage of counts (of primary sort event) we are interested
               in.
    
               callgrind_annotate stops printing functions when the sum of
               the cost percentage of the printed functions is bigger or
               equal to the given threshold percentage.
    
           **--sort=A,B,C**
               Sort columns by events A,B,C [event column order].
    
               Optionally, each event is followed by a : and a threshold, to
               specify different thresholds depending on the event.
    
               callgrind_annotate stops printing functions when the sum of
               the cost percentage of the printed functions for all the
               events is bigger or equal to the given event threshold
               percentages.
    
               When one or more thresholds are given via this option, the
               value of **--threshold** is ignored.
    
           **--show-percs= <no|yes> [default: no]**
               When enabled, a percentage is printed next to all event
               counts. This helps gauge the relative importance of each
               function and line.
    
           **--auto= <yes|no> [default: yes]**
               Annotate all source files containing functions that helped
               reach the event count threshold.
    
           **--context=N [default: 8]**
               Print N lines of context before and after annotated lines.
    
           **--inclusive= <yes|no> [default: no]**
               Add subroutine costs to functions calls.
    
           **--tree= <none|caller|calling|both> [default: none]**
               Print for each function their callers, the called functions or
               both.
    
           **-I, --include= <dir>**
               Add **dir** to the list of directories to search for source files.
    


* * *
# getcifsacl

## NAME



           getcifsacl - Userspace helper to display an ACL in a security
           descriptor for Common Internet File System (CIFS)
    


## SYNOPSIS



              getcifsacl [-v|-r] {file system object}
    


## DESCRIPTION



           This tool is part of the cifs-utils suite.
    
           **getcifsacl** is a userspace helper program for the Linux CIFS client
           file system. It is intended to display a security descriptor,
           including DACL and SACL for a file system object.
    
           This program uses a plugin to handle the mapping of SIDs to user
           and group names. _/etc/cifs-utils/idmap-plugin_ should be a symlink
           that points to the correct plugin to use.
    
           Fields of an ACE such as SID, type, flags, and mask are displayed
           separated by /. Numeric values of type, flags, and mask are
           displayed in hexadecimal format.
    


## OPTIONS



           **-v** Print version number and exit.
    
           **-r** Display a security descriptor in raw mode. Values such as
                  type and flags are displayed in hexadecimal format, a SID
                  is not mapped to a name.
    
           **-R** List the ACLs of all files and directories recursively.
    


## NOTES



           Kernel support for getcifsacl/setcifsacl utilities was initially
           introduced in the 2.6.37 kernel.
    


* * *
# find-repos-of-install

## NAME



           find-repos-of-install - report which Yum repository a package was
           installed from
    


## SYNOPSIS



           **find-repos-of-install**[options] package1 [package2...]
    


## DESCRIPTION



           **find-repos-of-install** is a program which reports the Yum
           repository that a specified package was installed from.
    


## OPTIONS



           **--version**
                  Report program version and exit.
    
           **-h, --help**
                  Display a help message, and then quit.
    
           **--repoid=REPOID**
                  Specify repo ids to query, can be specified multiple times
                  (default is all enabled).
    
           **--enablerepo=ENABLEREPOS**
                  In addition to the default set, query the given additional
                  repository, even if it is disabled in YUM configuration.
                  Can be used multiple times.
    
           **--disablerepo=DISABLEREPOS**
                  Do not query the given repository, even if it is enabled in
                  YUM configuration.  Can be used multiple times.
    
           **--repofrompath=REPOID,PATH/URL**
                  Specify a path or url to a repository (same path as in a
                  baseurl) to add to the repositories for this query. This
                  option can be used multiple times. If you want to view only
                  the pkgs from this repository combine this with --repoid.
                  The repoid for the repository is specified by REPOID.
    
           **-C, --cache**
                  Tells repoquery to run entirely from YUM cache - does not
                  download any metadata or update the cache. Queries in this
                  mode can fail or give partial/incorrect results if the
                  cache isn't fully populated beforehand with eg "yum
                  makecache".
    
           **--tempcache**
                  Use a temp dir for storing/accessing yum-cache.
    
           **--sync2yumdb**
                  Sync anything that is found to the yumdb, if available.
    


* * *
# logname

## NAME



           logname - print user´s login name
    


## SYNOPSIS



           **logname**[_OPTION_]
    


## DESCRIPTION



           Print the user's login name.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# shuf

## NAME



           shuf - generate random permutations
    


## SYNOPSIS



           **shuf**[_OPTION_]... [_FILE_]
           **shuf** _-e_ [_OPTION_]... [_ARG_]...
           **shuf** _-i LO-HI_ [_OPTION_]...
    


## DESCRIPTION



           Write a random permutation of the input lines to standard output.
    
           With no FILE, or when FILE is -, read standard input.
    
           Mandatory arguments to long options are mandatory for short
           options too.
    
           **-e** , **--echo**
                  treat each ARG as an input line
    
           **-i** , **--input-range** =_LO-HI_
                  treat each number LO through HI as an input line
    
           **-n** , **--head-count** =_COUNT_
                  output at most COUNT lines
    
           **-o** , **--output** =_FILE_
                  write result to FILE instead of standard output
    
           **--random-source** =_FILE_
                  get random bytes from FILE
    
           **-r** , **--repeat**
                  output lines can be repeated
    
           **-z** , **--zero-terminated**
                  line delimiter is NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# git-whatchanged

## NAME



           git-whatchanged - Show logs with differences each commit
           introduces
    


## SYNOPSIS



           **git whatchanged** _< option>_...
    


## WARNING



           **git whatchanged** has been deprecated and is scheduled for removal
           in a future version of Git, as it is merely **git log** with different
           default; **whatchanged** is not even shorter to type than **log --raw**.
    


## DESCRIPTION



           Shows commit logs and diff output each commit introduces.
    
           New users are encouraged to use git-log(1) instead. The
           **whatchanged** command is essentially the same as git-log(1) but
           defaults to showing the raw format diff output and skipping
           merges.
    
           The command is primarily kept for historical reasons; fingers of
           many people who learned Git long before **git log** was invented by
           reading the Linux kernel mailing list are trained to type it.
    


## EXAMPLES



           **git whatchanged -p v2.6.12.. include/scsi drivers/scsi**
               Show as patches the commits since version _v2.6.12_ that changed
               any file in the include/scsi or drivers/scsi subdirectories
    
           **git whatchanged --since=** "2 **weeks ago** " **-- gitk**
               Show the changes during the last two weeks to the file _gitk_.
               The "--" is necessary to avoid confusion with the **branch** named
               _gitk_
    


## GIT



           Part of the git(1) suite
    


* * *
# pmdagluster

## NAME



           **pmdagluster** - Gluster Filesystem PMDA
    


## DESCRIPTION



           **pmdagluster** is a Performance Metrics Domain Agent (PMDA) which
           exports metric values about mounted gluster filesystems using the
           **gluster**(8) command.  This PMDA exports metrics about volumes and
           bricks both local and remote to the node where pmdagluster is
           running.
    
           The gluster filesystem supports fine-grained control over enabling
           statistics on individual volumes, so that the values are
           optionally enabled or disabled on systems where they are not
           desired to be monitored.
    
           The pmstore(1) command can be used to enable and disable profiling
           of volumes.  Using the individual instances of the
           gluster.volume.profile metric, one can set their values (and
           associated profiling) either on (1) or off (0).  Additionally,
           pminfo(1) can report on the current status of profiling of each
           volume.
    
                # pminfo ‐f gluster.volume.profile
    
                gluster.volume.profile
                    inst [0 or "gv0"] value 0
                    inst [1 or "gv1"] value 1
    
                # pmstore ‐i "gv0" gluster.volume.profile 1
                gluster.volume.profile inst [0 or "gv0"] old value=0 new value=1
    
           Further details on the gluster filesystem can be found at
           **http://www.gluster.org **.
    


## INSTALLATION



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


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


* * *
# flatpak-config

## NAME



           flatpak-config - Manage configuration
    


## SYNOPSIS



    
           **flatpak config**[OPTION...]
    
           **flatpak config**[OPTION...] --set KEY VALUE
    
           **flatpak config**[OPTION...] --unset|--get KEY
    


## DESCRIPTION



           The flatpak config command shows or modifies the configuration of
           a flatpak installation. The following keys are supported:
    
           _languages_
               The languages that are included when installing Locale
               extensions. The value is a semicolon-separated list of
               two-letter language codes, or one of the special values * or
               *all*. If this key is unset, flatpak defaults to including the
               _extra-languages_ key and the current locale.
    
           _extra-languages_
               This key is used when languages is not set, and it defines
               extra locale extensions on top of the system configured
               languages. The value is a semicolon-separated list of locale
               identifiers (language, optional locale, optional codeset,
               optional modifier) as documented by setlocale(3) (for example,
               en;en_DK;zh_HK.big5hkscs;uz_UZ.utf8@cyrillic).
    
           For configuration of individual remotes, see
           flatpak-remote-modify(1). For configuration of individual
           applications, see flatpak-override(1).
    


## OPTIONS



           The following options are understood:
    
           **-h** , **--help**
               Show help options and exit.
    
           **--list**
               Print all keys and their values.
    
           **--set**
               Set key KEY to VALUE.
    
           **--unset**
               Unset key KEY.
    
           **--get**
               Print value of KEY.
    
           **-u** , **--user**
               Configure per-user installation.
    
           **--system**
               Configure system-wide installation.
    
           **--installation=NAME**
               Configure the system-wide installation specified by NAME among
               those defined in /etc/flatpak/installations.d/. Using
               **--installation=default** is equivalent to using **--system**.
    
           **-v** , **--verbose**
               Print debug information during command processing.
    
           **--ostree-verbose**
               Print OSTree debug information during command processing.
    


## EXAMPLES



           **$ flatpak config --set languages "sv;en;fi"**
    


* * *