neulab/tldr huggingface dataset:
Copyright (C) 2002-2007 The Regents of the University of California. Produced at Lawrence Livermore National Laboratory (cf, DISCLAIMER). Copyright (C) 2008-2010 Lawrence Livermore National Security. Copyright (C) 2010-2016 SchedMD LLC.
scancel(1), scontrol(1), sinfo(1), srun(1), slurm_load_ctl_conf (3), slurm_load_jobs (3), slurm_load_node (3), slurm_load_partitions (3)
UDISKSCTL(1)                      User Commands                     UDISKSCTL(1)
udisksctl - The udisks command line tool
udisksctl status
udisksctl info {--object-path OBJECT | --block-device DEVICE | --drive DRIVE}
udisksctl mount {--object-path OBJECT | --block-device DEVICE} [--filesystem-type TYPE] [--options OPTIONS...] [--no-user-interaction]
udisksctl unmount {--object-path OBJECT | --block-device DEVICE} [--force] [--no-user-interaction]
udisksctl unlock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction] [--key-file PATH] [--read-only]
udisksctl lock {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]
udisksctl loop-setup --file PATH [--read-only] [--offset OFFSET] [--size SIZE] [--no-user-interaction]
udisksctl loop-delete {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]
udisksctl power-off {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]
udisksctl smart-simulate --file PATH {--object-path OBJECT | --block-device DEVICE} [--no-user-interaction]
udisksctl monitor
udisksctl dump
udisksctl help
udisksctl is a command-line program used to interact with the udisksd(8) daemon process.
status Shows high-level information about disk drives and block devices.
info Shows detailed information about OBJECT, DEVICE or DRIVE.
mount Mounts a device. The device will be mounted in a subdirectory in the /run/media hierarchy - upon successful completion, the mount point will be printed to standard output.
-t, --filesystem-type Filesystem type to use. If not specified, autodetected filesystem type will be used.
-o, --options The device will be mounted with a safe set of default options. You can influence the options passed to the mount(8) command using this option. Note that only safe options are allowed - requests with inherently unsafe options such as suid or dev that would allow the caller to gain additional privileges, are rejected.
unmount Unmounts a device. This only works if the device is mounted. The option --force can be used to request that the device is unmounted even if active references exists.
-f, --force Lazy unmount. Detach the filesystem from the file hierarchy now, and clean up all references to this filesystem as soon as it is not busy anymore.
unlock Unlocks an encrypted device. The passphrase will be requested from the controlling terminal and upon successful completion, the cleartext device will be printed to standard output.
--key-file=PATH Read passphrase from the given file.
lock Locks a device. This only works if the device is a cleartext device backed by a cryptotext device.
loop-setup Sets up a loop device backed by FILE.
-f, --file=FILE File to set up a loop device for.
-o, --offset=OFFSET The data start is moved OFFSET bytes into the specified file.
-s, --size=SIZE The data end is set to no more than SIZE bytes after the data start.
loop-delete Tears down a loop device.
power-off Arranges for the drive to be safely removed and powered off. On the OS side this includes ensuring that no process is using the drive, then requesting that in-flight buffers and caches are committed to stable storage. The exact steps for powering off the drive depends on the drive itself and the interconnect used. For drives connected through USB, the effect is that the USB device will be deconfigured followed by disabling the upstream hub port it is connected to.
Note that as some physical devices contain multiple drives (for example 4-in-1 flash card reader USB devices) powering off one drive may affect other drives. As such there are not a lot of guarantees associated with performing this action. Usually the effect is that the drive disappears as if it was unplugged.
smart-simulate Sets SMART data from the libatasmart blob given by FILE - see /usr/share/doc/libatasmart-devel-VERSION/ for blobs shipped with libatasmart. This is a debugging feature used to check that applications act correctly when a disk is failing.
-f, --file=FILE File with the libatasmart blob.
monitor Monitors the daemon for events.
dump Prints the current state of the daemon.
help Prints help and exit.
For commands that require a device as an argument following options can be used to specify it.
-b, --block-device=DEVICE Specify a device by its device file path. For example /dev/sda.
-p, --object-path=OBJECT Specify a device by the UDisks internal object path without the /org/freedesktop/UDisks2 prefix. For example block_devices/sda for the /dev/sda disk.
-d, --drive=DRIVE Specify a drive by name, for example VirtIO_Disk. This can be currently used only together with the info command.
The option --no-user-interaction can be used to request that no interaction (such as the user being presented with an authentication dialog) must occur when checking with polkit(8) whether the caller is authorized to perform the requested action.
This program does not assume that the caller is the super user - it is intended to be used by unprivileged users and authorizations are checked by the udisks daemon using polkit(8). Additionally, this program is not intended to be used by scripts or other programs - options/commands may change in incompatible ways in the future even in maintenance releases. See the “API STABILITY” section of udisks(8) for more information.
udisksctl ships with a bash completion script to complete commands, objects, block devices and some options.
This man page was originally written for UDisks2 by David Zeuthen <zeuthen@gmail.com> with a lot of help from many others.
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at https://github.com/storaged-project/udisks/issues.
udisks(8), udisksd(8), umount.udisks2(8), polkit(8)
PHPUNIT(1)                        User Commands                       PHPUNIT(1)
phpunit - PHPUnit command line interface
phpunit [options] UnitTest [UnitTest.php] phpunit [options] <directory>
Code Coverage Options:
--coverage-clover <file> Generate code coverage report in Clover XML format
--coverage-crap4j <file> Generate code coverage report in Crap4J XML format
--coverage-html <dir> Generate code coverage report in HTML format
--coverage-php <file> Export PHP_CodeCoverage object to file
--coverage-text=<file> Generate code coverage report in text format Default: Standard output
--coverage-xml <dir> Generate code coverage report in PHPUnit XML format
--whitelist <dir> Whitelist <dir> for code coverage analysis
--disable-coverage-ignore Disable annotations for ignoring code coverage
--no-coverage Ignore code coverage configuration
--dump-xdebug-filter <file> Generate script to set Xdebug code coverage filter
Logging Options:
--log-junit <file> Log test execution in JUnit XML format to file
--log-teamcity <file> Log test execution in TeamCity format to file
--testdox-html <file> Write agile documentation in HTML format to file
--testdox-text <file> Write agile documentation in Text format to file
--testdox-xml <file> Write agile documentation in XML format to file
--reverse-list Print defects in reverse order
Test Selection Options:
--filter <pattern> Filter which tests to run
--testsuite <name,...> Filter which testsuite to run
--group ... Only runs tests from the specified group(s)
--exclude-group ... Exclude tests from the specified group(s)
--list-groups List available test groups
--list-suites List available test suites
--list-tests List available tests
--list-tests-xml <file> List available tests in XML format
--test-suffix ... Only search for test in files with specified suffix(es). Default: Test.php,.phpt
Test Execution Options:
--dont-report-useless-tests Do not report tests that do not test anything
--strict-coverage Be strict about @covers annotation usage
--strict-global-state Be strict about changes to global state
--disallow-test-output Be strict about output during tests
--disallow-resource-usage Be strict about resource usage during small tests
--enforce-time-limit Enforce time limit based on test size
--default-time-limit=<sec> Timeout in seconds for tests without @small, @medium or @large
--disallow-todo-tests Disallow @todo-annotated tests
--process-isolation Run each test in a separate PHP process
--globals-backup Backup and restore $GLOBALS for each test
--static-backup Backup and restore static attributes for each test
--colors=<flag> Use colors in output ("never", "auto" or "always")
--columns <n> Number of columns to use for progress output
--columns max Use maximum number of columns for progress output
--stderr Write to STDERR instead of STDOUT
--stop-on-defect Stop execution upon first not-passed test
--stop-on-error Stop execution upon first error
--stop-on-failure Stop execution upon first error or failure
--stop-on-warning Stop execution upon first warning
--stop-on-risky Stop execution upon first risky test
--stop-on-skipped Stop execution upon first skipped test
--stop-on-incomplete Stop execution upon first incomplete test
--fail-on-warning Treat tests with warnings as failures
--fail-on-risky Treat risky tests as failures
-v|--verbose Output more verbose information
--debug Display debugging information
--loader <loader> TestSuiteLoader implementation to use
--repeat <times> Runs the test(s) repeatedly
--teamcity Report test execution progress in TeamCity format
--testdox Report test execution progress in TestDox format
--testdox-group Only include tests from the specified group(s)
--testdox-exclude-group Exclude tests from the specified group(s)
--printer <printer> TestListener implementation to use
--resolve-dependencies Resolve dependencies between tests
--order-by=<order> Run tests in order: default|reverse|random|defects|depends
--random-order-seed=<N> Use a specific random seed <N> for random order
--cache-result Write run result to cache to enable ordering tests defects-first
Configuration Options:
--prepend <file> A PHP script that is included as early as possible
--bootstrap <file> A PHP script that is included before the tests run
-c|--configuration <file> Read configuration from XML file
--no-configuration Ignore default configuration file (phpunit.xml)
--no-logging Ignore logging configuration
--no-extensions Do not load PHPUnit extensions
--include-path <path(s)> Prepend PHP's include_path with given path(s)
-d key[=value] Sets a php.ini value
--generate-configuration Generate configuration file with suggested settings
--cache-result-file=<file> Specify result cache path and filename
Miscellaneous Options:
-h|--help Prints this usage information
--version Prints the version and exits
--atleast-version <min> Checks that version is greater than min and exits
--check-version Check whether PHPUnit is the latest version
quotacheck(8)                System Manager's Manual               quotacheck(8)
quotacheck - scan a filesystem for disk usage, create, check and repair quota files
quotacheck [ -gubcfinvdMmR ] [ -F quota-format ] -a | filesystem
quotacheck examines each filesystem, builds a table of current disk usage, and compares this table against that recorded in the disk quota file for the filesystem (this step is omitted if option -c is specified). If any inconsistencies are detected, both the quota file and the current system copy of the incorrect quotas are updated (the latter only occurs if an active filesystem is checked which is not advised).  By default, only user quotas are checked.  quotacheck expects each filesystem to be checked to have quota files named [a]quota.user and [a]quota.group located at the root of the associated filesystem.  If a file is not present, quotacheck will create it.
If the quota file is corrupted, quotacheck tries to save as much data as possible.  Rescuing data may need user intervention. With no additional options quotacheck will simply exit in such a situation. When in interactive mode (option -i) , the user is asked for advice. Advice can also be provided from command line (see option -n) , which is useful when quotacheck is run automatically (ie. from script) and failure is unacceptable.
quotacheck should be run each time the system boots and mounts non-valid filesystems.  This is most likely to happen after a system crash.
It is strongly recommended to run quotacheck with quotas turned off for the filesystem. Otherwise, possible damage or loss to data in the quota files can result.  It is also unwise to run quotacheck on a live filesystem as actual usage may change during the scan.  To prevent this, quotacheck tries to remount the filesystem read-only before starting the scan.  After the scan is done it remounts the filesystem read-write. You can disable this with option -m.  You can also make quotacheck ignore the failure to remount the filesystem read-only with option -M.
-b, --backup Forces quotacheck to make backups of the quota file before writing the new data.
-v, --verbose quotacheck reports its operation as it progresses.  Normally it operates silently.  If the option is specified twice, also the current directory is printed (note that printing can slow down the scan measurably).
-d, --debug Enable debugging mode.  It will result in a lot of information which can be used in debugging the program. The output is very verbose and the scan will be slow.
-u, --user Only user quotas listed in /etc/mtab or on the filesystems specified are to be checked.  This is the default action.
-g, --group Only group quotas listed in /etc/mtab or on the filesystems specified are to be checked.
-c, --create-files Don't read existing quota files. Just perform a new scan and save it to disk.  quotacheck also skips scanning of old quota files when they are not found.
-f, --force Forces checking and writing of new quota files on filesystems with quotas enabled. This is not recommended as the created quota files may be out of sync.
-M, --try-remount This flag forces checking of filesystem in read-write mode if a remount fails. Do this only when you are sure no process will write to a filesystem while scanning.
-m, --no-remount Don't try to remount filesystem read-only. See comment with option -M.
-i, --interactive Interactive mode. By default quotacheck exits when it finds an error. In interactive mode user is asked for input instead.  See option -n.
-n, --use-first-dquot If the quota files become corrupted, it is possible for duplicate entries for a single user or group ID to exist.  Normally in this case, quotacheck exits or asks user for input. When this option is set, the first entry found is always used (this option works in interactive mode too).
-F, --format=format-name Check and fix quota files of specified format (ie. don't perform format auto-detection). This is recommended as detection might not work well on corrupted quota files.  Possible format names are: vfsold Original quota format with 16-bit UIDs / GIDs, vfsv0 Quota format with 32-bit UIDs / GIDs, 64-bit space usage, 32-bit inode usage and limits, vfsv1 Quota format with 64-bit quota limits and usage, rpc (quota over NFS), xfs (quota on XFS filesystem)
-a, --all Check all mounted non-NFS filesystems in /etc/mtab
-R, --exclude-root When used together with the -a option, all filesystems except for the root filesystem are checked for quotas.
quotacheck should only be run by super-user. Non-privileged users are presumably not allowed to read all the directories on the given filesystem.
quota(1), quotactl(2), fstab(5), quotaon(8), repquota(8), convertquota(8), setquota(8), edquota(8), fsck(8), efsck(8), e2fsck(8), xfsck(8)
Jan Kara <jack@suse.cz> Based on old quotacheck by: Edvard Tuinder <ed@elm.net> Marco van Wieringen <mvw@planets.elm.net>
license(3)                          QuantLib                          license(3)
license - QuantLib License
QuantLib is Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl Copyright (C) 2003, 2004, 2005, 2006 StatPro Italia srl Copyright (C) 2002, 2003, 2004, 2005, 2006 Ferdinando Ametrano
Copyright (C) 2001, 2002, 2003 Nicolas Di Césaré Copyright (C) 2001, 2002, 2003 Sadruddin Rejeb
Copyright (C) 2002, 2003, 2004 Decillion Pty(Ltd)
Copyright (C) 2003, 2004 Neil Firth Copyright (C) 2003, 2004 Roman Gitlin Copyright (C) 2003 Niels Elken Sønderby Copyright (C) 2003 Kawanishi Tomoya
Copyright (C) 2004 FIMAT Group Copyright (C) 2004 M-Dimension Consulting Inc. Copyright (C) 2004 Mike Parker Copyright (C) 2004 Walter Penschke Copyright (C) 2004 Gianni Piolanti Copyright (C) 2004, 2005, 2006 Klaus Spanderen Copyright (C) 2004 Jeff Yu
Copyright (C) 2005 Toyin Akin Copyright (C) 2005 Sercan Atalik Copyright (C) 2005, 2006 Theo Boafo Copyright (C) 2005, 2006 Piter Dias Copyright (C) 2005 Gary Kennedy Copyright (C) 2005, 2006 Joseph Wang Copyright (C) 2005 Charles Whitmore
Copyright (C) 2006 Banca Profilo S.p.A. Copyright (C) 2006 Marco Bianchetti Copyright (C) 2006 Yiping Chen Copyright (C) 2006 Warren Chou Copyright (C) 2006 Cristina Duminuco Copyright (C) 2006 Giorgio Facchinetti Copyright (C) 2006 Chiara Fornarola Copyright (C) 2006 Silvia Frasson Copyright (C) 2006 Richard Gould Copyright (C) 2006 Mark Joshi Copyright (C) 2006 Allen Kuo Copyright (C) 2006 Roland Lichters Copyright (C) 2006 Katiuscia Manzoni Copyright (C) 2006 Mario Pucci
QuantLib includes code taken from Peter Jäckel's book 'Monte Carlo Methods in Finance'.
QuantLib includes software developed by the University of Chicago, as Operator of Argonne National Laboratory.
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the names of the copyright holders nor the names of the QuantLib Group and its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Comments on Copyright and License QuantLib is Non-Copylefted Free Software [1] released under the modified BSD License [2] (also know as XFree86-style license).
QuantLib is Open Source [3] because of its license: it is OSI Certified Open Source Software [4]. OSI Certified is a certification mark of the Open Source Initiative [5].
The modified BSD License is GPL compatible as confirmed by the Free Software Foundation [6].
This license has been adopted to allow free use of QuantLib and its source, to make QuantLib flourish as a free-software/open-source project. It allows proprietary extensions to be commercialized.
[1] http://www.gnu.org/philosophy/categories.html#Non- CopyleftedFreeSoftware [2] http://www.opensource.org/licenses/bsd-license.html [3] http://www.opensource.org/docs/definition.html [4] http://www.opensource.org/docs/certification_mark.html [5] http://www.opensource.org [6] http://www.gnu.org/philosophy/bsd.html
XPROP(1)                     General Commands Manual                    XPROP(1)
xprop - property displayer for X
xprop [-help] [-grammar] [-id id] [-root] [-name name] [-frame] [-font font] [-display display] [-len n] [-notype] [-fs file] [-remove property- name] [-set property-name value] [-spy] [-f atom format [dformat]]* [format [dformat] atom]*
The xprop utility is for displaying window and font properties in an X server.  One window or font is selected using the command line arguments or possibly in the case of a window, by clicking on the desired window. A list of properties is then given, possibly with formatting information.
-help   Print out a summary of command line options.
-grammar Print out a detailed grammar for all command line options.
-id id  This argument allows the user to select window id on the command line rather than using the pointer to select the target window. This is very useful in debugging X applications where the target window is not mapped to the screen or where the use of the pointer might be impossible or interfere with the application.
-name name This argument allows the user to specify that the window named name is the target window on the command line rather than using the pointer to select the target window.
-font font This argument allows the user to specify that the properties of font font should be displayed.
-root   This argument specifies that X's root window is the target window.  This is useful in situations where the root window is completely obscured.
-display display This argument allows you to specify the server to connect to; see X(7).
-len n  Specifies that at most n bytes of any property should be read or displayed.
-notype Specifies that the type of each property should not be displayed.
-fs file Specifies that file file should be used as a source of more formats for properties.
-frame  Specifies that when selecting a window by hand (i.e. if none of -name, -root, or -id are given), look at the window manager frame (if any) instead of looking for the client window.
-remove property-name Specifies the name of a property to be removed from the indicated window.
-set property-name value Specifies the name of a property and a property value, to be set on the indicated window.
-spy    Examine window properties forever, looking for property change events.
-f name format [dformat] Specifies that the format for name should be format and that the dformat for name should be dformat.  If dformat is missing, " = $0+\n" is assumed.
For each of these properties, its value on the selected window or font is printed using the supplied formatting information if any.  If no formatting information is supplied, internal defaults are used.  If a property is not defined on the selected window or font, "not defined" is printed as the value for that property.  If no property list is given, all the properties possessed by the selected window or font are printed.
A window may be selected in one of four ways.  First, if the desired window is the root window, the -root argument may be used.  If the desired window is not the root window, it may be selected in two ways on the command line, either by id number such as might be obtained from xwininfo, or by name if the window possesses a name.  The -id argument selects a window by id number in either decimal or hex (must start with 0x) while the -name argument selects a window by name.
The last way to select a window does not involve the command line at all. If none of -font, -id, -name, and -root are specified, a crosshairs cursor is displayed and the user is allowed to choose any visible window by pressing any pointer button in the desired window.  If it is desired to display properties of a font as opposed to a window, the -font argument must be used.
Other than the above four arguments and the -help argument for obtaining help, and the -grammar argument for listing the full grammar for the command line, all the other command line arguments are used in specifying both the format of the properties to be displayed and how to display them.  The -len n argument specifies that at most n bytes of any given property will be read and displayed.  This is useful for example when displaying the cut buffer on the root window which could run to several pages if displayed in full.
Normally each property name is displayed by printing first the property name then its type (if it has one) in parentheses followed by its value. The -notype argument specifies that property types should not be displayed.  The -fs argument is used to specify a file containing a list of formats for properties while the -f argument is used to specify the format for one property.
The formatting information for a property actually consists of two parts, a format and a dformat.  The format specifies the actual formatting of the property (i.e., is it made up of words, bytes, or longs?, etc.) while the dformat specifies how the property should be displayed.
The following paragraphs describe how to construct formats and dformats. However, for the vast majority of users and uses, this should not be necessary as the built in defaults contain the formats and dformats necessary to display all the standard properties.  It should only be necessary to specify formats and dformats if a new property is being dealt with or the user dislikes the standard display format.  New users especially are encouraged to skip this part.
A format consists of one of 0, 8, 16, or 32 followed by a sequence of one or more format characters.  The 0, 8, 16, or 32 specifies how many bits per field there are in the property.  Zero is a special case meaning use the field size information associated with the property itself.  (This is only needed for special cases like type INTEGER which is actually three different types depending on the size of the fields of the property.)
A value of 8 means that the property is a sequence of bytes while a value of 16 would mean that the property is a sequence of words.  The difference between these two lies in the fact that the sequence of words will be byte swapped while the sequence of bytes will not be when read by a machine of the opposite byte order of the machine that originally wrote the property.  For more information on how properties are formatted and stored, consult the Xlib manual.
Once the size of the fields has been specified, it is necessary to specify the type of each field (i.e., is it an integer, a string, an atom, or what?)  This is done using one format character per field.  If there are more fields in the property than format characters supplied, the last character will be repeated as many times as necessary for the extra fields.  The format characters and their meaning are as follows:
a      The field holds an atom number.  A field of this type should be of size 32.
b      The field is an boolean.  A 0 means false while anything else means true.
c      The field is an unsigned number, a cardinal.
i      The field is a signed integer.
m      The field is a set of bit flags, 1 meaning on.
s      This field and the next ones until either a 0 or the end of the property represent a sequence of bytes.  This format character is only usable with a field size of 8 and is most often used to represent a string.
t      This field and the next ones until either a 0 or the end of the property represent an internationalized text string. This format character is only usable with a field size of 8. The string is assumed to be in an ICCCM compliant encoding and is converted to the current locale encoding before being output.
x      The field is a hex number (like 'c' but displayed in hex - most useful for displaying window ids and the like)
An example format is 32ica which is the format for a property of three fields of 32 bits each, the first holding a signed integer, the second an unsigned integer, and the third an atom.
The format of a dformat unlike that of a format is not so rigid.  The only limitations on a dformat is that one may not start with a letter or a dash.  This is so that it can be distinguished from a property name or an argument.  A dformat is a text string containing special characters instructing that various fields be printed at various points in a manner similar to the formatting string used by printf.  For example, the dformat " is ( $0, $1 \)\n" would render the POINT 3, -4 which has a format of 32ii as " is ( 3, -4 )\n".
Any character other than a $, ?, \, or a ( in a dformat prints as itself. To print out one of $, ?, \, or ( precede it by a \.  For example, to print out a $, use \$.  Several special backslash sequences are provided as shortcuts.  \n will cause a newline to be displayed while \t will cause a tab to be displayed.  \o where o is an octal number will display character number o.
A $ followed by a number n causes field number n to be displayed.  The format of the displayed field depends on the formatting character used to describe it in the corresponding format.  I.e., if a cardinal is described by 'c' it will print in decimal while if it is described by a 'x' it is displayed in hex.
If the field is not present in the property (this is possible with some properties), <field not available> is displayed instead.  $n+ will display field number n then a comma then field number n+1 then another comma then ... until the last field defined.  If field n is not defined, nothing is displayed.  This is useful for a property that is a list of values.
A ? is used to start a conditional expression, a kind of if-then statement.  ?exp(text) will display text if and only if exp evaluates to non-zero.  This is useful for two things.  First, it allows fields to be displayed if and only if a flag is set.  And second, it allows a value such as a state number to be displayed as a name rather than as just a number.  The syntax of exp is as follows:
exp    ::= term | term=exp | !exp
term   ::= n | $n | mn
The ! operator is a logical ``not'', changing 0 to 1 and any non-zero value to 0.  = is an equality operator.  Note that internally all expressions are evaluated as 32 bit numbers so -1 is not equal to 65535. = returns 1 if the two values are equal and 0 if not.  n represents the constant value n while $n represents the value of field number n.  mn is 1 if flag number n in the first field having format character 'm' in the corresponding format is 1, 0 otherwise.
Examples: ?m3(count: $3\n) displays field 3 with a label of count if and only if flag number 3 (count starts at 0!) is on. ?$2=0(True)?!$2=0(False) displays the inverted value of field 2 as a boolean.
In order to display a property, xprop needs both a format and a dformat. Before xprop uses its default values of a format of 32x and a dformat of " = { $0+ }\n", it searches several places in an attempt to find more specific formats.  First, a search is made using the name of the property.  If this fails, a search is made using the type of the property.  This allows type STRING to be defined with one set of formats while allowing property WM_NAME which is of type STRING to be defined with a different format.  In this way, the display formats for a given type can be overridden for specific properties.
The locations searched are in order: the format if any specified with the property name (as in 8x WM_NAME), the formats defined by -f options in last to first order, the contents of the file specified by the -fs option if any, the contents of the file specified by the environmental variable XPROPFORMATS if any, and finally xprop's built in file of formats.
The format of the files referred to by the -fs argument and the XPROPFORMATS variable is one or more lines of the following form:
name format [dformat]
Where name is either the name of a property or the name of a type, format is the format to be used with name and dformat is the dformat to be used with name.  If dformat is not present, " = $0+\n" is assumed.
To display the name of the root window: xprop -root WM_NAME
To display the window manager hints for the clock: xprop -name xclock WM_HINTS
To display the start of the cut buffer: xprop -root -len 100 CUT_BUFFER0
To display the point size of the fixed font: xprop -font fixed POINT_SIZE
To display all the properties of window # 0x200007: xprop -id 0x200007
DISPLAY To get default display.
XPROPFORMATS Specifies the name of a file from which additional formats are to be obtained.
X(7), xwininfo(1)
Mark Lillibridge, MIT Project Athena
DEX(1)                                 dex                                DEX(1)
dex - DesktopEntry Execution
dex [options] [DesktopEntryFile]...
dex, DesktopEntry Execution, is a program to generate and execute DesktopEntry files of the Application type.
-h, --help Show this help message and exit
-a, --autostart Autostart programs
-c PATH, --create PATH Create a DesktopEntry file for the program at the given path. An optional second argument is used to specify the filename of the created DesktopEntry file, or specify the filename - to print the file to stdout. By default a new file is created with the .desktop file extension.
-d, --dry-run Dry run, don't execute any command
-e ENVIRONMENT, --environment ENVIRONMENT Specify the Desktop Environment an autostart should be performed for; works only in combination with --autostart
-s SEARCHPATHS, --search-paths SEARCHPATHS Colon separated list of paths to search for desktop files, overriding the default search list
-t DIRECTORY, --target-directory DIRECTORY Create files in target directory
--term TERM The terminal emulator that will be used to run the program if Terminal=true is set in the desktop file, defaults to x-terminal-emulator
-w, --wait Block until the program exits
--test Perform a self-test
-v, --verbose Verbose output
-V, --version Display version information
Perform an autostart/execute all programs in the autostart folders. dex -a
Perform an autostart/execute all programs in the specified folders. dex -a -s /etc/xdg/autostart/:~/.config/autostart/
Preview the programs would be executed in a regular autostart. dex -ad
Preview the programs would be executed in a GNOME specific autostart. dex -ad -e GNOME
Create a DesktopEntry for a program in the current directory. dex -c /usr/bin/skype
Create a DesktopEntry for a programs in autostart directory. dex -t ~/.config/autostart -c /usr/bin/skype /usr/bin/nm-applet
Execute a single program from command line and enable verbose output. dex -v skype.desktop
Execute a single program (with Terminal=true in the desktop file) in gnome-terminal. dex --term gnome-terminal nvim.desktop
Execute a single program and block until it exits. dex --wait nvim.desktop
Jan Christoph Ebersbach, Johannes LÃ¶thberg
BITCOIN-CLI(1)                    User Commands                   BITCOIN-CLI(1)
bitcoin-cli - manual page for bitcoin-cli v22.0.0
bitcoin-cli [options] <command> [params]  Send command to Bitcoin Core bitcoin-cli [options] -named <command> [name=value]...  Send command to Bitcoin Core (with named arguments) bitcoin-cli [options] help                List commands bitcoin-cli [options] help <command>      Get help for a command
Bitcoin Core RPC client version v22.0.0
Print this help message and exit
-addrinfo
Get the number of addresses known to the node, per network and total.
-conf=<file>
Specify configuration file. Relative paths will be prefixed by datadir location. (default: bitcoin.conf)
-datadir=<dir>
Specify data directory
-generate
Generate blocks immediately, equivalent to RPC getnewaddress followed by RPC generatetoaddress. Optional positional integer arguments are number of blocks to generate (default: 1) and maximum iterations to try (default: 1000000), equivalent to RPC generatetoaddress nblocks and maxtries arguments. Example: bitcoin-cli -generate 4 1000
-getinfo
Get general information from the remote server. Note that unlike server-side RPC calls, the results of -getinfo is the result of multiple non-atomic requests. Some entries in the result may represent results from different states (e.g. wallet balance may be as of a different block from the chain state reported)
-named
Pass named instead of positional arguments (default: false)
-netinfo
Get network peer connection information from the remote server. An optional integer argument from 0 to 4 can be passed for different peers listings (default: 0). Pass "help" for detailed help documentation.
-rpcclienttimeout=<n>
Timeout in seconds during HTTP requests, or 0 for no timeout. (default: 900)
-rpcconnect=<ip>
Send commands to node running on <ip> (default: 127.0.0.1)
-rpccookiefile=<loc>
Location of the auth cookie. Relative paths will be prefixed by a net-specific datadir location. (default: data dir)
-rpcpassword=<pw>
Password for JSON-RPC connections
-rpcport=<port>
Connect to JSON-RPC on <port> (default: 8332, testnet: 18332, signet: 38332, regtest: 18443)
-rpcuser=<user>
Username for JSON-RPC connections
-rpcwait
Wait for RPC server to start
-rpcwaittimeout=<n>
Timeout in seconds to wait for the RPC server to start, or 0 for no timeout. (default: 0)
-rpcwallet=<walletname>
Send RPC for non-default wallet on RPC server (needs to exactly match corresponding -wallet option passed to bitcoind). This changes the RPC endpoint used, e.g. http://127.0.0.1:8332/wallet/<walletname>
-stdin
Read extra arguments from standard input, one per line until EOF/Ctrl-D (recommended for sensitive information such as passphrases). When combined with -stdinrpcpass, the first line from standard input is used for the RPC password.
-stdinrpcpass
Read RPC password from standard input as a single line. When combined with -stdin, the first line from standard input is used for the RPC password. When combined with -stdinwalletpassphrase, -stdinrpcpass consumes the first line, and -stdinwalletpassphrase consumes the second.
-stdinwalletpassphrase
Read wallet passphrase from standard input as a single line. When combined with -stdin, the first line from standard input is used for the wallet passphrase.
Print version and exit
Debugging/Testing options:
Chain selection options:
-chain=<chain>
Use the chain <chain> (default: main). Allowed values: main, test, signet, regtest
-signet
Use the signet chain. Equivalent to -chain=signet. Note that the network is defined by the -signetchallenge parameter
-signetchallenge
Blocks must satisfy the given script to be considered valid (only for signet networks; defaults to the global default signet test network challenge)
-signetseednode
Specify a seed node for the signet network, in the hostname[:port] format, e.g. sig.net:1234 (may be used multiple times to specify multiple seed nodes; defaults to the global default signet test network seed node(s))
-testnet
Use the test chain. Equivalent to -chain=test.
LVDISPLAY(8)                 System Manager's Manual                LVDISPLAY(8)
lvdisplay â€” Display information about a logical volume
lvdisplay [ option_args ] [ position_args ]
lvdisplay shows the attributes of LVs, like size, read/write status, snapshot information, etc.
lvs(8) is a preferred alternative that shows the same information and more, using a more compact and configurable output format.
lvdisplay [ -a|--all ] [ -c|--colon ] [ -C|--columns ] [ -H|--history ] [ -m|--maps ] [ -o|--options String ] [ -O|--sort String ] [ -S|--select String ] [    --aligned ] [    --binary ] [    --configreport log|vg|lv|pv|pvseg|seg ] [    --foreign ] [    --ignorelockingfailure ] [    --logonly ] [    --noheadings ] [    --nosuffix ] [    --readonly ] [    --reportformat basic|json ] [    --segments ] [    --separator String ] [    --shared ] [    --unbuffered ] [    --units [Number]r|R|h|H|b|B|s|S|k|K|m|M|g|G|t|T|p|P|e|E ] [ COMMON_OPTIONS ] [ VG|LV|Tag ... ]
-m|--maps Display the mapping of logical extents to PVs and physical extents.  To map physical extents to logical extents use: pvs --segments -o+lv_name,seg_start_pe,segtype
--segments
SMBGET(1)                         User Commands                        SMBGET(1)
smbget - wget-like utility for download files over SMB
smbget [-a, --guest] [-r, --resume] [-R, --recursive] [-U, --user=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-O, --stdout] [-u, --update] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]
smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line.
The files should be in the smb-URL standard, e.g. use smb://host/share/file for the UNC path \\\\HOST\\SHARE\\file.
-a, --guest Work as user guest
-r, --resume Automatically resume aborted files
-R, --recursive Recursively download files
-U, --user=username[%password] Username (and password) to use
-w, --workgroup=STRING Workgroup to use (optional)
-n, --nonprompt Don't ask anything (non-interactive)
-d, --debuglevel=INT Debuglevel to use
-D, --dots Show dots as progress indication
-o, --outputfile Write the file that is being downloaded to the specified file. Can not be used together with -R.
-O, --stdout Write the file that is being downloaded to standard output.
-f, --rcfile Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overridden by the contents of the rcfile.
-q, --quiet Be quiet
-v, --verbose Be verbose
-b, --blocksize Number of bytes to download in a block. Defaults to 64000.
-?, --help Show help message
--usage Display brief usage message
-u, --update Download only when remote file is newer than local file or local file is missing.
SMB URL's should be specified in the following format:
smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
smb:// means all the workgroups
smb://name/ means, if name is a workgroup, all the servers in this workgroup, or if name is a server, all the shares on this server.
# Recursively download 'src' directory smbget -R smb://rhonwyn/jelmer/src # Download FreeBSD ISO and enable resuming smbget -r smb://rhonwyn/isos/FreeBSD5.1.iso # Recursively download all ISOs smbget -Rr smb://rhonwyn/isos # Backup my data on rhonwyn smbget -Rr smb://rhonwyn/
Permission denied is returned in some cases where the cause of the error is unknown (such as an illegally formatted smb:// url or trying to get a directory without -R turned on).
The smbget manpage was written by Jelmer Vernooij.
yum(8)                                                                    yum(8)
yum - Yellowdog Updater Modified
yum [options] [command] [package ...]
yum is an interactive, rpm based, package manager. It can automatically perform system updates, including dependency analysis and obsolete processing based on "repository" metadata. It can also perform installation of new packages, removal of old packages and perform queries on the installed and/or available packages among many other commands/services (see below). yum is similar to other high level package managers like apt-get and smart.
While there are some graphical interfaces directly to the yum code, more recent graphical interface development is happening with PackageKit and the gnome-packagekit application.
command is one of: * install package1 [package2] [...] * update [package1] [package2] [...] * update-to [package1] [package2] [...] * check-update * upgrade [package1] [package2] [...] * upgrade-to [package1] [package2] [...] * distribution-synchronization [package1] [package2] [...] * remove | erase package1 [package2] [...] * list [...] * info [...] * provides | whatprovides feature1 [feature2] [...] * clean [ packages | metadata | expire-cache | rpmdb | plugins | all ] * makecache * groups [...] * search string1 [string2] [...] * shell [filename] * resolvedep dep1 [dep2] [...] * localinstall rpmfile1 [rpmfile2] [...] (maintained for legacy reasons only - use install) * localupdate rpmfile1 [rpmfile2] [...] (maintained for legacy reasons only - use update) * reinstall package1 [package2] [...] * downgrade package1 [package2] [...] * deplist package1 [package2] [...] * repolist [all|enabled|disabled] * version [ all | installed | available | group-* | nogroups* | grouplist | groupinfo ] * history [info|list|packages-list|summary|addon- info|redo|undo|rollback|new] * check * help [command]
Unless the --help or -h option is given, one of the above commands must be present.
Repository configuration is honored in all operations.
install Is used to install the latest version of a package or group of packages while ensuring that all dependencies are satisfied.  (See Specifying package names for more information) If no package matches the given package name(s), they are assumed to be a shell glob and any matches are then installed. If the name starts with an @ character the rest of the name is used as though passed to the groupinstall command. If the name starts with a - character, then a search is done within the transaction and any matches are removed. If the name is a file, then install works like localinstall. If the name doesn't match a package, then package "provides" are searched (Eg. "_sqlitecache.so()(64bit)") as are filelists (Eg. "/usr/bin/yum"). Also note that for filelists, wildcards will match multiple packages.
update If run without any packages, update will update every currently installed package.  If one or more packages or package globs are specified, Yum will only update the listed packages.  While updating packages, yum will ensure that all dependencies are satisfied. (See Specifying package names for more information) If the packages or globs specified match to packages which are not currently installed then update will not install them. update operates on groups, files, provides and filelists just like the "install" command.
If the main obsoletes configure option is true (default) or the --obsoletes flag is present yum will include package obsoletes in its calculations - this makes it better for distro-version changes, for example: upgrading from somelinux 8.0 to somelinux 9.
Note that "update" works on installed packages first, and only if there are no matches does it look for available packages. The difference is most noticable when you do "update foo-1-2" which will act exactly as "update foo" if foo-1-2 is installed. You can use the "update-to" if you'd prefer that nothing happen in the above case.
update-to This command works like "update" but always specifies the version of the package we want to update to.
check-update Implemented so you could know if your machine had any updates that needed to be applied without running it interactively. Returns exit value of 100 if there are packages available for an update. Also returns a list of the packages to be updated in list format. Returns 0 if no packages are available for update. Returns 1 if an error occurred.  Running in verbose mode also shows obsoletes.
upgrade Is the same as the update command with the --obsoletes flag set. See update for more details.
upgrade-to This command works like "upgrade" but always specifies the version of the package we want to update to.
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or downgrading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
If you give the optional argument "full", then the command will also reinstall packages where the install checksum and the available checksum do not match. And remove old packages (can be used to sync. rpmdb versions). The optional argument "different" can be used to specify the default operation.
This command does not perform operations on groups, local packages or negative selections.
remove or erase Are used to remove the specified packages from the system as well as removing any packages which depend on the package being removed. remove operates on groups, files, provides and filelists just like the "install" command.(See Specifying package names for more information)
Note that "yum" is included in the protected_packages configuration, by default.  So you can't accidentally remove yum itself.
list   Is used to list various information about available packages; more complete details are available in the List Options section below.
provides or whatprovides Is used to find out which package provides some feature or file. Just use a specific name or a file-glob-syntax wildcards to list the packages available or installed that provide that feature or file.
search This is used to find packages when you know something about the package but aren't sure of it's name. By default search will try searching just package names and summaries, but if that "fails" it will then try descriptions and url.
Yum search orders the results so that those packages matching more terms will appear first.