neulab/tldr huggingface dataset:
-b,--build <dir> Directory to unpack packages into and build in.  The default in a virtualenv is "<venv path>/build".  The default for global installs is "<OS temp dir>/pip_build_<username>".
-t,--target <dir> Install packages into <dir>.
-d,--download <dir> Download packages into <dir> instead of installing them, regardless of what's already installed.
--download-cache <dir> Cache downloaded packages in <dir>.
--src <dir> Directory to check out editable projects into.  The default in a virtualenv is "<venv path>/src".  The default for global installs is "<current dir>/src".
-U, --upgrade Upgrade all packages to the newest available version.  This process is recursive regardless of whether a dependency is already satisfied.
--force-reinstall When upgrading, reinstall all packages even if they are already up-to-date.
-I, --ignore-installed Ignore the installed packages (reinstalling instead).
--no-deps Don't install package dependencies.
--install-option <options> Extra arguments to be supplied to the setup.py install command (use like --install-option ="--install-scripts=/usr/local/bin"). Use multiple --install-option options to pass multiple options to setup.py install. If you are using an option with a directory path, be sure to use absolute path.
--global-option <options> Extra global options to be supplied to the setup.py call before the install command.
--user Install using the user scheme.
--egg  Install packages as eggs, not 'flat', like pip normally does. This option is not about installing from eggs. (WARNING: Because this option overrides pip's normal install logic, requirements files may not behave as expected.)
--root <dir> Install everything relative to this alternate root directory.
--compile Compile py files to pyc.
--no-compile Do not compile py files to pyc.
--no-use-wheel Do not find and prefer wheel archives when searching indexes and find-links locations.
--pre  Include pre-release and development versions. By default, pip only finds stable versions.
--no-clean Don't clean up build directories.
Package Index Options:
-i,--index-url <url> Base URL of Python Package Index (default https://pypi.python.org/simple/).
--extra-index-url <url> Extra URLs of package indexes to use in addition to --index-url.
--no-index Ignore package index (only looking at --find-links URLs instead).
-f,--find-links <url> If a url or path to an html file, then parse for links to archives. If a local path or file:// url that's a directory, then look for archives in the directory listing.
--allow-external <package> Allow the installation of externally hosted files
--allow-all-external Allow the installation of all externally hosted files
--allow-unverified <package> Allow the installation of insecure and unverifiable files
--process-dependency-links Enable the processing of dependency links.
pip is able to uninstall most installed packages. Known exceptions are:
• Pure distutils packages installed with python setup.py install, which leave behind no metadata to determine what files were installed.
• Script wrappers installed by python setup.py develop.
-r,--requirement <file> Uninstall all the packages listed in the given requirements file. This option can be used multiple times.
-y, --yes Don't ask for confirmation of uninstall deletions.
This manual page was originally written by Jeff Licquia <‐ licquia@debian.org>, later rewritten by Carl Chenet <chaica@debian.org>. It was rewritten again and the source converted to reStructuredText by Barry Warsaw <barry@debian.org>.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, version 3 or any later version published by the Free Software Foundation.
Barry Warsaw <barry@debian.org>
PIDSTAT(1)                     Linux User's Manual                    PIDSTAT(1)
pidstat - Report statistics for Linux tasks.
pidstat [ -d ] [ -H ] [ -h ] [ -I ] [ -l ] [ -R ] [ -r ] [ -s ] [ -t ] [ -U [ username ] ] [ -u ] [ -V ] [ -v ] [ -w ] [ -C comm ] [ -G process_name ] [ --dec={ 0 | 1 | 2 } ] [ --human ] [ -p { pid[,...]  | SELF | ALL } ] [ -T { TASK | CHILD | ALL } ] [ interval [ count ] ] [ -e program args ]
The pidstat command is used for monitoring individual tasks currently being managed by the Linux kernel.  It writes to standard output activities for every task selected with option -p or for every task managed by the Linux kernel if option -p ALL has been used. Not selecting any tasks is equivalent to specifying -p ALL but only active tasks (tasks with non-zero statistics values) will appear in the report.
The pidstat command can also be used for monitoring the child processes of selected tasks.  Read about option -T below.
The interval parameter specifies the amount of time in seconds between each report.  A value of 0 (or no parameters at all) indicates that tasks statistics are to be reported for the time since system startup (boot). The count parameter can be specified in conjunction with the interval parameter if this one is not set to zero. The value of count determines the number of reports generated at interval seconds apart. If the interval parameter is specified without the count parameter, the pidstat command generates reports continuously.
You can select information about specific task activities using flags. Not specifying any flags selects only CPU activity.
-C comm Display only tasks whose command name includes the string comm. This string can be a regular expression.
-d     Report I/O statistics (kernels 2.6.20 and later only).  The following values may be displayed:
UID    The real user identification number of the task being monitored.
USER   The name of the real user owning the task being monitored.
PID    The identification number of the task being monitored.
kB_rd/s Number of kilobytes the task has caused to be read from disk per second.
kB_wr/s Number of kilobytes the task has caused, or shall cause to be written to disk per second.
kB_ccwr/s Number of kilobytes whose writing to disk has been cancelled by the task. This may occur when the task truncates some dirty pagecache. In this case, some IO which another task has been accounted for will not be happening.
iodelay Block I/O delay of the task being monitored, measured in clock ticks. This metric includes the delays spent waiting for sync block I/O completion and for swapin block I/O completion.
Command The command name of the task.
--dec={ 0 | 1 | 2 } Specify the number of decimal places to use (0 to 2, default value is 2).
-e program args Execute program with given arguments args and monitor it with pidstat.  pidstat stops when program terminates.
-G process_name Display only processes whose command name includes the string process_name.  This string can be a regular expression. If option -t is used together with option -G then the threads belonging to that process are also displayed (even if their command name doesn't include the string process_name).
-H     Display timestamp in seconds since the epoch.
-h     Display all activities horizontally on a single line, with no average statistics at the end of the report. This is intended to make it easier to be parsed by other programs.
--human Print sizes in human readable format (e.g. 1.0k, 1.2M, etc.)  The units displayed with this option supersede any other default units (e.g.  kilobytes, sectors...) associated with the metrics.
-I     In an SMP environment, indicate that tasks CPU usage (as displayed by option -u) should be divided by the total number of processors.
-l     Display the process command name and all its arguments.
-p { pid[,...] | SELF | ALL } Select tasks (processes) for which statistics are to be reported. pid is the process identification number. The SELF keyword indicates that statistics are to be reported for the pidstat process itself, whereas the ALL keyword indicates that statistics are to be reported for all the tasks managed by the system.
-R     Report realtime priority and scheduling policy information.  The following values may be displayed:
prio   The realtime priority of the task being monitored.
policy The scheduling policy of the task being monitored.
-r     Report page faults and memory utilization.
When reporting statistics for individual tasks, the following values may be displayed:
minflt/s Total number of minor faults the task has made per second, those which have not required loading a memory page from disk.
majflt/s Total number of major faults the task has made per second, those which have required loading a memory page from disk.
VSZ    Virtual Size: The virtual memory usage of entire task in kilobytes.
RSS    Resident Set Size: The non-swapped physical memory used by the task in kilobytes.
%MEM   The tasks's currently used share of available physical memory.
When reporting global statistics for tasks and all their children, the following values may be displayed:
UID    The real user identification number of the task which is being monitored together with its children.
USER   The name of the real user owning the task which is being monitored together with its children.
PID    The identification number of the task which is being monitored together with its children.
minflt-nr Total number of minor faults made by the task and all its children, and collected during the interval of time.
majflt-nr Total number of major faults made by the task and all its children, and collected during the interval of time.
Command The command name of the task which is being monitored together with its children.
-s     Report stack utilization.  The following values may be displayed:
StkSize The amount of memory in kilobytes reserved for the task as stack, but not necessarily used.
StkRef The amount of memory in kilobytes used as stack, referenced by the task.
-T { TASK | CHILD | ALL } This option specifies what has to be monitored by the pidstat command. The TASK keyword indicates that statistics are to be reported for individual tasks (this is the default option) whereas the CHILD keyword indicates that statistics are to be globally reported for the selected tasks and all their children. The ALL keyword indicates that statistics are to be reported for individual tasks and globally for the selected tasks and their children.
Note: Global statistics for tasks and all their children are not available for all options of pidstat.  Also these statistics are not necessarily relevant to current time interval: The statistics of a child process are collected only when it finishes or it is killed.
-t     Also display statistics for threads associated with selected tasks.
This option adds the following values to the reports:
TGID   The identification number of the thread group leader.
TID    The identification number of the thread being monitored.
-U [ username ] Display the real user name of the tasks being monitored instead of the UID.  If username is specified, then only tasks belonging to the specified user are displayed.
-u     Report CPU utilization.
%usr   Percentage of CPU used by the task while executing at the user level (application), with or without nice priority. Note that this field does NOT include time spent running a virtual processor.
%system Percentage of CPU used by the task while executing at the system level (kernel).
%guest Percentage of CPU spent by the task in virtual machine (running a virtual processor).
%wait  Percentage of CPU spent by the task while waiting to run.
%CPU   Total percentage of CPU time used by the task. In an SMP environment, the task's CPU usage will be divided by the total number of CPU's if option -I has been entered on the command line.
CPU    Processor number to which the task is attached.
usr-ms Total number of milliseconds spent by the task and all its children while executing at the user level (application), with or without nice priority, and collected during the interval of time. Note that this field does NOT include time spent running a virtual processor.
system-ms Total number of milliseconds spent by the task and all its children while executing at the system level (kernel), and collected during the interval of time.
guest-ms Total number of milliseconds spent by the task and all its children in virtual machine (running a virtual processor).
-V     Print version number then exit.
-v     Report values of some kernel tables. The following values may be displayed:
threads Number of threads associated with current task.
fd-nr  Number of file descriptors associated with current task.
-w     Report task switching activity (kernels 2.6.23 and later only). The following values may be displayed:
cswch/s Total number of voluntary context switches the task made per second.  A voluntary context switch occurs when a task blocks because it requires a resource that is unavailable.
nvcswch/s Total number of non voluntary context switches the task made per second.  A involuntary context switch takes place when a task executes for the duration of its time slice and then is forced to relinquish the processor.
The pidstat command takes into account the following environment variables:
S_COLORS By default statistics are displayed in color when the output is connected to a terminal.  Use this variable to change the settings. Possible values for this variable are never, always or auto (the latter is equivalent to the default settings). Please note that the color (being red, yellow, or some other color) used to display a value is not indicative of any kind of issue simply because of the color. It only indicates different ranges of values.
S_COLORS_SGR Specify the colors and other attributes used to display statistics on the terminal.  Its value is a colon-separated list of capabilities that defaults to H=31;1:I=32;22:M=35;1:N=34;1:Z=34;22.  Supported capabilities are:
H=     SGR (Select Graphic Rendition) substring for percentage values greater than or equal to 75%.
I=     SGR substring for item values like PID, UID or CPU number.
M=     SGR substring for percentage values in the range from 50% to 75%.
N=     SGR substring for non-zero statistics values and for tasks names.
Z=     SGR substring for zero values and for threads names.
S_TIME_FORMAT If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header. The pidstat command will use the ISO 8601 format (YYYY-MM- DD) instead.  The timestamp will also be compliant with ISO 8601 format.
pidstat 2 5 Display five reports of CPU statistics for every active task in the system at two second intervals.
pidstat -r -p 1643 2 5 Display five reports of page faults and memory statistics for PID 1643 at two second intervals.
pidstat -C "fox|bird" -r -p ALL Display global page faults and memory statistics for all the processes whose command name includes the string "fox" or "bird".
pidstat -T CHILD -r 2 5 Display five reports of page faults statistics at two second intervals for the child processes of all tasks in the system. Only child processes with non-zero statistics values are displayed.
/proc filesystem must be mounted for the pidstat command to work.
Although pidstat speaks of kilobytes (kB), megabytes (MB)..., it actually uses kibibytes (kiB), mebibytes (MiB)...  A kibibyte is equal to 1024 bytes, and a mebibyte is equal to 1024 kibibytes.
/proc contains various files with system statistics.
Sebastien Godard (sysstat <at> orange.fr)
sar(1), top(1), ps(1), mpstat(1), iostat(1), vmstat(8)
https://github.com/sysstat/sysstat http://pagesperso-orange.fr/sebastien.godard/
RSPEC(1)                                                                RSPEC(1)
rspec - standalone test runner for Ruby RSpec test suites
rspec [options] [files or directories]
The Ruby script rspec allows you to run tests written with RSpec, a testing tool for Ruby, from the command line. When run without arguments, rspec finds automatically all the spec files of your projects, and runs them. It is possible to restrict the tests to a subset by specifying the names of particular spec files or by using some of the filtering options.
Various options can be passed to rspec to modify the output of the tests, or the way the tests are run.
-I PATH Specify PATH to add to $LOAD_PATH (may be used more than once).
-r, --require PATH Require a file.
-O, --options PATH Specify the path to a custom options file.
--order TYPE[:SEED] Run examples by the specified order type. TYPE can be either default, for which files are ordered based on the underlying file system's order, or rand, for which the order of files, groups and examples is randomized. random is an alias for rand. A SEED can be indicated for the random type, e.g. --order random:123
--seed SEED Equivalent of --order rand:SEED.
-d, --debugger Enable debugging.
--fail-fast Abort the run on first failure.
--failure-exit-code CODE Override the exit code used when there are failing specs.
-X, --[no-]drb Run examples via DRb.
--drb-port PORT Port to connect to the DRb server.
--init Initialize your project with RSpec.
--configure Deprecated. Use --init instead.
-f, --format FORMATTER Choose a formatter. The various choices are [p]rogress (default - dots), [d]ocumentation (group and example names), [h]tml, [t]extmate or a custom formatter class name.
-o, --out FILE Write output to a file instead of STDOUT. This option applies to the previously specified --format, or the default format if no format is specified.
-b, --backtrace Enable full backtrace.
-c, --[no-]color, --[no-]colour Enable color in the output.
-p, --profile Enable profiling of examples and list 10 slowest examples.
In addition to the following options for selecting specific files, groups, or examples, you can select a single example by appending the line number to the filename:
rspec path/to/a_spec.rb:37
-P, --pattern PATTERN Load files matching pattern (default: "spec/**/*_spec.rb").
-e, --example STRING Run examples whose full nested names include STRING.
-l, --line_number LINE Specify line number of an example or group (may be used more than once).
-t, --tag TAG[:VALUE] Run examples with the specified tag, or exclude examples by adding ~ before the tag, e.g. ~slow.  TAG is always converted to a symbol.
--default_path PATH Set the default path where RSpec looks for examples (can be a path to a file or a directory).
-v, --version Display the version.
-h, --help Display a message similar to this manpage.
This man page inspired by the help message of rspec, has been written by CÃ©dric Boutillier for the Debian Project, but may be used by others.
xvfb-run(1)                  General Commands Manual                 xvfb-run(1)
xvfb-run - run specified X client or command in a virtual X server environment
xvfb-run [ options ] command
xvfb-run is a wrapper for the Xvfb(1x) command which simplifies the task of running commands (typically an X client, or a script containing a list of clients to be run) within a virtual X server environment.
xvfb-run sets up an X authority file (or uses an existing user-specified one), writes a cookie to it (see xauth(1x)) and then starts the Xvfb X server as a background process.  The process ID of Xvfb is stored for later use.  The specified command is then run using the X display corresponding to the Xvfb server just started and the X authority file created earlier.
When the command exits, its status is saved, the Xvfb server is killed (using the process ID stored earlier), the X authority cookie removed, and the authority file deleted (if the user did not specify one to use). xvfb-run then exits with the exit status of command.
xvfb-run requires the xauth command to function.
-a, --auto-servernum Try to get a free server number, starting at 99, or the argument to --server-num.
-e file, --error-file=file Store output from xauth and Xvfb in file.  The default is /dev/null.
-f file, --auth-file=file Store X authentication data in file.  By default, a temporary directory called xvfb-run.PID (where PID is the process ID of xvfb-run itself) is created in the directory specified by the environment variable TMPDIR (or /tmp if that variable is null or unset), and the tempfile(1) command is used to create a file in that temporary directory called Xauthority.
-h, --help Display a usage message and exit.
-n servernumber, --server-num=servernumber Use servernumber as the server number (but see the -a, --auto-servernum option above).  The default is 99.
-l, --listen-tcp Enable TCP port listening in the X server.  For security reasons (to avoid denial-of-service attacks or exploits), TCP port listening is disabled by default.
-p protocolname, --xauth-protocol=protocolname Use protocolname as the X authority protocol to use.  The default is ‘.’, which xauth interprets as its own default protocol, which is MIT-MAGIC-COOKIE-1.
-s arguments, --server-args=arguments Pass arguments to the Xvfb server.  Be careful to quote any whitespace characters that may occur within arguments to prevent them from regarded as separators for xvfb-run's own arguments. Also, note that specification of ‘-nolisten tcp’ in arguments may override the function of xvfb-run's own -l, --listen-tcp option, and that specification of the server number (e.g., ‘:1’) may be ignored because of the way the X server parses its argument list. Use the xvfb-run option -n servernumber, --server-num=servernumber to achieve the latter function.  The default is ‘-screen 0 640x480x8’.
-w delay, --wait=delay Wait delay seconds after launching Xvfb before attempting to start the specified command.  The default is 3.
COLUMNS indicates the width of the terminal device in character cells. This value is used for formatting diagnostic messages.  If not set, the terminal is queried using stty(1) to determine its width. If that fails, a value of ‘80’ is assumed.
TMPDIR specifies the directory in which to place xvfb-run's temporary directory for storage of the X authority file; only used if the -f or --auth-file options are not specified.
Unless the -f or --auth-file options are specified, a temporary directory and file within it are created (and deleted) to store the X authority cookies used by the Xvfb server and client(s) run under it.  See tempfile(1).  If -f or --auth-file are used, then the specified X authority file is only written to, not created or deleted (though xauth creates an authority file itself if told to use use that does not already exist).
An error file with a user-specified name is also created if the -e or --error-file options are specifed; see above.
xvfb-run uses its exit status as well as output to standard error to communicate diagnostics.  The exit status of ‘1’ is not used, and should be interpreted as failure of the specified command.
0      xvfb-run only uses this exit status if the -h, --help option is given.  In all other situations, this may be interpreted as success of the specified command.
2      No command to run was specified.
3      The xauth command is not available.
4      The temporary directory that was going to be used already exists; since xvfb-run produces a uniquely named directory, this may indicate an attempt by another process on the system to exploit a temporary file race condition.
5      A problem was encountered while cleaning up the temporary directory.
6      A problem was encountered while using getopt(1) to parse the command-line arguments.
xvfb-run --auto-servernum --server-num=1 xlogo runs the xlogo(1x) demonstration client inside the Xvfb X server on the first available server number greater than or equal to 1.
xvfb-run --server-args="-screen 0 1024x768x24" ico -faces runs the ico(1x) demonstration client (and passes it the -faces argument) inside the Xvfb X server, configured with a root window of 1024 by 768 pixels and a color depth of 24 bits.
Note that the demo X clients used in the above examples will not exit on their own, so they will have to be killed before xvfb-run will exit.
See the Debian Bug Tracking System ⟨http://bugs.debian.org/xvfb⟩.  If you wish to report a bug in xvfb-run, please use the reportbug(1) command.
xfvb-run was written by Branden Robinson and Jeff Licquia with sponsorship from Progeny Linux Systems.
Xvfb(1x), xauth(1x)
GIT-STRIPSPACE(1)                  Git Manual                  GIT-STRIPSPACE(1)
git-stripspace - Remove unnecessary whitespace
git stripspace [-s | --strip-comments] git stripspace [-c | --comment-lines]
Read text, such as commit messages, notes, tags and branch descriptions, from the standard input and clean it in the manner used by Git.
With no arguments, this will:
•   remove trailing whitespace from all lines
•   collapse multiple consecutive empty lines into one empty line
•   remove empty lines from the beginning and end of the input
•   add a missing \n to the last line if necessary.
In the case where the input consists entirely of whitespace characters, no output will be produced.
NOTE: This is intended for cleaning metadata, prefer the --whitespace=fix mode of git-apply(1) for correcting whitespace of patches or files in the repository.
-s, --strip-comments Skip and remove all lines starting with comment character (default #).
-c, --comment-lines Prepend comment character and blank to each line. Lines will automatically be terminated with a newline. On empty lines, only the comment character will be prepended.
Given the following noisy input with $ indicating the end of a line:
|A brief introduction   $ |   $ |$ |A new paragraph$ |# with a commented-out line    $ |explaining lots of stuff.$ |$ |# An old paragraph, also commented-out. $ |      $ |The end.$ |  $
Use git stripspace with no arguments to obtain:
|A brief introduction$ |$ |A new paragraph$ |# with a commented-out line$ |explaining lots of stuff.$ |$ |# An old paragraph, also commented-out.$ |$ |The end.$
Use git stripspace --strip-comments to obtain:
|A brief introduction$ |$ |A new paragraph$ |explaining lots of stuff.$ |$ |The end.$
VGCREATE(8)                  System Manager's Manual                 VGCREATE(8)
vgcreate â€” Create a volume group
vgcreate position_args [ option_args ]
vgcreate creates a new VG on block devices. If the devices were not previously initialized as PVs with pvcreate(8), vgcreate will inititialize them, making them PVs. The pvcreate options for initializing devices are also available with vgcreate.
When vgcreate uses an existing PV, that PV's existing values for metadata size, PE start, etc, are used, even if different values are specified in the vgcreate command.  To change these values, first use pvremove on the device.
vgcreate VG_new PV ... [ -A|--autobackup y|n ] [ -c|--clustered y|n ] [ -l|--maxlogicalvolumes Number ] [ -p|--maxphysicalvolumes Number ] [ -M|--metadatatype lvm2 ] [ -s|--physicalextentsize Size[m|UNIT] ] [ -f|--force ] [ -Z|--zero y|n ] [    --addtag Tag ] [    --alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit ] [    --metadataprofile String ] [    --labelsector Number ] [    --metadatasize Size[m|UNIT] ] [    --pvmetadatacopies 0|1|2 ] [    --[vg]metadatacopies all|unmanaged|Number ] [    --reportformat basic|json ] [    --dataalignment Size[k|UNIT] ] [    --dataalignmentoffset Size[k|UNIT] ] [    --shared ] [    --systemid String ] [    --locktype sanlock|dlm|none ] [    --setautoactivation y|n ] [ COMMON_OPTIONS ]
--addtag Tag Adds a tag to a PV, VG or LV. This option can be repeated to add multiple tags at once. See lvm(8) for information about tags.
-c|--clustered y|n This option was specific to clvm and is now replaced by the --shared option with lvmlockd(8).
--dataalignment Size[k|UNIT] Align the start of a PV data area with a multiple of this number. To see the location of the first Physical Extent (PE) of an existing PV, use pvs -o +pe_start. In addition, it may be shifted by an alignment offset, see --dataalignmentoffset.  Also specify an appropriate PE size when creating a VG.
--dataalignmentoffset Size[k|UNIT] Shift the start of the PV data area by this additional offset.
--labelsector Number By default the PV is labelled with an LVM2 identifier in its second sector (sector 1). This lets you use a different sector near the start of the disk (between 0 and 3 inclusive - see LABEL_SCAN_SECTORS in the source). Use with care.
--locktype sanlock|dlm|none Specify the VG lock type directly in place of using --shared.  See lvmlockd(8) for more information.
-l|--maxlogicalvolumes Number Sets the maximum number of LVs allowed in a VG.
-p|--maxphysicalvolumes Number Sets the maximum number of PVs that can belong to the VG.  The value 0 removes any limitation.  For large numbers of PVs, also see options --pvmetadatacopies, and --vgmetadatacopies for improving performance.
--metadataprofile String The metadata profile to use for command configuration.  See lvm.conf(5) for more information about profiles.
--metadatasize Size[m|UNIT] The approximate amount of space used for each VG metadata area. The size may be rounded.
-M|--metadatatype lvm2 Specifies the type of on-disk metadata to use.  lvm2 (or just 2) is the current, standard format.  lvm1 (or just 1) is no longer used.
-s|--physicalextentsize Size[m|UNIT] Sets the physical extent size of PVs in the VG.  The value must be either a power of 2 of at least 1 sector (where the sector size is the largest sector size of the PVs currently used in the VG), or at least 128KiB.  Once this value has been set, it is difficult to change without recreating the VG, unless no extents need moving.
--pvmetadatacopies 0|1|2 The number of metadata areas to set aside on a PV for storing VG metadata.  When 2, one copy of the VG metadata is stored at the front of the PV and a second copy is stored at the end.  When 1, one copy of the VG metadata is stored at the front of the PV. When 0, no copies of the VG metadata are stored on the given PV. This may be useful in VGs containing many PVs (this places limitations on the ability to use vgsplit later.)
--setautoactivation y|n Set the autoactivation property on a VG or LV.  Display the property with vgs or lvs "-o autoactivation".  When the autoactivation property is disabled, the VG or LV will not be activated by a command doing autoactivation (vgchange, lvchange, or pvscan using -aay.)  If autoactivation is disabled on a VG, no LVs will be autoactivated in that VG, and the LV autoactivation property has no effect.  If autoactivation is enabled on a VG, autoactivation can be disabled for individual LVs.
--shared Create a shared VG using lvmlockd if LVM is compiled with lockd support.  lvmlockd will select lock type sanlock or dlm depending on which lock manager is running. This allows multiple hosts to share a VG on shared devices. lvmlockd and a lock manager must be configured and running.  See lvmlockd(8) for more information about shared VGs.
--systemid String Specifies the system ID that will be given to the new VG, overriding the system ID of the host running the command. A VG is normally created without this option, in which case the new VG is given the system ID of the host creating it. Using this option requires caution because the system ID of the new VG may not match the system ID of the host running the command, leaving the VG inaccessible to the host.  See lvmsystemid(7) for more information.
--[vg]metadatacopies all|unmanaged|Number Number of copies of the VG metadata that are kept.  VG metadata is kept in VG metadata areas on PVs in the VG, i.e. reserved space at the start and/or end of the PVs.  Keeping a copy of the VG metadata on every PV can reduce performance in VGs containing a large number of PVs.  When this number is set to a non-zero value, LVM will automatically choose PVs on which to store metadata, using the metadataignore flags on PVs to achieve the specified number.  The number can also be replaced with special string values: unmanaged causes LVM to not automatically manage the PV metadataignore flags.  all causes LVM to first clear the metadataignore flags on all PVs, and then to become unmanaged.
-Z|--zero y|n Controls if the first 4 sectors (2048 bytes) of the device are wiped.  The default is to wipe these sectors unless either or both of --restorefile or --uuid are specified.
Create a VG with two PVs, using the default physical extent size. vgcreate myvg /dev/sdk1 /dev/sdl1
OCAML(1)                     General Commands Manual                    OCAML(1)
ocaml - The OCaml interactive toplevel
ocaml [ options ] [ object-files ] [ script-file ]
The ocaml(1) command is the toplevel system for OCaml, that permits interactive use of the OCaml system through a read-eval-print loop. In this mode, the system repeatedly reads OCaml phrases from the input, then typechecks, compiles and evaluates them, then prints the inferred type and result value, if any. The system prints a # (hash) prompt before reading each phrase.
A toplevel phrase can span several lines. It is terminated by ;; (a double-semicolon). The syntax of toplevel phrases is as follows.
The toplevel system is started by the command ocaml(1).  Phrases are read on standard input, results are printed on standard output, errors on standard error. End-of-file on standard input terminates ocaml(1).
If one or more object-files (ending in .cmo or .cma) are given, they are loaded silently before starting the toplevel.
If a script-file is given, phrases are read silently from the file, errors printed on standard error.  ocaml(1) exits after the execution of the last phrase.
The following command-line options are recognized by ocaml(1).
-absname Show absolute filenames in error messages.
-I directory Add the given directory to the list of directories searched for source and compiled files. By default, the current directory is searched first, then the standard library directory. Directories added with -I are searched after the current directory, in the order in which they were given on the command line, but before the standard library directory.
Directories can also be added to the search path once the toplevel is running with the #directory directive.
-init file Load the given file instead of the default initialization file. See the "Initialization file" section below.
-noassert Do not compile assertion checks.  Note that the special form assert false is always compiled because it is typed specially.
-noinit Do not load any initialization file.  See the "Initialization file" section below.
-noprompt Do not display any prompt when waiting for input.
-nopromptcont Do not display the secondary prompt when waiting for continuation lines in multi-line inputs.  This should be used e.g. when running ocaml(1) in an emacs(1) window.
-nostdlib Do not include the standard library directory in the list of directories searched for source and compiled files.
-open module Opens the given module before starting the toplevel. If several -open options are given, they are processed in order, just as if the statements open! module1;; ... open! moduleN;; were input.
-rectypes Allow arbitrary recursive types during type-checking.  By default, only recursive types where the recursion goes through an object type are supported.
-stdin Read the standard input as a script file rather than starting an interactive session.
-unsafe Turn bound checking off on array and string accesses (the v.(i)ands.[i] constructs). Programs compiled with -unsafe are therefore slightly faster, but unsafe: anything can happen if the program accesses an array or string outside of its bounds.
-version Print version string and exit.
-vnum  Print short version number and exit.
-no-version Do not print the version banner at startup.
-w warning-list Enable or disable warnings according to the argument warning-list. See ocamlc(1) for the syntax of the warning-list argument.
-warn-error warning-list Mark as fatal the warnings described by the argument warning-list. Note that a warning is not triggered (and does not trigger an error) if it is disabled by the -w option.  See ocamlc(1) for the syntax of the warning-list argument.
- file Use file as a script file name, even when it starts with a hyphen (-).
When ocaml(1) is invoked, it will read phrases from an initialization file before giving control to the user. The default file is .ocamlinit in the current directory if it exists, otherwise XDG_CONFIG_HOME/ocaml/init.ml according to the XDG base directory specification lookup if it exists (on Windows this is skipped), otherwise .ocamlinit in the user's home directory ( HOME variable).  You can specify a different initialization file by using the -init file option, and disable initialization files by using the -noinit option.
Note that you can also use the #use directive to read phrases from a file.
OCAMLTOP_UTF_8 When printing string values, non-ascii bytes (>0x7E) are printed as decimal escape sequence if OCAMLTOP_UTF_8 is set to false. Otherwise they are printed unescaped.
TERM   When printing error messages, the toplevel system attempts to underline visually the location of the error. It consults the TERM variable to determines the type of output terminal and look up its capabilities in the terminal database.
XDG_CONFIG_HOME HOME .ocamlinit lookup procedure (see above).
ocamlc(1), ocamlopt(1), ocamlrun(1). The OCaml user's manual, chapter "The toplevel system".
LPASS(1)                              lpass                             LPASS(1)
lpass - command line interface for LastPass
lpass [ --version, -v | --help, -h ] lpass <subcommand> [<args>]
lpass is a simple command line interface to LastPass. It is comprised of several subcommands:
lpass login [--trust] [--plaintext-key [--force, -f]] [--color=auto|never|always] USERNAME lpass logout [--force, -f] [--color=auto|never|always] lpass passwd lpass show [--sync=auto|now|no] [--clip, -c] [--quiet, -q] [--expand-multi, -x] [--json, -j] [--all|--username|--password|--url|--notes|--field=FIELD|--id|--name|--attach=ATTACHID] [--basic-regexp, -G|--fixed-strings, -F] [--color=auto|never|always] {NAME|UNIQUEID}* lpass ls [--sync=auto|now|no] [--long, -l] [-m] [-u] [--color=auto|never|always] [GROUP] lpass mv [--sync=auto|now|no] [--color=auto|never|always] {UNIQUENAME|UNIQUEID} GROUP lpass add [--sync=auto|now|no] [--non-interactive] {--name|--username, -u|--password, -p|--url|--notes|--field=FIELD|--note-type=NOTETYPE} [--color=auto|never|always] {NAME|UNIQUEID} lpass edit [--sync=auto|now|no] [--non-interactive] {--name|--username, -u|--password, -p|--url|--notes|--field=FIELD} [--color=auto|never|always] {NAME|UNIQUEID} lpass generate [--sync=auto|now|no] [--clip, -c] [--username=USERNAME] [--url=URL] [--no-symbols] [--color=auto|never|always] {NAME|UNIQUEID} LENGTH lpass duplicate [--sync=auto|now|no] [--color=auto|never|always] {UNIQUENAME|UNIQUEID} lpass rm [--sync=auto|now|no] [--color=auto|never|always] {UNIQUENAME|UNIQUEID} lpass status [--quiet, -q] [--color=auto|never|always] lpass sync [--background, -b] [--color=auto|never|always] lpass import [--sync=auto|now|no] [--keep-dupes] [FILENAME] lpass export [--sync=auto|now|no] [--color=auto|never|always] [--fields=FIELDLIST] lpass share userls SHARE lpass share useradd [--read-only=[true|false]] [--hidden=[true|false]] [--admin=[true|false]] SHARE USERNAME lpass share usermod [--read-only=[true|false]] [--hidden=[true|false]] [--admin=[true|false]] SHARE USERNAME lpass share userdel SHARE USERNAME lpass share create SHARE lpass share rm SHARE lpass share limit [--deny|--allow] [--add|--rm|--clear] SHARE USERNAME [sites]
Synchronization The --sync options control when the current operation involves a synchronization with the server. If now is set, and the command makes a change, the change is synchronized before the command exits. If now is set, and the command displays a value, the local cache is synchronized before the value is shown. If now is set, and the command is otherwise successful, but synchronization fails, the command will return an error. If auto is set, and the command makes a change, the change is synchronized to the server in the background. If auto is set, and the command displays a value, the local cache is synchronized before the value is shown only if the local cache is more than 5 seconds (or LPASS_AUTO_SYNC_TIME seconds, if set) old. If no is set, the command will not interact with the server, unless there is a current upload queue being processed. Any local changes that are not synchronized with the server will exist in a queue of timestamped requests which will be synchronized on the next occurring synchronization.
The sync command forces a synchronization of the local cache with the LastPass servers, and does not exit until the local cache is synchronized or until an error occurs. Alternatively, if --background is specified, the synchronization occurs in a daemonized process.
Agent An agent process will be spawned in the background on a first successful command, and all subsequent commands will use the agent for decryption, instead of asking a user for a password. The agent will quit after one hour, unless the LPASS_AGENT_TIMEOUT environment variable is set to an alternative number of seconds in which to quit, or 0 to never quit. If the environment variable LPASS_AGENT_DISABLE is set to 1, the agent will not be used.
Password Entry The pinentry program, part of gpg2(1), may be used for inputting passwords if it is installed. A custom path to the pinentry program can be provided by the LPASS_PINENTRY environment variable.
If pinentry program is unavailable, or if the LPASS_DISABLE_PINENTRY environment variable is set to 1, passwords will be read from standard input and a prompt will be displayed on standard error.
The program used for inputting passwords may also be configured by setting the LPASS_ASKPASS environment variable. LPASS_ASKPASS is expected to be a binary that produces a prompt using its first command-line argument, and outputs the entered password to standard out. ssh-askpass implements this protocol, as does the following shell script:
#!/bin/bash echo -n "$*: " >/dev/stderr stty -echo read answer stty echo echo $answer
Entry Specification Commands that take a UNIQUENAME will fail if the provided name is used multiple times, and return an error. Commands may alternatively take a UNIQUEID, which will be the integer ID provided by LastPass for identifying entries uniquely. Commands that take either a NAME or a UNIQUEID will create a new entry if a NAME is specified and otherwise overwrite an existing entry if UNIQUEID is specified.
Logging In The login subcommand will initialize a local cache and configuration folder, then attempt to authenticate itself with the LastPass servers, using the provided command line credentials or by interactively prompting (in the case of multifactor or an unprovided password). The --trust option will cause subsequent logins to not require multifactor authentication. If the --plaintext-key option is specified, the decryption key will be saved to the hard disk in plaintext. Please note that use of this option is discouraged except in limited situations, as it greatly decreases the security of data.
The logout subcommand will remove the local cache and stored encryption keys. It will prompt the user to confirm, unless --force is specified.
The passwd subcommand may be used to change your LastPass password: it will prompt for the old and new password and then re-encrypt all records with the newly derived key.
Viewing The show subcommand will display a password or selected field.
By default, the site you specify with the show subcommand must exactly match the name of the site. If the --fixed-strings or -F option is set, then the show subcommand will find a site containing that exact substring; if the --basic-regexp or -G option is set, then the show subcommand will find a site matching a case-insensitive regular expression.
By default if your show subcommand matches more than one site, then the show subcommand will generate a warning and display the names of matching sites but no other information. The --expand-multi or -x option will instead show the requested information from all of the matching sites.
The ls subcommand will list names in groups in a tree structure. If the --long or -l option is set, then also list the last modification time. The -u option may be passed to show the last use (last touch) time instead, if available. Both times are in GMT.
Passing --json to show will generate json output instead of human-readable text.
In addition to using the built-in formats, both show and ls subcommands support printf-style format strings by using the --format option with the following placeholders:
•   %ai: account id
•   %an: account name
•   %aN: account name including path
•   %au: account user
•   %ap: account password
•   %am: account modification time
•   %aU: account last touch time
•   %as: account share name
•   %ag: account group name
•   %al: account URL
•   %fn: field name (for show)
•   %fv: field value (for show)
A slash can be added between the % and the placeholder to indicate that a slash should be appended, only if the printed value is expanded to a non-empty string. For example, this command will properly show the full path to an account: lpass ls --format="%/as%/ag%an".
Modifying The edit subcommand will edit the selected field. If --non-interactive is not set, the selected field will be edited using EDITOR; otherwise the command will accept data until EOF or, unless the notes field is being edited, the first new line. Please note that when editing interactively, the contents of the field may be saved on disk in tmp files or in editor swap files, depending on your system configuration.
The generate subcommand will create a randomly generated password for the chosen key name, and optionally add a url and username while inserting the generated password.
The rm command will remove the specified entry, and the duplicate command will create a duplicate entry of the one specified, but with a different ID.
Backup The export subcommand will dump all account information including passwords to stdout (unencrypted) in CSV format. The optional --fields=FIELDLIST argument may contain a comma-separated subset of the following fields:
id, url, username, password, extra, name, fav, id, grouping, group, fullname, last_touch, last_modified_gmt, attachpresent
The import subcommand does the reverse: accounts from an unencrypted CSV file are uploaded to the server.
It is recommended that such backups be encrypted at rest, for example by piping to and from gpg.
Shared Folder Commands The share command and its accompanying subcommands can be used to manipulate shared folders, if available to the (enterprise or premium) user. The userls, useradd, usermod, and userdel subcommands may be used to query and modify membership of the shared folder, while the create and rm share subcommands may be used to add new, or delete existing shared folders. The normal generate and edit commands may be used to edit accounts within the shared folder.
The share limit command may be used to manipulate account access lists on the share for a specific user. Running with no arguments will display the current access levels for a user. The --add, --rm, and --clear options may be used to add to, remove from, or reset the list. Passing --allow or --deny will make the list a whitelist or blacklist, respectively.
Clipboard Commands that take a -c or --clip option will copy the output to the clipboard, using xclip(1) or xsel(1) on X11-based systems, pbcopy(1) on OSX, or putclip on Cygwin. The command to be used can be overridden by specifying the LPASS_CLIPBOARD_COMMAND environment variable.
Color Output The --color option controls colored output to the terminal. By default, commands will use --color=auto, in which color output is used unless the output is not a tty (for example, when passed to a pipe or file). If always is used, colors are produced regardless of the output detection. If never is used, no color escape sequences are emitted.
Configuration lpass stores configuration in the following locations, in descending order of precedence:
•   The directory $LPASS_HOME, if set
•   $XDG_CONFIG_HOME/lpass, $XDG_DATA_HOME/lpass, and $XDG_RUNTIME_DIR/lpass (or equivalent defaults), if at least $XDG_RUNTIME_DIR is set
•   $HOME/.lpass
All configuration may be specified via environment variables. Alternatively, a set of environment variable overrides may be specified in $LPASS_HOME/env in the form of:
VARIABLE1=VALUE1 VARIABLE2=VALUE2 ...
Aliases Default options can be specified for any command by creating command aliases. Command aliases are stored in the configuration directory (see previous section) with files named alias.command. For example, to force the ls subcommand to never use color, make an alias.ls file with the appropriate option:
echo 'ls --color=never' > ~/.config/lpass/alias.ls
Similarly, new subcommands can be created based on built-in subcommands with options. Thus,
echo 'show --password -c' > ~/.config/lpass/alias.passclip
would create a passclip subcommand that copies your password onto the clipboard.