neulab/tldr huggingface dataset:
Unless --norc is used, ShellCheck will look for a file .shellcheckrc or shellcheckrc in the script's directory and each parent directory.  If found, it will read key=value pairs from it and treat them as file-wide directives.
Here is an example .shellcheckrc:
# Look for 'source'd files relative to the checked script, # and also look for absolute paths in /mnt/chroot source-path=SCRIPTDIR source-path=/mnt/chroot
# Turn on warnings for unquoted variables with safe values enable=quote-safe-variables
# Turn on warnings for unassigned uppercase variables enable=check-unassigned-uppercase
# Allow [ ! -z foo ] instead of suggesting -n disable=SC2236
If no .shellcheckrc is found in any of the parent directories, ShellCheck will look in ~/.shellcheckrc followed by the XDG config directory (usually ~/.config/shellcheckrc) on Unix, or %APPDATA%/shellcheckrc on Windows.  Only the first file found will be used.
Note for Snap users: the Snap sandbox disallows access to hidden files. Use shellcheckrc without the dot instead.
Note for Docker users: ShellCheck will only be able to look for files that are mounted in the container, so ~/.shellcheckrc will not be read.
The environment variable SHELLCHECK_OPTS can be set with default flags:
export SHELLCHECK_OPTS='--shell=bash --exclude=SC2016'
Its value will be split on spaces and prepended to the command line on each invocation.
ShellCheck uses the following exit codes:
• 0: All files successfully scanned with no issues.
• 1: All files successfully scanned with some issues.
• 2: Some files could not be processed (e.g.  file not found).
• 3: ShellCheck was invoked with bad syntax (e.g.  unknown flag).
• 4: ShellCheck was invoked with bad options (e.g.  unknown formatter).
This version of ShellCheck is only available in English.  All files are leniently decoded as UTF-8, with a fallback of ISO-8859-1 for invalid sequences.  LC_CTYPE is respected for output, and defaults to UTF-8 for locales where encoding is unspecified (such as the C locale).
Windows users seeing commitBuffer: invalid argument (invalid character) should set their terminal to use UTF-8 with chcp 65001.
ShellCheck is developed and maintained by Vidar Holen, with assistance from a long list of wonderful contributors.
Bugs and issues can be reported on GitHub:
https://github.com/koalaman/shellcheck/issues
Copyright 2012-2019, Vidar Holen and contributors.  Licensed under the GNU General Public License version 3 or later, see https://gnu.org/licenses/gpl.html
sh(1) bash(1)
PASS(1)                          Password Store                          PASS(1)
pass - stores, retrieves, generates, and synchronizes passwords securely
pass [ COMMAND ] [ OPTIONS ]... [ ARGS ]...
pass is a very simple password store that keeps passwords inside gpg2(1) encrypted files inside a simple directory tree residing at ~/.password- store.  The pass utility provides a series of commands for manipulating the password store, allowing the user to add, remove, edit, synchronize, generate, and manipulate passwords.
If no COMMAND is specified, COMMAND defaults to either show or ls, depending on the type of specifier in ARGS. Alternatively, if PASSWORD_STORE_ENABLE_EXTENSIONS is set to "true", and the file .extensions/COMMAND.bash exists inside the password store and is executable, then it is sourced into the environment, passing any arguments and environment variables. Extensions existing in a system-wide directory, only installable by the administrator, are always enabled.
Otherwise COMMAND must be one of the valid commands listed below.
Several of the commands below rely on or provide additional functionality if the password store directory is also a git repository. If the password store directory is a git repository, all password store modification commands will cause a corresponding git commit. Sub-directories may be separate nested git repositories, and pass will use the inner-most directory relative to the current password. See the EXTENDED GIT EXAMPLE section for a detailed description using init and git(1).
The init command must be run before other commands in order to initialize the password store with the correct gpg key id. Passwords are encrypted using the gpg key set with init.
There is a corresponding bash completion script for use with tab completing password names in bash(1).
init [ --path=sub-folder, -p sub-folder ] gpg-id... Initialize new password storage and use gpg-id for encryption. Multiple gpg-ids may be specified, in order to encrypt each password with multiple ids. This command must be run first before a password store can be used. If the specified gpg-id is different from the key used in any existing files, these files will be reencrypted to use the new id.  Note that use of gpg-agent(1) is recommended so that the batch decryption does not require as much user intervention. If --path or -p is specified, along with an argument, a specific gpg-id or set of gpg-ids is assigned for that specific sub folder of the password store. If only one gpg-id is given, and it is an empty string, then the current .gpg-id file for the specified sub-folder (or root if unspecified) is removed.
ls subfolder List names of passwords inside the tree at subfolder by using the tree(1) program. This command is alternatively named list.
grep [GREPOPTIONS] search-string Searches inside each decrypted password file for search-string, and displays line containing matched string along with filename. Uses grep(1) for matching. GREPOPTIONS are passed to grep(1) as- is. (Note: the GREP_OPTIONS environment variable functions as well.)
find pass-names... List names of passwords inside the tree that match pass-names by using the tree(1) program. This command is alternatively named search.
show [ --clip[=line-number], -c[line-number] ] [ --qrcode[=line-number], -q[line-number] ] pass-name Decrypt and print a password named pass-name. If --clip or -c is specified, do not print the password but instead copy the first (or otherwise specified) line to the clipboard using xclip(1) or wl-clipboard(1) and then restore the clipboard after 45 (or PASSWORD_STORE_CLIP_TIME) seconds. If --qrcode or -q is specified, do not print the password but instead display a QR code using qrencode(1) either to the terminal or graphically if supported.
insert [ --echo, -e | --multiline, -m ] [ --force, -f ] pass-name Insert a new password into the password store called pass-name. This will read the new password from standard in. If --echo or -e is not specified, disable keyboard echo when the password is entered and confirm the password by asking for it twice. If --multiline or -m is specified, lines will be read until EOF or Ctrl+D is reached. Otherwise, only a single line from standard in is read. Prompt before overwriting an existing password, unless --force or -f is specified. This command is alternatively named add.
edit pass-name Insert a new password or edit an existing password using the default text editor specified by the environment variable EDITOR or using vi(1) as a fallback. This mode makes use of temporary files for editing, but care is taken to ensure that temporary files are created in /dev/shm in order to avoid writing to difficult-to-erase disk sectors. If /dev/shm is not accessible, fallback to the ordinary TMPDIR location, and print a warning.
generate [ --no-symbols, -n ] [ --clip, -c ] [ --in-place, -i | --force, -f ] pass-name [pass-length] Generate a new password using /dev/urandom of length pass-length (or PASSWORD_STORE_GENERATED_LENGTH if unspecified) and insert into pass-name. If --no-symbols or -n is specified, do not use any non-alphanumeric characters in the generated password. The character sets used in generating passwords can be changed with the PASSWORD_STORE_CHARACTER_SET and PASSWORD_STORE_CHARACTER_SET_NO_SYMBOLS environment variables, described below.  If --clip or -c is specified, do not print the password but instead copy it to the clipboard using xclip(1) or wl-clipboard(1) and then restore the clipboard after 45 (or PASSWORD_STORE_CLIP_TIME) seconds. If --qrcode or -q is specified, do not print the password but instead display a QR code using qrencode(1) either to the terminal or graphically if supported. Prompt before overwriting an existing password, unless --force or -f is specified. If --in-place or -i is specified, do not interactively prompt, and only replace the first line of the password file with the new generated password, keeping the remainder of the file intact.
rm [ --recursive, -r ] [ --force, -f ] pass-name Remove the password named pass-name from the password store. This command is alternatively named remove or delete. If --recursive or -r is specified, delete pass-name recursively if it is a directory. If --force or -f is specified, do not interactively prompt before removal.
mv [ --force, -f ] old-path new-path Renames the password or directory named old-path to new-path. This command is alternatively named rename. If --force is specified, silently overwrite new-path if it exists. If new-path ends in a trailing /, it is always treated as a directory. Passwords are selectively reencrypted to the corresponding keys of their new destination.
cp [ --force, -f ] old-path new-path Copies the password or directory named old-path to new-path. This command is alternatively named copy. If --force is specified, silently overwrite new-path if it exists. If new-path ends in a trailing /, it is always treated as a directory. Passwords are selectively reencrypted to the corresponding keys of their new destination.
git git-command-args... If the password store is a git repository, pass git-command-args as arguments to git(1) using the password store as the git repository. If git-command-args is init, in addition to initializing the git repository, add the current contents of the password store to the repository in an initial commit. If the git config key pass.signcommits is set to true, then all commits will be signed using user.signingkey or the default git signing key. This config key may be turned on using: `pass git config --bool --add pass.signcommits true`
help   Show usage message.
version Show version information.
Initialize password store zx2c4@laptop ~ $ pass init Jason@zx2c4.com mkdir: created directory ‘/home/zx2c4/.password-store’ Password store initialized for Jason@zx2c4.com.
List existing passwords in store zx2c4@laptop ~ $ pass Password Store ├── Business │   ├── some-silly-business-site.com │   └── another-business-site.net ├── Email │   ├── donenfeld.com │   └── zx2c4.com └── France ├── bank ├── freebox └── mobilephone
Alternatively, "pass ls".
Find existing passwords in store that match .com zx2c4@laptop ~ $ pass find .com Search Terms: .com ├── Business │   ├── some-silly-business-site.com └── Email ├── donenfeld.com └── zx2c4.com
Alternatively, "pass search .com".
Show existing password zx2c4@laptop ~ $ pass Email/zx2c4.com sup3rh4x3rizmynam3
Copy existing password to clipboard zx2c4@laptop ~ $ pass -c Email/zx2c4.com Copied Email/jason@zx2c4.com to clipboard. Will clear in 45 seconds.
Add password to store zx2c4@laptop ~ $ pass insert Business/cheese-whiz-factory Enter password for Business/cheese-whiz-factory: omg so much cheese what am i gonna do
Add multiline password to store zx2c4@laptop ~ $ pass insert -m Business/cheese-whiz-factory Enter contents of Business/cheese-whiz-factory and press Ctrl+D when finished:
Hey this is my awesome multi line passworrrrrrrrd. ^D
Generate new password zx2c4@laptop ~ $ pass generate Email/jasondonenfeld.com 15 The generated password to Email/jasondonenfeld.com is: $(-QF&Q=IN2nFBx
Generate new alphanumeric password zx2c4@laptop ~ $ pass generate -n Email/jasondonenfeld.com 12 The generated password to Email/jasondonenfeld.com is: YqFsMkBeO6di
Generate new password and copy it to the clipboard zx2c4@laptop ~ $ pass generate -c Email/jasondonenfeld.com 19 Copied Email/jasondonenfeld.com to clipboard. Will clear in 45 seconds.
Remove password from store zx2c4@laptop ~ $ pass remove Business/cheese-whiz-factory rm: remove regular file ‘/home/zx2c4/.password- store/Business/cheese-whiz-factory.gpg’? y removed ‘/home/zx2c4/.password-store/Business/cheese-whiz- factory.gpg’
Here, we initialize new password store, create a git repository, and then manipulate and sync passwords. Make note of the arguments to the first call of pass git push; consult git-push(1) for more information.
zx2c4@laptop ~ $ pass init Jason@zx2c4.com mkdir: created directory ‘/home/zx2c4/.password-store’ Password store initialized for Jason@zx2c4.com.
zx2c4@laptop ~ $ pass git init Initialized empty Git repository in /home/zx2c4/.password-store/.git/ [master (root-commit) 998c8fd] Added current contents of password store. 1 file changed, 1 insertion(+) create mode 100644 .gpg-id
zx2c4@laptop ~ $ pass git remote add origin kexec.com:pass-store
zx2c4@laptop ~ $ pass generate Amazon/amazonemail@email.com 21 mkdir: created directory ‘/home/zx2c4/.password-store/Amazon’ [master 30fdc1e] Added generated password for Amazon/amazonemail@email.com to store. 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 Amazon/amazonemail@email.com.gpg The generated password to Amazon/amazonemail@email.com is: <5m,_BrZY`antNDxKN<0A
zx2c4@laptop ~ $ pass git push -u --all Counting objects: 4, done. Delta compression using up to 2 threads. Compressing objects: 100% (3/3), done. Writing objects: 100% (4/4), 921 bytes, done. Total 4 (delta 0), reused 0 (delta 0) To kexec.com:pass-store * [new branch]      master -> master Branch master set up to track remote branch master from origin.
zx2c4@laptop ~ $ pass insert Amazon/otheraccount@email.com Enter password for Amazon/otheraccount@email.com: som3r3a11yb1gp4ssw0rd!!88** [master b9b6746] Added given password for Amazon/otheraccount@email.com to store. 1 file changed, 0 insertions(+), 0 deletions(-) create mode 100644 Amazon/otheraccount@email.com.gpg
zx2c4@laptop ~ $ pass rm Amazon/amazonemail@email.com rm: remove regular file ‘/home/zx2c4/.password- store/Amazon/amazonemail@email.com.gpg’? y removed ‘/home/zx2c4/.password-store/Amazon/amazonemail@email.com.gpg’ rm 'Amazon/amazonemail@email.com.gpg' [master 288b379] Removed Amazon/amazonemail@email.com from store. 1 file changed, 0 insertions(+), 0 deletions(-) delete mode 100644 Amazon/amazonemail@email.com.gpg
zx2c4@laptop ~ $ pass git push Counting objects: 9, done. Delta compression using up to 2 threads. Compressing objects: 100% (5/5), done. Writing objects: 100% (7/7), 1.25 KiB, done. Total 7 (delta 0), reused 0 (delta 0) To kexec.com:pass-store
~/.password-store The default password storage directory.
~/.password-store/.gpg-id Contains the default gpg key identification used for encryption and decryption.  Multiple gpg keys may be specified in this file, one per line. If this file exists in any sub directories, passwords inside those sub directories are encrypted using those keys. This should be set using the init command.
~/.password-store/.extensions The directory containing extension files.
PASSWORD_STORE_DIR Overrides the default password storage directory.
PASSWORD_STORE_KEY Overrides the default gpg key identification set by init. Keys must not contain spaces and thus use of the hexadecimal key signature is recommended.  Multiple keys may be specified separated by spaces.
PASSWORD_STORE_GPG_OPTS Additional options to be passed to all invocations of GPG.
PASSWORD_STORE_X_SELECTION Overrides the selection passed to xclip, by default clipboard. See xclip(1) for more info.
PASSWORD_STORE_CLIP_TIME Specifies the number of seconds to wait before restoring the clipboard, by default 45 seconds.
PASSWORD_STORE_UMASK Sets the umask of all files modified by pass, by default 077.
PASSWORD_STORE_GENERATED_LENGTH The default password length if the pass-length parameter to generate is unspecified.
PASSWORD_STORE_CHARACTER_SET The character set to be used in password generation for generate. This value is to be interpreted by tr. See tr(1) for more info.
PASSWORD_STORE_CHARACTER_SET_NO_SYMBOLS The character set to be used in no-symbol password generation for generate, when --no-symbols, -n is specified. This value is to be interpreted by tr. See tr(1) for more info.
PASSWORD_STORE_ENABLE_EXTENSIONS This environment variable must be set to "true" for extensions to be enabled.
PASSWORD_STORE_EXTENSIONS_DIR The location to look for executable extension files, by default PASSWORD_STORE_DIR/.extensions.
PASSWORD_STORE_SIGNING_KEY If this environment variable is set, then all .gpg-id files and non-system extension files must be signed using a detached signature using the GPG key specified by the full 40 character upper-case fingerprint in this variable. If multiple fingerprints are specified, each separated by a whitespace character, then signatures must match at least one.  The init command will keep signatures of .gpg-id files up to date.
EDITOR The location of the text editor used by edit.
gpg2(1), tr(1), git(1), xclip(1), wl-clipboard(1), qrencode(1).
pass was written by Jason A. Donenfeld ⟨Jason@zx2c4.com⟩.  For updates and more information, a project page is available on the World Wide Web ⟨http://www.passwordstore.org/⟩.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
BLENDER(1)                   General Commands Manual                  BLENDER(1)
blender - a full-featured 3D application
blender [args ...] [file] [args ...]
blender is a full-featured 3D application. It supports the entirety of the 3D pipeline - modeling, rigging, animation, simulation, rendering, compositing, motion tracking, and video editing.
Use Blender to create 3D images and animations, films and commercials, content for games, architectural and industrial visualizations, and scientific visualizations.
https://www.blender.org
Color management: using fallback mode for management Color management: Error could not find role data role.  Blender 3.0.0 Usage: blender [args ...] [file] [args ...]
Render Options: -b or --background Run in background (often used for UI-less rendering).
-a or --render-anim Render frames from start to end (inclusive).
-S or --scene <name> Set the active scene <name> for rendering.
-f or --render-frame <frame> Render frame <frame> and save it.
* +<frame> start frame relative, -<frame> end frame relative. * A comma separated list of frames can also be used (no spaces). * A range of frames can be expressed using '..' separator between the first and last frames (inclusive).
-s or --frame-start <frame> Set start to frame <frame>, supports +/- for relative frames too.
-e or --frame-end <frame> Set end to frame <frame>, supports +/- for relative frames too.
-j or --frame-jump <frames> Set number of frames to step forward after each rendered frame.
-o or --render-output <path> Set the render path and file name. Use '//' at the start of the path to render relative to the blend-file.
The '#' characters are replaced by the frame number, and used to define zero padding.
* 'animation_##_test.png' becomes 'animation_01_test.png' * 'test-######.png' becomes 'test-000001.png'
When the filename does not contain '#', The suffix '####' is added to the filename.
The frame number will be added at the end of the filename, eg: # blender -b animation.blend -o //render_ -F PNG -x 1 -a
-E or --engine <engine> Specify the render engine. Use '-E help' to list available engines.
-t or --threads <threads> Use amount of <threads> for rendering and other operations [1-1024], 0 for systems processor count.
Format Options: -F or --render-format <format> Set the render format. Valid options are:
Formats that can be compiled into Blender, not available on all systems:
-x or --use-extension <bool> Set option to add the file extension to the end of the file.
Animation Playback Options: -a <options> <file(s)> Instead of showing Blender's user interface, this runs Blender as an animation player, to view movies and image sequences rendered in Blender (ignored if '-b' is set).
Playback Arguments:
-p <sx> <sy> Open with lower left corner at <sx>, <sy>. -m Read from disk (Do not buffer). -f <fps> <fps-base> Specify FPS to start with. -j <frame> Set frame step to <frame>. -s <frame> Play from <frame>. -e <frame> Play until <frame>. -c <cache_memory> Amount of memory in megabytes to allow for caching images during playback. Zero disables (clamping to a fixed number of frames instead).
Window Options: -w or --window-border Force opening with borders.
-W or --window-fullscreen Force opening in fullscreen mode.
-p or --window-geometry <sx> <sy> <w> <h> Open with lower left corner at <sx>, <sy> and width and height as <w>, <h>.
-M or --window-maximized Force opening maximized.
-con or --start-console Start with the console window open (ignored if '-b' is set), (Windows only).
--no-native-pixels Do not use native pixel size, for high resolution displays (MacBook 'Retina').
--no-window-focus Open behind other windows and without taking focus.
Python Options: -y or --enable-autoexec Enable automatic Python script execution.
-Y or --disable-autoexec Disable automatic Python script execution (pydrivers & startup scripts), (compiled as non-standard default).
-P or --python <filename> Run the given Python script file.
--python-text <name> Run the given Python script text block.
--python-expr <expression> Run the given expression as a Python script.
--python-console Run Blender with an interactive console.
--python-exit-code <code> Set the exit-code in [0..255] to exit if a Python exception is raised (only for scripts executed from the command line), zero disables.
--python-use-system-env Allow Python to use system environment variables such as 'PYTHONPATH' and the user site-packages directory.
--addons <addon(s)> Comma separated list (no spaces) of add-ons to enable in addition to any default add-ons.
Logging Options: --log <match> Enable logging categories, taking a single comma separated argument. Multiple categories can be matched using a '.*' suffix, so '--log "wm.*"' logs every kind of window-manager message. Sub-string can be matched using a '*' prefix and suffix, so '--log "*undo*"' logs every kind of undo-related message. Use "^" prefix to ignore, so '--log "*,^wm.operator.*"' logs all except for 'wm.operators.*' Use "*" to log everything.
--log-level <level> Set the logging verbosity level (higher for more details) defaults to 1, use -1 to log all levels.
--log-show-basename Only show file name in output (not the leading path).
--log-show-backtrace Show a back trace for each log message (debug builds only).
--log-show-timestamp Show a timestamp for each log message in seconds since start.
--log-file <filename> Set a file to output the log to.
Debug Options: -d or --debug Turn debugging on.
* Enables memory error detection * Disables mouse grab (to interact with a debugger in some cases) * Keeps Python's 'sys.stdin' rather than setting it to None
--debug-value <value> Set debug value of <value> on startup.
--debug-events Enable debug messages for the event system.
--debug-ffmpeg Enable debug messages from FFmpeg library.
--debug-handlers Enable debug messages for event handling.
--debug-libmv Enable debug messages from libmv library.
--debug-cycles Enable debug messages from Cycles.
--debug-memory Enable fully guarded memory allocation and debugging.
--debug-jobs Enable time profiling for background jobs.
--debug-python Enable debug messages for Python.
--debug-depsgraph Enable all debug messages from dependency graph.
--debug-depsgraph-eval Enable debug messages from dependency graph related on evaluation.
--debug-depsgraph-build Enable debug messages from dependency graph related on graph construction.
--debug-depsgraph-tag Enable debug messages from dependency graph related on tagging.
--debug-depsgraph-no-threads Switch dependency graph to a single threaded evaluation.
--debug-depsgraph-time Enable debug messages from dependency graph related on timing.
--debug-depsgraph-pretty Enable colors for dependency graph debug messages.
--debug-depsgraph-uuid Verify validness of session-wide identifiers assigned to ID datablocks.
--debug-ghost Enable debug messages for event handling.
--debug-gpu Enable GPU debug context and information for OpenGL 4.3+.
--debug-gpu-force-workarounds Enable workarounds for typical GPU issues and disable all GPU extensions.
--debug-wm Enable debug messages for the window manager, shows all operators in search, shows keymap errors.
--debug-xr Enable debug messages for virtual reality contexts. Enables the OpenXR API validation layer, (OpenXR) debug messages and general information prints.
--debug-xr-time Enable debug messages for virtual reality frame rendering times.
--debug-all Enable all debug messages.
--debug-io Enable debug messages for I/O (Collada, ...).
--debug-fpe Enable floating-point exceptions.
--debug-exit-on-error Immediately exit when internal errors are detected.
--disable-crash-handler Disable the crash handler.
--disable-abort-handler Disable the abort handler.
--verbose <verbose> Set the logging verbosity level for debug messages that support it.
Misc Options: --open-last Open the most recently opened blend file, instead of the default startup file.
--app-template <template> Set the application template (matching the directory name), use 'default' for none.
--factory-startup Skip reading the BLENDER_STARTUP_FILE in the users home directory.
--enable-event-simulate Enable event simulation testing feature 'bpy.types.Window.event_simulate'.
--env-system-datafiles Set the BLENDER_SYSTEM_DATAFILES environment variable.
--env-system-scripts Set the BLENDER_SYSTEM_SCRIPTS environment variable.
--env-system-python Set the BLENDER_SYSTEM_PYTHON environment variable.
-noaudio Force sound system to None.
-setaudio Force sound system to a specific device.
-h or --help Print this help text and exit.
/? Print this help text and exit (Windows only).
-R Register blend-file extension, then exit (Windows only).
-r Silently register blend-file extension, then exit (Windows only).
-v or --version Print Blender version and exit.
-- End option processing, following arguments passed unchanged. Access via Python's 'sys.argv'.
Other Options: --debug-freestyle Enable debug messages for Freestyle.
Argument Parsing: Arguments must be separated by white space, eg: # blender -ba test.blend ...will exit since '-ba' is an unknown argument.
Argument Order: Arguments are executed in the order they are given. eg: # blender --background test.blend --render-frame 1 --render-output '/tmp' ...will not render to '/tmp' because '--render-frame 1' renders before the output path is set. # blender --background --render-output /tmp test.blend --render-frame 1 ...will not render to '/tmp' because loading the blend-file overwrites the render output that was set. # blender --background test.blend --render-output /tmp --render-frame 1 ...works as expected.
$BLENDER_USER_CONFIG      Directory for user configuration files. $BLENDER_USER_SCRIPTS     Directory for user scripts. $BLENDER_SYSTEM_SCRIPTS   Directory for system wide scripts. $BLENDER_USER_DATAFILES   Directory for user data files (icons, translations, ..). $BLENDER_SYSTEM_DATAFILES Directory for system wide data files. $BLENDER_SYSTEM_PYTHON    Directory for system Python libraries. $OCIO                     Path to override the OpenColorIO config file. $TMP or $TMPDIR           Store temporary files here.
luxrender(1)
This manpage was written for a Debian GNU/Linux system by Daniel Mester <mester@uni-bremen.de> and updated by Cyril Brulebois <cyril.brulebois@enst-bretagne.fr> and Dan Eicher <dan@trollwerks.org>.
PDFPOSTER(1)                                                        PDFPOSTER(1)
pdfposter - Scale and tile PDF images/pages to print on multiple pages.
pdfposter <options> infile outfile
pdfposter can be used to create a large poster by building it from multiple pages and/or printing it on large media. It expects as input a PDF file, normally printing on a single page. The output is again a PDF file, maybe containing multiple pages together building the poster.  The input page will be scaled to obtain the desired size.
The program uses a simple but efficient method which is possible with PDF: All new pages share the same data stream of the scaled page. Thus resulting file grows moderately.
To control its operation, you need to specify either the size of the desired poster or a scale factor for the image:
• Given the poster size, it calculates the required number of sheets to print on, and from that a scale factor to fill these sheets optimally with the input image.
• Given a scale factor, it derives the required number of pages from the input image size, and positions the scaled image centered on this area.
General Options -h, --help Show help message and exit
--help-media-names List available media and distance names and exit
--help-box-definitions Show help about specifying BOX for --media-size and --poster-size and exit
-v, --verbose Be verbose. Tell about scaling, rotation and number of pages. Can be used more than once to increase the verbosity.
-n, --dry-run Show what would have been done, but do not generate files.
Defining Input -f, --first First page to convert (default: first page).
-l, --last Last page to convert (default: last page).
-A, --art-box Use the content area defined by the ArtBox (default: use the area defined by the TrimBox)
Defining Output -m BOX, --media-size=BOX Specify the desired media size to print on.  See below for BOX. The default is A4 in the standard package.
-p BOX, --poster-size=BOX Specify the poster size. See below for BOX.  pdfposter will autonomously choose scaling and rotation to best fit the input onto the poster (see EXAMPLES below).
If you give neither the -s nor the -p option, the default poster size is identical to the media size.
-s NUMBER Specify a linear scaling factor to produce the poster.  Together with the input image size and optional margins, this induces an output poster size. So don't specify both -s and -p.
Default is deriving the scale factor to fit a given poster size.
Box Definition The BOX mentioned above is a specification of horizontal and vertical size. The syntax is as follows (with multiplier being specified optionally): box = [ multiplier ] unit
multiplier = number "x" number
unit = medianame or distancename
Many international media names are recognised by the program, in upper and lower case, and can be shortened to their first few characters, as long as unique. For instance 'A0', 'Let'. Distance names are like 'cm', 'inch', 'ft'.
Medias are typically not quadratic but rectangular, which means width and height differ. Thus using media names is a bit tricky:
10x20cm obvious: 10 cm x 20 cm (portrait)
20x10cm same as 10x20cm, since all boxes are rotated to portrait format
Now when using media names it gets tricky:
1x1a4  same as approx. 21x29cm (21 cm x 29 cm, portrait)
1x2a4  same as approx. 21x58cm (21 cm x 58 cm, portrait)
This are two a4 pages put together at the small side: One portrait page wide and two portrait pages high.
2x1a4  same as approx. 42x29cm, which is rotated to portrait and is (approx.) the same as 29x42cm (29 cm x 42 cm)
This are two a4 pages put together at the long side: Two portrait pages wide and one portrait page high.
pdfposter -mA3 -pA0 a4.pdf out.pdf Prints an A4 input file on 8 A3 pages, forming an A0 poster.
pdfposter -p3x3Let a4.pdf out.pdf Prints an inputfile on a poster of 3x3 Letter pages.
pdfposter -mA0 input.pdf out.pdf Enlarges an inputfile to print on a large-media A0 capable device.
pdfposter -s4 input.pdf out.pdf Enlarge an inputfile exactly 4 times, print on the default A4 media, and let pdfposter determine the number of pages required.
pdfposter -m10x10cm -pa0 a4.pdf out.pdf Just to show how efficient pdfposter is: This will create a file containing 192 pages, but only 15 times as big as the single page. With a4.pdf being a quite empty page, this ratio should be even better for filled pages.
More examples including sample pictures can be found at https://pdfposter.readthedocs.io/en/latest/Examples.html
Examples for automatic scaling • For printing 2 portrait A4 pages high (approx. 58cm) and let pdfposter determine how many portrait pages wide, specify a large number of vertical pages. eg:
pdfposter -p999x2a4 testpage-wide.pdf out.pdf
• For printing 2 landscape A4 pages high (approx. 20cm) and let pdfposter determine how many landscape pages wide, specify a large number of horizontal pages. eg:
pdfposter -p2x999a4 testpage-wide.pdf out.pdf
poster(1), pdfnup(1) https://pypi.org/project/pdfnup/, pdfsplit(1) https://pypi.org/project/pdfsplit/, pdfgrid(1) https://pypi.org/project/pdfgrid/
Project Homepage https://pdfposter.readthedocs.io/
Hartmut Goebel <h.goebel@crazy-compilers.com>
Licence: GNU Public Licence v3 (GPLv3)
2008-2018 by Hartmut Goebel
GPGV(1)                       GNU Privacy Guard 2.2                      GPGV(1)
gpgv - Verify OpenPGP signatures
gpgv [options] signed_files
gpgv is an OpenPGP signature verification tool.
This program is actually a stripped-down version of gpg which is only able to check signatures. It is somewhat smaller than the fully-blown gpg and uses a different (and simpler) way to check that the public keys used to make the signature are valid. There are no configuration files and only a few options are implemented.
gpgv assumes that all keys in the keyring are trustworthy.  That does also mean that it does not check for expired or revoked keys.
If no --keyring option is given, gpgv looks for a ``default'' keyring named ‘trustedkeys.kbx’ (preferred) or ‘trustedkeys.gpg’ in the home directory of GnuPG, either the default home directory or the one set by the --homedir option or the GNUPGHOME environment variable.  If any --keyring option is used, gpgv will not look for the default keyring. The --keyring option may be used multiple times and all specified keyrings will be used together.
The program returns 0 if everything is fine, 1 if at least one signature was bad, and other error codes for fatal errors.
gpgv recognizes these options:
--verbose -v     Gives more information during processing. If used twice, the input data is listed in detail.
--quiet -q     Try to be as quiet as possible.
--keyring file Add file to the list of keyrings.  If file begins with a tilde and a slash, these are replaced by the HOME directory. If the filename does not contain a slash, it is assumed to be in the home- directory ("~/.gnupg" if --homedir is not used).
--output file -o file Write output to file; to write to stdout use -.  This option can be used to get the signed text from a cleartext or binary signature; it also works for detached signatures, but in that case this option is in general not useful.  Note that an existing file will be overwritten.
--logger-fd n Write log output to file descriptor n and not to stderr.
--log-file file Same as --logger-fd, except the logger data is written to file file.  Use ‘socket://’ to log to socket.
--ignore-time-conflict GnuPG normally checks that the timestamps associated with keys and signatures have plausible values. However, sometimes a signature seems to be older than the key due to clock problems. This option turns these checks into warnings.
--weak-digest name Treat the specified digest algorithm as weak.  Signatures made over weak digests algorithms are normally rejected. This option can be supplied multiple times if multiple algorithms should be considered weak.  MD5 is always considered weak, and does not need to be listed explicitly.
gpgv pgpfile gpgv sigfile [datafile] Verify the signature of the file. The second form is used for detached signatures, where sigfile is the detached signature (either ASCII-armored or binary) and datafile contains the signed data; if datafile is "-" the signed data is expected on stdin; if datafile is not given the name of the file holding the signed data is constructed by cutting off the extension (".asc", ".sig" or ".sign") from sigfile.
~/.gnupg/trustedkeys.gpg The default keyring with the allowed keys.
gpg(1)
gh-workflow - View details about GitHub Actions workflows
gh workflow <command> [flags]
List, view, and run workflows in GitHub Actions.
gh(1), gh-workflow-disable(1), gh-workflow-enable(1), gh-workflow- list(1), gh-workflow-run(1), gh-workflow-view(1)
IOSTAT(1)                      Linux User's Manual                     IOSTAT(1)
iostat - Report Central Processing Unit (CPU) statistics and input/output statistics for devices and partitions.
iostat [ -c ] [ -d ] [ -h ] [ -k | -m ] [ -N ] [ -s ] [ -t ] [ -V ] [ -x ] [ -y ] [ -z ] [ --dec={ 0 | 1 | 2 } ] [ { -f | +f } directory ] [ -j { ID | LABEL | PATH | UUID | ... } ] [ -o JSON ] [ [ -H ] -g group_name ] [ --human ] [ --pretty ] [ -p [ device[,...] | ALL ] ] [ device [...] | ALL ] [ interval [ count ] ]
The iostat command is used for monitoring system input/output device loading by observing the time the devices are active in relation to their average transfer rates. The iostat command generates reports that can be used to change system configuration to better balance the input/output load between physical disks.
The first report generated by the iostat command provides statistics concerning the time since the system was booted, unless the -y option is used (in this case, this first report is omitted).  Each subsequent report covers the time since the previous report. All statistics are reported each time the iostat command is run. The report consists of a CPU header row followed by a row of CPU statistics. On multiprocessor systems, CPU statistics are calculated system-wide as averages among all processors. A device header row is displayed followed by a line of statistics for each device that is configured.
The interval parameter specifies the amount of time in seconds between each report. The count parameter can be specified in conjunction with the interval parameter. If the count parameter is specified, the value of count determines the number of reports generated at interval seconds apart. If the interval parameter is specified without the count parameter, the iostat command generates reports continuously.
The iostat command generates two types of reports, the CPU Utilization report and the Device Utilization report.
CPU Utilization Report The first report generated by the iostat command is the CPU Utilization Report. For multiprocessor systems, the CPU values are global averages among all processors.  The report has the following format:
%user  Show the percentage of CPU utilization that occurred while executing at the user level (application).
%system Show the percentage of CPU utilization that occurred while executing at the system level (kernel).
Device Utilization Report The second report generated by the iostat command is the Device Utilization Report.  The device report provides statistics on a per physical device or partition basis. Block devices and partitions for which statistics are to be displayed may be entered on the command line.  If no device nor partition is entered, then statistics are displayed for every device used by the system, and providing that the kernel maintains statistics for it.  If the ALL keyword is given on the command line, then statistics are displayed for every device defined by the system, including those that have never been used.  Transfer rates are shown in 1K blocks by default, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used.  The report may show the following fields, depending on the flags used (e.g.  -x, -s and -k or -m):
Device: This column gives the device (or partition) name as listed in the /dev directory.
tps    Indicate the number of transfers per second that were issued to the device. A transfer is an I/O request to the device. Multiple logical requests can be combined into a single I/O request to the device. A transfer is of indeterminate size.
Blk_read/s (kB_read/s, MB_read/s) Indicate the amount of data read from the device expressed in a number of blocks (kilobytes, megabytes) per second. Blocks are equivalent to sectors and therefore have a size of 512 bytes.
Blk_wrtn/s (kB_wrtn/s, MB_wrtn/s) Indicate the amount of data written to the device expressed in a number of blocks (kilobytes, megabytes) per second.
Blk_dscd/s (kB_dscd/s, MB_dscd/s) Indicate the amount of data discarded for the device expressed in a number of blocks (kilobytes, megabytes) per second.
Blk_w+d/s (kB_w+d/s, MB_w+d/s) Indicate the amount of data written to or discarded for the device expressed in a number of blocks (kilobytes, megabytes) per second.
Blk_read (kB_read, MB_read) The total number of blocks (kilobytes, megabytes) read.
Blk_wrtn (kB_wrtn, MB_wrtn) The total number of blocks (kilobytes, megabytes) written.
Blk_dscd (kB_dscd, MB_dscd) The total number of blocks (kilobytes, megabytes) discarded.
Blk_w+d (kB_w+d, MB_w+d) The total number of blocks (kilobytes, megabytes) written or discarded.
r/s    The number (after merges) of read requests completed per second for the device.
w/s    The number (after merges) of write requests completed per second for the device.
d/s    The number (after merges) of discard requests completed per second for the device.
f/s    The number (after merges) of flush requests completed per second for the device.  This counts flush requests executed by disks. Flush requests are not tracked for partitions. Before being merged, flush operations are counted as writes.
sec/s (kB/s, MB/s) The number of sectors (kilobytes, megabytes) read from, written to or discarded for the device per second.
rsec/s (rkB/s, rMB/s) The number of sectors (kilobytes, megabytes) read from the device per second.
wsec/s (wkB/s, wMB/s) The number of sectors (kilobytes, megabytes) written to the device per second.
dsec/s (dkB/s, dMB/s) The number of sectors (kilobytes, megabytes) discarded for the device per second.
rqm/s  The number of I/O requests merged per second that were queued to the device.
rrqm/s The number of read requests merged per second that were queued to the device.
wrqm/s The number of write requests merged per second that were queued to the device.
drqm/s The number of discard requests merged per second that were queued to the device.
%rrqm  The percentage of read requests merged together before being sent to the device.
%wrqm  The percentage of write requests merged together before being sent to the device.
%drqm  The percentage of discard requests merged together before being sent to the device.
rareq-sz The average size (in kilobytes) of the read requests that were issued to the device.
wareq-sz The average size (in kilobytes) of the write requests that were issued to the device.
dareq-sz The average size (in kilobytes) of the discard requests that were issued to the device.
r_await The average time (in milliseconds) for read requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.
w_await The average time (in milliseconds) for write requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.
d_await The average time (in milliseconds) for discard requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them.
f_await The average time (in milliseconds) for flush requests issued to the device to be served.  The block layer combines flush requests and executes at most one at a time. Thus flush operations could be twice as long: Wait for current flush request, then execute it, then wait for the next one.
%util  Percentage of elapsed time during which I/O requests were issued to the device (bandwidth utilization for the device). Device saturation occurs when this value is close to 100% for devices serving requests serially.  But for devices serving requests in parallel, such as RAID arrays and modern SSDs, this number does not reflect their performance limits.
-c     Display the CPU utilization report.
-d     Display the device utilization report.
-f directory +f directory Specify an alternative directory for iostat to read devices statistics. Option -f tells iostat to use only the files located in the alternative directory, whereas option +f tells it to use both the standard kernel files and the files located in the alternative directory to read device statistics.
directory is a directory containing files with statistics for devices managed in userspace.  It may contain:
- a "diskstats" file whose format is compliant with that located in "/proc", - statistics for individual devices contained in files whose format is compliant with that of files located in "/sys".
In particular, the following files located in directory may be used by iostat:
directory/block/device/stat directory/block/device/partition/stat
partition files must have an entry in directory/dev/block/ directory, e.g.:
directory/dev/block/major:minor --> ../../block/device/partition
-g group_name { device [...] | ALL } Display statistics for a group of devices.  The iostat command reports statistics for each individual device in the list then a line of global statistics for the group displayed as group_name and made up of all the devices in the list. The ALL keyword means that all the block devices defined by the system shall be included in the group.
-H     This option must be used with option -g and indicates that only global statistics for the group are to be displayed, and not statistics for individual devices in the group.
-h     This option is equivalent to specifying --human --pretty.
-j { ID | LABEL | PATH | UUID | ... } [ device [...] | ALL ] Display persistent device names. Keywords ID, LABEL, etc. specify the type of the persistent name. These keywords are not limited, only prerequisite is that directory with required persistent names is present in /dev/disk.  Optionally, multiple devices can be specified in the chosen persistent name type.  Because persistent device names are usually long, option --pretty is implicitly set with this option.
-k     Display statistics in kilobytes per second.
-m     Display statistics in megabytes per second.
-N     Display the registered device mapper names for any device mapper devices.  Useful for viewing LVM2 statistics.
-p [ { device[,...] | ALL } ] Display statistics for block devices and all their partitions that are used by the system.  If a device name is entered on the command line, then statistics for it and all its partitions are displayed. Last, the ALL keyword indicates that statistics have to be displayed for all the block devices and partitions defined by the system, including those that have never been used. If option -j is defined before this option, devices entered on the command line can be specified with the chosen persistent name type.
--pretty Make the Device Utilization Report easier to read by a human.
-s     Display a short (narrow) version of the report that should fit in 80 characters wide screens.
-t     Print the time for each report displayed. The timestamp format may depend on the value of the S_TIME_FORMAT environment variable (see below).
-x     Display extended statistics.
-y     Omit first report with statistics since system boot, if displaying multiple records at given interval.
-z     Tell iostat to omit output for any devices for which there was no activity during the sample period.
The iostat command takes into account the following environment variables:
POSIXLY_CORRECT When this variable is set, transfer rates are shown in 512-byte blocks instead of the default 1K blocks.
I=     SGR substring for device names.
S_TIME_FORMAT If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header. The iostat command will use the ISO 8601 format (YYYY-MM- DD) instead.  The timestamp displayed with option -t will also be compliant with ISO 8601 format.
iostat Display a single history since boot report for all CPU and Devices.
iostat -d 2 Display a continuous device report at two second intervals.
iostat -d 2 6 Display six reports at two second intervals for all devices.
iostat -x sda sdb 2 6 Display six reports of extended statistics at two second intervals for devices sda and sdb.
iostat -p sda 2 6 Display six reports at two second intervals for device sda and all its partitions (sda1, etc.)
/proc filesystem must be mounted for iostat to work.
Kernels older than 2.6.x are no longer supported.
Although iostat speaks of kilobytes (kB), megabytes (MB)..., it actually uses kibibytes (kiB), mebibytes (MiB)...  A kibibyte is equal to 1024 bytes, and a mebibyte is equal to 1024 kibibytes.