neulab/tldr huggingface dataset:
-A, --almost-all Do not list implied . and ..
--classic Enable classic mode (no colours or icons)
-L, --dereference When showing file information for a symbolic link, show information for the file the link references rather than for the link itself
-d, --directory-only Display directories themselves, and not their contents (recursively when used with –tree)
-X, --extensionsort Sort by file extension
--help Prints help information
-h, --human-readable For ls compatibility purposes ONLY, currently set by default
--ignore-config Ignore the configuration file
-F, --classify Append indicator (one of */=>@|) at the end of the file names
-i, --inode Display the index number of each file
-l, --long Display extended file metadata as a table
--no-symlink Do not display symlink target
-1, --oneline Display one entry per line
-R, --recursive Recurse into directories
-r, --reverse Reverse the order of the sort
-S, --sizesort Sort by size
-t, --timesort Sort by time modified
--total-size Display the total size of directories
--tree Recurse into directories and present the result as a tree
-v, --versionsort Natural sort of (version) numbers within text
--blocks <blocks>... Specify the blocks that will be displayed and in what order [possible values: permission, user, group, size, date, name, inode]
--color <color>... When to use terminal colours [default: auto] [possible values: always, auto, never]
--date <date>... How to display date [possible values: date, relative, +date-time- format] [default: date]
--depth <num>... Stop recursing into directories after reaching specified depth
--group-dirs <group-dirs>... Sort the directories then the files [default: none] [possible values: none, first, last]
--icon <icon>... When to print the icons [default: auto] [possible values: always, auto, never]
--icon-theme <icon-theme>... Whether to use fancy or unicode icons [default: fancy] [possible values: fancy, unicode]
-I, --ignore-glob <pattern>... Do not display files/directories with names matching the glob pattern(s).  More than one can be specified by repeating the argument [default: ]
--size <size>... How to display size [default: default] [possible values: default, short, bytes]
--sort <WORD>... Sort by WORD instead of name [possible values: size, time, version, extension]
<FILE>... A file or directory to list [default: .]
lsd    Display listing for current directory
lsd /etc Display listing of /etc
lsd -la Display listing of current directory, including files starting with . and the current directory’s entry.
LS_COLORS Used to determine color for displaying filenames.  See dir_colors.
XDG_CONFIG_HOME Used to locate optional config file.  If XDG_CONFIG_HOME is set, use $XDG_CONFIG_HOME/lsd/config.yaml else $HOME/.config/lsd/config.yaml.
OPENSSL-GENPKEY(1)                   OpenSSL                  OPENSSL-GENPKEY(1)
openssl-genpkey - generate a private key
openssl genpkey [-help] [-out filename] [-outform DER|PEM] [-pass arg] [-cipher] [-paramfile file] [-algorithm alg] [-pkeyopt opt:value] [-genparam] [-text] [-engine id] [-provider name] [-provider-path path] [-propquery propq] [-config configfile]
This command generates a private key.
-outform DER|PEM The output format, except when -genparam is given; the default is PEM.  See openssl-format-options(1) for details.
When -genparam is given, -outform is ignored.
-pass arg The output file password source. For more information about the format of arg see openssl-passphrase-options(1).
-cipher This option encrypts the private key with the supplied cipher. Any algorithm name accepted by EVP_get_cipherbyname() is acceptable such as des3.
-algorithm alg Public key algorithm to use such as RSA, DSA or DH. If used this option must precede any -pkeyopt options. The options -paramfile and -algorithm are mutually exclusive. Engines may add algorithms in addition to the standard built-in ones.
Valid built-in algorithm names for private key generation are RSA, RSA-PSS, EC, X25519, X448, ED25519 and ED448.
Valid built-in algorithm names for parameter generation (see the -genparam option) are DH, DSA and EC.
Note that the algorithm name X9.42 DH may be used as a synonym for the DH algorithm. These are identical and do not indicate the type of parameters that will be generated. Use the dh_paramgen_type option to indicate whether PKCS#3 or X9.42 DH parameters are required. See "DH Parameter Generation Options" below for more details.
-pkeyopt opt:value Set the public key algorithm option opt to value. The precise set of options supported depends on the public key algorithm used and its implementation. See "KEY GENERATION OPTIONS" and "PARAMETER GENERATION OPTIONS" below for more details.
-genparam Generate a set of parameters instead of a private key. If used this option must precede any -algorithm, -paramfile or -pkeyopt options.
-paramfile filename Some public key algorithms generate a private key based on a set of parameters.  They can be supplied using this option. If this option is used the public key algorithm used is determined by the parameters. If used this option must precede any -pkeyopt options. The options -paramfile and -algorithm are mutually exclusive.
-text Print an (unencrypted) text representation of private and public keys and parameters along with the PEM or DER structure.
-config configfile See "Configuration Option" in openssl(1).
The options supported by each algorithm and indeed each implementation of an algorithm can vary. The options for the OpenSSL implementations are detailed below. There are no key generation options defined for the X25519, X448, ED25519 or ED448 algorithms.
RSA Key Generation Options rsa_keygen_bits:numbits The number of bits in the generated key. If not specified 2048 is used.
rsa_keygen_primes:numprimes The number of primes in the generated key. If not specified 2 is used.
rsa_keygen_pubexp:value The RSA public exponent value. This can be a large decimal or hexadecimal value if preceded by "0x". Default value is 65537.
RSA-PSS Key Generation Options Note: by default an RSA-PSS key has no parameter restrictions.
rsa_keygen_bits:numbits, rsa_keygen_primes:numprimes, rsa_keygen_pubexp:value These options have the same meaning as the RSA algorithm.
rsa_pss_keygen_md:digest If set the key is restricted and can only use digest for signing.
rsa_pss_keygen_mgf1_md:digest If set the key is restricted and can only use digest as it's MGF1 parameter.
rsa_pss_keygen_saltlen:len If set the key is restricted and len specifies the minimum salt length.
EC Key Generation Options The EC key generation options can also be used for parameter generation.
ec_paramgen_curve:curve The EC curve to use. OpenSSL supports NIST curve names such as "P-256".
ec_param_enc:encoding The encoding to use for parameters. The encoding parameter must be either named_curve or explicit. The default value is named_curve.
The options supported by each algorithm and indeed each implementation of an algorithm can vary. The options for the OpenSSL implementations are detailed below.
DSA Parameter Generation Options dsa_paramgen_bits:numbits The number of bits in the generated prime. If not specified 2048 is used.
dsa_paramgen_q_bits:numbits qbits:numbits The number of bits in the q parameter. Must be one of 160, 224 or 256. If not specified 224 is used.
dsa_paramgen_md:digest digest:digest The digest to use during parameter generation. Must be one of sha1, sha224 or sha256. If set, then the number of bits in q will match the output size of the specified digest and the dsa_paramgen_q_bits parameter will be ignored. If not set, then a digest will be used that gives an output matching the number of bits in q, i.e. sha1 if q length is 160, sha224 if it 224 or sha256 if it is 256.
properties:query The digest property query string to use when fetching a digest from a provider.
type:type The type of generation to use. Set this to 1 to use legacy FIPS186-2 parameter generation. The default of 0 uses FIPS186-4 parameter generation.
gindex:index The index to use for canonical generation and verification of the generator g.  Set this to a positive value ranging from 0..255 to use this mode. Larger values will only use the bottom byte.  This index must then be reused during key validation to verify the value of g. If this value is not set then g is not verifiable. The default value is -1.
hexseed:seed The seed seed data to use instead of generating a random seed internally.  This should be used for testing purposes only. This will either produced fixed values for the generated parameters OR it will fail if the seed did not generate valid primes.
DH Parameter Generation Options dh_paramgen_prime_len:numbits The number of bits in the prime parameter p. The default is 2048.
dh_paramgen_subprime_len:numbits The number of bits in the sub prime parameter q. The default is 256 if the prime is at least 2048 bits long or 160 otherwise. Only relevant if used in conjunction with the dh_paramgen_type option to generate X9.42 DH parameters.
dh_paramgen_generator:value The value to use for the generator g. The default is 2.
dh_paramgen_type:value The type of DH parameters to generate. Use 0 for PKCS#3 DH and 1 for X9.42 DH.  The default is 0.
dh_rfc5114:num If this option is set, then the appropriate RFC5114 parameters are used instead of generating new parameters. The value num can be one of 1, 2 or 3 corresponding to RFC5114 DH parameters consisting of 1024 bit group with 160 bit subgroup, 2048 bit group with 224 bit subgroup and 2048 bit group with 256 bit subgroup as mentioned in RFC5114 sections 2.1, 2.2 and 2.3 respectively. If present this overrides all other DH parameter options.
EC Parameter Generation Options The EC parameter generation options are the same as for key generation. See "EC Key Generation Options" above.
The use of the genpkey program is encouraged over the algorithm specific utilities because additional algorithm options and ENGINE provided algorithms can be used.
Generate an RSA private key using default parameters:
openssl genpkey -algorithm RSA -out key.pem
Encrypt output private key using 128 bit AES and the passphrase "hello":
openssl genpkey -algorithm RSA -out key.pem -aes-128-cbc -pass pass:hello
Generate a 2048 bit RSA key using 3 as the public exponent:
openssl genpkey -algorithm RSA -out key.pem \ -pkeyopt rsa_keygen_bits:2048 -pkeyopt rsa_keygen_pubexp:3
Generate 2048 bit DSA parameters that can be validated: The output values for gindex and seed are required for key validation purposes and are not saved to the output pem file).
openssl genpkey -genparam -algorithm DSA -out dsap.pem -pkeyopt pbits:2048 \ -pkeyopt qbits:224 -pkeyopt digest:SHA256 -pkeyopt gindex:1 -text
Generate DSA key from parameters:
openssl genpkey -paramfile dsap.pem -out dsakey.pem
Generate 2048 bit DH parameters:
openssl genpkey -genparam -algorithm DH -out dhp.pem \ -pkeyopt dh_paramgen_prime_len:2048
Generate 2048 bit X9.42 DH parameters:
openssl genpkey -genparam -algorithm DH -out dhpx.pem \ -pkeyopt dh_paramgen_prime_len:2048 \ -pkeyopt dh_paramgen_type:1
Output RFC5114 2048 bit DH parameters with 224 bit subgroup:
openssl genpkey -genparam -algorithm DH -out dhp.pem -pkeyopt dh_rfc5114:2
Generate DH key from parameters:
openssl genpkey -paramfile dhp.pem -out dhkey.pem
Generate EC parameters:
openssl genpkey -genparam -algorithm EC -out ecp.pem \ -pkeyopt ec_paramgen_curve:secp384r1 \ -pkeyopt ec_param_enc:named_curve
Generate EC key from parameters:
openssl genpkey -paramfile ecp.pem -out eckey.pem
Generate EC key directly:
openssl genpkey -algorithm EC -out eckey.pem \ -pkeyopt ec_paramgen_curve:P-384 \ -pkeyopt ec_param_enc:named_curve
Generate an X25519 private key:
openssl genpkey -algorithm X25519 -out xkey.pem
Generate an ED448 private key:
openssl genpkey -algorithm ED448 -out xkey.pem
The ability to use NIST curve names, and to generate an EC key directly, were added in OpenSSL 1.0.2.  The ability to generate X25519 keys was added in OpenSSL 1.1.0.  The ability to generate X448, ED25519 and ED448 keys was added in OpenSSL 1.1.1.
The -engine option was deprecated in OpenSSL 3.0.
Copyright 2006-2020 The OpenSSL Project Authors. All Rights Reserved.
SCRAPY(1)                    General Commands Manual                   SCRAPY(1)
scrapy - the Scrapy command-line tool
scrapy [command] [OPTIONS] ...
Scrapy is controlled through the scrapy command-line tool. The script provides several commands, for different purposes. Each command supports its own particular syntax. In other words, each command supports a different set of arguments and options.
fetch [OPTION] URL Fetch a URL using the Scrapy downloader
--headers Print response HTTP headers instead of body
runspider [OPTION] spiderfile Run a spider
--output=FILE Store scraped items to FILE in XML format
settings [OPTION] Query Scrapy settings
--get=SETTING Print raw setting value
--getbool=SETTING Print setting value, intepreted as a boolean
--getint=SETTING Print setting value, intepreted as an integer
--getfloat=SETTING Print setting value, intepreted as an float
--getlist=SETTING Print setting value, intepreted as an float
--init Print initial setting value (before loading extensions and spiders)
shell URL | file Launch the interactive scraping console
startproject projectname Create new project with an initial project template
--help, -h Print command help and options
--logfile=FILE Log file. if omitted stderr will be used
--loglevel=LEVEL, -L LEVEL Log level (default: None)
--nolog Disable logging completely
--spider=SPIDER Always use this spider when arguments are urls
--profile=FILE Write python cProfile stats to FILE
--lsprof=FILE Write lsprof profiling stats to FILE
--pidfile=FILE Write process ID to FILE
--set=NAME=VALUE, -s NAME=VALUE Set/override setting (may be repeated)
Scrapy was written by the Scrapy Developers.
This manual page was written by Ignace Mouzannar <mouzannar@gmail.com>, for the Debian project (but may be used by others).
WG(8)                               WireGuard                              WG(8)
wg - set and retrieve configuration of WireGuard interfaces
wg [ COMMAND ] [ OPTIONS ]... [ ARGS ]...
wg is the configuration utility for getting and setting the configuration of WireGuard tunnel interfaces. The interfaces themselves can be added and removed using ip-link(8) and their IP addresses and routing tables can be set using ip-address(8) and ip-route(8).  The wg utility provides a series of sub-commands for changing WireGuard-specific aspects of WireGuard interfaces.
If no COMMAND is specified, COMMAND defaults to show.  Sub-commands that take an INTERFACE must be passed a WireGuard interface.
show { <interface> | all | interfaces } [public-key | private-key | listen-port | fwmark | peers | preshared-keys | endpoints | allowed-ips | latest-handshakes | persistent-keepalive | transfer | dump] Shows current WireGuard configuration and runtime information of specified <interface>.  If no <interface> is specified, <interface> defaults to all.  If interfaces is specified, prints a list of all WireGuard interfaces, one per line, and quits. If no options are given after the interface specification, then prints a list of all attributes in a visually pleasing way meant for the terminal. Otherwise, prints specified information grouped by newlines and tabs, meant to be used in scripts. For this script- friendly display, if all is specified, then the first field for all categories of information is the interface name. If dump is specified, then several lines are printed; the first contains in order separated by tab: private-key, public-key, listen-port, fwmark. Subsequent lines are printed for each peer and contain in order separated by tab: public-key, preshared-key, endpoint, allowed-ips, latest-handshake, transfer-rx, transfer-tx, persistent-keepalive.
showconf <interface> Shows the current configuration of <interface> in the format described by CONFIGURATION FILE FORMAT below.
set <interface> [listen-port <port>] [fwmark <fwmark>] [private-key <file-path>] [peer <base64-public-key> [remove] [preshared-key <file- path>] [endpoint <ip>:<port>] [persistent-keepalive <interval seconds>] [allowed-ips <ip1>/<cidr1>[,<ip2>/<cidr2>]...] ]... Sets configuration values for the specified <interface>. Multiple peers may be specified, and if the remove argument is given for a peer, that peer is removed, not configured. If listen-port is not specified, or set to 0, the port will be chosen randomly when the interface comes up. Both private-key and preshared-key must be files, because command line arguments are not considered private on most systems but if you are using bash(1), you may safely pass in a string by specifying as private-key or preshared-key the expression: <(echo PRIVATEKEYSTRING). If /dev/null or another empty file is specified as the filename for either private-key or preshared-key, the key is removed from the device. The use of preshared-key is optional, and may be omitted; it adds an additional layer of symmetric-key cryptography to be mixed into the already existing public-key cryptography, for post-quantum resistance.  If allowed-ips is specified, but the value is the empty string, all allowed ips are removed from the peer. The use of persistent-keepalive is optional and is by default off; setting it to 0 or "off" disables it.  Otherwise it represents, in seconds, between 1 and 65535 inclusive, how often to send an authenticated empty packet to the peer, for the purpose of keeping a stateful firewall or NAT mapping valid persistently. For example, if the interface very rarely sends traffic, but it might at anytime receive traffic from a peer, and it is behind NAT, the interface might benefit from having a persistent keepalive interval of 25 seconds; however, most users will not need this. The use of fwmark is optional and is by default off; setting it to 0 or "off" disables it. Otherwise it is a 32-bit fwmark for outgoing packets and may be specified in hexadecimal by prepending "0x".
setconf <interface> <configuration-filename> Sets the current configuration of <interface> to the contents of <configuration-filename>, which must be in the format described by CONFIGURATION FILE FORMAT below.
addconf <interface> <configuration-filename> Appends the contents of <configuration-filename>, which must be in the format described by CONFIGURATION FILE FORMAT below, to the current configuration of <interface>.
syncconf <interface> <configuration-filename> Like setconf, but reads back the existing configuration first and only makes changes that are explicitly different between the configuration file and the interface. This is much less efficient than setconf, but has the benefit of not disrupting current peer sessions. The contents of <configuration-filename> must be in the format described by CONFIGURATION FILE FORMAT below.
genkey Generates a random private key in base64 and prints it to standard output.
genpsk Generates a random preshared key in base64 and prints it to standard output.
pubkey Calculates a public key and prints it in base64 to standard output from a corresponding private key (generated with genkey) given in base64 on standard input.
A private key and a corresponding public key may be generated at once by calling: $ umask 077 $ wg genkey | tee private.key | wg pubkey > public.key
help   Shows usage message.
The configuration file format is based on INI. There are two top level sections -- Interface and Peer. Multiple Peer sections may be specified, but only one Interface section may be specified.
The Interface section may contain the following fields:
•      PrivateKey — a base64 private key generated by wg genkey. Required.
•      ListenPort — a 16-bit port for listening. Optional; if not specified, chosen randomly.
•      FwMark — a 32-bit fwmark for outgoing packets. If set to 0 or "off", this option is disabled. May be specified in hexadecimal by prepending "0x". Optional.
The Peer sections may contain the following fields:
•      PublicKey — a base64 public key calculated by wg pubkey from a private key, and usually transmitted out of band to the author of the configuration file. Required.
•      PresharedKey — a base64 preshared key generated by wg genpsk. Optional, and may be omitted. This option adds an additional layer of symmetric-key cryptography to be mixed into the already existing public-key cryptography, for post-quantum resistance.
•      AllowedIPs — a comma-separated list of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed. The catch-all 0.0.0.0/0 may be specified for matching all IPv4 addresses, and ::/0 may be specified for matching all IPv6 addresses. May be specified multiple times.
•      Endpoint — an endpoint IP or hostname, followed by a colon, and then a port number. This endpoint will be updated automatically to the most recent source IP address and port of correctly authenticated packets from the peer.  Optional.
•      PersistentKeepalive — a seconds interval, between 1 and 65535 inclusive, of how often to send an authenticated empty packet to the peer for the purpose of keeping a stateful firewall or NAT mapping valid persistently. For example, if the interface very rarely sends traffic, but it might at anytime receive traffic from a peer, and it is behind NAT, the interface might benefit from having a persistent keepalive interval of 25 seconds. If set to 0 or "off", this option is disabled. By default or when unspecified, this option is off. Most users will not need this. Optional.
This example may be used as a model for writing configuration files, following an INI-like syntax. Characters after and including a '#' are considered comments and are thus ignored.
[Interface] PrivateKey = yAnz5TF+lXXJte14tji3zlMNq+hd2rYUIgJBgB3fBmk= ListenPort = 51820
[Peer] PublicKey = xTIBA5rboUvnH4htodjb6e697QjLERt1NAB4mZqp8Dg= Endpoint = 192.95.5.67:1234 AllowedIPs = 10.192.122.3/32, 10.192.124.1/24
[Peer] PublicKey = TrMvSoP4jYQlY6RIzBgbssQqY3vxI2Pi+y71lOWWXX0= Endpoint = [2607:5300:60:6b0::c05f:543]:2468 AllowedIPs = 10.192.122.4/32, 192.168.0.0/16
[Peer] PublicKey = gN65BkIKy1eCE9pP1wdc8ROUtkHLF2PfAqYdyYBz6EA= Endpoint = test.wireguard.com:18981 AllowedIPs = 10.10.10.230/32
Sometimes it is useful to have information on the current runtime state of a tunnel. When using the Linux kernel module on a kernel that supports dynamic debugging, debugging information can be written into dmesg(1) by running as root:
# modprobe wireguard && echo module wireguard +p > /sys/kernel/debug/dynamic_debug/control
On OpenBSD and FreeBSD, debugging information can be written into dmesg(1) on a per-interface basis by using ifconfig(1):
# ifconfig wg0 debug
On userspace implementations, it is customary to set the LOG_LEVEL environment variable to verbose.
WG_COLOR_MODE If set to always, always print ANSI colorized output. If set to never, never print ANSI colorized output. If set to auto, something invalid, or unset, then print ANSI colorized output only when writing to a TTY.
WG_HIDE_KEYS If set to never, then the pretty-printing show sub-command will show private and preshared keys in the output. If set to always, something invalid, or unset, then private and preshared keys will be printed as "(hidden)".
WG_ENDPOINT_RESOLUTION_RETRIES If set to an integer or to infinity, DNS resolution for each peer's endpoint will be retried that many times for non-permanent errors, with an increasing delay between retries. If unset, the default is 15 retries.
wg-quick(8), ip(8), ip-link(8), ip-address(8), ip-route(8).
wg was written by Jason A. Donenfeld ⟨Jason@zx2c4.com⟩.  For updates and more information, a project page is available on the World Wide Web ⟨https://www.wireguard.com/⟩.
JDUPES(1)                    General Commands Manual                   JDUPES(1)
jdupes - finds and performs actions upon duplicate files
jdupes [ options ] DIRECTORIES ...
Searches the given path(s) for duplicate files. Such files are found by comparing file sizes, then partial and full file hashes, followed by a byte-by-byte comparison. The default behavior with no other "action options" specified (delete, summarize, link, dedupe, etc.) is to print sets of matching files.
-@ --loud output annoying low-level debug info while running
-0 --print-null when printing matches, use null bytes instead of CR/LF bytes, just like 'find -print0' does. This has no effect with any action mode other than the default "print matches" (delete, link, etc. will still print normal line endings in the output.)
-1 --one-file-system do not match files that are on different filesystems or devices
-A --no-hidden exclude hidden files from consideration
-B --dedupe issue the btrfs same-extents ioctl to trigger a deduplication on disk. The program must be built with btrfs support for this option to be available
-C --chunk-size=BYTES set the I/O chunk size manually; larger values may improve performance on rotating media by reducing the number of head seeks required, but also increases memory usage and can reduce performance in some cases
-D --debug if this feature is compiled in, show debugging statistics and info at the end of program execution
-f --omit-first omit the first file in each set of matches
-H --hard-links normally, when two or more files point to the same disk area they are treated as non-duplicates; this option will change this behavior
-i --reverse reverse (invert) the sort order of matches
-I --isolate isolate each command-line parameter from one another; only match if the files are under different parameter specifications
-L --link-hard replace all duplicate files with hardlinks to the first file in each set of duplicates
-M --print-summarize print matches and summarize the duplicate file information at the end
-N --no-prompt when used together with --delete, preserve the first file in each set of duplicates and delete the others without prompting the user
-O --param-order parameter order preservation is more important than the chosen sort; this is particularly useful with the -N option to ensure that automatic deletion behaves in a controllable way
-o --order=WORD order files according to WORD: time - sort by modification time name - sort by filename (default)
-P --print=type print extra information to stdout; valid options are: early - matches that pass early size/permission/link/etc. checks partial - files whose partial hashes match fullhash - files whose full hashes match
-Q --quick [WARNING: RISK OF DATA LOSS, SEE CAVEATS] skip byte-for-byte verification of duplicate pairs (use hashes only)
-l --link-soft replace all duplicate files with symlinks to the first file in each set of duplicates
-T --partial-only [WARNING: EXTREME RISK OF DATA LOSS, SEE CAVEATS] match based on hash of first block of file data, ignoring the rest
-u --print-unique print only a list of unique (non-duplicate, unmatched) files
-v --version display jdupes version and compilation feature flags
-X --ext-filter=spec:info exclude/filter files based on specified criteria; general format:
jdupes -X filter[:value][size_suffix]
Some filters take no value or multiple values. Filters that can take a numeric option generally support the size multipliers K/M/G/T/P/E with or without an added iB or B. Multipliers are binary-style unless the -B suffix is used, which will use decimal multipliers. For example, 16k or 16kib = 16384; 16kb = 16000. Multipliers are case-insensitive.
Filters have cumulative effects: jdupes -X size+:99 -X size-:101 will cause only files of exactly 100 bytes in size to be included.
Extension matching is case-insensitive.  Path substring matching is case-sensitive.
Supported filters are:
`size[+-=]:number[suffix]' match only if size is greater (+), less than (-), or equal to (=) the specified number. The +/- and = specifiers can be combined, i.e.  "size+=:4K" will only consider files with a size greater than or equal to four kilobytes (4096 bytes).
`noext:ext1[,ext2,...]' exclude files with certain extension(s), specified as a comma-separated list. Do not use a leading dot.
`onlyext:ext1[,ext2,...]' only include files with certain extension(s), specified as a comma-separated list. Do not use a leading dot.
`nostr:text_string' exclude all paths containing the substring text_string. This scans the full file path, so it can be used to match directories: -X nostr:dir_name/
`onlystr:text_string' require all paths to contain the substring text_string. This scans the full file path, so it can be used to match directories: -X onlystr:dir_name/
`newer:datetime` only include files newer than specified date.  Date/time format: "YYYY-MM-DD HH:MM:SS" (time is optional).
`older:datetime` only include files older than specified date.  Date/time format: "YYYY-MM-DD HH:MM:SS" (time is optional).
-z --zero-match consider zero-length files to be duplicates; this replaces the old default behavior when -n was not specified
-Z --soft-abort if the user aborts the program (as with CTRL-C) act on the matches that were found before the abort was received. For example, if -L and -Z are specified, all matches found prior to the abort will be hard linked. The default behavior without -Z is to abort without taking any actions.
A set of arrows are used in hard linking to show what action was taken on each link candidate. These arrows are as follows:
---->  This file was successfully hard linked to the first file in the duplicate chain
-@@->  This file was successfully symlinked to the first file in the chain
-==->  This file was already a hard link to the first file in the chain
-//->  Linking this file failed due to an error during the linking process
Duplicate files are listed together in groups with each file displayed on a separate line. The groups are then separated from each other by blank lines.
jdupes a --recurse: b will follow subdirectories under b, but not those under a.
jdupes a --recurse b will follow subdirectories under both a and b.
jdupes -O dir1 dir3 dir2 will always place 'dir1' results first in any match set (where relevant)
Using -1 or --one-file-system prevents matches that cross filesystems, but a more relaxed form of this option may be added that allows cross- matching for all filesystems that each parameter is present on.
-Z or --soft-abort used to be --hardabort in jdupes prior to v1.5 and had the opposite behavior.  Defaulting to taking action on abort is probably not what most users would expect. The decision to invert rather than reassign to a different option was made because this feature was still fairly new at the time of the change.
The -O or --param-order option allows the user greater control over what appears in the first position of a match set, specifically for keeping the -N option from deleting all but one file in a set in a seemingly random way. All directories specified on the command line will be used as the sorting order of result sets first, followed by the sorting algorithm set by the -o or --order option. This means that the order of all match pairs for a single directory specification will retain the old sorting behavior even if this option is specified.
The -Q or --quick option only reads each file once, hashes it, and performs comparisons based solely on the hashes. There is a small but significant risk of a hash collision which is the purpose of the failsafe byte-for-byte comparison that this option explicitly bypasses. Do not use it on ANY data set for which any amount of data loss is unacceptable. This option is not included in the help text for the program due to its risky nature.  You have been warned!
The -T or --partial-only option produces results based on a hash of the first block of file data in each file, ignoring everything else in the file. Partial hash checks have always been an important exclusion step in the jdupes algorithm, usually hashing the first 4096 bytes of data and allowing files that are different at the start to be rejected early. In certain scenarios it may be a useful heuristic for a user to see that a set of files has the same size and the same starting data, even if the remaining data does not match; one example of this would be comparing files with data blocks that are damaged or missing such as an incomplete file transfer or checking a data recovery against known-good copies to see what damaged data can be deleted in favor of restoring the known-good copy. This option is meant to be used with informational actions and can result in EXTREME DATA LOSS if used with options that delete files, create hard links, or perform other destructive actions on data based on the matching output. Because of the potential for massive data destruction, this option MUST BE SPECIFIED TWICE to take effect and will error out if it is only specified once.
Using the -C or --chunk-size option to override I/O chunk size can increase performance on rotating storage media by reducing "head thrashing," reading larger amounts of data sequentially from each file. This tunable size can have bad side effects; the default size maximizes algorithmic performance without regard to the I/O characteristics of any given device and uses a modest amount of memory, but other values may greatly increase memory usage or incur a lot more system call overhead. Try several different values to see how they affect performance for your hardware and data set. This option does not affect match results in any way, so even if it slows down the file matching process it will not hurt anything.
Send bug reports to jody@jodybruchon.com or use the issue tracker at:
http://github.com/jbruchon/jdupes/issues
If you find this software useful, please consider financially supporting its development through the author's home page:
https://www.jodybruchon.com/
jdupes is created and maintained by Jody Bruchon <jody@jodybruchon.com> and was forked from fdupes 1.51 by Adrian Lopez <adrian2@caribe.net>
Copyright (C) 2015-2021 Jody Lee Bruchon and contributors Forked from fdupes 1.51, Copyright (C) 1999-2014 Adrian Lopez and contributors
QRENCODE(1)                  General Commands Manual                 QRENCODE(1)
qrencode - Encode input data in a QR Code and save as a PNG or EPS image.
qrencode [-o FILENAME] [OPTION]...  [STRING]
Libqrencode is a library for encoding data in a QR Code symbol, a kind of 2D symbology that can be scanned by handy terminals such as a mobile phone with CCD. The capacity of QR Code is up to 7000 digits or 4000 characters, and has high robustness.
Qrencode is a utility software using libqrencode to encode string data in a QR Code and save as a PNG or EPS image.
-h, --help display help message.
-o FILENAME, --output=FILENAME write image to FILENAME. If '-' is specified, the result will be output to standard output. If -S is given, structured symbols are written to FILENAME-01.png, FILENAME-02.png, ... (suffix is removed from FILENAME, if specified)
-r FILENAME, --read-from=FILENAME read input data from FILENAME.
-s NUMBER, --size=NUMBER specify the size of dot (pixel). (default=3)
-l {LMQH}, --level={LMQH} specify error correction level from L (lowest) to H (highest). (default=L)
-v NUMBER, --symversion=NUMBER specify the minimum version of the symbol. See SYMBOL VERSIONS for more information. (default=auto)
-m NUMBER, --margin=NUMBER specify the width of margin. (default=4)
-d NUMBER, --dpi=NUMBER specify the DPI of the generated PNG. (default=72)
-t {PNG,PNG32,EPS,SVG,XPM,ANSI,ANSI256,ASCII,ASCIIi,UTF8,UTF8i,ANSIUTF8,ANSIUTF8i,ANSI256UTF8} --type={PNG,PNG32,EPS,SVG,XPM,ANSI,ANSI256,ASCII,ASCIIi,UTF8,UTF8i,ANSIUTF8,ANSIUTF8i,ANSI256UTF8} specify the type of the generated image. (default=PNG)
-S, --structured make structured symbols. Version number must be specified with '-v'.
-k, --kanji assume that the input text contains kanji (shift-jis).
-c, --casesensitive encode lower-case alphabet characters in 8-bit mode. (default)
-i, --ignorecase ignore case distinctions and use only upper-case characters.
-8, --8bit encode entire data in 8-bit mode. -k, -c and -i will be ignored.
-M, --micro encode in a Micro QR Code. See MICRO QR CODE for more information.
--rle  enable run-length encoding for SVG.
--svg-path use single path to draw modules for SVG.
--inline only useful for SVG output, generates an SVG without the XML tag.
--foreground=RRGGBB[AA] --background=RRGGBB[AA] specify foreground/background color in hexadecimal notation. 6-digit (RGB) or 8-digit (RGBA) form are supported.  Color output support available only in PNG, EPS and SVG.
--strict-version disable automatic version number adjustment. If the input data is too large for the specified version, the program exits with the code of 1.
-V, --version display the version number and copyrights of the qrencode.
--verbose display verbose information to stderr.
[STRING] input data. If it is not specified, data will be taken from standard input.
The symbol versions of QR Code range from Version 1 to Version 40.  Each version has a different module configuration or number of modules, ranging from Version 1 (21 x 21 modules) up to Version 40 (177 x 177 modules).  Each higher version number comprises 4 additional modules per side by default.  See http://www.qrcode.com/en/about/version.html for a detailed version list.
With Micro QR Code, You can embed data in a smaller area than with QR Code, but the data capacity is strongly limited. The symbol versions range from Version 1 to 4.
qrencode -l L -v 1 -o output.png 'Hello, world!' encode into a symbol version 1, level L.
qrencode -iSv 1 --output=output.png read standard input and encode it into a structured-appended symbols in case-insensitive mode.
qrencode -S -v 40 -l L -r bigfile.txt -o output.png read input data from bigfile.txt and encode into a symbol version 40, level L.
Written by Kentaro Fukuchi.
Main Web Site: https://fukuchi.org/works/qrencode/
Source code repository: https://github.com/fukuchi/libqrencode/
Copyright (C) 2006-2018 Kentaro Fukuchi.
GIT-PRUNE(1)                       Git Manual                       GIT-PRUNE(1)
git-prune - Prune all unreachable objects from the object database
git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...]
Note In most cases, users should run git gc, which calls git prune. See the section "NOTES", below.
This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the unpacked objects that are also found in packs by running git prune-packed. It also removes entries from .git/shallow that are not reachable by any ref.
Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1).
-n, --dry-run Do not remove anything; just report what it would remove.
-v, --verbose Report all removed objects.
--progress Show progress.
--expire <time> Only expire loose objects older than <time>.
<head>... In addition to objects reachable from any of our references, keep objects reachable from listed <head>s.
To prune objects not used by your repository or another that borrows from your repository via its .git/objects/info/alternates:
$ git prune $(cd ../another && git rev-parse --all)
In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other housekeeping tasks.
For a description of which objects are considered for pruning, see git fsck's --unreachable option.
git-fsck(1), git-gc(1), git-reflog(1)
MTR(8)                        System Administration                       MTR(8)
mtr - a network diagnostic tool
mtr [-4|-6] [-F FILENAME] [--report] [--report-wide] [--xml] [--gtk] [--curses] [--displaymode MODE] [--raw] [--csv] [--json] [--split] [--no- dns] [--show-ips] [-o FIELDS] [-y IPINFO] [--aslookup] [-i INTERVAL] [-c COUNT] [-s PACKETSIZE] [-B BITPATTERN] [-G GRACEPERIOD] [-Q TOS] [--mpls] [-I NAME] [-a ADDRESS] [-f FIRST-TTL] [-m MAX-TTL] [-U MAX-UNKNOWN] [--udp] [--tcp] [--sctp] [-P PORT] [-L LOCALPORT] [-Z TIMEOUT] [-M MARK] HOSTNAME
mtr combines the functionality of the traceroute and ping programs in a single network diagnostic tool.
As mtr starts, it investigates the network connection between the host mtr runs on and HOSTNAME by sending packets with purposely low TTLs.  It continues to send packets with low TTL, noting the response time of the intervening routers.  This allows mtr to print the response percentage and response times of the internet route to HOSTNAME.  A sudden increase in packet loss or response time is often an indication of a bad (or simply overloaded) link.
The results are usually reported as round-trip-response times in milliseconds and the percentage of packet loss.
-h, --help Print the summary of command line argument options.
-v, --version Print the installed version of mtr.
-4     Use IPv4 only.
-6     Use IPv6 only.  (IPV4 may be used for DNS lookups.)
-F FILENAME, --filename FILENAME Reads the list of hostnames from the specified file.
-r, --report This option puts mtr into report mode.  When in this mode, mtr will run for the number of cycles specified by the -c option, and then print statistics and exit.
This mode is useful for generating statistics about network quality. Note that each running instance of mtr generates a significant amount of network traffic.  Using mtr to measure the quality of your network may result in decreased network performance.
-w, --report-wide This option puts mtr into wide report mode.  When in this mode, mtr will not cut hostnames in the report.
-x, --xml Use this option to tell mtr to use the xml output format.  This format is better suited for automated processing of the measurement results.
-t, --curses Use this option to force mtr to use the curses based terminal interface (if available).  In case the list of hops exceeds the height of your terminal, you can use the + and - keys to scroll up and down half a page.
Ctrl-L clears spurious error messages that may overwrite other parts of the display.
--displaymode MODE Use this option to select the initial display mode: 0 (default) selects statistics, 1 selects the stripchart without latency information, and 2 selects the stripchart with latency information.
-g, --gtk Use this option to force mtr to use the GTK+ based X11 window interface (if available).  GTK+ must have been available on the system when mtr was built for this to work.  See the GTK+ web page at ⟨http://www.gtk.org/⟩ for more information about GTK+.
-l, --raw Use the raw output format.  This format is better suited for archival of the measurement results.  It could be parsed to be presented into any of the other display methods.
Example of the raw output format: h 0 10.1.1.1 p 0 339 h 1 46.149.16.4 p 1 530 h 2 172.31.1.16 p 2 531 h 3 82.221.168.236 p 3 1523 h 5 195.130.211.8 p 5 1603 h 6 193.4.58.17 p 6 1127 h 7 193.4.58.17 d 7 www.isnic.is
-C, --csv Use the Comma-Separated-Value (CSV) output format.  (Note: The separator is actually a semi-colon ';'.)
Example of the CSV output format: MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;1;r-76520-PROD.greenqloud.internal;288 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;2;46.149.16.4;2086 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;3;172.31.1.16;600 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;4;82.221.168.236;1163 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;5;???;0 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;6;rix-k2-gw.isnic.is;1654 MTR.0.86+git:16e39fc0;1435562787;OK;nic.is;7;www.isnic.is;1036
-j, --json Use this option to tell mtr to use the JSON output format.  This format is better suited for automated processing of the measurement results.  Jansson library must have been available on the system when mtr was built for this to work.
-p, --split Use this option to set mtr to spit out a format that is suitable for a split-user interface.
-n, --no-dns Use this option to force mtr to display numeric IP numbers and not try to resolve the host names.
-b, --show-ips Use this option to tell mtr to display both the host names and numeric IP numbers.  In split mode this adds an extra field to the output.  In report mode, there is usually too little space to add the IPs, and they will be truncated.  Use the wide report (-w) mode to see the IPs in report mode.
-o FIELDS, --order FIELDS Use this option to specify which fields to display and in which order.  You may use one or more space characters to separate fields. Available fields:
┌──┬─────────────────────┐ │L │ Loss ratio          │ ├──┼─────────────────────┤ │D │ Dropped packets     │ ├──┼─────────────────────┤ │R │ Received packets    │ ├──┼─────────────────────┤ │S │ Sent Packets        │ ├──┼─────────────────────┤ │N │ Newest RTT(ms)      │ ├──┼─────────────────────┤ │B │ Min/Best RTT(ms)    │ ├──┼─────────────────────┤ │A │ Average RTT(ms)     │ ├──┼─────────────────────┤ │W │ Max/Worst RTT(ms)   │ ├──┼─────────────────────┤ │V │ Standard Deviation  │ ├──┼─────────────────────┤ │G │ Geometric Mean      │ ├──┼─────────────────────┤ │J │ Current Jitter      │ ├──┼─────────────────────┤ │M │ Jitter Mean/Avg.    │ ├──┼─────────────────────┤ │X │ Worst Jitter        │ ├──┼─────────────────────┤ │I │ Interarrival Jitter │ └──┴─────────────────────┘ Example: -o "LSD NBAW  X"
-y n, --ipinfo n Displays information about each IP hop.  Valid values for n are:
0   Display AS number (equivalent to -z) 1   Display IP prefix 2   Display country code of the origin AS 3   Display RIR (ripencc, arin, ...) 4   Display the allocation date of the IP prefix
It is possible to cycle between these fields at runtime (using the y key).
-z, --aslookup Displays the Autonomous System (AS) number alongside each hop. Equivalent to --ipinfo 0.
Example (columns to the right not shown for clarity): 1. AS???   r-76520-PROD.greenqloud.internal 2. AS51969 46.149.16.4 3. AS???   172.31.1.16 4. AS30818 82.221.168.236 5. ??? 6. AS???   rix-k2-gw.isnic.is 7. AS1850  www.isnic.is
-i SECONDS, --interval SECONDS Use this option to specify the positive number of seconds between ICMP ECHO requests.  The default value for this parameter is one second.  The root user may choose values between zero and one.
-c COUNT, --report-cycles COUNT Use this option to set the number of pings sent to determine both the machines on the network and the reliability of those machines. Each cycle lasts one second.
-s PACKETSIZE, --psize PACKETSIZE This option sets the packet size used for probing.  It is in bytes, inclusive IP and ICMP headers.
If set to a negative number, every iteration will use a different, random packet size up to that number.
-B NUM, --bitpattern NUM Specifies bit pattern to use in payload.  Should be within range 0 - 255.  If NUM is greater than 255, a random pattern is used.
-G SECONDS, --gracetime SECONDS Use this option to specify the positive number of seconds to wait for responses after the final request. The default value is five seconds.
-Q NUM, --tos NUM Specifies value for type of service field in IP header.  Should be within range 0 - 255.
-e, --mpls Use this option to tell mtr to display information from ICMP extensions for MPLS (RFC 4950) that are encoded in the response packets.
-I NAME, --interface NAME Use the network interface with a specific name for sending network probes.  This can be useful when you have multiple network interfaces with routes to your destination, for example both wired Ethernet and WiFi, and wish to test a particular interface.
-a ADDRESS, --address ADDRESS Use this option to bind the outgoing socket to ADDRESS, so that all packets will be sent with ADDRESS as source address.  NOTE that this option doesn't apply to DNS requests (which could be and could not be what you want).
-f NUM, --first-ttl NUM Specifies with what TTL to start.  Defaults to 1.
-m NUM, --max-ttl NUM Specifies the maximum number of hops (max time-to-live value) traceroute will probe.  Default is 30.
-U NUM, --max-unknown NUM Specifies the maximum unknown host. Default is 5.
-u, --udp Use UDP datagrams instead of ICMP ECHO.
-T, --tcp Use TCP SYN packets instead of ICMP ECHO.  PACKETSIZE is ignored, since SYN packets can not contain data.
-S, --sctp Use Stream Control Transmission Protocol packets instead of ICMP ECHO.
-P PORT, --port PORT The target port number for TCP/SCTP/UDP traces.
-L LOCALPORT, --localport LOCALPORT The source port number for UDP traces.
-Z SECONDS, --timeout SECONDS The number of seconds to keep probe sockets open before giving up on the connection.  Using large values for this, especially combined with a short interval, will use up a lot of file descriptors.
-M MARK, --mark MARK Set the mark for each packet sent through this socket similar to the netfilter MARK target but socket-based.  MARK is 32 unsigned integer.  See socket(7) for full description of this socket option.
mtr recognizes a few environment variables.