neulab/tldr huggingface dataset:
rebase [--object OBJECTDEF] [--image-opts] [-U] [-q] [-f FMT] [-t CACHE] [-T SRC_CACHE] [-p] [-u] -b BACKING_FILE [-F BACKING_FMT] FILENAME Changes the backing file of an image. Only the formats qcow2 and qed support changing the backing file.
The backing file is changed to BACKING_FILE and (if the image format of FILENAME supports this) the backing file format is changed to BACKING_FMT. If BACKING_FILE is specified as "" (the empty string), then the image is rebased onto no backing file (i.e. it will exist independently of any backing file).
CACHE specifies the cache mode to be used for FILENAME, whereas SRC_CACHE specifies the cache mode for reading backing files.
There are two different modes in which rebase can operate:
Safe mode This is the default mode and performs a real rebase operation. The new backing file may differ from the old one and qemu-img rebase will take care of keeping the guest-visible content of FILENAME unchanged.
In order to achieve this, any clusters that differ between BACKING_FILE and the old backing file of FILENAME are merged into FILENAME before actually changing the backing file.
Note that the safe mode is an expensive operation, comparable to converting an image. It only works if the old backing file still exists.
Unsafe mode qemu-img uses the unsafe mode if -u is specified. In this mode, only the backing file name and format of FILENAME is changed without any checks on the file contents. The user must take care of specifying the correct new backing file, or the guest-visible content of the image will be corrupted.
This mode is useful for renaming or moving the backing file to somewhere else.  It can be used without an accessible old backing file, i.e. you can use it to fix an image whose backing file has already been moved/renamed.
You can use rebase to perform a "diff" operation on two disk images.  This can be useful when you have copied or cloned a guest, and you want to get back to a thin image on top of a template or base image.
Say that base.img has been cloned as modified.img by copying it, and that the modified.img guest has run so there are now some changes compared to base.img.  To construct a thin image called diff.qcow2 that contains just the differences, do:
qemu-img create -f qcow2 -b modified.img diff.qcow2 qemu-img rebase -b base.img diff.qcow2
At this point, modified.img can be discarded, since base.img + diff.qcow2 contains the same information.
resize [--object OBJECTDEF] [--image-opts] [-f FMT] [--preallocation=PREALLOC] [-q] [--shrink] FILENAME [+ | -]SIZE Change the disk image as if it had been created with SIZE.
Before using this command to shrink a disk image, you MUST use file system and partitioning tools inside the VM to reduce allocated file systems and partition sizes accordingly.  Failure to do so will result in data loss!
When shrinking images, the --shrink option must be given. This informs qemu-img that the user acknowledges all loss of data beyond the truncated image's end.
After using this command to grow a disk image, you must use file system and partitioning tools inside the VM to actually begin using the new space on the device.
When growing an image, the --preallocation option may be used to specify how the additional image area should be allocated on the host.  See the format description in the Notes section which values are allowed.  Using this option may result in slightly more data being allocated than necessary.
Supported image file formats:
raw Raw disk image format (default). This format has the advantage of being simple and easily exportable to all other emulators. If your file system supports holes (for example in ext2 or ext3 on Linux or NTFS on Windows), then only the written sectors will reserve space. Use qemu-img info to know the real size used by the image or ls -ls on Unix/Linux.
preallocation Preallocation mode (allowed values: off, falloc, full).  falloc mode preallocates space for image by calling posix_fallocate(). full mode preallocates space for image by writing data to underlying storage.  This data may or may not be zero, depending on the storage location.
qcow2 QEMU image format, the most versatile format. Use it to have smaller images (useful if your filesystem does not supports holes, for example on Windows), optional AES encryption, zlib based compression and support of multiple VM snapshots.
compat Determines the qcow2 version to use. compat=0.10 uses the traditional image format that can be read by any QEMU since 0.10.  compat=1.1 enables image format extensions that only QEMU 1.1 and newer understand (this is the default). Amongst others, this includes zero clusters, which allow efficient copy-on-read for sparse images.
backing_file File name of a base image (see create subcommand)
backing_fmt Image format of the base image
encryption If this option is set to on, the image is encrypted with 128-bit AES-CBC.
The use of encryption in qcow and qcow2 images is considered to be flawed by modern cryptography standards, suffering from a number of design problems:
• The AES-CBC cipher is used with predictable initialization vectors based on the sector number. This makes it vulnerable to chosen plaintext attacks which can reveal the existence of encrypted data.
• The user passphrase is directly used as the encryption key. A poorly chosen or short passphrase will compromise the security of the encryption.
• In the event of the passphrase being compromised there is no way to change the passphrase to protect data in any qcow images. The files must be cloned, using a different encryption passphrase in the new file. The original file must then be securely erased using a program like shred, though even this is ineffective with many modern storage technologies.
• Initialization vectors used to encrypt sectors are based on the guest virtual sector number, instead of the host physical sector. When a disk image has multiple internal snapshots this means that data in multiple physical sectors is encrypted with the same initialization vector. With the CBC mode, this opens the possibility of watermarking attacks if the attack can collect multiple sectors encrypted with the same IV and some predictable data. Having multiple qcow2 images with the same passphrase also exposes this weakness since the passphrase is directly used as the key.
Use of qcow / qcow2 encryption is thus strongly discouraged. Users are recommended to use an alternative encryption technology such as the Linux dm-crypt / LUKS system.
cluster_size Changes the qcow2 cluster size (must be between 512 and 2M). Smaller cluster sizes can improve the image file size whereas larger cluster sizes generally provide better performance.
preallocation Preallocation mode (allowed values: off, metadata, falloc, full). An image with preallocated metadata is initially larger but can improve performance when the image needs to grow. falloc and full preallocations are like the same options of raw format, but sets up metadata also.
lazy_refcounts If this option is set to on, reference count updates are postponed with the goal of avoiding metadata I/O and improving performance. This is particularly interesting with cache=writethrough which doesn't batch metadata updates. The tradeoff is that after a host crash, the reference count tables must be rebuilt, i.e. on the next open an (automatic) qemu-img check -r all is required, which may take some time.
This option can only be enabled if compat=1.1 is specified.
nocow  If this option is set to on, it will turn off COW of the file. It's only valid on btrfs, no effect on other file systems.
Btrfs has low performance when hosting a VM image file, even more when the guest on the VM also using btrfs as file system. Turning off COW is a way to mitigate this bad performance. Generally there are two ways to turn off COW on btrfs:
• Disable it by mounting with nodatacow, then all newly created files will be NOCOW
• For an empty file, add the NOCOW file attribute. That's what this option does.
Note: this option is only valid to new or empty files. If there is an existing file which is COW and has data blocks already, it couldn't be changed to NOCOW by setting nocow=on. One can issue lsattr filename to check if the NOCOW flag is set or not (Capital 'C' is NOCOW flag).
data_file Filename where all guest data will be stored. If this option is used, the qcow2 file will only contain the image's metadata.
Note: Data loss will occur if the given filename already exists when using this option with qemu-img create since qemu-img will create the data file anew, overwriting the file's original contents. To simply update the reference to point to the given pre-existing file, use qemu-img amend.
data_file_raw If this option is set to on, QEMU will always keep the external data file consistent as a standalone read-only raw image.
It does this by forwarding all write accesses to the qcow2 file through to the raw data file, including their offsets. Therefore, data that is visible on the qcow2 node (i.e., to the guest) at some offset is visible at the same offset in the raw data file. This results in a read-only raw image. Writes that bypass the qcow2 metadata may corrupt the qcow2 metadata because the out-of-band writes may result in the metadata falling out of sync with the raw image.
If this option is off, QEMU will use the data file to store data in an arbitrary manner. The file’s content will not make sense without the accompanying qcow2 metadata. Where data is written will have no relation to its offset as seen by the guest, and some writes (specifically zero writes) may not be forwarded to the data file at all, but will only be handled by modifying qcow2 metadata.
This option can only be enabled if data_file is set.
Other QEMU also supports various other image file formats for compatibility with older QEMU versions or other hypervisors, including VMDK, VDI, VHD (vpc), VHDX, qcow1 and QED. For a full list of supported formats see qemu-img --help.  For a more detailed description of these formats, see the QEMU block drivers reference documentation.
The main purpose of the block drivers for these formats is image conversion.  For running VMs, it is recommended to convert the disk images to either raw or qcow2 in order to achieve good performance.
GTOP(l)                                                                  GTOP(l)
gTop - GTK+ based graphical top-like system monitor
gtop [--help] [--version]
gTop is a system monitor for the X Window System which uses the GTK+ widget set. It is based upon the console program top(1)
This is pretty straightforward.
--help Prints the command line options.
--version Prints the version of gTop that you're using.
•      add callbacks to properties dialog so properties can be applied and saved
•      separate ProcProcData mainpulation, so it can be used in "details"
•      tooltips for proclist column titles
•      toolbar
•      kill, term
•      process tree
•      save state
•      save clist geometry this could be done global (gnome_clist widget, like gnome_entry)
Radek Doulik (doulik@karlin.mff.cuni.cz)
Martin Baulig (martin@home-of-linux.org)
JEST.JS(1)                        User Commands                       JEST.JS(1)
jest.js - manual page for jest.js 27.3.1-dev
jest.js [--config=<pathToConfigFile>] [TestPathPattern]
--help, -h Show help                              [boolean]
--version, -v Print the version and exit             [boolean]
--all  The opposite of `onlyChanged`. If `onlyChanged` is set by default, running jest with `--all` will force Jest to run all tests instead of running only tests related to changed files.
[boolean]
--automock Automock all files by default.         [boolean]
--bail, -b Exit the test suite immediately after `n` number of failing tests. [boolean]
--cache Whether to use the transform cache. Disable the cache using --no-cache.                [boolean]
--cacheDirectory The directory where Jest should store its cached dependency information.                 [string]
--changedFilesWithAncestor Runs tests related to the current changes and the changes made in the last commit. Behaves similarly to `--onlyChanged`. [boolean]
--changedSince Runs tests related to the changes since the provided branch. If the current branch has diverged from the given branch, then only changes made locally will be tested. Behaves similarly to `--onlyChanged`.           [string]
--ci   Whether to run Jest in continuous integration (CI) mode. This option is on by default in most popular CI environments. It will prevent snapshots from being written unless explicitly requested. [boolean]
--clearCache Clears the configured Jest cache directory and then exits. Default directory can be found by calling jest --showConfig [boolean]
--clearMocks Automatically clear mock calls and instances between every test. Equivalent to calling jest.clearAllMocks() between each test.[boolean]
--collectCoverage Alias for --coverage.                  [boolean]
--collectCoverageFrom A glob pattern relative to <rootDir> matching the files that coverage info needs to be collected from. [string]
--collectCoverageOnlyFrom Explicit list of paths coverage will be restricted to. [array]
--color Forces test results output color highlighting (even if stdout is not a TTY). Set to false if you would like to have no colors. [boolean]
--colors Alias for `--color`.                   [boolean]
--config, -c The path to a jest config file specifying how to find and execute tests. If no rootDir is set in the config, the directory containing the config file is assumed to be the rootDir for the project.This can also be a JSON encoded value which Jest will use as configuration.   [string]
--coverage Indicates that test coverage information should be collected and reported in the output.
--coverageDirectory The directory where Jest should output its coverage files. [string]
--coveragePathIgnorePatterns An array of regexp pattern strings that are matched against all file paths before executing the test. If the file pathmatches any of the patterns, coverage information will be skipped.
[array]
--coverageProvider Select between Babel and V8 to collect coverage [choices: "babel", "v8"]
--coverageReporters A list of reporter names that Jest uses when writing coverage reports. Any istanbul reporter can be used. [array]
--coverageThreshold A JSON string with which will be used to configure minimum threshold enforcement for coverage results [string]
--debug Print debugging info about your jest config.  [boolean]
--detectLeaks **EXPERIMENTAL**: Detect memory leaks in tests.  After executing a test, it will try to garbage collect the global object used, and fail if it was leaked                             [boolean]
--detectOpenHandles Print out remaining open handles preventing Jest from exiting at the end of a test run. Implies `runInBand`. [boolean]
--env  The test environment used for all tests. This can point to any file or node module. Examples: `jsdom`, `node` or `path/to/my-environment.js`
[string]
--errorOnDeprecated Make calling deprecated APIs throw helpful error messages. [boolean]
--expand, -e Use this flag to show full diffs instead of a patch. [boolean]
--filter Path to a module exporting a filtering function.  This method receives a list of tests which can be manipulated to exclude tests from running.  Especially useful when used in conjunction with a testing infrastructure to filter known broken tests. [string]
--findRelatedTests Find related tests for a list of source files that were passed in as arguments. Useful for pre-commit hook integration to run the minimal amount of tests necessary.             [boolean]
--forceExit Force Jest to exit after all tests have completed running. This is useful when resources set up by test code cannot be adequately cleaned up.                                    [boolean]
--globalSetup The path to a module that runs before All Tests.  [string]
--globalTeardown The path to a module that runs after All Tests.  [string]
--globals A JSON string with map of global variables that need to be available in all test environments.
--haste A JSON string with map of variables for the haste module system [string]
--init Generate a basic configuration file    [boolean]
--injectGlobals Should Jest inject global variables or not [boolean]
--json Prints the test results in JSON. This mode will send all other test output and user messages to stderr. [boolean]
--lastCommit Run all tests affected by file changes in the last commit made. Behaves similarly to `--onlyChanged`. [boolean]
--listTests Lists all tests Jest will run given the arguments and exits. Most useful in a CI system together with `--findRelatedTests` to determine the tests Jest will run based on specific files
--logHeapUsage Logs the heap usage after every test. Useful to debug memory leaks. Use together with `--runInBand` and `--expose-gc` in node.
--maxConcurrency Specifies the maximum number of tests that are allowed to runconcurrently. This only affects tests using `test.concurrent`. [number]
--maxWorkers, -w Specifies the maximum number of workers the worker-pool will spawn for running tests. This defaults to the number of the cores available on your machine. (its usually best not to override this default)                           [string]
--moduleDirectories An array of directory names to be searched recursively up from the requiring module's location. [array]
--moduleFileExtensions An array of file extensions your modules use.  If you require modules without specifying a file extension, these are the extensions Jest will look for.                           [array]
--moduleNameMapper A JSON string with a map from regular expressions to module names or to arrays of module names that allow to stub out resources, like images or styles with a single module
--modulePathIgnorePatterns An array of regexp pattern strings that are matched against all module paths before those paths are to be considered "visible" to the module loader.                           [array]
--modulePaths An alternative API to setting the NODE_PATH env variable, modulePaths is an array of absolute paths to additional locations to search when resolving modules.                       [array]
--noStackTrace Disables stack trace in test results output [boolean]
--notify Activates notifications for test results.  [boolean]
--notifyMode Specifies when notifications will appear for test results. [string]
--onlyChanged, -o Attempts to identify which tests to run based on which files have changed in the current repository. Only works if you're running tests in a git or hg repository at the moment.
--onlyFailures, -f Run tests that failed in the previous execution.  [boolean]
--outputFile Write test results to a file when the --json option is also specified.               [string]
--passWithNoTests Will not fail if no tests are found (for example while using `--testPathPattern`.)      [boolean]
--preset A preset that is used as a base for Jest's configuration. [string]
--prettierPath The path to the "prettier" module used for inline snapshots. [string]
--projects A list of projects that use Jest to run all tests of all projects in a single instance of Jest. [array]
--reporters A list of custom reporters for the test suite.  [array]
--resetMocks Automatically reset mock state between every test. Equivalent to calling jest.resetAllMocks() between each test. [boolean]
--resetModules If enabled, the module registry for every test file will be reset before running each individual test. [boolean]
--resolver A JSON string which allows the use of a custom resolver. [string]
--restoreMocks Automatically restore mock state and implementation between every test. Equivalent to calling jest.restoreAllMocks() between each test.                                  [boolean]
--rootDir The root directory that Jest should scan for tests and modules within.               [string]
--roots A list of paths to directories that Jest should use to search for files in.              [array]
--runInBand, -i Run all tests serially in the current process (rather than creating a worker pool of child processes that run tests). This is sometimes useful for debugging, but such use cases are pretty rare.                           [boolean]
--runTestsByPath Used when provided patterns are exact file paths. This avoids converting them into a regular expression and matching it against every single file.                           [boolean]
--runner Allows to use a custom runner instead of Jest's default test runner.                    [string]
--selectProjects Run only the tests of the specified projects.Jest uses the attribute `displayName` in the configuration to identify each project.
--setupFiles A list of paths to modules that run some code to configure or set up the testing environment before each test. [array]
--setupFilesAfterEnv A list of paths to modules that run some code to configure or set up the testing framework before each test [array]
--showConfig Print your jest config and then exits. [boolean]
--silent Prevent tests from printing messages through the console. [boolean]
--skipFilter Disables the filter provided by --filter. Useful for CI jobs, or local enforcement when fixing tests. [boolean]
--snapshotSerializers A list of paths to snapshot serializer modules Jest should use for snapshot testing.    [array]
--testEnvironment Alias for --env                         [string]
--testEnvironmentOptions A JSON string with options that will be passed to the `testEnvironment`. The relevant options depend on the environment. [string]
--testFailureExitCode Exit code of `jest` command if the test run failed [string]
--testLocationInResults Add `location` information to the test results [boolean]
--testMatch The glob patterns Jest uses to detect test files. [array]
--testNamePattern, -t Run only tests with a name that matches the regex pattern. [string]
--testPathIgnorePatterns An array of regexp pattern strings that are matched against all test paths before executing the test. If the test path matches any of the patterns, it will be skipped.            [array]
--testPathPattern A regexp pattern string that is matched against all tests paths before executing the test.
--testRegex A string or array of string regexp patterns that Jest uses to detect test files.          [array]
--testResultsProcessor Allows the use of a custom results processor.  This processor must be a node module that exports a function expecting as the first argument the result object.             [string]
--testRunner Allows to specify a custom test runner. The default is `jest-circus/runner`. A path to a custom test runner can be provided: `<rootDir>/path/to/testRunner.js`.      [string]
--testSequencer Allows to specify a custom test sequencer. The default is `@jest/test-sequencer`. A path to a custom test sequencer can be provided: `<rootDir>/path/to/testSequencer.js`    [string]
--testTimeout This option sets the default timeouts of test cases. [number]
--testURL This option sets the URL for the jsdom environment. [string]
--timers Setting this value to fake allows the use of fake timers for functions such as setTimeout.
--transform A JSON string which maps from regular expressions to paths to transformers.   [string]
--transformIgnorePatterns An array of regexp pattern strings that are matched against all source file paths before transformation. [array]
--unmockedModulePathPatterns An array of regexp pattern strings that are matched against all modules before the module loader will automatically return a mock for them.                                    [array]
--updateSnapshot, -u Use this flag to re-record snapshots. Can be used together with a test suite pattern or with `--testNamePattern` to re-record snapshot for test matching the pattern              [boolean]
--useStderr Divert all output to stderr.           [boolean]
--verbose Display individual test results with the test suite hierarchy. [boolean]
--watch Watch files for changes and rerun tests related to changed files. If you want to re-run all tests when a file has changed, use the `--watchAll` option.                   [boolean]
--watchAll Watch files for changes and rerun all tests. If you want to re-run only the tests related to the changed files, use the `--watch` option.
--watchPathIgnorePatterns An array of regexp pattern strings that are matched against all paths before trigger test re-run in watch mode. If the test path matches any of the patterns, it will be skipped. [array]
--watchman Whether to use watchman for file crawling.  Disable using --no-watchman.           [boolean]
Documentation: https://jestjs.io/
XCLIP(1)                     General Commands Manual                    XCLIP(1)
xclip - command line interface to X selections (clipboard)
xclip [OPTION] [FILE]...
Reads from standard in, or from one or more files, and makes the data available as an X selection for pasting into X applications. Prints current X selection to standard out.
-i, -in read text into X selection from standard input or files (default)
-o, -out print the selection to standard out (generally for piping to a file or program)
-f, -filter when xclip is invoked in the in mode with output level set to silent (the defaults), the filter option will cause xclip to print the text piped to standard in back to standard out unmodified
-r, -rmlastnl when the last character of the selection is a newline character, remove it. Newline characters that are not the last character in the selection are not affected. If the selection does not end with a newline character, this option has no effect. This option is useful for copying one-line output of programs like pwd to the clipboard to paste it again into the command prompt without executing the line immideately due to the newline character pwd appends.
-l, -loops number of X selection requests (pastes into X applications) to wait for before exiting, with a value of 0 (default) causing xclip to wait for an unlimited number of requests until another application (possibly another invocation of xclip) takes ownership of the selection
-t, -target specify a particular data format using the given target atom. With -o the special target atom name "TARGETS" can be used to get a list of valid target atoms for this selection.  For more information about target atoms refer to ICCCM section 2.6.2
-d, -display X display to use (e.g. "localhost:0"), xclip defaults to the value in $DISPLAY if this option is omitted
-h, -help show quick summary of options
-selection specify which X selection to use, options are "primary" to use XA_PRIMARY (default), "secondary" for XA_SECONDARY or "clipboard" for XA_CLIPBOARD
-version show version information
-silent fork into the background to wait for requests, no informational output, errors only (default)
-quiet show informational messages on the terminal and run in the foreground
-verbose provide a running commentary of what xclip is doing
-noutf8 operate in legacy (i.e. non UTF-8) mode for backwards compatibility (Use this option only when really necessary, as the old behavior was broken)
xclip reads text from standard in or files and makes it available to other X applications for pasting as an X selection (traditionally with the middle mouse button). It reads from all files specified, or from standard in if no files are specified. xclip can also print the contents of a selection to standard out with the -o option.
xclip was designed to allow tighter integration of X applications and command line programs. The default action is to silently wait in the background for X selection requests (pastes) until another X application places data in the clipboard, at which point xclip exits silently. You can use the -verbose option to see if and when xclip actually receives selection requests from other X applications.
Options can be abbreviated as long as they remain unambiguous. For example, it is possible to use -d or -disp instead of -display. However, -v couldn't be used because it is ambiguous (it could be short for -verbose or -version), so it would be interpreted as a filename.
Note that only the first character of the selection specified with the -selection option is important. This means that "p", "sec" and "clip" would have the same effect as using "primary", "secondary" or "clipboard" respectively.
I hate man pages without examples!
uptime | xclip
Put your uptime in the X selection. Then middle click in an X application to paste.
xclip -loops 10 -verbose /etc/motd
Exit after /etc/motd (message of the day) has been pasted 10 times. Show how many selection requests (pastes) have been processed.
xclip -o > helloworld.c
Put the contents of the selection into a file.
xclip -t text/html index.html
Middle click in an X application supporting HTML to paste the contents of the given file as HTML.
DISPLAY X display to use if none is specified with the -display option.
Please report any bugs, problems, queries, experiences, etc. directly to the author.
Kim Saunders <kims@debian.org> Peter Ã…strand <astrand@lysator.liu.se>
ember(1)                     General Commands Manual                    ember(1)
ember - 3D client for the WorldForge project.
ember is a client framework for Worldforge.  It's not meant to be a standalone game, instead its purpose is to provide a solid and extensible base from which to build game-specific clients. One of the goals of ember is to allow for easy customization of the codebase. Currently it supports the game world of Mason.
This manpage is written by Michael Koch <konqueror@gmx.de> for the Debian distribution
LDAPSEARCH(1)                General Commands Manual               LDAPSEARCH(1)
ldapsearch - LDAP search tool
ldapsearch [-V[V]] [-d debuglevel] [-n] [-v] [-c] [-u] [-t[t]] [-T path] [-F prefix] [-A] [-L[L[L]]] [-S attribute] [-b searchbase] [-s {base|one|sub|children}] [-a {never|always|search|find}] [-l timelimit] [-z sizelimit] [-f file] [-M[M]] [-x] [-D binddn] [-W] [-w passwd] [-y passwdfile] [-H ldapuri] [-P {2|3}] [-e [!]ext[=extparam]] [-E [!]ext[=extparam]] [-o opt[=optparam]] [-O security-properties] [-I] [-Q] [-N] [-U authcid] [-R realm] [-X authzid] [-Y mech] [-Z[Z]] filter [attrs...]
ldapsearch is a shell-accessible interface to the ldap_search_ext(3) library call.
ldapsearch opens a connection to an LDAP server, binds, and performs a search using specified parameters.   The filter should conform to the string representation for search filters as defined in RFC 4515.  If not provided, the default filter, (objectClass=*), is used.
If ldapsearch finds one or more entries, the attributes specified by attrs are returned.  If * is listed, all user attributes are returned. If + is listed, all operational attributes are returned.  If no attrs are listed, all user attributes are returned.  If only 1.1 is listed, no attributes will be returned.
The search results are displayed using an extended version of LDIF. Option -L controls the format of the output.
-V[V]  Print version info.  If -VV is given, exit after providing version info. Otherwise proceed with the specified search
-d debuglevel Set the LDAP debugging level to debuglevel.  ldapsearch must be compiled with LDAP_DEBUG defined for this option to have any effect.
-n     Show what would be done, but don't actually perform the search. Useful for debugging in conjunction with -v.
-v     Run in verbose mode, with many diagnostics written to standard output.
-c     Continuous operation mode. Errors are reported, but ldapsearch will continue with searches. The default is to exit after reporting an error.  Only useful in conjunction with -f.
-u     Include the User Friendly Name form of the Distinguished Name (DN) in the output.
-t[t]  A single -t writes retrieved non-printable values to a set of temporary files.  This is useful for dealing with values containing non-character data such as jpegPhoto or audio. A second -t writes all retrieved values to files.
-T path Write temporary files to directory specified by path (default: system default tmp directory). The environment variables TMPDIR, TMP, or TEMP will override the default path.
-F prefix URL prefix for temporary files.  Default is file://path where path is the system default tmp directory or the value specified with -T.
-A     Retrieve attributes only (no values).  This is useful when you just want to see if an attribute is present in an entry and are not interested in the specific values.
-L     Search results are display in LDAP Data Interchange Format detailed in ldif(5).  A single -L restricts the output to LDIFv1. A second -L disables comments.  A third -L disables printing of the LDIF version.  The default is to use an extended version of LDIF.
-S attribute Sort the entries returned based on attribute. The default is not to sort entries returned.  If attribute is a zero-length string (""), the entries are sorted by the components of their Distinguished Name.  See ldap_sort(3) for more details. Note that ldapsearch normally prints out entries as it receives them. The use of the -S option defeats this behavior, causing all entries to be retrieved, then sorted, then printed.
-b searchbase Use searchbase as the starting point for the search instead of the default.
-s {base|one|sub|children} Specify the scope of the search to be one of base, one, sub, or children to specify a base object, one-level, subtree, or children search.  The default is sub.  Note: children scope requires LDAPv3 subordinate feature extension.
-a {never|always|search|find} Specify how aliases dereferencing is done.  Should be one of never, always, search, or find to specify that aliases are never dereferenced, always dereferenced, dereferenced when searching, or dereferenced only when locating the base object for the search. The default is to never dereference aliases.
-l timelimit wait at most timelimit seconds for a search to complete.  A timelimit of 0 (zero) or none means no limit.  A timelimit of max means the maximum integer allowable by the protocol.  A server may impose a maximal timelimit which only the root user may override.
-z sizelimit retrieve at most sizelimit entries for a search.  A sizelimit of 0 (zero) or none means no limit.  A sizelimit of max means the maximum integer allowable by the protocol.  A server may impose a maximal sizelimit which only the root user may override.
-f file Read a series of lines from file, performing one LDAP search for each line.  In this case, the filter given on the command line is treated as a pattern where the first and only occurrence of %s is replaced with a line from file.  Any other occurrence of the the % character in the pattern will be regarded as an error.  Where it is desired that the search filter include a % character, the character should be encoded as \25 (see RFC 4515).  If file is a single - character, then the lines are read from standard input. ldapsearch will exit when the first non-successful search result is returned, unless -c is used.
-M[M]  Enable manage DSA IT control.  -MM makes control critical.
-x     Use simple authentication instead of SASL.
-D binddn Use the Distinguished Name binddn to bind to the LDAP directory. For SASL binds, the server is expected to ignore this value.
-W     Prompt for simple authentication.  This is used instead of specifying the password on the command line.
-w passwd Use passwd as the password for simple authentication.
-y passwdfile Use complete contents of passwdfile as the password for simple authentication.
-H ldapuri Specify URI(s) referring to the ldap server(s); a list of URI, separated by whitespace or commas is expected; only the protocol/host/port fields are allowed.  As an exception, if no host/port is specified, but a DN is, the DN is used to look up the corresponding host(s) using the DNS SRV records, according to RFC 2782.  The DN must be a non-empty sequence of AVAs whose attribute type is "dc" (domain component), and must be escaped according to RFC 2396.
-P {2|3} Specify the LDAP protocol version to use.
-e [!]ext[=extparam]
-E [!]ext[=extparam]
Specify general extensions with -e and search extensions with -E. ´!´ indicates criticality.
General extensions: [!]assert=<filter>    (an RFC 4515 Filter) !authzid=<authzid>    ("dn:<dn>" or "u:<user>") [!]bauthzid           (RFC 3829 authzid control) [!]chaining[=<resolve>[/<cont>]] [!]manageDSAit [!]noop ppolicy [!]postread[=<attrs>] (a comma-separated attribute list) [!]preread[=<attrs>]  (a comma-separated attribute list) [!]relax sessiontracking[=<username>] abandon,cancel,ignore (SIGINT sends abandon/cancel, or ignores response; if critical, doesn't wait for SIGINT. not really controls)
Search extensions: !dontUseCopy [!]domainScope                       (domain scope) [!]mv=<filter>                       (matched values filter) [!]pr=<size>[/prompt|noprompt]       (paged results/prompt) [!]sss=[-]<attr[:OID]>[/[-]<attr[:OID]>...]  (server side sorting) [!]subentries[=true|false]           (subentries) [!]sync=ro[/<cookie>]                (LDAP Sync refreshOnly) rp[/<cookie>][/<slimit>]     (LDAP Sync refreshAndPersist) [!]vlv=<before>/<after>(/<offset>/<count>|:<value>)  (virtual list view) [!]deref=derefAttr:attr[,attr[...]][;derefAttr:attr[,attr[...]]] [!]<oid>[=:<value>|::<b64value>]
-o opt[=optparam]
Specify any ldap.conf(5) option or one of the following: nettimeout=<timeout>  (in seconds, or "none" or "max") ldif_wrap=<width>     (in columns, or "no" for no wrapping)
-O security-properties Specify SASL security properties.
-I     Enable SASL Interactive mode.  Always prompt.  Default is to prompt only as needed.
-Q     Enable SASL Quiet mode.  Never prompt.
-N     Do not use reverse DNS to canonicalize SASL host name.
-U authcid Specify the authentication ID for SASL bind. The form of the ID depends on the actual SASL mechanism used.
-R realm Specify the realm of authentication ID for SASL bind. The form of the realm depends on the actual SASL mechanism used.
-X authzid Specify the requested authorization ID for SASL bind.  authzid must be one of the following formats: dn:<distinguished name> or u:<username>
-Y mech Specify the SASL mechanism to be used for authentication. If it's not specified, the program will choose the best mechanism the server knows.
-Z[Z]  Issue StartTLS (Transport Layer Security) extended operation. If you use -ZZ, the command will require the operation to be successful.
If one or more entries are found, each entry is written to standard output in LDAP Data Interchange Format or ldif(5):
version: 1
# bjensen, example, net dn: uid=bjensen,dc=example,dc=net objectClass: person objectClass: dcObject uid: bjensen cn: Barbara Jensen sn: Jensen ...
If the -t option is used, the URI of a temporary file is used in place of the actual value.  If the -A option is given, only the "attributename" part is written.
ldapsearch -LLL "(sn=smith)" cn sn telephoneNumber
will perform a subtree search (using the default search base and other parameters defined in ldap.conf(5)) for entries with a surname (sn) of smith.  The common name (cn), surname (sn) and telephoneNumber values will be retrieved and printed to standard output.  The output might look something like this if two entries are found:
dn: uid=jts,dc=example,dc=com cn: John Smith cn: John T. Smith sn: Smith sn;lang-en: Smith sn;lang-de: Schmidt telephoneNumber: 1 555 123-4567
dn: uid=sss,dc=example,dc=com cn: Steve Smith cn: Steve S. Smith sn: Smith sn;lang-en: Smith sn;lang-de: Schmidt telephoneNumber: 1 555 765-4321
ldapsearch -LLL -u -t "(uid=xyz)" jpegPhoto audio
will perform a subtree search using the default search base for entries with user id of "xyz".  The user friendly form of the entry's DN will be output after the line that contains the DN itself, and the jpegPhoto and audio values will be retrieved and written to temporary files.  The output might look like this if one entry with one value for each of the requested attributes is found:
dn: uid=xyz,dc=example,dc=com ufn: xyz, example, com audio:< file:///tmp/ldapsearch-audio-a19924 jpegPhoto:< file:///tmp/ldapsearch-jpegPhoto-a19924
This command:
ldapsearch -LLL -s one -b "c=US" "(o=University*)" o description
will perform a one-level search at the c=US level for all entries whose organization name (o) begins with University.  The organization name and description attribute values will be retrieved and printed to standard output, resulting in output similar to this:
dn: o=University of Alaska Fairbanks,c=US o: University of Alaska Fairbanks description: Naturally Inspiring description: leaf node only
dn: o=University of Colorado at Boulder,c=US o: University of Colorado at Boulder description: No personnel information description: Institution of education and research
dn: o=University of Colorado at Denver,c=US o: University of Colorado at Denver o: UCD o: CU/Denver o: CU-Denver description: Institute for Higher Learning and Research
dn: o=University of Florida,c=US o: University of Florida o: UFl description: Warper of young minds
Exit status is zero if no errors occur.  Errors result in a non-zero exit status and a diagnostic message being written to standard error.
ldapadd(1), ldapdelete(1), ldapmodify(1), ldapmodrdn(1), ldap.conf(5), ldif(5), ldap(3), ldap_search_ext(3), ldap_sort(3)
The OpenLDAP Project <http://www.openldap.org/>
OpenLDAP Software is developed and maintained by The OpenLDAP Project <http://www.openldap.org/>.  OpenLDAP Software is derived from the University of Michigan LDAP 3.3 Release.
BTRFS-SCRUB(8)                    Btrfs Manual                    BTRFS-SCRUB(8)
btrfs-scrub - scrub btrfs filesystem, verify block checksums
btrfs scrub <subcommand> <args>
btrfs scrub is used to scrub a mounted btrfs filesystem, which will read all data and metadata blocks from all devices and verify checksums. Automatically repair corrupted blocks if there’s a correct copy available.
Note Scrub is not a filesystem checker (fsck) and does not verify nor repair structural damage in the filesystem. It really only checks checksums of data and tree blocks, it doesn’t ensure the content of tree blocks is valid and consistent. There’s some validation performed when metadata blocks are read from disk but it’s not extensive and cannot substitute full btrfs check run.
The user is supposed to run it manually or via a periodic system service. The recommended period is a month but could be less. The estimated device bandwidth utilization is about 80% on an idle filesystem. The IO priority class is by default idle so background scrub should not significantly interfere with normal filesystem operation. The IO scheduler set for the device(s) might not support the priority classes though.
The scrubbing status is recorded in /var/lib/btrfs/ in textual files named scrub.status.UUID for a filesystem identified by the given UUID. (Progress state is communicated through a named pipe in file scrub.progress.UUID in the same directory.) The status file is updated every 5 seconds. A resumed scrub will continue from the last saved position.
Scrub can be started only on a mounted filesystem, though it’s possible to scrub only a selected device. See scrub start for more.
cancel <path>|<device> If a scrub is running on the filesystem identified by path or device, cancel it.
If a device is specified, the corresponding filesystem is found and btrfs scrub cancel behaves as if it was called on that filesystem. The progress is saved in the status file so btrfs scrub resume can continue from the last position.
resume [-BdqrR] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device> Resume a cancelled or interrupted scrub on the filesystem identified by path or on a given device. The starting point is read from the status file if it exists.
This does not start a new scrub if the last scrub finished successfully.
see scrub start.
start [-BdqrRf] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device> Start a scrub on all devices of the mounted filesystem identified by path or on a single device. If a scrub is already running, the new one will not start. A device of an unmounted filesystem cannot be scrubbed this way.
Without options, scrub is started as a background process. The automatic repairs of damaged copies is performed by default for block group profiles with redundancy.
The default IO priority of scrub is the idle class. The priority can be configured similar to the ionice(1) syntax using -c and -n options. Note that not all IO schedulers honor the ionice settings.
-B do not background and print scrub statistics when finished
-d print separate statistics for each device of the filesystem (-B only) at the end
-r run in read-only mode, do not attempt to correct anything, can be run on a read-only filesystem
-R raw print mode, print full data instead of summary
-c <ioprio_class> set IO priority class (see ionice(1) manpage)
-n <ioprio_classdata> set IO priority classdata (see ionice(1) manpage)
-f force starting new scrub even if a scrub is already running, this can useful when scrub status file is damaged and reports a running scrub although it is not, but should not normally be necessary
-q (deprecated) alias for global -q option
status [options] <path>|<device> Show status of a running scrub for the filesystem identified by path or for the specified device.
If no scrub is running, show statistics of the last finished or cancelled scrub for that filesystem or device.
-d print separate statistics for each device of the filesystem
-R print all raw statistics without postprocessing as returned by the status ioctl
--raw print all numbers raw values in bytes without the B suffix
btrfs scrub returns a zero exit status if it succeeds. Non zero is returned in case of failure:
1 scrub couldn’t be performed
2 there is nothing to resume
3 scrub found uncorrectable errors
mkfs.btrfs(8), ionice(1)
TAIL(1)                           User Commands                          TAIL(1)
tail - output the last part of files
tail [OPTION]... [FILE]...
Print the last 10 lines of each FILE to standard output.  With more than one FILE, precede each with a header giving the file name.
-c, --bytes=[+]NUM output the last NUM bytes; or use -c +NUM to output starting with byte NUM of each file
-f, --follow[={name|descriptor}] output appended data as the file grows;
an absent option argument means 'descriptor'
-F     same as --follow=name --retry
-n, --lines=[+]NUM output the last NUM lines, instead of the last 10; or use -n +NUM to output starting with line NUM
--max-unchanged-stats=N with --follow=name, reopen a FILE which has not
changed size after N (default 5) iterations to see if it has been unlinked or renamed (this is the usual case of rotated log files); with inotify, this option is rarely useful
--pid=PID with -f, terminate after process ID, PID dies
-q, --quiet, --silent never output headers giving file names
--retry keep trying to open a file if it is inaccessible
-s, --sleep-interval=N with -f, sleep for approximately N seconds (default 1.0) between iterations; with inotify and --pid=P, check process P at least once every N seconds
-v, --verbose always output headers giving file names
NUM may have a multiplier suffix: b 512, kB 1000, K 1024, MB 1000*1000, M 1024*1024, GB 1000*1000*1000, G 1024*1024*1024, and so on for T, P, E, Z, Y.  Binary prefixes can be used, too: KiB=K, MiB=M, and so on.
With --follow (-f), tail defaults to following the file descriptor, which means that even if a tail'ed file is renamed, tail will continue to track its end.  This default behavior is not desirable when you really want to track the actual name of the file, not the file descriptor (e.g., log rotation).  Use --follow=name in that case.  That causes tail to track the named file in a way that accommodates renaming, removal and creation.
Written by Paul Rubin, David MacKenzie, Ian Lance Taylor, and Jim Meyering.
head(1)
Full documentation <https://www.gnu.org/software/coreutils/tail> or available locally via: info '(coreutils) tail invocation'
toilet(1)                    General Commands Manual                   toilet(1)
TOIlet - display large colourful characters
toilet [ -hkostvSW ] [ -d fontdirectory ] [ -f fontfile ] [ -F filter ] [ -w outputwidth ] [ -I infocode ] [ -E format ] [ message ]
TOIlet prints text using large characters made of smaller characters. It is similar in many ways to FIGlet with additional features such as Unicode handling, colour fonts, filters and various export formats.
TOIlet either reads its input from the command line or from the standard input.
-f, --font <name> Use the given font instead of the default value. Fonts are .flf or .tlf files stored in the /usr/share/figlet directory. Fonts are looked first in the font directory, then in the current directory. There is also a special built-in font called term that serves as a fallback if no font is available.