neulab/tldr huggingface dataset:
• --keep-env-derivations Enable the keep-env-derivations setting.
• --keep-failed Enable the keep-failed setting.
• --keep-going Enable the keep-going setting.
• --keep-outputs Enable the keep-outputs setting.
• --log-lines value Set the log-lines setting.
• --max-build-log-size value Set the max-build-log-size setting.
• --max-free value Set the max-free setting.
• --max-jobs value Set the max-jobs setting.
• --max-silent-time value Set the max-silent-time setting.
• --min-free value Set the min-free setting.
• --min-free-check-interval value Set the min-free-check-interval setting.
• --nar-buffer-size value Set the nar-buffer-size setting.
• --narinfo-cache-negative-ttl value Set the narinfo-cache-negative-ttl setting.
• --narinfo-cache-positive-ttl value Set the narinfo-cache-positive-ttl setting.
• --netrc-file value Set the netrc-file setting.
• --nix-path value Set the nix-path setting.
• --no-allow-dirty Disable the allow-dirty setting.
• --no-allow-import-from-derivation Disable the allow-import-from-derivation setting.
• --no-allow-new-privileges Disable the allow-new-privileges setting.
• --no-allow-symlinked-store Disable the allow-symlinked-store setting.
• --no-allow-unsafe-native-code-during-evaluation Disable the allow-unsafe-native-code-during-evaluation setting.
• --no-auto-optimise-store Disable the auto-optimise-store setting.
• --no-builders-use-substitutes Disable the builders-use-substitutes setting.
• --no-compress-build-log Disable the compress-build-log setting.
• --no-enforce-determinism Disable the enforce-determinism setting.
• --no-eval-cache Disable the eval-cache setting.
• --no-fallback Disable the fallback setting.
• --no-filter-syscalls Disable the filter-syscalls setting.
• --no-fsync-metadata Disable the fsync-metadata setting.
• --no-http2 Disable the http2 setting.
• --no-impersonate-linux-26 Disable the impersonate-linux-26 setting.
• --no-keep-build-log Disable the keep-build-log setting.
• --no-keep-derivations Disable the keep-derivations setting.
• --no-keep-env-derivations Disable the keep-env-derivations setting.
• --no-keep-failed Disable the keep-failed setting.
• --no-keep-going Disable the keep-going setting.
• --no-keep-outputs Disable the keep-outputs setting.
• --no-preallocate-contents Disable the preallocate-contents setting.
• --no-print-missing Disable the print-missing setting.
• --no-pure-eval Disable the pure-eval setting.
• --no-require-sigs Disable the require-sigs setting.
• --no-restrict-eval Disable the restrict-eval setting.
• --no-run-diff-hook Disable the run-diff-hook setting.
• --no-sandbox Disable sandboxing.
• --no-sandbox-fallback Disable the sandbox-fallback setting.
• --no-show-trace Disable the show-trace setting.
• --no-substitute Disable the substitute setting.
• --no-sync-before-registering Disable the sync-before-registering setting.
• --no-trace-function-calls Disable the trace-function-calls setting.
• --no-use-case-hack Disable the use-case-hack setting.
• --no-use-registries Disable the use-registries setting.
• --no-use-sqlite-wal Disable the use-sqlite-wal setting.
• --no-warn-dirty Disable the warn-dirty setting.
• --plugin-files value Set the plugin-files setting.
• --post-build-hook value Set the post-build-hook setting.
• --pre-build-hook value Set the pre-build-hook setting.
• --preallocate-contents Enable the preallocate-contents setting.
• --print-missing Enable the print-missing setting.
• --pure-eval Enable the pure-eval setting.
• --relaxed-sandbox Enable sandboxing, but allow builds to disable it.
• --repeat value Set the repeat setting.
• --require-sigs Enable the require-sigs setting.
• --restrict-eval Enable the restrict-eval setting.
• --run-diff-hook Enable the run-diff-hook setting.
• --sandbox Enable sandboxing.
• --sandbox-build-dir value Set the sandbox-build-dir setting.
• --sandbox-dev-shm-size value Set the sandbox-dev-shm-size setting.
• --sandbox-fallback Enable the sandbox-fallback setting.
• --sandbox-paths value Set the sandbox-paths setting.
• --secret-key-files value Set the secret-key-files setting.
• --show-trace Enable the show-trace setting.
• --stalled-download-timeout value Set the stalled-download-timeout setting.
• --store value Set the store setting.
• --substitute Enable the substitute setting.
• --substituters value Set the substituters setting.
• --sync-before-registering Enable the sync-before-registering setting.
• --system value Set the system setting.
• --system-features value Set the system-features setting.
• --tarball-ttl value Set the tarball-ttl setting.
• --timeout value Set the timeout setting.
• --trace-function-calls Enable the trace-function-calls setting.
• --trusted-public-keys value Set the trusted-public-keys setting.
• --trusted-substituters value Set the trusted-substituters setting.
• --trusted-users value Set the trusted-users setting.
• --use-case-hack Enable the use-case-hack setting.
• --use-registries Enable the use-registries setting.
• --use-sqlite-wal Enable the use-sqlite-wal setting.
• --user-agent-suffix value Set the user-agent-suffix setting.
• --warn-dirty Enable the warn-dirty setting.
PASSWD(1)                         User Commands                        PASSWD(1)
passwd - change user password
passwd [options] [LOGIN]
The passwd command changes passwords for user accounts. A normal user may only change the password for their own account, while the superuser may change the password for any account.  passwd also changes the account or associated password validity period.
Password Changes The user is first prompted for their old password, if one is present. This password is then encrypted and compared against the stored password. The user has only one chance to enter the correct password. The superuser is permitted to bypass this step so that forgotten passwords may be changed.
After the password has been entered, password aging information is checked to see if the user is permitted to change the password at this time. If not, passwd refuses to change the password and exits.
The user is then prompted twice for a replacement password. The second entry is compared against the first and both are required to match in order for the password to be changed.
Then, the password is tested for complexity. As a general guideline, passwords should consist of 6 to 8 characters including one or more characters from each of the following sets:
•   lower case alphabetics
•   digits 0 thru 9
•   punctuation marks
Care must be taken not to include the system default erase or kill characters.  passwd will reject any password which is not suitably complex.
Hints for user passwords The security of a password depends upon the strength of the encryption algorithm and the size of the key space. The legacy UNIX System encryption method is based on the NBS DES algorithm. More recent methods are now recommended (see ENCRYPT_METHOD). The size of the key space depends upon the randomness of the password which is selected.
Compromises in password security normally result from careless password selection or handling. For this reason, you should not select a password which appears in a dictionary or which must be written down. The password should also not be a proper name, your license number, birth date, or street address. Any of these may be used as guesses to violate system security.
You can find advice on how to choose a strong password on http://en.wikipedia.org/wiki/Password_strength
The options which apply to the passwd command are:
-a, --all This option can be used only with -S and causes show status for all users.
-d, --delete Delete a user's password (make it empty). This is a quick way to disable a password for an account. It will set the named account passwordless.
-e, --expire Immediately expire an account's password. This in effect can force a user to change their password at the user's next login.
-i, --inactive INACTIVE This option is used to disable an account after the password has been expired for a number of days. After a user account has had an expired password for INACTIVE days, the user may no longer sign on to the account.
-k, --keep-tokens Indicate password change should be performed only for expired authentication tokens (passwords). The user wishes to keep their non-expired tokens as before.
-l, --lock Lock the password of the named account. This option disables a password by changing it to a value which matches no possible encrypted value (it adds a ´!´ at the beginning of the password).
Note that this does not disable the account. The user may still be able to login using another authentication token (e.g. an SSH key). To disable the account, administrators should use usermod --expiredate 1 (this set the account's expire date to Jan 2, 1970).
Users with a locked password are not allowed to change their password.
-n, --mindays MIN_DAYS Set the minimum number of days between password changes to MIN_DAYS. A value of zero for this field indicates that the user may change their password at any time.
-r, --repository REPOSITORY change password in REPOSITORY repository
-S, --status Display account status information. The status information consists of 7 fields. The first field is the user's login name. The second field indicates if the user account has a locked password (L), has no password (NP), or has a usable password (P). The third field gives the date of the last password change. The next four fields are the minimum age, maximum age, warning period, and inactivity period for the password. These ages are expressed in days.
-u, --unlock Unlock the password of the named account. This option re-enables a password by changing the password back to its previous value (to the value before using the -l option).
-w, --warndays WARN_DAYS Set the number of days of warning before a password change is required. The WARN_DAYS option is the number of days prior to the password expiring that a user will be warned that their password is about to expire.
-x, --maxdays MAX_DAYS Set the maximum number of days a password remains valid. After MAX_DAYS, the password is required to be changed.
Password complexity checking may vary from site to site. The user is urged to select a password as complex as he or she feels comfortable with.
Users may not be able to change their password on a system if NIS is enabled and they are not logged into the NIS server.
OBSCURE_CHECKS_ENAB (boolean) Enable additional checks upon password changes.
PASS_ALWAYS_WARN (boolean) Warn about weak passwords (but still allow them) if you are root.
PASS_CHANGE_TRIES (number) Maximum number of attempts to change password if rejected (too easy).
PASS_MAX_LEN (number), PASS_MIN_LEN (number) Number of significant characters in the password for crypt(). PASS_MAX_LEN is 8 by default. Don't change unless your crypt() is better. This is ignored if MD5_CRYPT_ENAB set to yes.
The passwd command exits with the following values:
2 invalid combination of options
3 unexpected failure, nothing done
4 unexpected failure, passwd file missing
5 passwd file busy, try again
6 invalid argument to option
chpasswd(8), passwd(5), shadow(5), login.defs(5), usermod(8).
GIT-COMMIT(1)                      Git Manual                      GIT-COMMIT(1)
git-commit - Record changes to the repository
git commit [-a | --interactive | --patch] [-s] [-v] [-u<mode>] [--amend] [--dry-run] [(-c | -C | --squash) <commit> | --fixup [(amend|reword):]<commit>)] [-F <file> | -m <msg>] [--reset-author] [--allow-empty] [--allow-empty-message] [--no-verify] [-e] [--author=<author>] [--date=<date>] [--cleanup=<mode>] [--[no-]status] [-i | -o] [--pathspec-from-file=<file> [--pathspec-file-nul]] [(--trailer <token>[(=|:)<value>])...] [-S[<keyid>]] [--] [<pathspec>...]
Create a new commit containing the current contents of the index and the given log message describing the changes. The new commit is a direct child of HEAD, usually the tip of the current branch, and the branch is updated to point to it (unless no branch is associated with the working tree, in which case HEAD is "detached" as described in git-checkout(1)).
The content to be committed can be specified in several ways:
1. by using git-add(1) to incrementally "add" changes to the index before using the commit command (Note: even modified files must be "added");
2. by using git-rm(1) to remove files from the working tree and the index, again before using the commit command;
3. by listing files as arguments to the commit command (without --interactive or --patch switch), in which case the commit will ignore changes staged in the index, and instead record the current content of the listed files (which must already be known to Git);
4. by using the -a switch with the commit command to automatically "add" changes from all known files (i.e. all files that are already listed in the index) and to automatically "rm" files in the index that have been removed from the working tree, and then perform the actual commit;
5. by using the --interactive or --patch switches with the commit command to decide one by one which files or hunks should be part of the commit in addition to contents in the index, before finalizing the operation. See the “Interactive Mode” section of git-add(1) to learn how to operate these modes.
The --dry-run option can be used to obtain a summary of what is included by any of the above for the next commit by giving the same set of parameters (options and paths).
If you make a commit and then find a mistake immediately after that, you can recover from it with git reset.
-a, --all Tell the command to automatically stage files that have been modified and deleted, but new files you have not told Git about are not affected.
-p, --patch Use the interactive patch selection interface to choose which changes to commit. See git-add(1) for details.
-C <commit>, --reuse-message=<commit> Take an existing commit object, and reuse the log message and the authorship information (including the timestamp) when creating the commit.
-c <commit>, --reedit-message=<commit> Like -C, but with -c the editor is invoked, so that the user can further edit the commit message.
--fixup=[(amend|reword):]<commit> Create a new commit which "fixes up" <commit> when applied with git rebase --autosquash. Plain --fixup=<commit> creates a "fixup!" commit which changes the content of <commit> but leaves its log message untouched.  --fixup=amend:<commit> is similar but creates an "amend!" commit which also replaces the log message of <commit> with the log message of the "amend!" commit.  --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.
The commit created by plain --fixup=<commit> has a subject composed of "fixup!" followed by the subject line from <commit>, and is recognized specially by git rebase --autosquash. The -m option may be used to supplement the log message of the created commit, but the additional commentary will be thrown away once the "fixup!" commit is squashed into <commit> by git rebase --autosquash.
The commit created by --fixup=amend:<commit> is similar but its subject is instead prefixed with "amend!". The log message of <commit> is copied into the log message of the "amend!" commit and opened in an editor so it can be refined. When git rebase --autosquash squashes the "amend!" commit into <commit>, the log message of <commit> is replaced by the refined log message from the "amend!" commit. It is an error for the "amend!" commit’s log message to be empty unless --allow-empty-message is specified.
--fixup=reword:<commit> is shorthand for --fixup=amend:<commit> --only. It creates an "amend!" commit with only a log message (ignoring any changes staged in the index). When squashed by git rebase --autosquash, it replaces the log message of <commit> without making any other changes.
Neither "fixup!" nor "amend!" commits change authorship of <commit> when applied by git rebase --autosquash. See git-rebase(1) for details.
--squash=<commit> Construct a commit message for use with rebase --autosquash. The commit message subject line is taken from the specified commit with a prefix of "squash! ". Can be used with additional commit message options (-m/-c/-C/-F). See git-rebase(1) for details.
--reset-author When used with -C/-c/--amend options, or when committing after a conflicting cherry-pick, declare that the authorship of the resulting commit now belongs to the committer. This also renews the author timestamp.
--short When doing a dry-run, give the output in the short-format. See git- status(1) for details. Implies --dry-run.
--branch Show the branch and tracking info even in short-format.
--porcelain When doing a dry-run, give the output in a porcelain-ready format. See git-status(1) for details. Implies --dry-run.
--long When doing a dry-run, give the output in the long-format. Implies --dry-run.
-z, --null When showing short or porcelain status output, print the filename verbatim and terminate the entries with NUL, instead of LF. If no format is given, implies the --porcelain output format. Without the -z option, filenames with "unusual" characters are quoted as explained for the configuration variable core.quotePath (see git- config(1)).
-F <file>, --file=<file> Take the commit message from the given file. Use - to read the message from the standard input.
--author=<author> Override the commit author. Specify an explicit author using the standard A U Thor <author@example.com> format. Otherwise <author> is assumed to be a pattern and is used to search for an existing commit by that author (i.e. rev-list --all -i --author=<author>); the commit author is then copied from the first such commit found.
--date=<date> Override the author date used in the commit.
-m <msg>, --message=<msg> Use the given <msg> as the commit message. If multiple -m options are given, their values are concatenated as separate paragraphs.
The -m option is mutually exclusive with -c, -C, and -F.
-t <file>, --template=<file> When editing the commit message, start the editor with the contents in the given file. The commit.template configuration variable is often used to give this option implicitly to the command. This mechanism can be used by projects that want to guide participants with some hints on what to write in the message in what order. If the user exits the editor without editing the message, the commit is aborted. This has no effect when a message is given by other means, e.g. with the -m or -F options.
-s, --signoff, --no-signoff Add a Signed-off-by trailer by the committer at the end of the commit log message. The meaning of a signoff depends on the project to which you’re committing. For example, it may certify that the committer has the rights to submit the work under the project’s license or agrees to some contributor representation, such as a Developer Certificate of Origin. (See http://developercertificate.org for the one used by the Linux kernel and Git projects.) Consult the documentation or leadership of the project to which you’re contributing to understand how the signoffs are used in that project.
--trailer <token>[(=|:)<value>] Specify a (<token>, <value>) pair that should be applied as a trailer. (e.g.  git commit --trailer "Signed-off-by:C O Mitter \ <committer@example.com>" --trailer "Helped-by:C O Mitter \ <committer@example.com>" will add the "Signed-off-by" trailer and the "Helped-by" trailer to the commit message.) The trailer.* configuration variables (git-interpret-trailers(1)) can be used to define if a duplicated trailer is omitted, where in the run of trailers each trailer would appear, and other details.
-n, --[no-]verify By default, the pre-commit and commit-msg hooks are run. When any of --no-verify or -n is given, these are bypassed. See also githooks(5).
--allow-empty Usually recording a commit that has the exact same tree as its sole parent commit is a mistake, and the command prevents you from making such a commit. This option bypasses the safety, and is primarily for use by foreign SCM interface scripts.
--allow-empty-message Like --allow-empty this command is primarily for use by foreign SCM interface scripts. It allows you to create a commit with an empty commit message without using plumbing commands like git-commit- tree(1).
--cleanup=<mode> This option determines how the supplied commit message should be cleaned up before committing. The <mode> can be strip, whitespace, verbatim, scissors or default.
strip Strip leading and trailing empty lines, trailing whitespace, commentary and collapse consecutive empty lines.
whitespace Same as strip except #commentary is not removed.
verbatim Do not change the message at all.
scissors Same as whitespace except that everything from (and including) the line found below is truncated, if the message is to be edited. "#" can be customized with core.commentChar.
# ------------------------ >8 ------------------------
default Same as strip if the message is to be edited. Otherwise whitespace.
The default can be changed by the commit.cleanup configuration variable (see git-config(1)).
-e, --edit The message taken from file with -F, command line with -m, and from commit object with -C are usually used as the commit log message unmodified. This option lets you further edit the message taken from these sources.
--no-edit Use the selected commit message without launching an editor. For example, git commit --amend --no-edit amends a commit without changing its commit message.
--amend Replace the tip of the current branch by creating a new commit. The recorded tree is prepared as usual (including the effect of the -i and -o options and explicit pathspec), and the message from the original commit is used as the starting point, instead of an empty message, when no other message is specified from the command line via options such as -m, -F, -c, etc. The new commit has the same parents and author as the current one (the --reset-author option can countermand this).
It is a rough equivalent for:
$ git reset --soft HEAD^ $ ... do something else to come up with the right tree ... $ git commit -c ORIG_HEAD
but can be used to amend a merge commit.
You should understand the implications of rewriting history if you amend a commit that has already been published. (See the "RECOVERING FROM UPSTREAM REBASE" section in git-rebase(1).)
--no-post-rewrite Bypass the post-rewrite hook.
-i, --include Before making a commit out of staged contents so far, stage the contents of paths given on the command line as well. This is usually not what you want unless you are concluding a conflicted merge.
-o, --only Make a commit by taking the updated working tree contents of the paths specified on the command line, disregarding any contents that have been staged for other paths. This is the default mode of operation of git commit if any paths are given on the command line, in which case this option can be omitted. If this option is specified together with --amend, then no paths need to be specified, which can be used to amend the last commit without committing changes that have already been staged. If used together with --allow-empty paths are also not required, and an empty commit will be created.
The mode parameter is optional (defaults to all), and is used to specify the handling of untracked files; when -u is not used, the default is normal, i.e. show untracked files and directories.
•   no - Show no untracked files
•   normal - Shows untracked files and directories
-v, --verbose Show unified diff between the HEAD commit and what would be committed at the bottom of the commit message template to help the user describe the commit by reminding what changes the commit has. Note that this diff output doesn’t have its lines prefixed with #. This diff will not be a part of the commit message. See the commit.verbose configuration variable in git-config(1).
If specified twice, show in addition the unified diff between what would be committed and the worktree files, i.e. the unstaged changes to tracked files.
-q, --quiet Suppress commit summary message.
--dry-run Do not create a commit, but show a list of paths that are to be committed, paths with local changes that will be left uncommitted and paths that are untracked.
--status Include the output of git-status(1) in the commit message template when using an editor to prepare the commit message. Defaults to on, but can be used to override configuration variable commit.status.
--no-status Do not include the output of git-status(1) in the commit message template when using an editor to prepare the default commit message.
<pathspec>... When pathspec is given on the command line, commit the contents of the files that match the pathspec without recording the changes already added to the index. The contents of these files are also staged for the next commit on top of what have been staged before.
When recording your own work, the contents of modified files in your working tree are temporarily stored to a staging area called the "index" with git add. A file can be reverted back, only in the index but not in the working tree, to that of the last commit with git restore --staged <file>, which effectively reverts git add and prevents the changes to this file from participating in the next commit. After building the state to be committed incrementally with these commands, git commit (without any pathname parameter) is used to record what has been staged so far. This is the most basic form of the command. An example:
$ edit hello.c $ git rm goodbye.c $ git add hello.c $ git commit
Instead of staging files after each individual change, you can tell git commit to notice the changes to the files whose contents are tracked in your working tree and do corresponding git add and git rm for you. That is, this example does the same as the earlier example if there is no other change in your working tree:
$ edit hello.c $ rm goodbye.c $ git commit -a
The command git commit -a first looks at your working tree, notices that you have modified hello.c and removed goodbye.c, and performs necessary git add and git rm for you.
After staging changes to many files, you can alter the order the changes are recorded in, by giving pathnames to git commit. When pathnames are given, the command makes a commit that only records the changes made to the named paths:
$ edit hello.c hello.h $ git add hello.c hello.h $ edit Makefile $ git commit Makefile
This makes a commit that records the modification to Makefile. The changes staged for hello.c and hello.h are not included in the resulting commit. However, their changes are not lost — they are still staged and merely held back. After the above sequence, if you do:
this second commit would record the changes to hello.c and hello.h as expected.
After a merge (initiated by git merge or git pull) stops because of conflicts, cleanly merged paths are already staged to be committed for you, and paths that conflicted are left in unmerged state. You would have to first check which paths are conflicting with git status and after fixing them manually in your working tree, you would stage the result as usual with git add:
$ git status | grep unmerged unmerged: hello.c $ edit hello.c $ git add hello.c
After resolving conflicts and staging the result, git ls-files -u would stop mentioning the conflicted path. When you are done, run git commit to finally record the merge:
As with the case to record your own changes, you can use -a option to save typing. One difference is that during a merge resolution, you cannot use git commit with pathnames to alter the order the changes are committed, because the merge should be recorded as a single commit. In fact, the command refuses to run when given pathnames (but see -i option).
Author and committer information is taken from the following environment variables, if set:
GIT_AUTHOR_NAME GIT_AUTHOR_EMAIL GIT_AUTHOR_DATE GIT_COMMITTER_NAME GIT_COMMITTER_EMAIL GIT_COMMITTER_DATE
(nb "<", ">" and "\n"s are stripped)
The author and committer names are by convention some form of a personal name (that is, the name by which other humans refer to you), although Git does not enforce or require any particular form. Arbitrary Unicode may be used, subject to the constraints listed above. This name has no effect on authentication; for that, see the credential.username variable in git- config(1).
In case (some of) these environment variables are not set, the information is taken from the configuration items user.name and user.email, or, if not present, the environment variable EMAIL, or, if that is not set, system user name and the hostname used for outgoing mail (taken from /etc/mailname and falling back to the fully qualified hostname when that file does not exist).
The author.name and committer.name and their corresponding email options override user.name and user.email if set and are overridden themselves by the environment variables.
The typical usage is to set just the user.name and user.email variables; the other options are provided for more complex use cases.
In addition to recognizing all date formats above, the --date option will also try to make sense of other, more human-centric date formats, such as relative dates like "yesterday" or "last Friday at noon".
Though not required, it’s a good idea to begin the commit message with a single short (less than 50 character) line summarizing the change, followed by a blank line and then a more thorough description. The text up to the first blank line in a commit message is treated as the commit title, and that title is used throughout Git. For example, git-format- patch(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body.
The editor used to edit the commit log message will be chosen from the GIT_EDITOR environment variable, the core.editor configuration variable, the VISUAL environment variable, or the EDITOR environment variable (in that order). See git-var(1) for details.
This command can run commit-msg, prepare-commit-msg, pre-commit, post-commit and post-rewrite hooks. See githooks(5) for more information.
$GIT_DIR/COMMIT_EDITMSG This file contains the commit message of a commit in progress. If git commit exits due to an error before creating a commit, any commit message that has been provided by the user (e.g., in an editor session) will be available in this file, but will be overwritten by the next invocation of git commit.
git-add(1), git-rm(1), git-mv(1), git-merge(1), git-commit-tree(1)
UNITS(1)                     General Commands Manual                    UNITS(1)
units — unit conversion and calculation program
[options] [from-unit [to-unit]]
The units program converts quantities expressed in various systems of measurement to their equivalents in other systems of measurement.  Like many similar programs, it can handle multiplicative scale changes. It can also handle nonlinear conversions such as Fahrenheit to Celsius; see Temperature Conversions.  The program can also perform conversions from and to sums of units, such as converting between meters and feet plus inches.
Basic operation is simple: you enter the units that you want to convert from and the units that you want to convert to.  You can use the program interactively with prompts, or you can use it from the command line.
Beyond simple unit conversions, units can be used as a general-purpose scientific calculator that keeps track of units in its calculations.  You can form arbitrary complex mathematical expressions of dimensions including sums, products, quotients, powers, and even roots of dimensions.  Thus you can ensure accuracy and dimensional consistency when working with long expressions that involve many different units that may combine in complex ways; for an illustration, see Complicated Unit Expressions.
The units are defined in an external data file.  You can use the extensive data file that comes with this program, or you can provide your own data file to suit your needs.  You can also use your own data file to supplement the standard data file.
You can change the default behavior of units with various options given on the command line. See Invoking Units for a description of the available options.
To invoke units for interactive use, type units at your shell prompt. The program will print something like this:
Currency exchange rates from www.timegenie.com on 2014-03-05 2860 units, 109 prefixes, 85 nonlinear units
At the ‘You have:’ prompt, type the quantity and units that you are converting from.  For example, if you want to convert ten meters to feet, type 10 meters.  Next, units will print ‘You want:’.  You should type the units you want to convert to.  To convert to feet, you would type feet. If the readline library was compiled in, then tab will complete unit names. See Readline Support for more information about readline.  To quit the program type quit or exit at either prompt.
The result will be displayed in two ways.  The first line of output, which is marked with a ‘*’ to indicate multiplication, gives the result of the conversion you have asked for.  The second line of output, which is marked with a ‘/’ to indicate division, gives the inverse of the conversion factor.  If you convert 10 meters to feet, units will print
* 32.808399 / 0.03048
which tells you that 10 meters equals about 32.8 feet.  The second number gives the conversion in the opposite direction.  In this case, it tells you that 1 foot is equal to about 0.03 dekameters since the dekameter is 10 meters.  It also tells you that 1/32.8 is about 0.03.
The units program prints the inverse because sometimes it is a more convenient number.  In the example above, for example, the inverse value is an exact conversion: a foot is exactly 0.03048 dekameters.  But the number given the other direction is inexact.
If you convert grains to pounds, you will see the following:
You have: grains You want: pounds * 0.00014285714 / 7000
From the second line of the output you can immediately see that a grain is equal to a seven thousandth of a pound.  This is not so obvious from the first line of the output.  If you find  the output format confusing, try using the ‘--verbose’ option:
You have: grain You want: aeginamina grain = 0.00010416667 aeginamina grain = (1 / 9600) aeginamina
If you request a conversion between units that measure reciprocal dimensions, then units will display the conversion results with an extra note indicating that reciprocal conversion has been done:
You have: 6 ohms You want: siemens reciprocal conversion * 0.16666667 / 6
Reciprocal conversion can be suppressed by using the ‘--strict’ option. As usual, use the ‘--verbose’ option to get more comprehensible output:
You have: tex You want: typp reciprocal conversion 1 / tex = 496.05465 typp 1 / tex = (1 / 0.0020159069) typp
You have: 20 mph You want: sec/mile reciprocal conversion 1 / 20 mph = 180 sec/mile 1 / 20 mph = (1 / 0.0055555556) sec/mile
If you enter incompatible unit types, the units program will print a message indicating that the units are not conformable and it will display the reduced form for each unit:
You have: ergs/hour You want: fathoms kg^2 / day conformability error 2.7777778e-11 kg m^2 / sec^3 2.1166667e-05 kg^2 m / sec
If you only want to find the reduced form or definition of a unit, simply press Enter at the ‘You want:’ prompt.  Here is an example:
You have: jansky You want: Definition: fluxunit = 1e-26 W/m^2 Hz = 1e-26 kg / s^2
The output from units indicates that the jansky is defined to be equal to a fluxunit which in turn is defined to be a certain combination of watts, meters, and hertz.  The fully reduced (and in this case somewhat more cryptic) form appears on the far right.
Some named units are treated as dimensionless in some situations.  These units include the radian and steradian.  These units will be treated as equal to 1 in units conversions.  Power is equal to torque times angular velocity.  This conversion can only be performed if the radian is dimensionless.
You have: (14 ft lbf) (12 radians/sec) You want: watts * 227.77742 / 0.0043902509
It is also possible to compute roots and other non-integer powers of dimensionless units; this allows computations such as the altitude of geosynchronous orbit:
You have: cuberoot(G earthmass / (circle/siderealday)^2) - earthradius You want: miles * 22243.267 / 4.4957425e-05
Named dimensionless units are not treated as dimensionless in other contexts.  They cannot be used as exponents so for example, ‘meter^radian’ is forbidden.
If you want a list of options you can type ? at the ‘You want:’ prompt. The program will display a list of named units that are conformable with the unit that you entered at the ‘You have:’ prompt above.  Conformable unit combinations will not appear on this list.
Typing help at either prompt displays a short help message.  You can also type help followed by a unit name.  This will invoke a pager on the units data base at the point where that unit is defined.  You can read the definition and comments that may give more details or historical information about the unit.  (You can generally quit out of the page by pressing ‘q’.)
Typing search text will display a list of all of the units whose names contain text as a substring along with their definitions.  This may help in the case where you aren't sure of the right unit name.
DOXYGEN(1)                        User Commands                       DOXYGEN(1)
doxygen - documentation system for various programming languages
Doxygen is a documentation system for C++, C, Java, Objective-C, IDL (Corba and Microsoft flavors), Fortran, Python, VHDL and to some extent PHP, C#, and D.
You can use doxygen in a number of ways:
1) Use doxygen to generate a template configuration file:
doxygen [-s] -g [configName]
2) Use doxygen to update an old configuration file:
doxygen [-s] -u [configName]
3) Use doxygen to generate documentation using an existing configuration file:
doxygen [configName]
4) Use doxygen to generate a template file controlling the layout of the generated documentation:
doxygen -l [layoutFileName]
In case layoutFileName is omitted layoutFileName.xml will be used as filename.  If - is used for layoutFileName doxygen will write to standard output.
5) Use doxygen to generate a template style sheet file for RTF, HTML or Latex.
RTF: doxygen -w rtf styleSheetFile
HTML: doxygen -w html headerFile footerFile styleSheetFile [configFile]
LaTeX: doxygen -w latex headerFile footerFile styleSheetFile [configFile]
6) Use doxygen to generate an rtf extensions file
RTF: doxygen -e rtf extensionsFile
If - is used for extensionsFile doxygen will write to standard output.
7) Use doxygen to compare the used configuration file with the template configuration file
doxygen -x [configFile]
8) Use doxygen to show a list of built-in emojis.
doxygen -f emoji outputFileName
If - is used for outputFileName doxygen will write to standard output.
If -s is specified the comments in the config file will be omitted.  If configName is omitted `Doxyfile' will be used as a default.  If - is used for configFile doxygen will write / read the configuration to /from standard output / input.
Doxygen version 1.9.2, Copyright Dimitri van Heesch 1997-2019
doxywizard(1).
PINOUT(1)                           gpiozero                           PINOUT(1)
pinout - GPIO Zero pinout tool [image]
pinout [-h] [-r REVISION] [-c] [-m] [-x]
A utility for querying Raspberry Pi GPIO pin-out information. Running pinout on its own will output a board diagram, and GPIO header diagram for the current Raspberry Pi. It is also possible to manually specify a revision of Pi, or (by remote_gpio) to output information about a remote Pi.
-r REVISION, --revision REVISION RPi revision. Default is to autodetect revision of current device
-c, --color Force colored output (by default, the output will include ANSI color codes if run in a color-capable terminal). See also --monochrome
-m, --monochrome Force monochrome output. See also --color
-x, --xyz Open pinout.xyz <https://pinout.xyz/> in the default web browser
To output information about the current Raspberry Pi:
$ pinout
For a Raspberry Pi model 3B, this will output something like the following:
,--------------------------------. | oooooooooooooooooooo J8     +==== | 1ooooooooooooooooooo        | USB |                             +==== |      Pi Model 3B V1.1          | |      +----+                 +==== | |D|  |SoC |                 | USB | |S|  |    |                 +==== | |I|  +----+                    | |                   |C|     +====== |                   |S|     |   Net | pwr        |HDMI| |I||A|  +====== `-| |--------|    |----|V|-------'
Revision           : a02082 SoC                : BCM2837 RAM                : 1024Mb Storage            : MicroSD USB ports          : 4 (excluding power) Ethernet ports     : 1 Wi-fi              : True Bluetooth          : True Camera ports (CSI) : 1 Display ports (DSI): 1
J8: 3V3  (1) (2)  5V GPIO2  (3) (4)  5V GPIO3  (5) (6)  GND GPIO4  (7) (8)  GPIO14 GND  (9) (10) GPIO15 GPIO17 (11) (12) GPIO18 GPIO27 (13) (14) GND GPIO22 (15) (16) GPIO23 3V3 (17) (18) GPIO24 GPIO10 (19) (20) GND GPIO9 (21) (22) GPIO25 GPIO11 (23) (24) GPIO8 GND (25) (26) GPIO7 GPIO0 (27) (28) GPIO1 GPIO5 (29) (30) GND GPIO6 (31) (32) GPIO12 GPIO13 (33) (34) GND GPIO19 (35) (36) GPIO16 GPIO26 (37) (38) GPIO20 GND (39) (40) GPIO21
By default, if stdout is a console that supports color, ANSI codes will be used to produce color output. Output can be forced to be --monochrome:
$ pinout --monochrome
Or forced to be --color, in case you are redirecting to something capable of supporting ANSI codes:
$ pinout --color | less -SR
To manually specify the revision of Pi you want to query, use --revision. The tool understands both old-style revision codes <https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision- codes/README.md> (such as for the model B):
$ pinout -r 000d
Or new-style revision codes <https://www.raspberrypi.org/documentation/hardware/raspberrypi/revision- codes/README.md> (such as for the Pi Zero W):
$ pinout -r 9000c1 [image]
You can also use the tool with remote_gpio to query remote Raspberry Pi's:
$ GPIOZERO_PIN_FACTORY=pigpio PIGPIO_ADDR=other_pi pinout
Or run the tool directly on a PC using the mock pin implementation (although in this case you'll almost certainly want to specify the Pi revision manually):
$ GPIOZERO_PIN_FACTORY=mock pinout -r a22042
GPIOZERO_PIN_FACTORY The library to use when communicating with the GPIO pins. Defaults to attempting to load RPi.GPIO, then RPIO, then pigpio, and finally uses a native Python implementation. Valid values include "rpigpio", "rpio", "pigpio", "native", and "mock". The latter is most useful on non-Pi platforms as it emulates a Raspberry Pi model 3B (by default).
PIGPIO_ADDR The hostname of the Raspberry Pi the pigpio library should attempt to connect to (if the pigpio pin factory is being used). Defaults to localhost.
PIGPIO_PORT The port number the pigpio library should attempt to connect to (if the pigpio pin factory is being used). Defaults to 8888.
remote-gpio(7)
Ben Nuttall
2015-2021 Ben Nuttall
docker-swarm - Manage Swarm
docker swarm
Manage Swarm
-h, --help[=false]      help for swarm
docker(1), docker-swarm-ca(1), docker-swarm-init(1), docker-swarm- join(1), docker-swarm-join-token(1), docker-swarm-leave(1), docker-swarm- unlock(1), docker-swarm-unlock-key(1), docker-swarm-update(1)
SS(8)                        System Manager's Manual                       SS(8)
ss - another utility to investigate sockets
ss [options] [ FILTER ]
ss is used to dump socket statistics. It allows showing information similar to netstat.  It can display more TCP and state information than other tools.
When no option is used ss displays a list of open non-listening sockets (e.g. TCP/UNIX/UDP) that have established connection.
-V, --version Output version information.
-H, --no-header Suppress header line.
-O, --oneline Print each socket's data on a single line.
-n, --numeric Do not try to resolve service names. Show exact bandwidth values, instead of human-readable.
-r, --resolve Try to resolve numeric address/ports.
-a, --all Display both listening and non-listening (for TCP this means established connections) sockets.
-l, --listening Display only listening sockets (these are omitted by default).
-o, --options Show timer information. For TCP protocol, the output format is:
timer:(<timer_name>,<expire_time>,<retrans>)
<timer_name> the name of the timer, there are five kind of timer names:
on : means one of these timers: TCP retrans timer, TCP early retrans timer and tail loss probe timer
keepalive: tcp keep alive timer
timewait: timewait stage timer
persist: zero window probe timer
unknown: none of the above timers
<expire_time> how long time the timer will expire
<retrans> how many times the retransmission occurred
-e, --extended Show detailed socket information. The output format is:
uid:<uid_number> ino:<inode_number> sk:<cookie>
<uid_number> the user id the socket belongs to
<inode_number> the socket's inode number in VFS
<cookie> an uuid of the socket
-m, --memory Show socket memory usage. The output format is:
skmem:(r<rmem_alloc>,rb<rcv_buf>,t<wmem_alloc>,tb<snd_buf>, f<fwd_alloc>,w<wmem_queued>,o<opt_mem>, bl<back_log>,d<sock_drop>)
<rmem_alloc> the memory allocated for receiving packet
<rcv_buf> the total memory can be allocated for receiving packet
<wmem_alloc> the memory used for sending packet (which has been sent to layer 3)
<snd_buf> the total memory can be allocated for sending packet
<fwd_alloc> the memory allocated by the socket as cache, but not used for receiving/sending packet yet. If need memory to send/receive packet, the memory in this cache will be used before allocate additional memory.
<wmem_queued> The memory allocated for sending packet (which has not been sent to layer 3)
<ropt_mem> The memory used for storing socket option, e.g., the key for TCP MD5 signature
<back_log> The memory used for the sk backlog queue. On a process context, if the process is receiving packet, and a new packet is received, it will be put into the sk backlog queue, so it can be received by the process immediately
<sock_drop> the number of packets dropped before they are de- multiplexed into the socket
-p, --processes Show process using socket.
-i, --info Show internal TCP information. Below fields may appear:
ts     show string "ts" if the timestamp option is set
sack   show string "sack" if the sack option is set
ecn    show string "ecn" if the explicit congestion notification option is set
ecnseen show string "ecnseen" if the saw ecn flag is found in received packets
fastopen show string "fastopen" if the fastopen option is set
cong_alg the congestion algorithm name, the default congestion algorithm is "cubic"
wscale:<snd_wscale>:<rcv_wscale> if window scale option is used, this field shows the send scale factor and receive scale factor
rto:<icsk_rto> tcp re-transmission timeout value, the unit is millisecond
backoff:<icsk_backoff> used for exponential backoff re-transmission, the actual re-transmission timeout value is icsk_rto << icsk_backoff
rtt:<rtt>/<rttvar> rtt is the average round trip time, rttvar is the mean deviation of rtt, their units are millisecond
ato:<ato> ack timeout, unit is millisecond, used for delay ack mode
mss:<mss> max segment size
cwnd:<cwnd> congestion window size
pmtu:<pmtu> path MTU value
ssthresh:<ssthresh> tcp congestion window slow start threshold
bytes_acked:<bytes_acked> bytes acked
bytes_received:<bytes_received> bytes received
segs_out:<segs_out> segments sent out
segs_in:<segs_in> segments received
send <send_bps>bps egress bps
lastsnd:<lastsnd> how long time since the last packet sent, the unit is millisecond
lastrcv:<lastrcv> how long time since the last packet received, the unit is millisecond
lastack:<lastack> how long time since the last ack received, the unit is millisecond
pacing_rate <pacing_rate>bps/<max_pacing_rate>bps the pacing rate and max pacing rate
rcv_space:<rcv_space> a helper variable for TCP internal auto tuning socket receive buffer
tcp-ulp-mptcp flags:[MmBbJjecv] token:<rem_token(rem_id)/loc_token(loc_id)> seq:<sn> sfseq:<ssn> ssnoff:<off> maplen:<maplen> MPTCP subflow information
--tos  Show ToS and priority information. Below fields may appear:
tos    IPv4 Type-of-Service byte
tclass IPv6 Traffic Class byte
class_id Class id set by net_cls cgroup. If class is zero this shows priority set by SO_PRIORITY.
--cgroup Show cgroup information. Below fields may appear:
cgroup Cgroup v2 pathname. This pathname is relative to the mount point of the hierarchy.
-K, --kill Attempts to forcibly close sockets. This option displays sockets that are successfully closed and silently skips sockets that the kernel does not support closing. It supports IPv4 and IPv6 sockets only.