tripathysagar/man_text huggingface dataset:
# collectl2pcp

## NAME



           **collectl2pcp** - import collectl data to a PCP archive
    


## SYNOPSIS



           **collectl2pcp**[**-fv?**]  [**-D** _debug_] _file_ [_file_ ...]  _archive_
    


## DESCRIPTION



           **collectl2pcp** reads raw **collectl**(1) data from each _file_ and creates
           a new PCP archive with basename _archive_.  Each input _file_ may be
           gzipped (with **.gz** suffix).  The PCP _archive_ and at least one input
           _file_ are required arguments.
    


## OPTIONS



           The available command line options are:
    
           **-f** , **--force**
                Overwrite _archive_ (and the index and meta files) if it
                already exists.
    
           **-v** , **--verbose**
                Report progress and errors verbosely.  This also reports a
                count of unsupported metric data in the **collectl**(1) input
                file(s), which is normally silently skipped.
    
           **-?** , **--help**
                Display usage message and exit.
    
           _file_ [_file_ ...]
                These are the **collectl**(1) input files.  If more than one is
                given, they must contain data for the same host and be given
                in time-stamp chronological order on the command line.  Note
                that when **collectl**(1) is run as a service, it normally
                creates files with date based names that will sort
                chronologically (e.g. **/var/log/collectl/*.gz** will be sorted
                correctly).
    


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


## DEBUGGING OPTIONS



           The **-D** or **--debug** option enables the output of additional
           diagnostics on _stderr_ to help triage problems, although the
           information is sometimes cryptic and primarily intended to provide
           guidance for developers rather end-users.  _debug_ is a comma
           separated list of debugging options; use pmdbg(1) with the **-l**
           option to obtain a list of the available debugging options and
           their meaning.
    


* * *
# git-mv

## NAME



           git-mv - Move or rename a file, a directory, or a symlink
    


## SYNOPSIS



           **git mv**[**-v**] [**-f**] [**-n**] [**-k**] _< source> <destination>_
           **git mv**[**-v**] [**-f**] [**-n**] [**-k**] _< source>_**...**_< destination-directory>_
    


## DESCRIPTION



           Move or rename a file, directory, or symlink.
    
           In the first form, it renames _< source>_, which must exist and be
           either a file, symlink or directory, to _< destination>_. In the
           second form, _< destination-directory>_ has to be an existing
           directory; the given sources will be moved into this directory.
    
           The index is updated after successful completion, but the change
           must still be committed.
    


## OPTIONS



           **-f** , **--force**
               Force renaming or moving of a file even if the <destination>
               exists.
    
           **-k**
               Skip move or rename actions which would lead to an error
               condition. An error happens when a source is neither existing
               nor controlled by Git, or when it would overwrite an existing
               file unless **-f** is given.
    
           **-n** , **--dry-run**
               Do nothing; only show what would happen
    
           **-v** , **--verbose**
               Report the names of files as they are moved.
    


## SUBMODULES



           Moving a submodule using a gitfile (which means they were cloned
           with a Git version 1.7.8 or newer) will update the gitfile and
           core.worktree setting to make the submodule work in the new
           location. It also will attempt to update the **submodule.**_< name>_**.path**
           setting in the gitmodules(5) file and stage that file (unless **-n**
           is used).
    


## BUGS



           Each time a superproject update moves a populated submodule (e.g.
           when switching between commits before and after the move) a stale
           submodule checkout will remain in the old location and an empty
           directory will appear in the new location. To populate the
           submodule again in the new location the user will have to run "git
           submodule update" afterwards. Removing the old directory is only
           safe when it uses a gitfile, as otherwise the history of the
           submodule will be deleted too. Both steps will be obsolete when
           recursive submodule update has been implemented.
    


## GIT



           Part of the git(1) suite
    


* * *
# whoami

## NAME



           whoami - print effective user name
    


## SYNOPSIS



           **whoami**[_OPTION_]...
    


## DESCRIPTION



           Print the user name associated with the current effective user ID.
           Same as id **-un**.
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# ppdc

## NAME



           ppdc - cups ppd compiler (deprecated)
    


## SYNOPSIS



           **ppdc**[ **-D** _name_[**=**_value_] ] [ **-I** _include-directory_ ] [ **-c** _message-_
           _catalog_ ] [ **-d** _output-directory_ ] [ **-l** _language(s)_ ] [ **-m**] [ **-t**]
           [ **-v**] [ **-z**] [ **--cr**] [ **--crlf**] [ **--lf**] _source-file_
    


## DESCRIPTION



           **ppdc** compiles PPDC source files into one or more PPD files.  **This**
           **program is deprecated and will be removed in a future release of**
           **CUPS.**
    


## OPTIONS



           **ppdc** 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.
    
           **-c** _message-catalog_
                Specifies a single message catalog file in GNU gettext
                (filename.po) or Apple strings (filename.strings) format to
                be used for localization.
    
           **-d** _output-directory_
                Specifies the output directory for PPD files.  The default
                output directory is "ppd".
    
           **-l** _language(s)_
                Specifies one or more languages to use when localizing the
                PPD file(s).  The default language is "en" (English).
                Separate multiple languages with commas, for example
                "de_DE,en_UK,es_ES,es_MX,es_US,fr_CA,fr_FR,it_IT" will create
                PPD files with German, UK English, Spanish (Spain, Mexico,
                and US), French (France and Canada), and Italian languages in
                each file.
    
           **-m** Specifies that the output filename should be based on the
                ModelName value instead of FileName or PCFileName.
    
           **-t** Specifies that PPD files should be tested instead of
                generated.
    
           **-v** Specifies verbose output, basically a running status of which
                files are being loaded or written.  **-z** Generates compressed
                PPD files (filename.ppd.gz).  The default is to generate
                uncompressed PPD files.
    
           **--cr**
    
           **--crlf**
    
           **--lf** Specifies the line ending to use - carriage return, carriage
                return and line feed, or line feed alone.  The default is to
                use the line feed character alone.
    


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


* * *
# join

## NAME



           join - join lines of two files on a common field
    


## SYNOPSIS



           **join**[_OPTION_]... _FILE1 FILE2_
    


## DESCRIPTION



           For each pair of input lines with identical join fields, write a
           line to standard output.  The default join field is the first,
           delimited by blanks.
    
           When FILE1 or FILE2 (not both) is -, read standard input.
    
           **-a** FILENUM
                  also print unpairable lines from file FILENUM, where
                  FILENUM is 1 or 2, corresponding to FILE1 or FILE2
    
           **-e** STRING
                  replace missing (empty) input fields with STRING; I.e.,
                  missing fields specified with '-12jo' options
    
           **-i** , **--ignore-case**
                  ignore differences in case when comparing fields
    
           **-j** FIELD
                  equivalent to '-1 FIELD **-2** FIELD'
    
           **-o** FORMAT
                  obey FORMAT while constructing output line
    
           **-t** CHAR
                  use CHAR as input and output field separator
    
           **-v** FILENUM
                  like **-a** FILENUM, but suppress joined output lines
    
           **-1** FIELD
                  join on this FIELD of file 1
    
           **-2** FIELD
                  join on this FIELD of file 2
    
           **--check-order**
                  check that the input is correctly sorted, even if all input
                  lines are pairable
    
           **--nocheck-order**
                  do not check that the input is correctly sorted
    
           **--header**
                  treat the first line in each file as field headers, print
                  them without trying to pair them
    
           **-z** , **--zero-terminated**
                  line delimiter is NUL, not newline
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    
           Unless **-t** CHAR is given, leading blanks separate fields and are
           ignored, else fields are separated by CHAR.  Any FIELD is a field
           number counted from 1.  FORMAT is one or more comma or blank
           separated specifications, each being 'FILENUM.FIELD' or '0'.
           Default FORMAT outputs the join field, the remaining fields from
           FILE1, the remaining fields from FILE2, all separated by CHAR.  If
           FORMAT is the keyword 'auto', then the first line of each file
           determines the number of fields output for each line.
    
           Important: FILE1 and FILE2 must be sorted on the join fields.
           E.g., use "sort **-k** 1b,1" if 'join' has no options, or use "join **-t**
           ''" if 'sort' has no options.  Comparisons honor the rules
           specified by 'LC_COLLATE'.  If the input is not sorted and some
           lines cannot be joined, a warning message will be given.
    


* * *
# udpong

## NAME



           udpong - unreliable datagram streaming over RDMA ping-pong test.
    


## SYNOPSIS



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


## DESCRIPTION



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


## OPTIONS



           -s server_address
                  The network name or IP address of the server system
                  listening for connections.  The used name or address must
                  route over an RDMA device.  This option must be specified
                  by the client.
    
           -b bind_address
                  The local network address to bind to.
    
           -B buffer_size
                  Indicates the size of the send and receive network buffers.
    
           -C transfer_count
                  The number of messages to transfer from the client to the
                  server and back again on each iteration.  (default 1000)
    
           -S transfer_size
                  The size of each send transfer, in bytes.  (default 1000)
    
           -p server_port
                  The server's port number.
    
           -T test_option
                  Specifies test parameters.  Available options are:
    
           s | socket  - uses standard socket calls to transfer data
    
           a | async - uses asynchronous operation (e.g. select / poll)
    
           b | blocking - uses blocking calls
    
           n | nonblocking - uses non-blocking calls
    
           e | echo - server echoes all messages
    


## NOTES



           Basic usage is to start udpong on a server system, then run udpong
           -s server_name on a client system.  udpong will run a series of
           latency and bandwidth performance tests.  Specifying a different
           transfer_count or transfer_size will run a user customized test
           using default values where none have been specified.
    
           Because this test maps RDMA resources to userspace, users must
           ensure that they have available system resources and permissions.
           See the libibverbs README file for additional details.
    


* * *
# git-get-tar-commit-id

## NAME



           git-get-tar-commit-id - Extract commit ID from an archive created
           using git-archive
    


## SYNOPSIS



           _git get-tar-commit-id_
    


## DESCRIPTION



           Read a tar archive created by _git archive_ from the standard input
           and extract the commit ID stored in it. It reads only the first
           1024 bytes of input, thus its runtime is not influenced by the
           size of the tar archive very much.
    
           If no commit ID is found, _git get-tar-commit-id_ quietly exits with
           a return code of 1. This can happen if the archive had not been
           created using _git archive_ or if the first parameter of _git archive_
           had been a tree ID instead of a commit ID or tag.
    


## GIT



           Part of the git(1) suite
    


* * *
# rev

## NAME



           rev - reverse lines characterwise
    


## SYNOPSIS



           **rev**[option] [_file_...]
    


## DESCRIPTION



           The **rev** utility copies the specified files to standard output,
           reversing the order of characters in every line. If no files are
           specified, standard input is read.
    
           This utility is a line-oriented tool and it uses in-memory
           allocated buffer for a whole wide-char line. If the input file is
           huge and without line breaks then allocating the memory for the
           file may be unsuccessful.
    


## OPTIONS



           **-0** , **--zero**
               _Zero termination_. Use the byte '\0' as line separator.
    
           **-h** , **--help**
               Display help text and exit.
    
           **-V** , **--version**
               Display version and exit.
    


## AVAILABILITY



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


* * *
# yum-verify

## NAME



           yum verify plugin
    


## SYNOPSIS



           **yum**[options] verify [package ...]
    


## DESCRIPTION



           This plugin extends **yum** with some commands that give verification
           information on the installed system, much like rpm -V. You can
           change how the verification is done and which files it applies to.
           In case any mismatches are found, the exit status is set to 1.
    
           added yum _command_ s are:
            * verify
            * verify-rpm
            * verify-all
    
           all of which take the same arguments as the list yum command. You
           can only verify packages that are installed on the system.
    
           **verify** Is the generic verification command, and is intended to
                  give the most useful output. It removes all false matches
                  due to multilib and ignores changes to configuration files
                  by default.
    
           **verify-rpm**
                  Does the same checks as rpm -V.
    
           **verify-all**
                  Is used to list all the differences, including some that
                  rpm itself will ignore.
    


## GENERAL OPTIONS



           These are the options added to yum that are available in the
           verify commands.  They are:
    
           **--verify-filenames**
                  This option is used to limit the filenames that the
                  packages will perform verification.
    
           **--verify-configuration-files**
                  This option is only useful in the generic verify command,
                  and will enable/disable verification of files that are
                  tagged as configuration files.
    


## EXAMPLES



           To do the same as rpm -Va, use:
    
                  yum verify-rpm
    
           To verify the packages starting with the name yum, use:
    
                  yum verify 'yum*'
    
           To verify the binaries that are in a bin directory, use:
    
                  yum verify --verify-filenames='*bin/*'
    
           To verify all include files, Eg. for multilib problems, use:
    
                  yum verify-all --verify-filenames='/usr/include/*'
    


## BUGS



           Currently yum-verify does not do verify-script checking or dependency checking,
           only file checking.
    
           Should you find any other bugs, 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-hash-object

## NAME



           git-hash-object - Compute object ID and optionally create an
           object from a file
    


## SYNOPSIS



           _git hash-object_ [-t <type>] [-w] [--path=<file> | --no-filters]
                           [--stdin [--literally]] [--] <file>...
           _git hash-object_ [-t <type>] [-w] --stdin-paths [--no-filters]
    


## DESCRIPTION



           Computes the object ID value for an object with specified type
           with the contents of the named file (which can be outside of the
           work tree), and optionally writes the resulting object into the
           object database. Reports its object ID to its standard output.
           When <type> is not specified, it defaults to "blob".
    


## OPTIONS



           -t <type>
               Specify the type of object to be created (default: "blob").
               Possible values are **commit** , **tree** , **blob** , and **tag**.
    
           -w
               Actually write the object into the object database.
    
           --stdin
               Read the object from standard input instead of from a file.
    
           --stdin-paths
               Read file names from the standard input, one per line, instead
               of from the command-line.
    
           --path
               Hash object as if it were located at the given path. The
               location of the file does not directly influence the hash
               value, but the path is used to determine which Git filters
               should be applied to the object before it can be placed in the
               object database. As a result of applying filters, the actual
               blob put into the object database may differ from the given
               file. This option is mainly useful for hashing temporary files
               located outside of the working directory or files read from
               stdin.
    
           --no-filters
               Hash the contents as is, ignoring any input filter that would
               have been chosen by the attributes mechanism, including the
               end-of-line conversion. If the file is read from standard
               input then this is always implied, unless the **--path** option is
               given.
    
           --literally
               Allow **--stdin** to hash any garbage into a loose object which
               might not otherwise pass standard object parsing or git-fsck
               checks. Useful for stress-testing Git itself or reproducing
               characteristics of corrupt or bogus objects encountered in the
               wild.
    


## GIT



           Part of the git(1) suite
    


* * *
# trace-cmd-start

## NAME



           trace-cmd-start - start the Ftrace Linux kernel tracer without
           recording
    


## SYNOPSIS



           **trace-cmd start**[_OPTIONS_]
    


## DESCRIPTION



           The trace-cmd(1) start enables all the Ftrace tracing the same way
           trace-cmd-record(1) does. The difference is that it does not run
           threads to create a trace.dat file. This is useful just to enable
           Ftrace and you are only interested in the trace after some event
           has occurred and the trace is stopped. Then the trace can be read
           straight from the Ftrace pseudo file system or can be extracted
           with trace-cmd-extract(1).
    


## OPTIONS



           The options are the same as trace-cmd-record(1), except that it
           does not take options specific to recording (**-s** , **-o** , **-N** , and **-t**).
    
           **--fork**
               This option is only available for trace-cmd start. It tells
               trace-cmd to not wait for the process to finish before
               returning. With this option, trace-cmd start will return right
               after it forks the process on the command line. This option
               only has an effect if trace-cmd start also executes a command.
    


## RESOURCES



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


## COPYING



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


## NOTES



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


* * *
# ibv_devinfo

## NAME



           ibv_devinfo - query RDMA devices
    


## SYNOPSIS



           **ibv_devinfo**[-d device] [-i port] [-l] [-v]
    


## DESCRIPTION



           Print information about RDMA devices available for use from
           userspace.
    


## OPTIONS



           **-d** , **--ib-dev** =_DEVICE_
                  use IB device _DEVICE_ (default all devices)
    
                  **-i** , **--ib-port** =_PORT_ query port _PORT_ (default all ports)
    
                  **-l** , **--list** only list names of RDMA devices
    
                  **-v** , **--verbose** print all available information about RDMA
                  devices
    


* * *
# gettext

## NAME



           gettext - translate message
    


## SYNOPSIS



           **gettext**[_OPTION_] [[_TEXTDOMAIN_] _MSGID_]
           **gettext**[_OPTION_] _-s_ [_MSGID_]...
    


## DESCRIPTION



           The **gettext** program translates a natural language message into the
           user's language, by looking up the translation in a message
           catalog.
    
           Display native language translation of a textual message.
    
       **Options and arguments:**
           **-d** , **--domain** =_TEXTDOMAIN_
                  retrieve translated messages from TEXTDOMAIN
    
           **-c** , **--context** =_CONTEXT_
                  specify context for MSGID
    
           **-e** enable expansion of some escape sequences
    
           **-n** suppress trailing newline
    
           **-E**(ignored for compatibility)
    
           [TEXTDOMAIN] MSGID
                  retrieve translated message corresponding to MSGID from
                  TEXTDOMAIN
    
       **Informative output:**
           **-h** , **--help**
                  display this help and exit
    
           **-V** , **--version**
                  display version information and exit
    
           If the TEXTDOMAIN parameter is not given, the domain is determined
           from the environment variable TEXTDOMAIN.  If the message catalog
           is not found in the regular directory, another location can be
           specified with the environment variable TEXTDOMAINDIR.  When used
           with the **-s** option the program behaves like the 'echo' command.
           But it does not simply copy its arguments to stdout.  Instead
           those messages found in the selected catalog are translated.
           Standard search directory: /usr/local/share/locale
    


* * *
# md5sum

## NAME



           md5sum - compute and check MD5 message digest
    


## SYNOPSIS



           **md5sum**[_OPTION_]... [_FILE_]...
    


## DESCRIPTION



           Print or check MD5 (128-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 RFC 1321.  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 MD5 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)
    


* * *
# diffman-git

## NAME



           diffman-git - compare changes to manual pages line by line
    


## SYNOPSIS



           **diffman-git**[_diff-options_ ...] [[_base-commit_] _commit_]
    


## DESCRIPTION



           The **diffman-git** command formats a manual page at two git(1)
           commits, and then runs diff(1) on the formatted outputs.
    
           If the _commit_ is not specified, it diffs the working directory
           against HEAD.
    
           If the _base-commit_ is not specified, the comparison is done
           against the previous commit.
    


## OPTIONS



           **-s** Report when two files are the same.
    
           **-U** _n_    output _n_ (default 3) lines of unified context.
    
           **-w** Ignore all white space.
    


## ENVIRONMENT



           See man(1).
    


## EXAMPLES



           $ **MAN_KEEP_FORMATTING= diffman-git 437e4afec6ca | less -R** ;
           --- 437e4afec6ca^:man/man3/sem_open.3
           +++ 437e4afec6ca:man/man3/sem_open.3
           @@ -14,3 +14,2 @@
           -     sem_t *sem_open(const char *name, int oflag);
           -     sem_t *sem_open(const char *name, int oflag,
           -                     mode_t mode, unsigned int value);
           +     sem_t *sem_open(const char *name, int oflag, ...
           +                     /* mode_t mode, unsigned int value */ );
    


