neulab/tldr huggingface dataset:
where role is the name of a valid color role, fg is the foreground color, bg is the background color and each option is one of the color modifying options. Multiple color specifications are then separated by a semicolon. For example:
export DJANGO_COLORS="error=yellow/blue,blink;notice=magenta"
would specify that errors be displayed using blinking yellow on blue, and notices displayed using magenta. All other color roles would be left uncolored.
Colors can also be specified by extending a base palette. If you put a palette name in a color specification, all the colors implied by that palette will be loaded. So:
export DJANGO_COLORS="light;error=yellow/blue,blink;notice=magenta"
would specify the use of all the colors in the light color palette, except for the colors for errors and notices which would be overridden as specified.
Bash completion If you use the Bash shell, consider installing the Django bash completion script, which lives in extras/django_bash_completion in the Django distribution. It enables tab-completion of django-admin and manage.py commands, so you can, for instance...
• Type django-admin.
• Press [TAB] to see all available options.
• Type sql, then [TAB], to see all available options whose names start with sql.
See /howto/custom-management-commands for how to add customized actions.
django.core.management.call_command(name, *args, **options)
To call a management command from code use call_command.
name   the name of the command to call or a command object. Passing the name is preferred unless the object is required for testing.
*args  a list of arguments accepted by the command. Arguments are passed to the argument parser, so you can use the same style as you would on the command line. For example, call_command('flush', 'verbosity=0').
**options named options accepted on the command-line. Options are passed to the command without triggering the argument parser, which means you'll need to pass the correct type. For example, call_command('flush', verbosity=0) (zero must be an integer rather than a string).
from django.core import management from django.core.management.commands import loaddata
management.call_command('flush', verbosity=0, interactive=False) management.call_command('loaddata', 'test_data', verbosity=0) management.call_command(loaddata.Command(), 'test_data', verbosity=0)
Note that command options that take no arguments are passed as keywords with True or False, as you can see with the interactive option above.
Named arguments can be passed by using either one of the following syntaxes:
# Similar to the command line management.call_command('dumpdata', '--natural-foreign')
# Named argument similar to the command line minus the initial dashes and # with internal dashes replaced by underscores management.call_command('dumpdata', natural_foreign=True)
# `use_natural_foreign_keys` is the option destination variable management.call_command('dumpdata', use_natural_foreign_keys=True)
Some command options have different names when using call_command() instead of django-admin or manage.py. For example, django-admin createsuperuser --no-input translates to call_command('createsuperuser', interactive=False). To find what keyword argument name to use for call_command(), check the command's source code for the dest argument passed to parser.add_argument().
Command options which take multiple options are passed a list:
management.call_command('dumpdata', exclude=['contenttypes', 'auth'])
The return value of the call_command() function is the same as the return value of the handle() method of the command.
call_command() now returns the value received from the command.handle() method. It now also accepts a command object as the first argument.
Note that you can redirect standard output and error streams as all commands support the stdout and stderr options. For example, you could write:
with open('/path/to/command_output') as f: management.call_command('dumpdata', stdout=f)
Django Software Foundation and contributors
LVRESIZE(8)                  System Manager's Manual                 LVRESIZE(8)
lvresize — Resize a logical volume
lvresize option_args position_args [ option_args ] [ position_args ]
--alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit -A|--autobackup y|n --commandprofile String --config String -d|--debug --devices PV --devicesfile String --driverloaded y|n -l|--extents [+|-]Number[PERCENT] -f|--force -h|--help --journal String --lockopt String --longhelp -n|--nofsck --nohints --nolocking --nosync --noudevsync --poolmetadatasize [+]Size[m|UNIT] --profile String -q|--quiet --reportformat basic|json -r|--resizefs -L|--size [+|-]Size[m|UNIT] -i|--stripes Number -I|--stripesize Size[k|UNIT] -t|--test --type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo| vdo-pool|cache|cache-pool|writecache -v|--verbose --version -y|--yes
lvresize resizes an LV in the same way as lvextend and lvreduce. See lvextend(8) and lvreduce(8) for more information.
Resize an LV by a specified size.
lvresize -L|--size [+|-]Size[m|UNIT] LV [ -l|--extents [+|-]Number[PERCENT] ] [ -r|--resizefs ] [    --poolmetadatasize [+]Size[m|UNIT] ] [ COMMON_OPTIONS ] [ PV ... ]
Resize an LV by specified PV extents.
lvresize LV PV ... [ -r|--resizefs ] [ COMMON_OPTIONS ]
Resize a pool metadata SubLV by a specified size.
lvresize --poolmetadatasize [+]Size[m|UNIT] LV1 [ COMMON_OPTIONS ] [ PV ... ]
Common options for command: [ -A|--autobackup y|n ] [ -f|--force ] [ -n|--nofsck ] [ -i|--stripes Number ] [ -I|--stripesize Size[k|UNIT] ] [    --alloc contiguous|cling|cling_by_tags|normal|anywhere|inherit ] [    --nosync ] [    --noudevsync ] [    --reportformat basic|json ] [    --type linear|striped|snapshot|raid|mirror|thin|thin-pool|vdo| vdo-pool|cache|cache-pool|writecache ]
-l|--extents [+|-]Number[PERCENT] Specifies the new size of the LV in logical extents.  The --size and --extents options are alternate methods of specifying size. The total number of physical extents used will be greater when redundant data is needed for RAID levels.  An alternate syntax allows the size to be determined indirectly as a percentage of the size of a related VG, LV, or set of PVs. The suffix %VG denotes the total size of the VG, the suffix %FREE the remaining free space in the VG, and the suffix %PVS the free space in the specified PVs.  For a snapshot, the size can be expressed as a percentage of the total size of the origin LV with the suffix %ORIGIN (100%ORIGIN provides space for the whole origin).  When expressed as a percentage, the size defines an upper limit for the number of logical extents in the new LV. The precise number of logical extents in the new LV is not determined until the command has completed.  When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
-L|--size [+|-]Size[m|UNIT] Specifies the new size of the LV.  The --size and --extents options are alternate methods of specifying size.  The total number of physical extents used will be greater when redundant data is needed for RAID levels.  When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
Extend an LV by 16MB using specific physical extents. lvresize -L+16M vg1/lv1 /dev/sda:0-1 /dev/sdb:0-1
Resize an LV to use 50% of the size volume group. lvresize -l50%VG vg1/lv1
MKDIR(1P)                   POSIX Programmer's Manual                  MKDIR(1P)
mkdir — make directories
mkdir [-p] [-m mode] dir...
The mkdir utility shall create the directories specified by the operands, in the order specified.
For each dir operand, the mkdir utility shall perform actions equivalent to the mkdir() function defined in the System Interfaces volume of POSIX.1‐2017, called with the following arguments:
1. The dir operand is used as the path argument.
2. The value of the bitwise-inclusive OR of S_IRWXU, S_IRWXG, and S_IRWXO is used as the mode argument. (If the -m option is specified, the value of the mkdir() mode argument is unspecified, but the directory shall at no time have permissions less restrictive than the -m mode option-argument.)
The mkdir utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-m mode   Set the file permission bits of the newly-created directory to the specified mode value. The mode option-argument shall be the same as the mode operand defined for the chmod utility. In the symbolic_mode strings, the op characters '+' and '-' shall be interpreted relative to an assumed initial mode of a=rwx; '+' shall add permissions to the default mode, '-' shall delete permissions from the default mode.
-p        Create any missing intermediate pathname components.
For each dir operand that does not name an existing directory, before performing the actions described in the DESCRIPTION above, the mkdir utility shall create any pathname components of the path prefix of dir that do not name an existing directory by performing actions equivalent to first calling the mkdir() function with the following arguments:
1. A pathname naming the missing pathname component, ending with a trailing <slash> character, as the path argument
2. The value zero as the mode argument
and then calling the chmod() function with the following arguments:
1. The same path argument as in the mkdir() call
2. The value (S_IWUSR|S_IXUSR|~filemask)&0777 as the mode argument, where filemask is the file mode creation mask of the process (see the System Interfaces volume of POSIX.1‐2017, umask())
Each dir operand that names an existing directory shall be ignored without error.
dir       A pathname of a directory to be created.
The following environment variables shall affect the execution of mkdir:
0    All the specified directories were created successfully, or the -p option was specified and all the specified directories either already existed or were created successfully.
The default file mode for directories is a=rwx (777 on most systems) with selected permissions removed in accordance with the file mode creation mask. For intermediate pathname components created by mkdir, the mode is the default modified by u+wx so that the subdirectories can always be created regardless of the file mode creation mask; if different ultimate permissions are desired for the intermediate directories, they can be changed afterwards with chmod.
Note that some of the requested directories may have been created even if an error occurs.
The System V -m option was included to control the file mode.
The System V -p option was included to create any needed intermediate directories and to complement the functionality provided by rmdir for removing directories in the path prefix as they become empty.  Because no error is produced if any path component already exists, the -p option is also useful to ensure that a particular directory exists.
The functionality of mkdir is described substantially through a reference to the mkdir() function in the System Interfaces volume of POSIX.1‐2017. For example, by default, the mode of the directory is affected by the file mode creation mask in accordance with the specified behavior of the mkdir() function. In this way, there is less duplication of effort required for describing details of the directory creation.
chmod, rm, rmdir, umask
The System Interfaces volume of POSIX.1‐2017, mkdir(), umask()
wasm2c â€” convert a WebAssembly binary file to a C source and header
wasm2c [options] file
wasm2c takes a WebAssembly module and produces an equivalent C source and header.
-o, --output=FILENAME Output file for the generated C source file, by default use stdout
Parse binary file test.wasm and write test.c and test.h
$ wasm2c test.wasm -o test.c
Parse test.wasm, write test.c and test.h, but ignore the debug names, if any
$ wasm2c test.wasm --no-debug-names -o test.c
wasm-interp(1), wasm-objdump(1), wasm-opcodecnt(1), wasm-strip(1), wasm-validate(1), wasm2wat(1), wast2json(1), wat-desugar(1), wat2wasm(1), spectest-interp(1)
OPAM(1)                            Opam Manual                           OPAM(1)
opam - source-based package management
opam COMMAND ...
Opam is a package manager. It uses the powerful mancoosi tools to handle dependencies, including support for version constraints, optional dependencies, and conflict management. The default configuration binds it to the official package repository for OCaml.
It has support for different remote repositories such as HTTP, rsync, git, darcs and mercurial. Everything is installed within a local opam directory, that can include multiple installation prefixes with different sets of intalled packages.
Use either opam <command> --help or opam help <command> for more information on a specific command.
admin Tools for repository administrators
clean Cleans up opam caches
config Display configuration options for packages.
env Prints appropriate shell variable assignments to stdout
exec Executes a command in the proper opam environment
help Display help about opam and opam commands.
init Initialize opam state, or set init options.
install Install a list of packages.
lint Checks and validate package description ('opam') files.
list Display the list of available packages.
lock Create locked opam files to share build environments across hosts.
option Global and switch configuration options settings
pin Pin a given package to a specific version or source.
reinstall Reinstall a list of packages.
remove Remove a list of packages.
repository Manage opam repositories.
show Display information about specific packages.
source Get the source of an opam package.
switch Manage multiple installation prefixes.
update Update the list of available packages.
upgrade Upgrade the installed package to latest version.
var Display and update the value associated with a given variable
info An alias for show.
remote An alias for repository.
search An alias for list --search.
uninstall An alias for remove.
unpin An alias for pin remove.
--no Answer no to all opam yes/no questions without prompting. See also --confirm-level. This is equivalent to setting $OPAMNO to "true".
-y, --yes Answer yes to all opam yes/no questions without prompting. See also --confirm-level. This is equivalent to setting $OPAMYES to "true".
--best-effort Don't fail if all requested packages can't be installed: try to install as many as possible. Note that not all external solvers may support this option (recent versions of aspcud or mccs should). This is equivalent to setting $OPAMBESTEFFORT environment variable.
--cli=MAJOR.MINOR (absent=2.1) Use the command-line interface syntax and semantics of MAJOR.MINOR. Intended for any persistent use of opam (scripts, blog posts, etc.), any version of opam in the same MAJOR series will behave as for the specified MINOR release. The flag was not available in opam 2.0, so to select the 2.0 CLI, set the OPAMCLI environment variable to 2.0 instead of using this parameter.
--color=WHEN Colorize the output. WHEN must be one of `always', `never' or `auto'.
--confirm-level=LEVEL Confirmation level, LEVEL must be one of `ask', `no', `yes' or `unsafe-yes'. Can be specified more than once. If --yes or --no are also given, the value of the last --confirm-level is taken into account. This is equivalent to setting  $OPAMCONFIRMLEVEL`.
--criteria=CRITERIA Specify user preferences for dependency solving for this run. Overrides both $OPAMCRITERIA and $OPAMUPGRADECRITERIA. For details on the supported language, and the external solvers available, see http://opam.ocaml.org/doc/External_solvers.html. A general guide to using solver preferences can be found at http://www.dicosmo.org/Articles/usercriteria.pdf.
--cudf=FILENAME Debug option: Save the CUDF requests sent to the solver to FILENAME-<n>.cudf.
--debug Print debug message to stderr. This is equivalent to setting $OPAMDEBUG to "true".
--debug-level=LEVEL Like --debug, but allows specifying the debug level (--debug sets it to 1). Equivalent to setting $OPAMDEBUG to a positive integer.
--git-version Print the git version of opam, if set (i.e. you are using a development version), and exit.
--ignore-pin-depends Ignore extra pins required by packages that get pinned, either manually through opam pin or through opam install DIR. This is equivalent to setting IGNOREPINDEPENDS=true.
--json=FILENAME Save the results of the opam run in a computer-readable file. If the filename contains the character `%', it will be replaced by an index that doesn't overwrite an existing file. Similar to setting the $OPAMJSON variable.
--no-aspcud Removed in 2.1.
--no-auto-upgrade When configuring or updating a repository that is written for an earlier opam version (1.2), opam internally converts it to the current format. This disables this behaviour. Note that repositories should define their format version in a 'repo' file at their root, or they will be assumed to be in the older format. It is, in any case, preferable to upgrade the repositories manually using opam admin upgrade [--mirror URL] when possible.
--no-self-upgrade Opam will replace itself with a newer binary found at OPAMROOT/opam if present. This disables this behaviour.
-q, --quiet Disables --verbose.
--root=ROOT Use ROOT as the current root path. This is equivalent to setting $OPAMROOT to ROOT.
--safe, --readonly Make sure nothing will be automatically updated or rewritten. Useful for calling from completion scripts, for example. Will fail whenever such an operation is needed ; also avoids waiting for locks, skips interactive questions and overrides the $OPAMDEBUG variable. This is equivalent to set environment variable $OPAMSAFE.
--solver=CMD Specify the CUDF solver to use for resolving package installation problems. This is either a predefined solver (this version of opam supports builtin-mccs+lp(), builtin-mccs+glpk, builtin-dummy-z3-solver, builtin-dummy-0install-solver, aspcud, mccs, aspcud-old, packup), or a custom command that should contain the variables %{input}%, %{output}%, %{criteria}%, and optionally %{timeout}%. This is equivalent to setting $OPAMEXTERNALSOLVER.
--strict Fail whenever an error is found in a package definition or a configuration file. The default is to continue silently if possible.
--switch=SWITCH Use SWITCH as the current compiler switch. This is equivalent to setting $OPAMSWITCH to SWITCH.
--use-internal-solver Disable any external solver, and use the built-in one (this requires that opam has been compiled with a built-in solver). This is equivalent to setting $OPAMNOASPCUD or $OPAMUSEINTERNALSOLVER.
-v, --verbose Be more verbose. One -v shows all package commands, repeat to also display commands called internally (e.g. tar, curl, patch etc.) Repeating n times is equivalent to setting $OPAMVERBOSE to "n".
-w, --working-dir Whenever updating packages that are bound to a local, version-controlled directory, update to the current working state of their source instead of the last committed state, or the ref they are pointing to. As source directory is copied as it is, if it isn't clean it may result on a opam build failure.This only affects packages explicitly listed on the command-line.It can also be set with $OPAMWORKINGDIR.
Opam makes use of the environment variables listed here. Boolean variables should be set to "0", "no", "false" or the empty string to disable, "1", "yes" or "true" to enable.
OPAMALLPARENS surround all filters with parenthesis.
OPAMASSUMEDEPEXTS see option `--assume-depexts'.
OPAMAUTOREMOVE see remove option `--auto-remove'.
OPAMBESTEFFORT see option `--best-effort'.
OPAMBESTEFFORTPREFIXCRITERIA sets the string that must be prepended to the criteria when the `--best-effort' option is set, and is expected to maximise the `opam-query' property in the solution.
OPAMBUILDDOC Removed in 2.1.
OPAMBUILDTEST Removed in 2.1.
OPAMCLI see option `--cli'.
OPAMCOLOR when set to always or never, sets a default value for the `--color' option.
OPAMCONFIRMLEVEL see option `--confirm-level`. OPAMCONFIRMLEVEL has priority over OPAMYES and OPAMNO.
OPAMCRITERIA specifies user preferences for dependency solving. The default value depends on the solver version, use `config report' to know the current setting. See also option --criteria.
OPAMCUDFFILE save the cudf graph to file-actions-explicit.dot.
OPAMCUDFTRIM controls the filtering of unrelated packages during CUDF preprocessing.
OPAMCURL can be used to select a given 'curl' program. See OPAMFETCH for more options.
OPAMDEBUG see options `--debug' and `--debug-level'.
OPAMDEBUGSECTIONS if set, limits debug messages to the space-separated list of sections. Sections can optionally have a specific debug level (for example, CLIENT:2 or CLIENT CUDF:2), but otherwise use `--debug-level'.
OPAMDIGDEPTH defines how aggressive the lookup for conflicts during CUDF preprocessing is.
OPAMDOWNLOADJOBS sets the maximum number of simultaneous downloads.
OPAMDROPWORKINGDIR overrides packages previously updated with --working-dir on update. Without this variable set, opam would keep them unchanged unless explicitly named on the command-line.
OPAMDRYRUN see option `--dry-run'.
OPAMEDITOR sets the editor to use for opam file editing, overrides $EDITOR and $VISUAL.
OPAMERRLOGLEN sets the number of log lines printed when a sub-process fails. 0 to print all.
OPAMEXTERNALSOLVER see option `--solver'.
OPAMFAKE see option `--fake'.
OPAMFETCH specifies how to download files: either `wget', `curl' or a custom command where variables %{url}%, %{out}%, %{retry}%, %{compress}% and %{checksum}% will be replaced. Overrides the 'download-command' value from the main config file.
OPAMFIXUPCRITERIA same as OPAMUPGRADECRITERIA, but specific to fixup.
OPAMIGNORECONSTRAINTS see install option `--ignore-constraints-on'.
OPAMIGNOREPINDEPENDS see option `--ignore-pin-depends'.
OPAMINPLACEBUILD see option `--inplace-build'.
OPAMJOBS sets the maximum number of parallel workers to run.
OPAMJSON log json output to the given file (use character `%' to index the files).
OPAMKEEPBUILDDIR see install option `--keep-build-dir'.
OPAMKEEPLOGS tells opam to not remove some temporary command logs and some backups. This skips some finalisers and may also help to get more reliable backtraces.
OPAMLOCKED combination of `--locked' and `--lock-suffix' options.
OPAMLOGS logdir sets log directory, default is a temporary directory in /tmp
OPAMMAKECMD set the system make command to use.
OPAMMERGEOUT merge process outputs, stderr on stdout.
OPAMNO answer no to any question asked, see options `--no` and `--confirm-level`. OPAMNO is ignored if either OPAMCONFIRMLEVEL or OPAMYES is set.
OPAMNOAGGREGATE with `opam admin check', don't aggregate packages.
OPAMNOASPCUD Deprecated.
OPAMNOAUTOUPGRADE disables automatic internal upgrade of repositories in an earlier format to the current one, on 'update' or 'init'.
OPAMNOCHECKSUMS enables option --no-checksums when available.
OPAMNODEPEXTS disables system dependencies handling, see option `--no-depexts'.
OPAMNOENVNOTICE Internal.
OPAMNOSELFUPGRADE see option `--no-self-upgrade'
OPAMPINKINDAUTO sets whether version control systems should be detected when pinning to a local path. Enabled by default since 1.3.0.
OPAMPRECISETRACKING fine grain tracking of directories.
OPAMPREPRO set this to false to disable CUDF preprocessing. Less efficient, but might help debugging solver issue.
OPAMREQUIRECHECKSUMS Enables option `--require-checksums' when available (e.g. for `opam install').
OPAMRETRIES sets the number of tries before failing downloads.
OPAMREUSEBUILDDIR see option `--reuse-build-dir'.
OPAMROOT see option `--root'. This is automatically set by `opam env --root=DIR --set-root'.
OPAMROOTISOK don't complain when running as root.
OPAMSAFE see option `--safe'.
OPAMSHOW see option `--show'.
OPAMSKIPUPDATE see option `--skip-updates'.
OPAMSKIPVERSIONCHECKS bypasses some version checks. Unsafe, for compatibility testing only.
OPAMSOLVERALLOWSUBOPTIMAL (default `true') allows some solvers to still return a solution when they reach timeout; while the solution remains assured to be consistent, there is no guarantee in this case that it fits the expected optimisation criteria. If `true', opam willcontinue with a warning, if `false' a timeout is an error. Currently only the builtin-z3 backend handles this degraded case.
OPAMSOLVERTIMEOUT change the time allowance of the solver. Default is 60.0, set to 0 for unlimited. Note that all solvers may not support this option.
OPAMSTATS display stats at the end of command.
OPAMSTATUSLINE display a dynamic status line showing what's currently going on on the terminal. (one of one of `always', `never' or `auto')
OPAMSTRICT fail on inconsistencies (file reading, switch import, etc.).
OPAMSWITCH see option `--switch'. Automatically set by `opam env --switch=SWITCH --set-switch'.
OPAMUNLOCKBASE see install option `--unlock-base'.
OPAMUPGRADECRITERIA specifies user preferences for dependency solving when performing an upgrade. Overrides OPAMCRITERIA in upgrades if both are set. See also option --criteria.
OPAMUSEINTERNALSOLVER see option `--use-internal-solver'.
OPAMUSEOPENSSL force openssl use for hash computing.
OPAMUTF8 use UTF8 characters in output (one of one of `always', `never' or `auto'). By default `auto', which is determined from the locale).
OPAMUTF8MSGS use extended UTF8 characters (camels) in opam messages. Implies OPAMUTF8. This is set by default on OSX only.
OPAMVALIDATIONHOOK if set, uses the `%{hook%}' command to validate an opam repository update.
OPAMVERBOSE see option `--verbose'.
OPAMVERSIONLAGPOWER do not use.
OPAMWITHDOC see install option `--with-doc'.
OPAMWITHTEST see install option `--with-test.
OPAMWORKINGDIR see option `--working-dir'.
OPAMYES see options `--yes' and `--confirm-level`. OPAMYES has has priority over OPAMNO and is ignored if OPAMCONFIRMLEVEL is set.
OPAMVAR_var overrides the contents of the variable var when substituting `%{var}%` strings in `opam` files.
OPAMVAR_package_var overrides the contents of the variable package:var when substituting `%{package:var}%` strings in `opam` files.
All scripts and programmatic invocations of opam should use `--cli' in order to ensure that they work seamlessly with future versions of the opam client. Additionally, blog posts or other documentation can benefit, as it prevents information from becoming stale.
Although opam only supports roots (~/.opam/) for the current version, it does provide backwards compatibility for its command-line interface.
Since CLI version support was only added in opam 2.1, use OPAMCLI to select 2.0 support (as opam 2.0 will just ignore it), and `--cli=2.1' for 2.1 (or later) versions, since an environment variable controlling the parsing of syntax is brittle. To this end, opam displays a warning if OPAMCLI specifies a valid version other than 2.0, and also if `--cli=2.0' is specified.
The command-line version is selected by using the `--cli' option or the OPAMCLI environment variable. `--cli' may be specified morethan once, where the last instance takes precedence. OPAMCLI is only inspected if `--cli' is not given.
As an exception to the following, the `exec' command returns 127 if the command was not found or couldn't be executed, and the command's exit value otherwise.
0   Success, or true for boolean queries.
1   False. Returned when a boolean return value is expected, e.g. when running with --check, or for queries like opam lint.
2   Bad command-line arguments, or command-line arguments pointing to an invalid context (e.g. file not following the expected format).
5   Not found. You requested something (package, version, repository, etc.) that couldn't be found.
10  Aborted. The operation required confirmation, which wasn't given.
15  Could not acquire the locks required for the operation.
20  There is no solution to the user request. This can be caused by asking to install two incompatible packages, for example.
30  Error in package definition, or other metadata files. Using --strict raises this error more often.
31  Package script error. Some package operations were unsuccessful. This may be an error in the packages or an incompatibility with your system. This can be a partial error.
40  Sync error. Could not fetch some remotes from the network. This can be a partial error.
50  Configuration error. Opam or system configuration doesn't allow operation, and needs fixing.
60  Solver failure. The solver failed to return a sound answer. It can be due to a broken external solver, or an error in solver configuration.
99  Internal error. Something went wrong, likely due to a bug in opam itself.
130 User interrupt. SIGINT was received, generally due to the user pressing Ctrl-C.
See https://opam.ocaml.org/doc.
Vincent Bernardoff <vb@luminar.eu.org> Raja Boujbel <raja.boujbel@ocamlpro.com> Roberto Di Cosmo <roberto@dicosmo.org> Thomas Gazagnaire <thomas@gazagnaire.org> Louis Gesbert <louis.gesbert@ocamlpro.com> Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr> Anil Madhavapeddy <anil@recoil.org> Guillem Rieu <guillem.rieu@ocamlpro.com> Ralf Treinen <ralf.treinen@pps.jussieu.fr> Frederic Tuong <tuong@users.gforge.inria.fr>
Check bug reports at https://github.com/ocaml/opam/issues.
cpufreq-aperf(1)                                                cpufreq-aperf(1)
cpufreq-aperf - Calculates the average frequency over a time period
cpufreq-aperf [options]
On latest processors exist two MSR registers referred to as: - MPERF increasing with maximum (P0) frequency in C0 - APERF increasing with current/actual frequency in C0
From this information the average frequency over a time period can be calculated and this is what this tool does.
A nice falloff feature beside the average frequency is the time a processor core remained in C0 (working state) or any CX (sleep state) processor sleep state during the measured time period. This information can be determined from the fact that MPERF only increases in C0 state.
-c --cpu <CPU> The <CPU> core to measure - default all cores.
-i --interval <seconds> Refresh rate - default 1 second.
-o --once Exit after one interval.
-h --help Prints the available options.
The msr driver must be loaded for this command to work.
Thomas Renninger <trenn@suse.de>
cpufreq-set(1), cpufreq-info(1)
GODOC(1)                     General Commands Manual                    GODOC(1)
godoc - extracts and generates documentation for Go programs
godoc [flag]
Godoc extracts and generates documentation for Go programs.
It runs as a web server and presents the documentation as a web page.
godoc -http=:6060
-timestamps=true show timestamps with directory listings
-index enable identifier and full text search index (no search box is shown if -index is not set)
-index_files="" glob pattern specifying index files; if not empty, the index is read from these files in sorted order
-index_throttle=0.75 index throttle value; a value of 0 means no time is allocated to the indexer (the indexer will never finish), a value of 1.0 means that index creation is running at full throttle (other goroutines may get no time while the index is built)
-index_interval=0 interval of indexing; a value of 0 sets it to 5 minutes, a negative value indexes only once at startup
-play=false enable playground
-links=true link identifiers to their declarations
-write_index=false write index to a file; the file name must be specified with -index_files
-maxresults=10000 maximum number of full text search results shown (no full text index is built if maxresults <= 0)
-notes="BUG" regular expression matching note markers to show (e.g., "BUG|TODO", ".*")
-goroot=$GOROOT Go root directory
-http=addr HTTP service address (e.g., '127.0.0.1:6060' or just ':6060')
-analysis=type,pointer comma-separated list of analyses to perform "type": display identifier resolution, type info, method sets, 'implements', and static callees "pointer": display channel peers, callers and dynamic callees (significantly slower) See https://golang.org/lib/godoc/analysis/help.html for details.
-templates="" directory containing alternate template files; if set, the directory may provide alternative template files for the files in $GOROOT/lib/godoc
-url=path print to standard output the data that would be served by an HTTP request for path
-zip="" zip file providing the file system to serve; disabled if empty
By default, godoc looks at the packages it finds via $GOROOT and $GOPATH (if set).
When the -index flag is set, a search index is maintained.  The index is created at startup.
The index contains both identifier and full text search information (searchable via regular expressions). The maximum number of full text search results shown can be set with the -maxresults flag; if set to 0, no full text results are shown, and only an identifier index but no full text search index is created.
By default, godoc uses the system's GOOS/GOARCH. You can provide the URL parameters "GOOS" and "GOARCH" to set the output on the web page for the target system.
The presentation mode of web pages served by godoc can be controlled with the "m" URL parameter; it accepts a comma-separated list of flag names as value:
all    show documentation for all declarations, not just the exported ones
methods show all embedded methods, not just those of unexported anonymous fields
src    show the original source code rather then the extracted documentation
text   present the page in textual (command-line) form rather than HTML
flat   present flat (not indented) directory listings using full paths
For instance, http://golang.org/pkg/math/big/?m=all,text shows the documentation for all (not just the exported) declarations of package big, in textual form (as it would appear when using godoc from the command line: "godoc -src math/big .*").
By default, godoc serves files from the file system of the underlying OS. Instead, a .zip file may be provided via the -zip flag, which contains the file system to serve. The file paths stored in the .zip file must use slash ('/') as path separator; and they must be unrooted.  $GOROOT (or -goroot) must be set to the .zip file directory path containing the Go root directory. For instance, for a .zip file created by the command:
zip go.zip $HOME/go
one may run godoc as follows:
godoc -http=:6060 -zip=go.zip -goroot=$HOME/go
Godoc documentation is converted to HTML or to text using the go/doc package; see https://golang.org/pkg/go/doc/#ToHTML for the exact rules. Godoc also shows example code that is runnable by the testing package; see https://golang.org/pkg/testing/#hdr-Examples for the conventions. See "Godoc: documenting Go code" for how to write good comments for godoc: http://golang.org/doc/articles/godoc_documenting_go_code.html
CRONTAB(5)                        File Formats                        CRONTAB(5)
crontab - files used to schedule the execution of programs
A crontab file contains instructions for the cron(8) daemon in the following simplified manner: "run this command at this time on this date".  Each user can define their own crontab.  Commands defined in any given crontab are executed under the user who owns that particular crontab.  Uucp and News usually have their own crontabs, eliminating the need for explicitly running su(1) as part of a cron command.
Blank lines, leading spaces, and tabs are ignored.  Lines whose first non-white space character is a pound-sign (#) are comments, and are not processed.  Note that comments are not allowed on the same line as cron commands, since they are considered a part of the command.  Similarly, comments are not allowed on the same line as environment variable settings.
An active line in a crontab is either an environment setting or a cron command.  An environment setting is of the form:
name = value
where the white spaces around the equal-sign (=) are optional, and any subsequent non-leading white spaces in value is a part of the value assigned to name.  The value string may be placed in quotes (single or double, but matching) to preserve leading or trailing white spaces.
Several environment variables are set up automatically by the cron(8) daemon.  SHELL is set to /bin/sh, and LOGNAME and HOME are set from the /etc/passwd line of the crontab´s owner.  HOME and SHELL can be overridden by settings in the crontab; LOGNAME can not.
(Note: the LOGNAME variable is sometimes called USER on BSD systems and is also automatically set).
In addition to LOGNAME, HOME, and SHELL, cron(8) looks at the MAILTO variable if a mail needs to be send as a result of running any commands in that particular crontab.  If MAILTO is defined (and non-empty), mail is sent to the specified address.  If MAILTO is defined but empty (MAILTO=""), no mail is sent.  Otherwise, mail is sent to the owner of the crontab.  This option is useful if you decide to use /bin/mail instead of /usr/lib/sendmail as your mailer.  Note that /bin/mail does not provide aliasing and UUCP usually does not read its mail.  If MAILFROM is defined (and non-empty), it is used as the envelope sender address, otherwise, ``root'' is used.
(Note: Both MAILFROM and MAILTO variables are expanded, so setting them as in the following example works as expected: MAILFROM=cron-$USER@cron.com ($USER is replaced by the system user) )
By default, cron sends a mail using the 'Content-Type:' header of 'text/plain' with the 'charset=' parameter set to the 'charmap/codeset' of the locale in which crond(8) is started up, i.e., either the default system locale, if no LC_* environment variables are set, or the locale specified by the LC_* environment variables (see locale(7)).  Different character encodings can be used for mailing cron job outputs by setting the CONTENT_TYPE and CONTENT_TRANSFER_ENCODING variables in a crontab to the correct values of the mail headers of those names.
The CRON_TZ variable specifies the time zone specific for the cron table. The user should enter a time according to the specified time zone into the table.  The time used for writing into a log file is taken from the local time zone, where the daemon is running.
The MLS_LEVEL environment variable provides support for multiple per-job SELinux security contexts in the same crontab.  By default, cron jobs execute with the default SELinux security context of the user that created the crontab file.  When using multiple security levels and roles, this may not be sufficient, because the same user may be running in different roles or in different security levels.  For more information about roles and SELinux MLS/MCS, see selinux(8) and the crontab example mentioned later on in this text.  You can set the MLS_LEVEL variable to the SELinux security context string specifying the particular SELinux security context in which you want jobs to be run.  crond will then set the execution context of those jobs that meet the specifications of the particular security context.  For more information, see crontab(1) -s option.
The RANDOM_DELAY variable allows delaying job startups by random amount of minutes with upper limit specified by the variable. The random scaling factor is determined during the cron daemon startup so it remains constant for the whole run time of the daemon.
The format of a cron command is similar to the V7 standard, with a number of upward-compatible extensions.  Each line has five time-and-date fields followed by a username (if this is the system crontab file), and followed by a command.  Commands are executed by cron(8) when the 'minute', 'hour', and 'month of the year' fields match the current time, and at least one of the two 'day' fields ('day of month', or 'day of week') match the current time (see "Note" below).
Note that this means that non-existent times, such as the "missing hours" during the daylight savings time conversion, will never match, causing jobs scheduled during the "missing times" not to be run.  Similarly, times that occur more than once (again, during the daylight savings time conversion) will cause matching jobs to be run twice.
cron(8) examines cron entries every minute.
The time and date fields are:
field          allowed values -----          -------------- minute         0-59 hour           0-23 day of month   1-31 month          1-12 (or names, see below) day of week    0-7 (0 or 7 is Sunday, or use names)
A field may contain an asterisk (*), which always stands for "first-last".
Ranges of numbers are allowed.  Ranges are two numbers separated with a hyphen.  The specified range is inclusive.  For example, 8-11 for an 'hours' entry specifies execution at hours 8, 9, 10, and 11. The first number must be less than or equal to the second one.
Lists are allowed.  A list is a set of numbers (or ranges) separated by commas.  Examples: "1,2,5,9", "0-4,8-12".
Step values can be used in conjunction with ranges.  Following a range with "/<number>" specifies skips of the number's value through the range. For example, "0-23/2" can be used in the 'hours' field to specify command execution for every other hour (the alternative in the V7 standard is "0, 2,4,6,8,10,12,14,16,18,20,22").  Step values are also permitted after an asterisk, so if specifying a job to be run every two hours, you can use "*/2".
Names can also be used for the 'month' and 'day of week' fields.  Use the first three letters of the particular day or month (case does not matter).  Ranges and lists of names are allowed. Examples: "mon,wed,fri", "jan-mar".
If the UID of the owner is 0 (root), the first character of a crontab entry can be "-" character. This will prevent cron from writing a syslog message about the command being executed.
The "sixth" field (the rest of the line) specifies the command to be run. The entire command portion of the line, up to a newline or a "%" character, will be executed by /bin/sh or by the shell specified in the SHELL variable of the cronfile.  A "%" character in the command, unless escaped with a backslash (\), will be changed into newline characters, and all data after the first % will be sent to the command as standard input.
Note: The day of a command's execution can be specified in the following two fields — 'day of month', and 'day of week'.  If both fields are restricted (i.e., do not contain the "*" character), the command will be run when either field matches the current time.  For example, "30 4 1,15 * 5" would cause a command to be run at 4:30 am on the 1st and 15th of each month, plus every Friday.
A crontab file syntax can be tested before an install using the -T option. See crontab(1) for details.
# use /bin/sh to run commands, no matter what /etc/passwd says SHELL=/bin/sh # mail any output to `paul', no matter whose crontab this is MAILTO=paul # CRON_TZ=Japan # run five minutes after midnight, every day 5 0 * * *       $HOME/bin/daily.job >> $HOME/tmp/out 2>&1 # run at 2:15pm on the first of every month -- output mailed to paul 15 14 1 * *     $HOME/bin/monthly # run at 10 pm on weekdays, annoy Joe 0 22 * * 1-5    mail -s "It's 10pm" joe%Joe,%%Where are your kids?% 23 0-23/2 * * * echo "run 23 minutes after midn, 2am, 4am ..., everyday" 5 4 * * sun     echo "run at 5 after 4 every sunday"
Jobs in /etc/cron.d/ The jobs in cron.d and /etc/crontab are system jobs, which are used usually for more than one user, thus, additionally the username is needed.  MAILTO on the first line is optional.
EXAMPLE OF A JOB IN /etc/cron.d/job #login as root #create job with preferred editor (e.g. vim) MAILTO=root * * * * * root touch /tmp/file
SELinux with multi level security (MLS) In a crontab, it is important to specify a security level by crontab -s or specifying the required level on the first line of the crontab.  Each level is specified in /etc/selinux/targeted/seusers.  When using crontab in the MLS mode, it is especially important to: - check/change the actual role, - set correct role for directory, which is used for input/output.
# login as root newrole -r sysadm_r mkdir /tmp/SystemHigh chcon -l SystemHigh /tmp/SystemHigh crontab -e # write in crontab file MLS_LEVEL=SystemHigh 0-59 * * * * id -Z > /tmp/SystemHigh/crontest
/etc/crontab main system crontab file.  /var/spool/cron/ a directory for storing crontabs defined by users.  /etc/cron.d/ a directory for storing system crontabs.
cron(8), crontab(1)
These special time specification "nicknames" which replace the 5 initial time and date fields, and are prefixed with the '@' character, are supported:
@reboot    :    Run once after reboot. @yearly    :    Run once a year, ie.  "0 0 1 1 *". @annually  :    Run once a year, ie.  "0 0 1 1 *". @monthly   :    Run once a month, ie. "0 0 1 * *". @weekly    :    Run once a week, ie.  "0 0 * * 0". @daily     :    Run once a day, ie.   "0 0 * * *". @hourly    :    Run once an hour, ie. "0 * * * *".
crontab files have to be regular files or symlinks to regular files, they must not be executable or writable for anyone else but the owner.  This requirement can be overridden by using the -p option on the crond command line.  If inotify support is in use, changes in the symlinked crontabs are not automatically noticed by the cron daemon.  The cron daemon must receive a SIGHUP signal to reload the crontabs.  This is a limitation of the inotify API.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing a newline (i.e. terminated by EOF), cron will consider the crontab (at least partially) broken.  A warning will be written to syslog.
Paul Vixie ⟨vixie@isc.org⟩
GDB(1)                        GNU Development Tools                       GDB(1)
gdb - The GNU Debugger
gdb [-help] [-nh] [-nx] [-q] [-batch] [-cd=dir] [-f] [-b bps] [-tty=dev] [-s symfile] [-e prog] [-se prog] [-c core] [-p procID] [-x cmds] [-d dir] [prog|prog procID|prog core]
The purpose of a debugger such as GDB is to allow you to see what is going on "inside" another program while it executes -- or what another program was doing at the moment it crashed.
GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act:
•   Start your program, specifying anything that might affect its behavior.
•   Make your program stop on specified conditions.
•   Examine what has happened, when your program has stopped.
•   Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.
You can use GDB to debug programs written in C, C++, Fortran and Modula-2.
GDB is invoked with the shell command "gdb".  Once started, it reads commands from the terminal until you tell it to exit with the GDB command "quit".  You can get online help from GDB itself by using the command "help".
You can run "gdb" with no arguments or options; but the most usual way to start GDB is with one argument or two, specifying an executable program as the argument:
gdb program
You can also start with both an executable program and a core file specified:
gdb program core
You can, instead, specify a process ID as a second argument or use option "-p", if you want to debug a running process:
gdb program 1234 gdb -p 1234
would attach GDB to process 1234.  With option -p you can omit the program filename.
Here are some of the most frequently needed GDB commands:
break [file:]function Set a breakpoint at function (in file).
run [arglist] Start your program (with arglist, if specified).
bt  Backtrace: display the program stack.
print expr Display the value of an expression.
c   Continue running your program (after stopping, e.g. at a breakpoint).
next Execute next program line (after stopping); step over any function calls in the line.
edit [file:]function look at the program line where it is presently stopped.
list [file:]function type the text of the program in the vicinity of where it is presently stopped.
step Execute next program line (after stopping); step into any function calls in the line.
help [name] Show information about GDB command name, or general information about using GDB.
quit Exit from GDB.
For full details on GDB, see Using GDB: A Guide to the GNU Source-Level Debugger, by Richard M. Stallman and Roland H. Pesch.  The same text is available online as the "gdb" entry in the "info" program.
Any arguments other than options specify an executable file and core file (or process ID); that is, the first argument encountered with no associated option flag is equivalent to a -se option, and the second, if any, is equivalent to a -c option if it's the name of a file.  Many options have both long and short forms; both are shown here.  The long forms are also recognized if you truncate them, so long as enough of the option is present to be unambiguous.  (If you prefer, you can flag option arguments with + rather than -, though we illustrate the more usual convention.)
All the options and command line arguments you give are processed in sequential order.  The order makes a difference when the -x option is used.
-help -h  List all options, with brief explanations.
-symbols=file -s file Read symbol table from file file.