The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
NAME cargo-login – Save an API token from the registry locally SYNOPSIS cargo login [OPTIONS] [<TOKEN>] OPTIONS -h, –help Print this message. –host HOST Host to set the token for -v, –verbose Use verbose output. -q, –quiet No output printed to stdout. –color WHEN Coloring: auto, always, never. SEE ALSO cargo(1), cargo-publish(1) COPYRIGHT This work…
NAME cargo-install – Install a Rust binary SYNOPSIS cargo install [OPTIONS] <CRATE> cargo install [OPTIONS] –list DESCRIPTION Install a Rust binary This command manages Cargo’s local set of install binary crates. Only packages which have [[bin]] targets can be installed, and all binaries are installed into the installation root’s bin folder. The installation root is…
NAME cargo-init – Create a new cargo package in the current directory SYNOPSIS cargo init [OPTIONS] DESCRIPTION Create a new cargo package in the current directory. Use the –vcs option to control the version control system to use. OPTIONS -h, –help Print this message. –vcs VCS Initialize a new repository for the given version control…
NAME cargo-generate-lockfile – Generate the lockfile for a project SYNOPSIS cargo generate-lockfile [OPTIONS] OPTIONS -h, –help Print this message. –manifest-path PATH Path to the manifest to generate a lockfile for. -v, –verbose Use verbose output. -q, –quiet No output printed to stdout. –color WHEN Coloring: auto, always, never. SEE ALSO cargo(1) COPYRIGHT This work is…
NAME cargo-fetch – Fetch dependencies of a package from the network SYNOPSIS cargo fetch [OPTIONS] DESCRIPTION If a lockfile is available, this command will ensure that all of the git dependencies and/or registries dependencies are downloaded and locally available. The network is never touched after a `cargo fetch` unless the lockfile changes. If the lockfile…
NAME cargo-doc – Build a package’s documentation SYNOPSIS cargo doc [OPTIONS] DESCRIPTION Build a package’s documentation. By default the documentation for the local package and all dependencies is built. The output is all placed in ‘target/doc’ in rustdoc’s usual format. If the –package argument is given, then SPEC is a package id specification which indicates…
NAME cargo-clean – Remove generated artifacts SYNOPSIS cargo clean [OPTIONS] DESCRIPTION Remove artifacts that cargo has generated in the past. If the –package argument is given, then SPEC is a package id specification which indicates which package should be built. If it is not given, then the current package is built. For more information on…
NAME cargo-check – Check the current project SYNOPSIS cargo check [OPTIONS] DESCRIPTION Check a local package and all of its dependencies. If the –package argument is given, then SPEC is a package id specification which indicates which package should be checked. If it is not given, then the current package is checked. For more information…
NAME cargo-build – Compile the current project SYNOPSIS cargo build [OPTIONS] DESCRIPTION Compile a local package and all of its dependencies. If the –package argument is given, then SPEC is a package id specification which indicates which package should be built. If it is not given, then the current package is built. For more information…
NAME cargo-bench – Execute benchmarks of a package SYNOPSIS cargo bench [OPTIONS] [–] [<ARGS>…] DESCRIPTION Execute all benchmarks of a local package. All of the trailing arguments are passed to the benchmark binaries generated for filtering benchmarks and generally providing options configuring how they run. If the –package argument is given, then SPEC is a…
NAME cardos-tool – displays information about Card OS-based security tokens or format them SYNOPSIS cardos-tool [OPTIONS] DESCRIPTION The cardos-tool utility is used to display information about smart cards and similar security tokens based on Siemens Card/OS M4. OPTIONS –info, -i Display information about the card or token. –format, -f Format the card or token. –reader…
NAME card_eventmgr – PCSC-Lite Event Manager SYNTAX card_eventmgr [debug] [[no]daemon] [timeout=<msecs>] [config_file=<filename>] [kill] [pidfile=<pidfile>] DESCRIPTION card_eventmgr is a smart card monitoring tool that listen to the status of the card reader and dispatch actions on several events. card_eventmgr can be used for several actions: like screen lock on card removal. Three events are supported: card…
NAME card – print reference card of program options SYNOPSIS card [OPTION]… PROGRAM… DESCRIPTION Print a reference card of the PROGRAMs thanks to their inline help. OPTIONS -h, –help display this help and exit -v, –version display version information and exit -o, –output=FILE save the output in FILE -l, –language=LL print the help in the…
NAME carbon-relay – replication and sharding data SYNOPSYS carbon-relay [options] start DESCRIPTION carbon-relay serves two distinct purposes: replication and sharding. The options are described below. OPTIONS -h, –help Show the embedded help. –debug Run in the foreground, log to stdout –profile=PROFILE Record performance profile data to the given file –pidfile=PIDFILE Write pid to the given…
NAME carbon-client – Graphite client to reroute carbon data SYNOPSYS carbon-client [options] DESCRIPTION Graphite client to reroute carbon data The options are described below. OPTIONS -h, –help Show the embedded help. –debug Log debug info to stdout –keyfunc=KEYFUNC Use a custom key function (path/to/module.py:myFunc) –replication=REPLICATION Replication factor –routing=ROUTING Routing method: "consistent-hashing" (default) or "relay" –relayrules=RELAYRULES…
NAME carbon-cache – accepts metrics over various protocols and writes them to disk SYNOPSYS carbon-cache [options] start DESCRIPTION carbon-cache accepts metrics over various protocols and writes them to disk as efficiently as possible. This requires caching metric values in RAM as they are received, and flushing them to disk on an interval using the underlying…
NAME carbon-c-relay — graphite relay, aggregator and rewriter https://travis-ci.org/grobian/carbon-c-relay SYNOPSIS carbon-c-relay -f config-file [ options … ] DESCRIPTION carbon-c-relay accepts, cleanses, matches, rewrites, forwards and aggregates graphite metrics by listening for incoming connections and relaying the messages to other servers defined in its configuration. The core functionality is to route messages via flexible rules to…
NAME carbon-aggregator – buffer metrics over time before reporting to carbon-cache SYNOPSYS carbon-aggregator [options] start DESCRIPTION carbon-aggregator can be run in front of carbon-cache to buffer metrics over time before reporting them into whisper. The options are described below. OPTIONS -h, –help Show the embedded help. –debug Run in the foreground, log to stdout –profile=PROFILE…
NAME captoinfo – convert a termcap description into a terminfo description SYNOPSIS captoinfo [-vn width] [-V] [-1] [-w width] file … DESCRIPTION captoinfo looks in each given text file for termcap descriptions. For each one found, an equivalent terminfo description is written to standard output. Termcap tc capabilities are translated directly to terminfo use capabilities….
NAME capsh – capability shell wrapper SYNOPSIS capsh [OPTION]… DESCRIPTION Linux capability support and use can be explored and constrained with this tool. This tool provides a handy wrapper for certain types of capability testing and environment creation. It also provides some debugging features useful for summarizing capability state. OPTIONS capsh takes a number of…