* * *
# nfs4_getfacl

## NAME



           nfs4_getfacl - get NFSv4 file/directory access control lists
    


## SYNOPSIS



           **nfs4_getfacl [-HR]** file ...
    


## DESCRIPTION



           **nfs4_getfacl** will display the NFSv4 Access Control List (ACL) for
           the files given as arguments, provided they are on mounted NFSv4
           filesystems which support ACLs.
    
           If the **-H** /**--more-help** flag is specified, **nfs4_getfacl** will print
           some information about NFSv4 ACLs and the fields used in ACEs.
    
           If the **-R** /**--recursive** flag is specified, **nfs4_getfacl** will list
           the NFSv4 ACLs of all files and directories recursively.
    
           If the **-c** /**--omit-header** flag is specified, **nfs4_getfacl** will not
           display the comment header (Do not print filename).
    
           If the **--dacl** flag is specified, **nfs4_getfacl** will retrieve the
           dacl. This functionality is only available if the server supports
           NFSv4 minor version 1 or newer.
    
           If the **--sacl** flag is specified, **nfs4_getfacl** will retrieve the
           sacl. This functionality is only available if the server supports
           NFSv4 minor version 1 or newer.
    
           The output format for an NFSv4 file ACL, e.g., is:
    
                  # file: /somedir
                  A::OWNER@:rwatTnNcCy
                  A::alice@nfsdomain.org:rxtncy
                  A::bob@nfsdomain.org:rwadtTnNcCy
                  A:g:GROUP@:rtncy
                  D:g:GROUP@:waxTC
                  A::EVERYONE@:rtncy
                  D::EVERYONE@:waxTC
    
           In the example output above, the user `alice@nfsdomain.org' has
           the equivalent of "read" and "execute" permissions,
           `bob@nfsdomain.org' has "read" and "write", and both `GROUP@' and
           `EVERYONE@' have "read".
    
           The ACL listings of multiple files are separated by blank lines.
    
           Refer to the nfs4_acl(5) manpage for detailed information about
           NFSv4 ACL terminology and syntax.
    


## CONTACT



           Please send bug reports, feature requests, and comments to <_linux-_
           _nfs@vger.kernel.org_ >.
    


* * *
# yum-versionlock

## NAME



           yum-versionlock - Version lock rpm packages
    


## SYNOPSIS



           **yum-versionlock**[ package-name [ package-name]] ...
    


## DESCRIPTION



           yum-versionlock(1) is a Yum plugin that takes a set of
           name/versions for packages and excludes all other versions of
           those packages (including optionally following obsoletes).  This
           allows you to protect packages from being updated by newer
           versions.
    
           The plugin provides a command "versionlock" which allows you to
           view and edit the list of locked packages easily.
    
           **yum versionlock add <package-wildcard>...**
                  Add a versionlock for all of the packages in the rpmdb
                  matching the given wildcards.
    
           **yum versionlock exclude <package-wildcard>...**
                  Opposite; disallow currently available versions of the
                  packages matching the given wildcards.
    
           **yum versionlock list**
                  List the current versionlock entries.
    
           **yum versionlock status**
                  List any available updates that are currently blocked by
                  versionlock.  That is, for each entry in the lock list,
                  print the newest package available in the repos unless it
                  is the particular locked/excluded version.
    
           **yum versionlock delete <entry-wildcard>...**
                  Remove any matching versionlock entries.
    
           **yum versionlock clear**
                  Remove all versionlock entries.
    


## FILES



           _/etc/yum/pluginconf.d/versionlock.conf_
                  The system wide configuration file. See
                  yum-versionlock.conf(5) for more information.
           _/etc/yum/pluginconf.d/versionlock.list_
                  The default place to put package version lock information
                  (one package and version per. line). The file takes entries
                  in the following format **EPOCH:NAME-VERSION-RELEASE.ARCH** See
                  rpm(8) for more information on custom query formats. If the
                  package does not have an EPOCH the number will default to
                  0.
    


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


## AVAILABILITY



           yum-versionlock is available via:
           # yum install yum-versionlock
    


* * *
# mariadb-waitpid

## NAME



           mariadb-waitpid - kill process and wait for its termination
           (mariadb-waitpid is now a symlink to mariadb-waitpid)
    


## SYNOPSIS



    
           **mariadb-waitpid [**_options_**]**_pid wait_time_
    


## DESCRIPTION



           **mariadb-waitpid** signals a process to terminate and waits for the
           process to exit. It uses the kill() system call and Unix signals,
           so it runs on Unix and Unix-like systems.
    
           Invoke **mariadb-waitpid** like this:
    
               shell> **mariadb-waitpid [**_options_**]**_pid wait_time_
    
           **mariadb-waitpid** sends signal 0 to the process identified by _pid_
           and waits up to _wait_time_ seconds for the process to terminate.
           _pid_ and _wait_time_ must be positive integers.
    
           If process termination occurs within the wait time or the process
           does not exist, **mariadb-waitpid** returns 0. Otherwise, it returns
           1.
    
           If the kill() system call cannot handle signal 0, **mariadb-**
           **waitpid()** uses signal 1 instead.
    
           **mariadb-waitpid** supports the following options:
    
           •   **--help** , **-?** , **-I**
    
               Display a help message and exit.
    
           •   **--verbose** , **-v**
    
               Verbose mode. Display a warning if signal 0 could not be used
               and signal 1 is used instead.
    
           •   **--version** , **-V**
    
               Display version information and exit.
    


* * *
# xtotroff

## Name



           xtotroff - convert X font metrics into groff font metrics
    


## Synopsis



           **xtotroff**[**-r** _resolution_] [**-s** _point-size_] _font-map_
    
           **xtotroff --help**
    
           **xtotroff -v**
           **xtotroff --version**
    


## Description



           _xtotroff_ uses _font-map_ to create _groff_(1) font description files
           from X11 fonts.  Each line in _font-map_ consists of a series of
           lines of paired _groff_ font names and X font names as X Logical
           Font Description (XLFD) patterns, with the pair members separated
           by spaces and/or tabs.  For example, an input _font-map_ file
           consisting of the line
                  TB -adobe-times-bold-r-normal--*-*-*-*-p-*-iso8859-1
           maps the XLFD on the right to the _groff_ font name **TB** ,
           conventionally “Times bold”.
    
           _xtotroff_ opens a connection to the running X server to query its
           font catalog, and aborts if it cannot.  If necessary, the
           wildcards in the XLFD patterns are populated with the arguments to
           the **-r** and **-s** options.  If a font name is still ambiguous,
           _xtotroff_ aborts.  For each successful mapping, _xtotroff_ creates a
           _groff_ font description file in the current working directory named
           for each _groff_ font, and reports the mapping to the standard
           output stream.
    


## Options



           **--help** displays a usage message, while **-v** and **--version** show
           version information; all exit afterward.
    
           **-r** _resolution_
                  Set the resolution for all font patterns in _font-map_.  The
                  value is used for both the horizontal and vertical
                  resolution.  If not specified, a resolution of 75dpi is
                  assumed.
    
           **-s** _point-size_
                  Set the point size for all font patterns in _font-map_.  If
                  not specified, a size of 10 points is assumed.
    


## Bugs



           The only supported font encodings are “iso8859-1” and “adobe-
           fontspecific”.
    


## See also



           “X Logical Font Description Conventions” 
           ⟨https://www.x.org/releases/X11R7.6/doc/xorg-docs/specs/XLFD/xlfd
           .html⟩, by Jim Flowers and Stephen Gildea.
    
           _X_(7), _groff_(1), _gxditview_(1), _troff_(1), _groff_font_(5)
    


* * *
# cgcc

## NAME



           cgcc - Compiler wrapper to run Sparse after compiling
    


## SYNOPSIS



           **cgcc**[_SPARSE OPTIONS_]... [_COMPILER OPTIONS_]... [_INPUT FILES_]...
           **make CC=cgcc**
    


## DESCRIPTION



           **cgcc** provides a wrapper around a C compiler (**cc** by default) which
           also invokes the Sparse static analysis tool.
    
           **cgcc** accepts all Sparse command-line options, such as warning
           options, and passes all other options through to the compiler.
    
           By providing the same interface as the C compiler, **cgcc** allows
           projects to run Sparse as part of their build without modifying
           their build system, by using **cgcc** as the compiler.  For many
           projects, setting **CC=cgcc** on the **make** command-line will work.
    


## ENVIRONMENT



           **REAL_CC**
                  If set, **cgcc** will use this as the compiler to invoke,
                  rather than the default **cc**.
    
           **CHECK** If set, **cgcc** will use this as the Sparse program to invoke,
                  rather than the default **sparse**.
    


* * *
# eval

## PROLOG



           This manual page is part of the POSIX Programmer's Manual.  The
           Linux implementation of this interface may differ (consult the
           corresponding Linux manual page for details of Linux behavior), or
           the interface may not be implemented on Linux.
    


## NAME



           eval — construct command by concatenating arguments
    


## SYNOPSIS



           eval **[**_argument_...**]**
    


## DESCRIPTION



           The _eval_ utility shall construct a command by concatenating
           _argument_ s together, separating each with a <space> character.  The
           constructed command shall be read and executed by the shell.
    


## OPTIONS



           None.
    


## OPERANDS



           See the DESCRIPTION.
    


## STDIN



           Not used.
    


## INPUT FILES



           None.
    


## ENVIRONMENT VARIABLES



           None.
    


## ASYNCHRONOUS EVENTS



           Default.
    


## STDOUT



           Not used.
    


## STDERR



           The standard error shall be used only for diagnostic messages.
    


## OUTPUT FILES



           None.
    


## EXTENDED DESCRIPTION



           None.
    


## EXIT STATUS



           If there are no _argument_ s, or only null _argument_ s, _eval_ shall
           return a zero exit status; otherwise, it shall return the exit
           status of the command defined by the string of concatenated
           _argument_ s separated by <space> characters, or a non-zero exit
           status if the concatenation could not be parsed as a command and
           the shell is interactive (and therefore did not abort).
    


## CONSEQUENCES OF ERRORS



           Default.
    
           _The following sections are informative._
    


## APPLICATION USAGE



           Since _eval_ is not required to recognize the **"--"** end of options
           delimiter, in cases where the argument(s) to _eval_ might begin with
           **'-'** it is recommended that the first argument is prefixed by a
           string that will not alter the commands to be executed, such as a
           <space> character:
    
               eval " $commands"
    
           or:
    
               eval " $(some_command)"
    


## EXAMPLES



           foo=10 x=foo
           y='$'$x
           echo $y
           **$foo**
           eval y='$'$x
           echo $y
           **10**
    


## RATIONALE



           This standard allows, but does not require, _eval_ to recognize
           **"--"**.  Although this means applications cannot use **"--"** to protect
           against options supported as an extension (or errors reported for
           unsupported options), the nature of the _eval_ utility is such that
           other means can be used to provide this protection (see
           APPLICATION USAGE above).
    


## FUTURE DIRECTIONS



           None.
    


* * *
# stg-hide

## NAME



           stg-hide - Hide patches in the series
    


## SYNOPSIS



           _stg hide_ [OPTIONS] <patch>...
    


## DESCRIPTION



           Hide patches in the series.
    
           Hidden patches are no longer shown in the plain _series_ output.
    


## OPTIONS



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


## STGIT



           Part of the StGit suite - see stg(1)
    


* * *
# dh_installalternatives

## NAME



           dh_installalternatives - install declarative alternative rules
    


## SYNOPSIS



           **dh_installalternatives**[_debhelper options_]
    


## DESCRIPTION



           **dh_installalternatives** is a debhelper program that is responsible
           for parsing the declarative alternatives format and insert the
           relevant maintscripts snippets to interface with
           update-alternatives(1)
    


## FILES



           debian/_package_.alternatives
               An example of the format:
    
                   Name: editor
                   Link: /usr/bin/editor
                   Alternative: /usr/bin/vim.basic
                   Dependents:
                     /usr/share/man/man1/editor.1.gz editor.1.gz /usr/share/man/man1/vim.1.gz
                     /usr/share/man/fr/man1/editor.1.gz editor.fr.1.gz /usr/share/man/fr/man1/vim.1.gz
                     /usr/share/man/it/man1/editor.1.gz editor.it.1.gz /usr/share/man/it/man1/vim.1.gz
                     /usr/share/man/pl/man1/editor.1.gz editor.pl.1.gz /usr/share/man/pl/man1/vim.1.gz
                     /usr/share/man/ru/man1/editor.1.gz editor.ru.1.gz /usr/share/man/ru/man1/vim.1.gz
                   Priority: 50
    
               The fields **Link** , **Name** , **Alternative** , and **Priority** are mandatory
               and correspond to the update-alternatives(1) **--install**
               parameters **link** , **name** , **path** , and **priority** respectively.
    
               The **Dependents** field is optional and consists of one or more
               lines. Each non-empty line must contain exactly 3 space
               separated values that match (in order) the values passed to
               the **--slave** parameter for update-alternatives(1).
    


## OPTIONS



           **-n** , **--no-scripts**
               Do not modify _postinst_ /_postrm_ /_prerm_ scripts.
    


* * *
# pwdx

## NAME



           pwdx - report current working directory of a process
    


## SYNOPSIS



           **pwdx**[_option_ ...] _pid_ ...
    


## OPTIONS



           **-V** , **--version**
                  Output version information and exit.
    
           **-h** , **--help**
                  Output help screen and exit.
    


## STANDARDS



           No standards apply, but **pwdx** looks an awful lot like a SunOS
           command.
    


* * *
# nproc

## NAME



           nproc - print the number of processing units available
    


## SYNOPSIS



           **nproc**[_OPTION_]...
    


## DESCRIPTION



           Print the number of processing units available to the current
           process, which may be less than the number of online processors
    
           **--all** print the number of installed processors
    
           **--ignore** =_N_
                  if possible, exclude N processing units
    
           **--help** display this help and exit
    
           **--version**
                  output version information and exit
    


* * *
# perf-kallsyms

## NAME



           perf-kallsyms - Searches running kernel for symbols
    


## SYNOPSIS



           _perf kallsyms_ [<options>] symbol_name[,symbol_name...]
    


## DESCRIPTION



           This command searches the running kernel kallsyms file for the
           given symbol(s) and prints information about it, including the
           DSO, the kallsyms begin/end addresses and the addresses in the ELF
           kallsyms symbol table (for symbols in modules).
    


## OPTIONS



           -v, --verbose
               Increase verbosity level, showing details about symbol table
               loading, etc.
    


* * *