neulab/tldr huggingface dataset:
WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access.
Account Flags This section contains flags that describe the attributes of the users account. This field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters:
•   U - This means this is a "User" account, i.e. an ordinary user.
•   N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(5) config file.
•   D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user.
•   X - This means the password does not expire.
•   W - This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC.
Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information regarding the flags that are supported please refer to the man page for the pdbedit command.
Last Change Time This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made.
All other colon separated fields are ignored at this time.
This man page is part of version 4.15.0 of the Samba suite.
smbpasswd(8), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm.
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
IOTOP(1)                     General Commands Manual                    IOTOP(1)
iotop - simple top-like I/O monitor
iotop [OPTIONS]
iotop watches I/O usage information output by the Linux kernel (requires 2.6.20 or later) and displays a table of current I/O usage by processes or threads on the system. At least the CONFIG_TASK_DELAY_ACCT, CONFIG_TASK_IO_ACCOUNTING, CONFIG_TASKSTATS and CONFIG_VM_EVENT_COUNTERS options need to be enabled in your Linux kernel build configuration.
iotop displays columns for the I/O bandwidth read and written by each process/thread during the sampling period. It also displays the percentage of time the thread/process spent while swapping in and while waiting on I/O. For each process, its I/O priority (class/level) is shown.  In addition, the total I/O bandwidth read and written during the sampling period is displayed at the top of the interface.
Use the left and right arrows to change the sorting, r to reverse the sorting order, o to toggle the --only option, p to toggle the --processes option, a to toggle the --accumulated option, q to quit or i to change the priority of a thread or a process' thread(s). Any other key will force a refresh.
--version Show the version number and exit
-h, --help Show usage information and exit
-o, --only Only show processes or threads actually doing I/O, instead of showing all processes or threads. This can be dynamically toggled by pressing o.
-b, --batch Turn on non-interactive mode.  Useful for logging I/O usage over time.
-n NUM, --iter=NUM Set the number of iterations before quitting (never quit by default).  This is most useful in non-interactive mode.
-d SEC, --delay=SEC Set the delay between iterations in seconds (1 second by default). Accepts non-integer values such as 1.1 seconds.
-p PID, --pid=PID A list of processes/threads to monitor (all by default).
-u USER, --user=USER A list of users to monitor (all by default)
-P, --processes Only show processes. Normally iotop shows all threads.
-a, --accumulated Show accumulated I/O instead of bandwidth. In this mode, iotop shows the amount of I/O processes have done since iotop started.
-k, --kilobytes Use kilobytes instead of a human friendly unit. This mode is useful when scripting the batch mode of iotop. Instead of choosing the most appropriate unit iotop will display all sizes in kilobytes.
-t, --time Add a timestamp on each line (implies --batch). Each line will be prefixed by the current time.
-q, --quiet suppress some lines of header (implies --batch). This option can be specified up to three times to remove header lines. -q     column names are only printed on the first iteration, -qq    column names are never printed, -qqq   the I/O summary is never printed.
ionice(1), top(1), vmstat(1), atop(1), htop(1)
iotop was written by Guillaume Chazarain.
This manual page was started by Paul Wise for the Debian project and is placed in the public domain.
PACMAN(8)                         Pacman Manual                        PACMAN(8)
pacman - package manager utility
pacman <operation> [options] [targets]
Pacman is a package management utility that tracks installed packages on a Linux system. It features dependency support, package groups, install and uninstall scripts, and the ability to sync your local machine with a remote repository to automatically upgrade packages. Pacman packages are a zipped tar format.
Since version 3.0.0, pacman has been the front-end to libalpm(3), the “Arch Linux Package Management” library. This library allows alternative front-ends to be written (for instance, a GUI front-end).
Invoking pacman involves specifying an operation with any potential options and targets to operate on. A target is usually a package name, file name, URL, or a search string. Targets can be provided as command line arguments. Additionally, if stdin is not from a terminal and a single hyphen (-) is passed as an argument, targets will be read from stdin.
-D, --database Operate on the package database. This operation allows you to modify certain attributes of the installed packages in pacman’s database. It also allows you to check the databases for internal consistency. See Database Options below.
-Q, --query Query the package database. This operation allows you to view installed packages and their files, as well as meta-information about individual packages (dependencies, conflicts, install date, build date, size). This can be run against the local package database or can be used on individual package files. In the first case, if no package names are provided in the command line, all installed packages will be queried. Additionally, various filters can be applied on the package list. See Query Options below.
-R, --remove Remove package(s) from the system. Groups can also be specified to be removed, in which case every package in that group will be removed. Files belonging to the specified package will be deleted, and the database will be updated. Most configuration files will be saved with a .pacsave extension unless the --nosave option is used. See Remove Options below.
-S, --sync Synchronize packages. Packages are installed directly from the remote repositories, including all dependencies required to run the packages. For example, pacman -S qt will download and install qt and all the packages it depends on. If a package name exists in more than one repository, the repository can be explicitly specified to clarify the package to install: pacman -S testing/qt. You can also specify version requirements: pacman -S "bash>=3.2". Quotes are needed, otherwise the shell interprets ">" as redirection to a file.
In addition to packages, groups can be specified as well. For example, if gnome is a defined package group, then pacman -S gnome will provide a prompt allowing you to select which packages to install from a numbered list. The package selection is specified using a space- and/or comma-separated list of package numbers. Sequential packages may be selected by specifying the first and last package numbers separated by a hyphen (-). Excluding packages is achieved by prefixing a number or range of numbers with a caret (^).
Packages that provide other packages are also handled. For example, pacman -S foo will first look for a foo package. If foo is not found, packages that provide the same functionality as foo will be searched for. If any package is found, it will be installed. A selection prompt is provided if multiple packages providing foo are found.
You can also use pacman -Su to upgrade all packages that are out-of-date. See Sync Options below. When upgrading, pacman performs version comparison to determine which packages need upgrading. This behavior operates as follows:
Alphanumeric: 1.0a < 1.0b < 1.0beta < 1.0p < 1.0pre < 1.0rc < 1.0 < 1.0.a < 1.0.1 Numeric: 1 < 1.0 < 1.1 < 1.1.1 < 1.2 < 2.0 < 3.0.0
Additionally, version strings can have an epoch value defined that will overrule any version comparison, unless the epoch values are equal. This is specified in an epoch:version-rel format. For example, 2:1.0-1 is always greater than 1:3.6-1.
-T, --deptest Check dependencies; this is useful in scripts such as makepkg to check installed packages. This operation will check each dependency specified and return a list of dependencies that are not currently satisfied on the system. This operation accepts no other options. Example usage: pacman -T qt "bash>=3.2".
-U, --upgrade Upgrade or add package(s) to the system and install the required dependencies from sync repositories. Either a URL or file path can be specified. This is a “remove-then-add” process. See Upgrade Options below; also see Handling Config Files for an explanation on how pacman takes care of configuration files.
-F, --files Query the files database. This operation allows you to look for packages owning certain files or display files owned by certain packages. Only packages that are part of your sync databases are searched. See File Options below.
-V, --version Display version and exit.
-h, --help Display syntax for the given operation. If no operation was supplied, then the general syntax is shown.
-b, --dbpath <path> Specify an alternative database location (the default is /var/lib/pacman). This should not be used unless you know what you are doing.  NOTE: If specified, this is an absolute path, and the root path is not automatically prepended.
-r, --root <path> Specify an alternative installation root (default is /). This should not be used as a way to install software into /usr/local instead of /usr.  NOTE: If database path or log file are not specified on either the command line or in pacman.conf(5), their default location will be inside this root path.  NOTE: This option is not suitable for performing operations on a mounted guest system. See --sysroot instead.
-v, --verbose Output paths such as the Root, Conf File, DB Path, Cache Dirs, etc.
--arch <arch> Specify an alternate architecture.
--cachedir <dir> Specify an alternative package cache location (the default is /var/cache/pacman/pkg). Multiple cache directories can be specified, and they are tried in the order they are passed to pacman.  NOTE: This is an absolute path, and the root path is not automatically prepended.
--color <when> Specify when to enable coloring. Valid options are always, never, or auto.  always forces colors on; never forces colors off; and auto only automatically enables colors when outputting onto a tty.
--config <file> Specify an alternate configuration file.
--debug Display debug messages. When reporting bugs, this option is recommended to be used.
--gpgdir <dir> Specify a directory of files used by GnuPG to verify package signatures (the default is /etc/pacman.d/gnupg). This directory should contain two files: pubring.gpg and trustdb.gpg.  pubring.gpg holds the public keys of all packagers.  trustdb.gpg contains a so-called trust database, which specifies that the keys are authentic and trusted.  NOTE: This is an absolute path, and the root path is not automatically prepended.
--hookdir <dir> Specify a alternative directory containing hook files (the default is /etc/pacman.d/hooks). Multiple hook directories can be specified with hooks in later directories taking precedence over hooks in earlier directories.  NOTE: This is an absolute path, and the root path is not automatically prepended.
--logfile <file> Specify an alternate log file. This is an absolute path, regardless of the installation root setting.
--noconfirm Bypass any and all “Are you sure?” messages. It’s not a good idea to do this unless you want to run pacman from a script.
--confirm Cancels the effects of a previous --noconfirm.
--disable-download-timeout Disable defaults for low speed limit and timeout on downloads. Use this if you have issues downloading files with proxy and/or security gateway.
--sysroot <dir> Specify an alternative system root. Pacman will chroot and chdir into the system root prior to running. This allows mounted guest systems to be properly operated on. Any other paths given will be interpreted as relative to the system root. Requires root privileges.
TRANSACTION OPTIONS (APPLY TO -S, -R AND -U) -d, --nodeps Skips dependency version checks. Package names are still checked. Normally, pacman will always check a package’s dependency fields to ensure that all dependencies are installed and there are no package conflicts in the system. Specify this option twice to skip all dependency checks.
--assume-installed <package=version> Add a virtual package "package" with version "version" to the transaction to satisfy dependencies. This allows to disable specific dependency checks without affecting all dependency checks. To disable all dependency checking, see the --nodeps option.
--dbonly Adds/removes the database entry only, leaving all files in place.
--noprogressbar Do not show a progress bar when downloading files. This can be useful for scripts that call pacman and capture the output.
--noscriptlet If an install scriptlet exists, do not execute it. Do not use this unless you know what you are doing.
-p, --print Only print the targets instead of performing the actual operation (sync, remove or upgrade). Use --print-format to specify how targets are displayed. The default format string is "%l", which displays URLs with -S, file names with -U, and pkgname-pkgver with -R.
--print-format <format> Specify a printf-like format to control the output of the --print operation. The possible attributes are: "%n" for pkgname, "%v" for pkgver, "%l" for location, "%r" for repository, and "%s" for size. Implies --print.
UPGRADE OPTIONS (APPLY TO -S AND -U) -w, --downloadonly Retrieve all packages from the server, but do not install/upgrade anything.
--asdeps Install packages non-explicitly; in other words, fake their install reason to be installed as a dependency. This is useful for makepkg and other build-from-source tools that need to install dependencies before building the package.
--asexplicit Install packages explicitly; in other words, fake their install reason to be explicitly installed. This is useful if you want to mark a dependency as explicitly installed so it will not be removed by the --recursive remove operation.
--ignore <package> Directs pacman to ignore upgrades of package even if there is one available. Multiple packages can be specified by separating them with a comma.
--ignoregroup <group> Directs pacman to ignore upgrades of all packages in group, even if there is one available. Multiple groups can be specified by separating them with a comma.
--needed Do not reinstall the targets that are already up-to-date.
--overwrite <glob> Bypass file conflict checks and overwrite conflicting files. If the package that is about to be installed contains files that are already installed and match glob, this option will cause all those files to be overwritten. Using --overwrite will not allow overwriting a directory with a file or installing packages with conflicting files and directories. Multiple patterns can be specified by separating them with a comma. May be specified multiple times. Patterns can be negated, such that files matching them will not be overwritten, by prefixing them with an exclamation mark. Subsequent matches will override previous ones. A leading literal exclamation mark or backslash needs to be escaped.
QUERY OPTIONS (APPLY TO -Q) -c, --changelog View the ChangeLog of a package if it exists.
-d, --deps Restrict or filter output to packages installed as dependencies. This option can be combined with -t for listing real orphans - packages that were installed as dependencies but are no longer required by any installed package.
-e, --explicit Restrict or filter output to explicitly installed packages. This option can be combined with -t to list explicitly installed packages that are not required by any other package.
-g, --groups Display all packages that are members of a named group. If a name is not specified, list all grouped packages.
-i, --info Display information on a given package. The -p option can be used if querying a package file instead of the local database. Passing two --info or -i flags will also display the list of backup files and their modification states.
-k, --check Check that all files owned by the given package(s) are present on the system. If packages are not specified or filter flags are not provided, check all installed packages. Specifying this option twice will perform more detailed file checking (including permissions, file sizes, and modification times) for packages that contain the needed mtree file.
-l, --list List all files owned by a given package. Multiple packages can be specified on the command line.
-m, --foreign Restrict or filter output to packages that were not found in the sync database(s). Typically these are packages that were downloaded manually and installed with --upgrade.
-n, --native Restrict or filter output to packages that are found in the sync database(s). This is the inverse filter of --foreign.
-o, --owns <file> Search for packages that own the specified file(s). The path can be relative or absolute, and one or more files can be specified.
-p, --file Signifies that the package supplied on the command line is a file and not an entry in the database. The file will be decompressed and queried. This is useful in combination with --info and --list.
-q, --quiet Show less information for certain query operations. This is useful when pacman’s output is processed in a script. Search will only show package names and not version, group, and description information; owns will only show package names instead of "file is owned by pkg" messages; group will only show package names and omit group names; list will only show files and omit package names; check will only show pairs of package names and missing files; a bare query will only show package names rather than names and versions.
-s, --search <regexp> Search each locally-installed package for names or descriptions that match regexp. When including multiple search terms, only packages with descriptions matching ALL of those terms are returned.
-t, --unrequired Restrict or filter output to print only packages neither required nor optionally required by any currently installed package. Specify this option twice to include packages which are optionally, but not directly, required by another package.
-u, --upgrades Restrict or filter output to packages that are out-of-date on the local system. Only package versions are used to find outdated packages; replacements are not checked here. This option works best if the sync database is refreshed using -Sy.
REMOVE OPTIONS (APPLY TO -R) -c, --cascade Remove all target packages, as well as all packages that depend on one or more target packages. This operation is recursive and must be used with care, since it can remove many potentially needed packages.
-n, --nosave Instructs pacman to ignore file backup designations. Normally, when a file is removed from the system, the database is checked to see if the file should be renamed with a .pacsave extension.
-s, --recursive Remove each target specified including all of their dependencies, provided that (A) they are not required by other packages; and (B) they were not explicitly installed by the user. This operation is recursive and analogous to a backwards --sync operation, and it helps keep a clean system without orphans. If you want to omit condition (B), pass this option twice.
-u, --unneeded Removes targets that are not required by any other packages. This is mostly useful when removing a group without using the -c option, to avoid breaking any dependencies.
SYNC OPTIONS (APPLY TO -S) -c, --clean Remove packages that are no longer installed from the cache as well as currently unused sync databases to free up disk space. When pacman downloads packages, it saves them in a cache directory. In addition, databases are saved for every sync DB you download from and are not deleted even if they are removed from the configuration file pacman.conf(5). Use one --clean switch to only remove packages that are no longer installed; use two to remove all files from the cache. In both cases, you will have a yes or no option to remove packages and/or unused downloaded databases.
If you use a network shared cache, see the CleanMethod option in pacman.conf(5).
-g, --groups Display all the members for each package group specified. If no group names are provided, all groups will be listed; pass the flag twice to view all groups and their members.
-i, --info Display information on a given sync database package. Passing two --info or -i flags will also display those packages in all repositories that depend on this package.
-l, --list List all packages in the specified repositories. Multiple repositories can be specified on the command line.
-q, --quiet Show less information for certain sync operations. This is useful when pacman’s output is processed in a script. Search will only show package names and not repository, version, group, and description information; list will only show package names and omit databases and versions; group will only show package names and omit group names.
-s, --search <regexp> This will search each package in the sync databases for names or descriptions that match regexp. When you include multiple search terms, only packages with descriptions matching ALL of those terms will be returned.
-u, --sysupgrade Upgrades all packages that are out-of-date. Each currently-installed package will be examined and upgraded if a newer package exists. A report of all packages to upgrade will be presented, and the operation will not proceed without user confirmation. Dependencies are automatically resolved at this level and will be installed/upgraded if necessary.
Pass this option twice to enable package downgrades; in this case, pacman will select sync packages whose versions do not match with the local versions. This can be useful when the user switches from a testing repository to a stable one.
Additional targets can also be specified manually, so that -Su foo will do a system upgrade and install/upgrade the "foo" package in the same operation.
-y, --refresh Download a fresh copy of the master package database from the server(s) defined in pacman.conf(5). This should typically be used each time you use --sysupgrade or -u. Passing two --refresh or -y flags will force a refresh of all package databases, even if they appear to be up-to-date.
DATABASE OPTIONS (APPLY TO -D) --asdeps <package> Mark a package as non-explicitly installed; in other words, set their install reason to be installed as a dependency.
--asexplicit <package> Mark a package as explicitly installed; in other words, set their install reason to be explicitly installed. This is useful if you want to keep a package installed even when it was initially installed as a dependency of another package.
-k, --check Check the local package database is internally consistent. This will check all required files are present and that installed packages have the required dependencies, do not conflict and that multiple packages do not own the same file. Specifying this option twice will perform a check on the sync databases to ensure all specified dependencies are available.
-q, --quiet Suppress messages on successful completion of database operations.
FILE OPTIONS (APPLY TO -F) -y, --refresh Download fresh package databases from the server. Use twice to force a refresh even if databases are up to date.
-l, --list List the files owned by the queried package.
-x, --regex Interpret each query as a regular expression.
-q, --quiet Show less information for certain file operations. This is useful when pacman’s output is processed in a script, however, you may want to use --machinereadable instead.
--machinereadable Print each match in a machine readable output format. The format is repository\0pkgname\0pkgver\0path\n with \0 being the NULL character and \n a linefeed.
Pacman uses the same logic as rpm to determine action against files that are designated to be backed up. During an upgrade, three MD5 hashes are used for each backup file to determine the required action: one for the original file installed, one for the new file that is about to be installed, and one for the actual file existing on the file system. After comparing these three hashes, the following scenarios can result:
original=X, current=X, new=X All three files are the same, so overwrites are not an issue. Install the new file.
original=X, current=X, new=Y The current file is the same as the original, but the new one differs. Since the user did not ever modify the file, and the new one may contain improvements or bug fixes, install the new file.
original=X, current=Y, new=X Both package versions contain the exact same file, but the one on the file system has been modified. Leave the current file in place.
original=X, current=Y, new=Y The new file is identical to the current file. Install the new file.
original=X, current=Y, new=Z All three files are different, so install the new file with a .pacnew extension and warn the user. The user must then manually merge any necessary changes into the original file.
original=NULL, current=Y, new=Z The package was not previously installed, and the file already exists on the file system. Install the new file with a .pacnew extension and warn the user. The user must then manually merge any necessary changes into the original file.
pacman -Ss ne.hack Search for regexp "ne.hack" in package database.
pacman -S gpm Download and install gpm including dependencies.
pacman -U /home/user/ceofhack-0.6-1-x86_64.pkg.tar.gz Install ceofhack-0.6-1 package from a local file.
pacman -Syu Update package list and upgrade all packages afterwards.
pacman -Syu gpm Update package list, upgrade all packages, and then install gpm if it wasn’t already installed.
See pacman.conf(5) for more details on configuring pacman using the pacman.conf file.
alpm-hooks(5), libalpm(3), makepkg(8), pacman.conf(5)
See the pacman website at https://archlinux.org/pacman/ for current information on pacman and its related tools.
Bugs? You must be kidding; there are no bugs in this software. But if we happen to be wrong, submit a bug report with as much detail as possible at the Arch Linux Bug Tracker in the Pacman section.
Current maintainers:
•   Allan McRae <allan@archlinux.org>
•   Andrew Gregory <andrew.gregory.8@gmail.com>
•   Morgan Adamiec <morganamilo@archlinux.org>
Past major contributors:
•   Judd Vinet <jvinet@zeroflux.org>
•   Aurelien Foret <aurelien@archlinux.org>
•   Aaron Griffin <aaron@archlinux.org>
•   Dan McGee <dan@archlinux.org>
•   Xavier Chantry <shiningxc@gmail.com>
•   Nagy Gabor <ngaba@bibl.u-szeged.hu>
For additional contributors, use git shortlog -s on the pacman.git repository.
bup(1)                                                                    bup(1)
bup - Backup program using rolling checksums and git file formats
bup [global options...] <command> [options...]
bup is a program for making backups of your files using the git file format.
Unlike git(1) itself, bup is optimized for handling huge data sets including individual very large files (such a virtual machine images). However, once a backup set is created, it can still be accessed using git tools.
The individual bup subcommands appear in their own man pages.
--version print bup’s version number.  Equivalent to bup-version(1)
-d, --bup-dir=BUP_DIR use the given BUP_DIR parameter as the bup repository location, instead of reading it from the $BUP_DIR environment variable or using the default ~/.bup location.
bup-fsck(1) Check backup sets for damage and add redundancy information
bup-ftp(1) Browse backup sets using an ftp-like client
bup-fuse(1) Mount your backup sets as a filesystem
bup-help(1) Print detailed help for the given command
bup-index(1) Create or display the index of files to back up
bup-on(1) Backup a remote machine to the local one
bup-restore(1) Extract files from a backup set
bup-save(1) Save files into a backup set (note: run “bup index” first)
bup-web(1) Launch a web server to examine backup sets
bup-damage(1) Deliberately destroy data
bup-drecurse(1) Recursively list files in your filesystem
bup-init(1) Initialize a bup repository
bup-join(1) Retrieve a file backed up using bup-split(1)
bup-ls(1) Browse the files in your backup sets
bup-margin(1) Determine how close your bup repository is to armageddon
bup-memtest(1) Test bup memory usage statistics
bup-midx(1) Index objects to speed up future backups
bup-newliner(1) Make sure progress messages don’t overlap with output
bup-random(1) Generate a stream of random output
bup-server(1) The server side of the bup client-server relationship
bup-split(1) Split a single file into its own backup set
bup-tick(1) Wait for up to one second.
bup-version(1) Report the version number of your copy of bup.
BUP_ASSUME_GIT_VERSION_IS_FINE If set to true, yes, or 1, assume the version of git in the path is acceptable.
git(1) and the README file from the bup distribution.
The home of bup is at <http://github.com/bup/bup/>.
VGS(8)                       System Manager's Manual                      VGS(8)
vgs â€” Display information about volume groups
vgs [ option_args ] [ position_args ]
vgs produces formatted output about VGs.
vgs [ -a|--all ] [ -o|--options String ] [ -S|--select String ] [ -O|--sort String ] [    --aligned ] [    --binary ] [    --configreport log|vg|lv|pv|pvseg|seg ] [    --foreign ] [    --ignorelockingfailure ] [    --logonly ] [    --nameprefixes ] [    --noheadings ] [    --nosuffix ] [    --readonly ] [    --reportformat basic|json ] [    --rows ] [    --separator String ] [    --shared ] [    --unbuffered ] [    --units [Number]r|R|h|H|b|B|s|S|k|K|m|M|g|G|t|T|p|P|e|E ] [    --unquoted ] [ COMMON_OPTIONS ] [ VG|Tag ... ]
--aligned Use with --separator to align the output columns
-a|--all List all VGs. Equivalent to not specifying any VGs.
--binary Use binary values "0" or "1" instead of descriptive literal values for columns that have exactly two valid values to report (not counting the "unknown" value which denotes that the value could not be determined).
--configreport log|vg|lv|pv|pvseg|seg See lvmreport(7).
--foreign Report/display foreign VGs that would otherwise be skipped.  See lvmsystemid(7) for more information about foreign VGs.
--ignorelockingfailure Allows a command to continue with read-only metadata operations after locking failures.
--logonly Suppress command report and display only log report.
--nameprefixes Add an "LVM2_" prefix plus the field name to the output. Useful with --noheadings to produce a list of field=value pairs that can be used to set environment variables (for example, in udev rules).
--noheadings Suppress the headings line that is normally the first line of output.  Useful if grepping the output.
--nosuffix Suppress the suffix on output sizes. Use with --units (except h and H) if processing the output.
-o|--options String Comma-separated, ordered list of fields to display in columns. String arg syntax is: [+|-|#]Field1[,Field2 ...]  The prefix + will append the specified fields to the default fields, - will remove the specified fields from the default fields, and # will compact specified fields (removing them when empty for all rows.) Use -o help to view the list of all available fields.  Use separate lists of fields to add, remove or compact by repeating the -o option: -o+field1,field2 -o-field3,field4 -o#field5.  These lists are evaluated from left to right.  Use field name lv_all to view all LV fields, vg_all all VG fields, pv_all all PV fields, pvseg_all all PV segment fields, seg_all all LV segment fields, and pvseg_all all PV segment columns.  See the lvm.conf(5) report section for more config options.  See lvmreport(7) for more information about reporting.
--readonly Run the command in a special read-only mode which will read on- disk metadata without needing to take any locks. This can be used to peek inside metadata used by a virtual machine image while the virtual machine is running. No attempt will be made to communicate with the device-mapper kernel driver, so this option is unable to report whether or not LVs are actually in use.
--rows Output columns as rows.
-S|--select String Select objects for processing and reporting based on specified criteria.  The criteria syntax is described by --select help and lvmreport(7).  For reporting commands, one row is displayed for each object matching the criteria.  See --options help for selectable object fields.  Rows can be displayed with an additional "selected" field (-o selected) showing 1 if the row matches the selection and 0 otherwise.  For non-reporting commands which process LVM entities, the selection is used to choose items to process.
--separator String String to use to separate each column. Useful if grepping the output.
--shared Report/display shared VGs that would otherwise be skipped when lvmlockd is not being used on the host.  See lvmlockd(8) for more information about shared VGs.
-O|--sort String Comma-separated ordered list of columns to sort by. Replaces the default selection. Precede any column with - for a reverse sort on that column.
--unbuffered Produce output immediately without sorting or aligning the columns properly.
--units [Number]r|R|h|H|b|B|s|S|k|K|m|M|g|G|t|T|p|P|e|E All sizes are output in these units: human-(r)eadable with '<' rounding indicator, (h)uman-readable, (b)ytes, (s)ectors, (k)ilobytes, (m)egabytes, (g)igabytes, (t)erabytes, (p)etabytes, (e)xabytes.  Capitalise to use multiples of 1000 (S.I.) instead of 1024.  Custom units can be specified, e.g. --units 3M.
--unquoted When used with --nameprefixes, output values in the field=value pairs are not quoted.
VG     Volume Group name.  See lvm(8) for valid names.
Tag    Tag name.  See lvm(8) for information about tag names and using tags in place of a VG, LV or PV.
The vg_attr bits are:
1  Permissions: (w)riteable, (r)ead-only
2  Resi(z)eable
3  E(x)ported
4  (p)artial: one or more physical volumes belonging to the volume group are missing from the system
5  Allocation policy: (c)ontiguous, c(l)ing, (n)ormal, (a)nywhere
6  (c)lustered, (s)hared
GIT-HELP(1)                        Git Manual                        GIT-HELP(1)
git-help - Display help information about Git
git help [-a|--all [--[no-]verbose]] [[-i|--info] [-m|--man] [-w|--web]] [COMMAND|GUIDE] git help [-g|--guides] git help [-c|--config]
With no options and no COMMAND or GUIDE given, the synopsis of the git command and a list of the most commonly used Git commands are printed on the standard output.
If the option --all or -a is given, all available commands are printed on the standard output.
If the option --guides or -g is given, a list of the Git concept guides is also printed on the standard output.
If a command, or a guide, is given, a manual page for that command or guide is brought up. The man program is used by default for this purpose, but this can be overridden by other options or configuration variables.
If an alias is given, git shows the definition of the alias on standard output. To get the manual page for the aliased command, use git COMMAND --help.
Note that git --help ... is identical to git help ... because the former is internally converted into the latter.
To display the git(1) man page, use git help git.
This page can be displayed with git help help or git help --help
-a, --all Prints all the available commands on the standard output. This option overrides any given command or guide name.
--verbose When used with --all print description for all recognized commands. This is the default.
-c, --config List all available configuration variables. This is a short summary of the list in git-config(1).
-g, --guides Prints a list of the Git concept guides on the standard output.
-i, --info Display manual page for the command in the info format. The info program will be used for that purpose.
-m, --man Display manual page for the command in the man format. This option may be used to override a value set in the help.format configuration variable.
By default the man program will be used to display the manual page, but the man.viewer configuration variable may be used to choose other display programs (see below).
-w, --web Display manual page for the command in the web (HTML) format. A web browser will be used for that purpose.
The web browser can be specified using the configuration variable help.browser, or web.browser if the former is not set. If none of these config variables is set, the git web--browse helper script (called by git help) will pick a suitable default. See git- web--browse(1) for more information about this.
help.format If no command-line option is passed, the help.format configuration variable will be checked. The following values are supported for this variable; they make git help behave as their corresponding command- line option:
•   "man" corresponds to -m|--man,
•   "info" corresponds to -i|--info,
•   "web" or "html" correspond to -w|--web.
help.browser, web.browser and browser.<tool>.path The help.browser, web.browser and browser.<tool>.path will also be checked if the web format is chosen (either by command-line option or configuration variable). See -w|--web in the OPTIONS section above and git-web--browse(1).
man.viewer The man.viewer configuration variable will be checked if the man format is chosen. The following values are currently supported:
•   "man": use the man program as usual,
•   "woman": use emacsclient to launch the "woman" mode in emacs (this only works starting with emacsclient versions 22),
•   "konqueror": use kfmclient to open the man page in a new konqueror tab (see Note about konqueror below).
Values for other tools can be used if there is a corresponding man.<tool>.cmd configuration entry (see below).
Multiple values may be given to the man.viewer configuration variable. Their corresponding programs will be tried in the order listed in the configuration file.
For example, this configuration:
[man] viewer = konqueror viewer = woman
will try to use konqueror first. But this may fail (for example, if DISPLAY is not set) and in that case emacs' woman mode will be tried.
If everything fails, or if no viewer is configured, the viewer specified in the GIT_MAN_VIEWER environment variable will be tried. If that fails too, the man program will be tried anyway.
man.<tool>.path You can explicitly provide a full path to your preferred man viewer by setting the configuration variable man.<tool>.path. For example, you can configure the absolute path to konqueror by setting man.konqueror.path. Otherwise, git help assumes the tool is available in PATH.
man.<tool>.cmd When the man viewer, specified by the man.viewer configuration variables, is not among the supported ones, then the corresponding man.<tool>.cmd configuration variable will be looked up. If this variable exists then the specified tool will be treated as a custom command and a shell eval will be used to run the command with the man page passed as arguments.
Note about konqueror When konqueror is specified in the man.viewer configuration variable, we launch kfmclient to try to open the man page on an already opened konqueror in a new tab if possible.
For consistency, we also try such a trick if man.konqueror.path is set to something like A_PATH_TO/konqueror. That means we will try to launch A_PATH_TO/kfmclient instead.
If you really want to use konqueror, then you can use something like the following:
[man] viewer = konq
[man "konq"] cmd = A_PATH_TO/konqueror
Note about git config --global Note that all these configuration variables should probably be set using the --global flag, for example like this:
$ git config --global help.format web $ git config --global web.browser firefox
as they are probably more user specific than repository specific. See git-config(1) for more information about this.
SHA1SUM(1)                        User Commands                       SHA1SUM(1)
sha1sum - compute and check SHA1 message digest
sha1sum [OPTION]... [FILE]...
Print or check SHA1 (160-bit) checksums.
With no FILE, or when FILE is -, read standard input.
-b, --binary read in binary mode
-c, --check read checksums from the FILEs and check them
--tag  create a BSD-style checksum
-t, --text read in text mode (default)
-z, --zero end each output line with NUL, not newline, and disable file name escaping
The following five options are useful only when verifying checksums: --ignore-missing don't fail or report status for missing files
--quiet don't print OK for each successfully verified file
--status don't output anything, status code shows success
--strict exit non-zero for improperly formatted checksum lines
-w, --warn warn about improperly formatted checksum lines
The sums are computed as described in FIPS-180-1.  When checking, the input should be a former output of this program.  The default mode is to print a line with: checksum, a space, a character indicating input mode ('*' for binary, ' ' for text or where binary is insignificant), and name for each FILE.
Note: There is no difference between binary mode and text mode on GNU systems.
Do not use the SHA-1 algorithm for security related purposes.  Instead, use an SHA-2 algorithm, implemented in the programs sha224sum(1), sha256sum(1), sha384sum(1), sha512sum(1), or the BLAKE2 algorithm, implemented in b2sum(1)
Written by Ulrich Drepper, Scott Miller, and David Madore.
cksum(1)
Full documentation <https://www.gnu.org/software/coreutils/sha1sum> or available locally via: info '(coreutils) sha1sum invocation'
phpcs(1)                     General Commands Manual                    phpcs(1)
phpcs - PHP code sniffer CLI tool
phpcs [-nwlsaepqvi] [-d key[=value]] [--colors] [--no-colors] [--cache=cacheFile] [--no-cache] [--tab-width=tabWidth] [--report=report] [--report-file=reportFile] [--report-report=reportFile] [--report-width=reportWidth] [--basepath=basepath] [--bootstrap=bootstrap] [--severity=severity] [--error-severity=severity] [--warning-severity=severity] [--runtime-set key value] [--config-set key value] [--config-delete key] [--config-show] [--standard=standard] [--sniffs=sniffs] [--exclude=sniffs] [--encoding=encoding] [--parallel=processes] [--generator=generator] [--extensions=extensions [--ignore=patterns] [--ignore-annotations] [--stdin-path=stdinPath] [--file-list=fileList] file ...
phpcs (or PHP_CodeSniffer) is a PHP5 script that tokenises PHP, JavaScript and CSS files to detect violations of a defined coding standard. It is an essential development tool that ensures your code remains clean and consistent.  It can also help prevent some common semantic errors made by developers.
cacheFile
Use a specific file for caching (uses a temporary file by default)
One or more files and/or directories to check
The encoding of the files being checked (default is iso-8859-1)
A comma separated list of file extensions to check.  The type of the file can be specified using: ext/type e.g., module/php,es/js
Uses either the "HTML", "Markdown" or "Text" generator (forces documentation generation instead of checking)
How many files should be checked simultaneously (default is 1)
Print either the full, xml, checkstyle, csv, json, junit, emacs, source, summary, diff, svnblame, gitblame, hgblame, or notifysend report (the full report is printed by default)
reportFile
Write the report to the specified file path
reportWidth
How many columns wide screen reports should be printed or set to "auto" to use current screen width, where supported
The minimum severity required to display an error or warning
A comma separated list of sniff codes to include or exclude during checking (all sniffs must be part of the specified standard)
Do not print warnings (shortcut for --warning-severity=0)
Print both warnings and errors (this is the default)
Show sniff codes in all reports
Run interactively
Explain a standard by showing the sniffs it includes
Stop error messages from being recorded (saves a lot of memory, but stops many reports from being used)
--colors
Use colors in output
--no-colors
Do not use colors in output (this is the default)
Cache results between runs
--no-cache
Do not cache results between runs (this is the default)
phpcbf(1)
FAIL2BAN-CLIENT(1)                User Commands               FAIL2BAN-CLIENT(1)
fail2ban-client - configure and control the server
fail2ban-client [OPTIONS] <COMMAND>
Fail2Ban v0.11.2 reads log file that contains password failure report and bans the corresponding IP addresses using firewall rules.
-c, --conf <DIR> configuration directory
-s, --socket <FILE> socket path
-p, --pidfile <FILE> pidfile path
--pname <NAME> name of the process (main thread) to identify instance (default fail2ban-server)
--loglevel <LEVEL> logging level
--logtarget <TARGET> logging target, use file-name or stdout, stderr, syslog or sysout.
--syslogsocket auto|<FILE>
-d     dump configuration. For debugging
--dp, --dump-pretty dump the configuration using more human readable representation
-t, --test test configuration (can be also specified with start parameters)
-i     interactive mode
-v     increase verbosity
-q     decrease verbosity
-x     force execution of the server (remove socket file)
-b     start server in background (default)
-f     start server in foreground
--async start server in async mode (for internal usage only, don't read configuration)
--timeout timeout to wait for the server (for internal usage only, don't read configuration)
--str2sec <STRING> convert time abbreviation format to seconds
-h, --help display this help message
-V, --version print the version (-V returns machine-readable short format)
start  starts the server and the jails
restart restarts the server
restart [--unban] [--if-exists] <JAIL> restarts the jail <JAIL> (alias for 'reload --restart ... <JAIL>')
reload [--restart] [--unban] [--all] reloads the configuration without restarting of the server, the option '--restart' activates completely restarting of affected jails, thereby can unban IP addresses (if option '--unban' specified)
reload [--restart] [--unban] [--if-exists] <JAIL> reloads the jail <JAIL>, or restarts it (if option '--restart' specified)
stop   stops all jails and terminate the server
unban --all unbans all IP addresses (in all jails and database)
unban <IP> ... <IP> unbans <IP> (in all jails and database)
banned return jails with banned IPs as dictionary
banned <IP> ... <IP>] return list(s) of jails where given IP(s) are banned
status gets the current status of the server
ping   tests if the server is alive
echo   for internal usage, returns back and outputs a given string
help   return this output
version return the server version
set loglevel <LEVEL> sets logging level to <LEVEL>.  Levels: CRITICAL, ERROR, WARNING, NOTICE, INFO, DEBUG, TRACEDEBUG, HEAVYDEBUG or corresponding numeric value (50-5)
get loglevel gets the logging level
set logtarget <TARGET> sets logging target to <TARGET>.  Can be STDOUT, STDERR, SYSLOG or a file
get logtarget gets logging target
set syslogsocket auto|<SOCKET> sets the syslog socket path to auto or <SOCKET>. Only used if logtarget is SYSLOG
get syslogsocket gets syslog socket path
flushlogs flushes the logtarget if a file and reopens it. For log rotation.
set dbfile <FILE> set the location of fail2ban persistent datastore. Set to "None" to disable
get dbfile get the location of fail2ban persistent datastore
set dbmaxmatches <INT> sets the max number of matches stored in database per ticket