neulab/tldr huggingface dataset:
--wrap=<command string> Sbatch will wrap the specified command string in a simple "sh" shell script, and submit that script to the slurm controller. When --wrap is used, a script name and arguments may not be specified on the command line; instead the sbatch-generated wrapper script is used.
-x, --exclude=<node name list> Explicitly exclude certain nodes from the resources granted to the job.
filename pattern sbatch allows for a filename pattern to contain one or more replacement symbols, which are a percent sign "%" followed by a letter (e.g. %j).
\\     Do not process any of the replacement symbols.
%%     The character "%".
%A     Job array's master job allocation number.
%a     Job array ID (index) number.
%J     jobid.stepid of the running job. (e.g. "128.0")
%j     jobid of the running job.
%N     short hostname. This will create a separate IO file per node.
%n     Node identifier relative to current job (e.g. "0" is the first node of the running job) This will create a separate IO file per node.
%s     stepid of the running job.
%t     task identifier (rank) relative to current job. This will create a separate IO file per task.
%u     User name.
%x     Job name.
A number placed between the percent character and format specifier may be used to zero-pad the result in the IO filename. This number is ignored if the format specifier corresponds to  non-numeric data (%N for example).
Some examples of how the format string may be used for a 4 task job step with a Job ID of 128 and step id of 0 are included below:
job%J.out      job128.0.out
job%4j.out     job0128.out
job%j-%2t.out  job128-00.out, job128-01.out, ...
Executing sbatch sends a remote procedure call to slurmctld. If enough calls from sbatch or other Slurm client commands that send remote procedure calls to the slurmctld daemon come in at once, it can result in a degradation of performance of the slurmctld daemon, possibly resulting in a denial of service.
Do not run sbatch or other Slurm client commands that send remote procedure calls to slurmctld from loops in shell scripts or other programs. Ensure that programs limit calls to sbatch to the minimum necessary for the information you are trying to gather.
Upon startup, sbatch will read and handle the options set in the following environment variables.  Note that environment variables will override any options set in a batch script, and command line options will override any environment variables.
SBATCH_ACCOUNT        Same as -A, --account
SBATCH_ACCTG_FREQ     Same as --acctg-freq
SBATCH_ARRAY_INX      Same as -a, --array
SBATCH_BATCH          Same as --batch
SBATCH_CLUSTERS or SLURM_CLUSTERS Same as --clusters
SBATCH_CONSTRAINT     Same as -C, --constraint
SBATCH_CORE_SPEC      Same as --core-spec
SBATCH_CPUS_PER_GPU   Same as --cpus-per-gpu
SBATCH_DEBUG          Same as -v, --verbose
SBATCH_DELAY_BOOT     Same as --delay-boot
SBATCH_DISTRIBUTION   Same as -m, --distribution
SBATCH_EXCLUSIVE      Same as --exclusive
SBATCH_EXPORT         Same as --export
SBATCH_GET_USER_ENV   Same as --get-user-env
SBATCH_GPUS           Same as -G, --gpus
SBATCH_GPU_BIND       Same as --gpu-bind
SBATCH_GPU_FREQ       Same as --gpu-freq
SBATCH_GPUS_PER_NODE  Same as --gpus-per-node
SBATCH_GPUS_PER_TASK  Same as --gpus-per-task
SBATCH_GRES           Same as --gres
SBATCH_GRES_FLAGS     Same as --gres-flags
SBATCH_HINT or SLURM_HINT Same as --hint
SBATCH_IGNORE_PBS     Same as --ignore-pbs
SBATCH_JOB_NAME       Same as -J, --job-name
SBATCH_MEM_BIND       Same as --mem-bind
SBATCH_MEM_PER_CPU    Same as --mem-per-cpu
SBATCH_MEM_PER_GPU    Same as --mem-per-gpu
SBATCH_MEM_PER_NODE   Same as --mem
SBATCH_NETWORK        Same as --network
SBATCH_NO_KILL        Same as -k, --no-kill
SBATCH_NO_REQUEUE     Same as --no-requeue
SBATCH_OPEN_MODE      Same as --open-mode
SBATCH_OVERCOMMIT     Same as -O, --overcommit
SBATCH_PARTITION      Same as -p, --partition
SBATCH_POWER          Same as --power
SBATCH_PROFILE        Same as --profile
SBATCH_QOS            Same as --qos
SBATCH_RESERVATION    Same as --reservation
SBATCH_REQ_SWITCH     When a tree topology is used, this defines the maximum count of switches desired for the job allocation and optionally the maximum time to wait for that number of switches. See --switches
SBATCH_REQUEUE        Same as --requeue
SBATCH_SIGNAL         Same as --signal
SBATCH_SPREAD_JOB     Same as --spread-job
SBATCH_THREAD_SPEC    Same as --thread-spec
SBATCH_TIMELIMIT      Same as -t, --time
SBATCH_USE_MIN_NODES  Same as --use-min-nodes
SBATCH_WAIT           Same as -W, --wait
SBATCH_WAIT_ALL_NODES Same as --wait-all-nodes
SBATCH_WAIT4SWITCH    Max time waiting for requested switches. See --switches
SBATCH_WCKEY          Same as --wckey
SLURM_CONF            The location of the Slurm configuration file.
SLURM_EXIT_ERROR      Specifies the exit code generated when a Slurm error occurs (e.g. invalid options).  This can be used by a script to distinguish application exit codes from various Slurm error conditions.
SLURM_STEP_KILLED_MSG_NODE_ID=ID If set, only the specified node will log when the job or step are killed by a signal.
The Slurm controller will set the following variables in the environment of the batch script.
SBATCH_MEM_BIND Set to value of the --mem-bind option.
SBATCH_MEM_BIND_LIST Set to bit mask used for memory binding.
SBATCH_MEM_BIND_PREFER Set to "prefer" if the --mem-bind option includes the prefer option.
SBATCH_MEM_BIND_TYPE Set to the memory binding type specified with the --mem-bind option.  Possible values are "none", "rank", "map_map", "mask_mem" and "local".
SBATCH_MEM_BIND_VERBOSE Set to "verbose" if the --mem-bind option includes the verbose option.  Set to "quiet" otherwise.
SLURM_*_HET_GROUP_# For a heterogeneous job allocation, the environment variables are set separately for each component.
SLURM_ARRAY_TASK_COUNT Total number of tasks in a job array.
SLURM_ARRAY_TASK_ID Job array ID (index) number.
SLURM_ARRAY_TASK_MAX Job array's maximum ID (index) number.
SLURM_ARRAY_TASK_MIN Job array's minimum ID (index) number.
SLURM_ARRAY_TASK_STEP Job array's index step size.
SLURM_ARRAY_JOB_ID Job array's master job ID number.
SLURM_CLUSTER_NAME Name of the cluster on which the job is executing.
SLURM_CPUS_ON_NODE Number of CPUS on the allocated node.
SLURM_CPUS_PER_GPU Number of CPUs requested per allocated GPU.  Only set if the --cpus-per-gpu option is specified.
SLURM_CPUS_PER_TASK Number of cpus requested per task.  Only set if the --cpus-per-task option is specified.
SLURM_DIST_PLANESIZE Plane distribution size. Only set for plane distributions.  See -m, --distribution.
SLURM_DISTRIBUTION Same as -m, --distribution
SLURM_EXPORT_ENV Same as -e, --export.
SLURM_GPUS Number of GPUs requested.  Only set if the -G, --gpus option is specified.
SLURM_GPU_BIND Requested binding of tasks to GPU.  Only set if the --gpu-bind option is specified.
SLURM_GPU_FREQ Requested GPU frequency.  Only set if the --gpu-freq option is specified.
SLURM_GPUS_PER_NODE Requested GPU count per allocated node.  Only set if the --gpus-per-node option is specified.
SLURM_GPUS_PER_SOCKET Requested GPU count per allocated socket.  Only set if the --gpus-per-socket option is specified.
SLURM_GPUS_PER_TASK Requested GPU count per allocated task.  Only set if the --gpus-per-task option is specified.
SLURM_GTIDS Global task IDs running on this node.  Zero  origin and comma separated.
SLURM_JOB_ACCOUNT Account name associated of the job allocation.
SLURM_JOB_ID (and SLURM_JOBID for backwards compatibility) The ID of the job allocation.
SLURM_JOB_CPUS_PER_NODE Count of processors available to the job on this node.  Note the select/linear plugin allocates entire nodes to jobs, so the value indicates the total count of CPUs on the node.  The select/cons_res plugin allocates individual processors to jobs, so this number indicates the number of processors on this node allocated to the job.
SLURM_JOB_DEPENDENCY Set to value of the --dependency option.
SLURM_JOB_NAME Name of the job.
SLURM_JOB_NODELIST (and SLURM_NODELIST for backwards compatibility) List of nodes allocated to the job.
SLURM_JOB_NUM_NODES (and SLURM_NNODES for backwards compatibility) Total number of nodes in the job's resource allocation.
SLURM_JOB_PARTITION Name of the partition in which the job is running.
SLURM_JOB_QOS Quality Of Service (QOS) of the job allocation.
SLURM_JOB_RESERVATION Advanced reservation containing the job allocation, if any.
SLURM_LOCALID Node local task ID for the process within a job.
SLURM_MEM_PER_CPU Same as --mem-per-cpu
SLURM_MEM_PER_GPU Requested memory per allocated GPU.  Only set if the --mem-per-gpu option is specified.
SLURM_MEM_PER_NODE Same as --mem
SLURM_NODE_ALIASES Sets of node name, communication address and hostname for nodes allocated to the job from the cloud. Each element in the set if colon separated and each set is comma separated. For example: SLURM_NODE_ALIASES=ec0:1.2.3.4:foo,ec1:1.2.3.5:bar
SLURM_NODEID ID of the nodes allocated.
SLURM_NTASKS (and SLURM_NPROCS for backwards compatibility) Same as -n, --ntasks
SLURM_NTASKS_PER_CORE Number of tasks requested per core.  Only set if the --ntasks-per-core option is specified.
SLURM_NTASKS_PER_GPU Number of tasks requested per GPU.  Only set if the --ntasks-per-gpu option is specified.
SLURM_NTASKS_PER_NODE Number of tasks requested per node.  Only set if the --ntasks-per-node option is specified.
SLURM_NTASKS_PER_SOCKET Number of tasks requested per socket.  Only set if the --ntasks-per-socket option is specified.
SLURM_HET_SIZE Set to count of components in heterogeneous job.
SLURM_PRIO_PROCESS The  scheduling priority (nice value) at the time of job submission.  This value is  propagated  to the spawned processes.
SLURM_PROCID The MPI rank (or relative process ID) of the current process
SLURM_PROFILE Same as --profile
SLURM_RESTART_COUNT If the job has been restarted due to system failure or has been explicitly requeued, this will be sent to the number of times the job has been restarted.
SLURM_SUBMIT_DIR The directory from which sbatch was invoked or, if applicable, the directory specified by the -D, --chdir option.
SLURM_SUBMIT_HOST The hostname of the computer from which sbatch was invoked.
SLURM_TASKS_PER_NODE Number of tasks to be initiated on each node. Values are comma separated and in the same order as SLURM_JOB_NODELIST.  If two or more consecutive nodes are to have the same task count, that count is followed by "(x#)" where "#" is the repetition count. For example, "SLURM_TASKS_PER_NODE=2(x3),1" indicates that the first three nodes will each execute two tasks and the fourth node will execute one task.
SLURM_TASK_PID The process ID of the task being started.
SLURM_TOPOLOGY_ADDR This is set only if the  system  has  the  topology/tree  plugin configured.   The value will be set to the names network switches which  may be  involved  in  the  job's  communications from the system's top level switch down to the leaf switch and  ending with node name. A period is used to separate each hardware component name.
SLURM_TOPOLOGY_ADDR_PATTERN This is set only if the  system  has  the  topology/tree  plugin configured. The value will be set  component  types  listed   in SLURM_TOPOLOGY_ADDR.   Each  component will be identified as either "switch" or "node".  A period is  used  to separate each hardware component type.
SLURMD_NODENAME Name of the node running the job script.
Specify a batch script by filename on the command line.  The batch script specifies a 1 minute time limit for the job.
$ cat myscript #!/bin/sh #SBATCH --time=1 srun hostname |sort
$ sbatch -N4 myscript salloc: Granted job allocation 65537
$ cat slurm-65537.out host1 host2 host3 host4
Pass a batch script to sbatch on standard input:
$ sbatch -N4 <<EOF > #!/bin/sh > srun hostname |sort > EOF sbatch: Submitted batch job 65541
$ cat slurm-65541.out host1 host2 host3 host4
To create a heterogeneous job with 3 components, each allocating a unique set of nodes:
sbatch -w node[2-3] : -w node4 : -w node[5-7] work.bash Submitted batch job 34987
Copyright (C) 2006-2007 The Regents of the University of California. Produced at Lawrence Livermore National Laboratory (cf, DISCLAIMER). Copyright (C) 2008-2010 Lawrence Livermore National Security. Copyright (C) 2010-2017 SchedMD LLC.
sinfo(1), sattach(1), salloc(1), squeue(1), scancel(1), scontrol(1), slurm.conf(5), sched_setaffinity (2), numa (3)
BlockOut2(6)                      Games Manual                      BlockOut2(6)
blockout2 - the tetris like game (3D tetris)
blockout2
BlockOut II is a free adaptation of the original BlockOut DOS game edited by California Dreams in 1989. BlockOut II has the same features than the original game with few graphic improvements. The score calculation is also nearly similar to the original game. BlockOut II has been designed by an addicted player for addicted players. BlockOut II is an open source project available for both Windows and Linux.
Use keys 'Q', 'W', 'E', 'A', 'S', 'D' for rotate item, 'Space' for drop item, 'Arrows' for move item, 'P' for pause.
ESLINT(1)                         User Commands                        ESLINT(1)
eslint - JavaScript
eslint [options] file.js [file.js] [dir]
Basic configuration: --no-eslintrc Disable use of configuration from .eslintrc.*
-c, --config path::String Use this configuration, overriding .eslintrc.* config options if present
--env [String] Specify environments
--ext [String] Specify JavaScript file extensions - default: .js
--global [String] Define global variables
--parser String Specify the parser to be used
--parser-options Object Specify parser options
Specifying rules and plugins: --rulesdir [path::String] Use additional rules from this directory
--plugin [String] Specify plugins
--rule Object Specify rules
Fixing problems: --fix  Automatically fix problems
--fix-dry-run Automatically fix problems without saving the changes to the file system
--fix-type Array Specify the types of fixes to apply (problem, suggestion, layout)
Ignoring files: --ignore-path path::String Specify path of ignore file
--no-ignore Disable use of ignore files and patterns
--ignore-pattern [String] Pattern of files to ignore (in addition to those in .eslintignore)
Using stdin: --stdin Lint code provided on <STDIN> - default: false
--stdin-filename String Specify filename to process STDIN as
Handling warnings: --quiet Report errors only - default: false
--max-warnings Int Number of warnings to trigger nonzero exit code - default: -1
Output: -o, --output-file path::String Specify file to write report to
-f, --format String Use a specific output format - default: stylish
--color, --no-color Force enabling/disabling of color
Inline configuration comments: --no-inline-config Prevent comments from changing config or rules
--report-unused-disable-directives Adds reported errors for unused eslint-disable directives
Caching: --cache Only check changed files - default: false
--cache-file path::String Path to the cache file. Deprecated: use --cache-location - default: .eslintcache
--cache-location path::String Path to the cache file or directory
Miscellaneous: --init Run config initialization wizard - default: false
--debug Output debugging information
-h, --help Show help
-v, --version Output the version number
--print-config path::String Print the configuration for the given file
reportbug(1)                 General Commands Manual                reportbug(1)
reportbug - reports a bug to a debbugs server
reportbug [options] <package | pseudo-package | absolute-pathname>
reportbug is primarily designed to report bugs in the Debian distribution; by default, it creates an email to the Debian bug tracking system at submit@bugs.debian.org with information about the bug you've found, and makes a carbon copy of the report for you as well.
Using the --bts option, you can also report bugs to other servers that use the Debian bug tracking system, debbugs.
You may specify either a package name or a filename; if you use a filename, it must either be an absolute filename (so beginning with a /) or if you want reportbug to search the system for a filename, see the --filename and --path options below. If installed, also dlocate is used to identify the filename location and thus the package containing it.
You can also specify a pseudo-package; these are used in the Debian bug tracking system to track issues that are not related to one specific package.  Run reportbug without any arguments, then enter other at the package prompt, to see a list of the most commonly-used pseudo-packages.
The program follows the usual GNU command line syntax, with long options starting with two dashes (`--').  A summary of options are included below.
--version Show the version of reportbug and exit.
-A FILENAME, --attach=FILENAME Attach a file to the bug report; both text and binary files are acceptable; this option can be specified multiple times to attach several files.  This routine will create a MIME attachment with the file included; in some cases (usually text files), it is probably better to use -i/--include option.  (Please note that Debian's bug tracking system has limited support for MIME attachments.)
This option supports also globbing (i.e. names with wildcards, like file.*) but remember to include them between single quotes (the previous example becomes: 'file.*') else the shell would expand it before calling reportbug leading to an error.
Be aware that when using an external MUA to send the message (such as mutt), the attachment feature is not available and no file will be attached at all: the MUA feature to attach files must be used instead (so from within the MUA).
-b, --no-query-bts Don't check the Debian bug tracking system to see if this problem has already been reported; useful for offline use or if you're really sure it's a bug.
--query-bts Check the Debian bug tracking system to see if this problem has already been reported (default).
-B SYSTEM, --bts=SYSTEM Instead of the Debian bug server (or the bug server specified in /etc/reportbug.conf, use the server specified by SYSTEM.
--body=BODY Use the specified BODY as the body of the message.  The body text will be wrapped at 70 columns, and the normal reportbug headers and footers will be added as appropriate.  The editor prompt and any "special" prompting will be bypassed.
--body-file=BODYFILE, --bodyfile=BODYFILE The contents of the (assumed to be) text file BODYFILE will be used as the message body.  This file is assumed to be properly formatted (i.e. reasonable line lengths, etc.).  The usual headers and footers will be added, and the editor step and "special" prompts will be skipped.  (BODYFILE may also be a named pipe; using a device special file may lead to unusual results.)
-c, --no-config-files Omit configuration files from the bug report without asking.  By default, you are asked if you want to include them; in some cases, doing so may cause sensitive information to be sent via email.
-C CLASS, --class=CLASS Specify report class for GNATS BTSes.
--configure Rerun the reportbug first time configuration routine, and write a new $HOME/.reportbugrc file.  This will erase any pre-existing settings in the file; however, a backup will be written as $HOME/.reportbugrc~.
--check-available Check for newer releases of the package at packages.debian.org (default).  In advanced and expert mode, check incoming.debian.org and http://ftp-master.debian.org/new.html too.
--no-check-available Do not check for newer releases of the package at packages.debian.org.
--debconf Include debconf settings in your report.
--no-debconf Do not include debconf settings from your report.
-d, --debug Don't send a real bug report to Debian; send it to yourself instead.  This is primarily used for testing by the maintainer.
--test Operate in test mode (maintainer use only).
--draftpath=DRAFTPATH Save the draft (for example, when exiting and saving the report without reporting it) into DRAFTPATH directory(default /tmp).
-e EDITOR, --editor=EDITOR Specify the editor to use, overriding any EDITOR or VISUAL environment variable setting.
--email=ADDRESS Set the email address your report should appear to be sent from (i.e. the address that appears in the From header).  This should be the actual Internet email address on its own (i.e. without a real name or comment part, like foo@example.com).  This setting will override the EMAIL and DEBEMAIL environment variables, but not REPORTBUGEMAIL.
--envelope-from Specify the Envelope From mail header (also known as Return-path); by default it's the From address but it can be selected a different one in case the MTA doesn't canonicalize local users to public addresses.
--mbox-reader-cmd=MBOX_READER_CMD Specify a command to open the bug reports mbox file. You can use %s to substitute the mbox file to be used, and %% to insert a literal percent sign. If no %s is specified, the mbox file name is supplied at the end of the argument list.
--exit-prompt Display a prompt before exiting; this is useful if reportbug is run in a transient terminal (i.e. from its Debian menu entry).
-f FILENAME, --filename=FILENAME Report a bug in the package containing FILENAME so you don't have to figure out what package the file belongs to.  The path will be searched for an exact path for FILENAME before attempting to broaden the search to all files. If dlocate is installed, FILENAME is actually a regular expression.
--from-buildd=BUILDD_FORMAT This options is a shortcut for buildd admins to report bugs from buildd log; the option expects a value in the format of $source_$version where $source is the source package the bug will be reported against and $version is its version.
--path If the -f/--filename option is also specified, only search the path for the specified FILENAME.  Specifying an absolute path with the -f/--filename option (i.e. one beginning with a /) overrides this behavior.
-g, --gnupg, --gpg Attach a digital signature to the bug report using GnuPG (the GNU Privacy Guard).  (This argument will be ignored if you are using an MUA to edit and send your report.)
-G, --gnus Use the Gnus mail and news reader to send your report, rather than using the editor.
-H HEADER, --header=HEADER Add a custom RFC2822 header to your email; for example, to send a carbon copy of the report to debian-68k@lists.linux-m68k.org you could use -H 'X-Debbugs-CC: debian-68k@lists.linux-m68k.org'
-i FILE, --include=FILE Include the specified FILE as part of the body of the message to be edited.  Can be used multiple times to add multiple files; text-only please!  From a suggestion by Michael Alan Dorman in the bug mailing list.  (See also the -A/--attach option.)
-I, --no-check-installed Do not check whether the package is installed before filing a report.  This is generally only useful when filing a report on a package you know is not installed on your system.
--check-installed Check if the specified package is installed when filing reports. (This is the default behavior of reportbug.)
-j JUSTIFICATION, --justification=JUSTIFICATION Bugs in Debian that have serious, grave, or critical severities must meet certain criteria to be classified as such.  This option allows you to specify the justification for a release-critical bug, instead of being prompted for it.
-k, --kudos Send appreciative email to the recorded maintainer address, rather than filing a bug report.  (You can also send kudos to packagename@packages.debian.org, for packages in the Debian archive; however, this option uses the Maintainer address from the control file, so it works with other package sources too.)
-K KEYID, --keyid=KEYID Private key to use for PGP/GnuPG signatures.  If not specified, the first key in the secret keyring that matches your email address will be used.
--latest-first Display the bug reports list sorted and with the latest reports at the top.
--license Show reportbug's copyright and license information on standard output.
--list-cc=ADDRESS Send a carbon copy of the report to the specified list after a report number is assigned; this is the equivalent to the option -H 'X-Debbugs-CC: ADDRESS'.  This option will only work as intended with debbugs systems.
--list-cc-me Send a carbon copy of the report to your automatically detected email address after a report number is assigned. This sets an X-Debbugs-CC header specifying that address. This option will only work as intended with debbugs systems. See the documentation for the --email option and the ENVIRONMENT section for information on how reportbug detects your email address.
-m, --maintonly Only send the bug to the package maintainer; the bug tracking system will not send a copy to the bug report distribution lists.
--max-attachment-size=MAX_ATTACHMENT_SIZE Specify the maximum size any attachment file can have (this also include the file for --body-file option). If an attachment file is too big, there could be problems in delivering the email (and also to compose it), so we set a limit to attachment size. By default this is 10 megabytes.
--mirror=MIRRORS Add a BTS mirror.
--mode=MODE Set the operating mode for reportbug.  reportbug currently has four operating modes: novice (the default), standard, advanced, and expert.
novice mode is designed to minimize prompting about things that "ordinary users" would be unlikely to know or care about, shifting the triage burden onto the maintainer.  Checking for new versions is only done for the stable distribution in this mode.  It is currently the default mode.
standard mode includes a relatively large number of prompts and tries to encourage users to not file frivolous or duplicate bug reports.
advanced mode is like standard mode, but may include shortcuts suitable for more advanced users of Debian, without being as close to the metal (and potential flamage) as expert mode.  (Currently, the only differences from standard mode are that it assumes familiarity with the "incoming" queue; it allows the reporting of bugs on "dependency" packages; and it does not prompt where to insert the report text in the editor.)
expert mode is designed to minimize prompts that are designed to discourage frivolous or unnecessary bug reports, "severity inflation," and the like.  In expert mode, reportbug assumes the user is thoroughly familiar with Debian policies.  In practice, this means that reporters are no longer required to justify setting a high severity on a bug report, and certain automated cleanups of the message are bypassed.  Individuals who do not regularly contribute to the Debian project are highly discouraged from using expert mode, as it can lead to flamage from maintainers when used improperly.
-M, --mutt Instead of spawning an editor to revise the bug report, use the mutt mail reader to edit and send it.
--mta=MTA Specify an alternate MTA, instead of /usr/sbin/sendmail (the default).  Any smtphost setting will override this one.
--mua=MUA Instead of spawning an editor to revise the bug report, use the specified MUA (mail user agent) to edit and send it. --mutt and --nmh options are processed.
-n, --mh, --nmh Instead of spawning an editor to revise the bug report, use the comp command (part of the nmh and mh mail systems) to edit and send it.
-N BUGNUMBER, --bugnumber BUGNUMBER Run reportbug against the specified bug report, useful when following-up a bug and its number is already known.
--no-bug-script Do not execute the bug script (if present); this option can be useful together with --template to suppress every interactive actions, since some bug scripts can ask questions.
--no-cc-menu Don't display the menu to enter additional addresses (CC).
--no-tags-menu Don't display the menu to enter additional tags.
-o FILE, --output=FILE Instead of sending an email, redirect it to the specified filename.
The output file is a full dump of the email message, so it contains both headers and mail body. If you want to use it as a template to create a new bug report, then you have to remove all the headers (mind the Subject one, though) and start the report at the Package pseudo-header.
-O, --offline Disable all external queries.  Currently has the same effect as --no-check-available --no-query-bts.
-p, --print Instead of sending an email, print the bug report to standard output, so you can redirect it to a file or pipe it to another program.
This option only outputs a template for a bug report (but, differently from --template it's more interactive); you will need to fill in the long description.
--paranoid Show the contents of the message before it is sent, including all headers.  Automatically disabled if in template mode.
--no-paranoid Don't show the full contents of the message before it is sent (default).
--pgp  Attach a digital signature to the bug report using PGP (Pretty Good Privacy).  Please note, however, that the Debian project is phasing out the use of PGP in favor of GnuPG.  (This argument will be ignored if using an MUA to edit and send your report.)
--proxy=PROXY, --http_proxy=PROXY Specify the WWW proxy server to use to handle the query of the bug tracking system.  You should only need this parameter if you are behind a firewall.  The PROXY argument should be formatted as a valid HTTP URL, including (if necessary) a port number; for example, http://192.168.1.1:3128/.
-P PSEUDO-HEADER, --pseudo-header=PSEUDO-HEADER Add a custom pseudo-header to your report; for example, to add the mytag usertag for the user humberto@example.com to the bug, you could use -P 'User: humberto@example.com' -P 'Usertags: mytag'.
-q, --quiet Suppress diagnostic messages to standard error.
-Q, --query-only Do not submit a bug report; just query the BTS.  Option ignored if you specify --no-bts-query.
--query-source Query on all binary packages built by the same source, not just the binary package specified.
--no-query-source Only query on the binary package specified on the command line.
--realname=NAME Set the real name (human-readable name) to use for your report.
--report-quiet Register the bug in the bug tracking system, but don't send a report to the package maintainer or anyone else.  Don't do this unless you're the maintainer of the package in question, or you really know what you are doing.
--reply-to=ADDRESS, --replyto=ADDRESS Set the Reply-To address header in your report.
-s SUBJECT, --subject=SUBJECT Set the subject of the bug report (i.e. a brief explanation of the problem, less than 60 characters).  If you do not specify this switch, you will be prompted for a subject.
--security-team If the 'security' tag is set, this option will explicitly specify to send the report only to the Debian Security Team, as this is an undisclosed vulnerability.
--no-security-team If the 'security' tag is set, this option will explicitly specify to not send the report only to the Debian Security Team, as this is not an undisclosed vulnerability.
-S SEVERITY, --severity=SEVERITY Specify a severity level, from critical, grave, serious, important, normal, minor, and wishlist.
--smtphost=HOST[:PORT] Use the mail transport agent (MTA) at HOST to send your report, instead of your local /usr/sbin/sendmail program.  This should generally be your ISP's outgoing mail server; you can also use 'localhost' if you have a working mail server running on your machine.  If the PORT is omitted, the standard port for SMTP, port 25, is used.
--timeout=SECONDS Specify the network timeout, the number of seconds to wait for a resource to respond. If nothing is specified, a default timeout of 1 minute is selected.
In case of a network error, there are chances it's due to a too low timeout: try passing the --timeout option with a higher value than default.
--tls  If using SMTP, use Transport Layer Security (TLS) encryption to secure the connection to the mail server.  Some SMTP servers may require this option.
--smtpuser=USERNAME If using SMTP, use the specified USERNAME for authentication.
--smtppasswd=PASSWORD If using SMTP, use the specified PASSWORD for authentication.  If the password isn't specified on the command line or in the configuration file, a prompt will be displayed asking for it.
Use of this option is insecure on multiuser systems.  Instead, you should set this option in $HOME/.reportbugrc and ensure it is only readable by your user (e.g. with chmod 600 $HOME/.reportbugrc).
--src, --source Specify to report the bug against the source package, and not the binary package (default behaviour).  In order for this option to work, you have to populate the relevant 'deb-src' lines in /etc/apt/sources.list so that apt cache will know about source packages too.
-t TYPE, --type=TYPE Specify the type of report to be submitted; currently accepts either gnats or debbugs.
-T TAG, --tag=TAG Specify a tag to be filed on this report, for example --tag=patch. Multiple tags can be specified using multiple -T/--tag arguments.
Alternatively, you can specify the 'tag' none to bypass the tags prompt without specifying any tags; this will also ignore any tags specified on the command line.
--template Output a template report to standard output. Differently from -p/--print, it tries to be not interactive, and presents a template without user's input.
-u INTERFACE, --interface=INTERFACE, --ui=INTERFACE Specify the user interface to use.  Valid options are text, urwid, and gtk; default is taken from the reportbug configuration files.
-v, --verify Verify the integrity of the package (if installed) using debsums before reporting.
--no-verify Do not verify the integrity of the package with debsums.
-V VERSION, --package-version=VERSION Specify the version of the package the problem was found in.  This is probably most useful if you are reporting a bug in a package that is not installable or installed on a different system.
-x, --no-cc Don't send a blind carbon copy (BCC) of the bug report to the submitter (i.e. yourself).
-z, --no-compress Don't compress configuration files by removing comments and blank lines.
reportbug lynx-ssl Report a bug in the lynx-ssl package.
reportbug --path --filename=ls Report a bug in the installed package that includes a program in your path called ls.
From version 0.22 on, reportbug has supported a simple run control file syntax.  Commands are read from /etc/reportbug.conf and $HOME/.reportbugrc with commands in the latter overriding those in the former.
Commands are not case sensitive, and currently take 0 or 1 argument; arguments containing whitespace must be enclosed in quotes.
Any line starting with # is taken to be a comment and will be ignored.
Generally, options corresponding to the long options for reportbug are supported, without leading -- sequences.  See reportbug.conf(5) for all acceptable options and detailed information.
VISUAL Editor to use for editing your bug report.
EDITOR Editor to use for editing the bug report (overridden by VISUAL).
REPORTBUGEMAIL, DEBEMAIL, EMAIL Email address to use as your from address (in this order). If no environment variable exists, the default is taken from your user name and /etc/mailname.
DEBFULLNAME, DEBNAME, NAME Real name to use; default is taken from /etc/passwd.
REPLYTO Address for Reply-To header in outgoing mail.
MAILCC Use the specified CC address on your email.  Note you can also use the -H option for this (and for Bcc's too).
MAILBCC Use the specified BCC address, instead of your email address.  (CC and BCC based on suggestions from Herbert Thielen in the bug wishlist).
http_proxy Provides the address of a proxy server to handle the BTS query. This should be a valid http URL for a proxy server, including any required port number (simply specifying a hostname, or omitting a port other than 80, WILL NOT WORK).
reportbug should probably be compatible with other bug tracking systems, like bugzilla (used by the GNOME and Mozilla projects) and jitterbug (used by Samba, AbiSource and FreeCiv) but it isn't.
reportbug.conf(5), http://www.debian.org/Bugs/Developer#tags for available tags, querybts(1)
Chris Lawrence <lawrencc@debian.org>, Sandro Tosi <morph@debian.org>.
SYSTEMCTL(1)                        systemctl                       SYSTEMCTL(1)
systemctl - Control the systemd system and service manager
systemctl [OPTIONS...] COMMAND [UNIT...]
systemctl may be used to introspect and control the state of the "systemd" system and service manager. Please refer to systemd(1) for an introduction into the basic concepts and functionality this tool manages.
Unit Commands (Introspection and Modification) list-units [PATTERN...] List units that systemd currently has in memory. This includes units that are either referenced directly or through a dependency, units that are pinned by applications programmatically, or units that were active in the past and have failed. By default only units which are active, have pending jobs, or have failed are shown; this can be changed with option --all. If one or more PATTERNs are specified, only units matching one of them are shown. The units that are shown are additionally filtered by --type= and --state= if those options are specified.
Note that this command does not show unit templates, but only instances of unit templates. Units templates that aren't instantiated are not runnable, and will thus never show up in the output of this command. Specifically this means that foo@.service will never be shown in this list — unless instantiated, e.g. as foo@bar.service. Use list-unit-files (see below) for listing installed unit template files.
Produces output similar to
UNIT                         LOAD   ACTIVE SUB     DESCRIPTION sys-module-fuse.device       loaded active plugged /sys/module/fuse -.mount                      loaded active mounted Root Mount boot-efi.mount               loaded active mounted /boot/efi systemd-journald.service     loaded active running Journal Service systemd-logind.service       loaded active running Login Service ● user@1000.service            loaded failed failed  User Manager for UID 1000 ... systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
LOAD   = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB    = The low-level unit activation state, values depend on unit type.
123 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.
The header and the last unit of a given type are underlined if the terminal supports that. A colored dot is shown next to services which were masked, not found, or otherwise failed.
The LOAD column shows the load state, one of loaded, not-found, bad-setting, error, masked. The ACTIVE columns shows the general unit state, one of active, reloading, inactive, failed, activating, deactivating. The SUB column shows the unit-type-specific detailed state of the unit, possible values vary by unit type. The list of possible LOAD, ACTIVE, and SUB states is not constant and new systemd releases may both add and remove values.
systemctl --state=help
command maybe be used to display the current set of possible values.
This is the default command.
list-sockets [PATTERN...] List socket units currently in memory, ordered by listening address. If one or more PATTERNs are specified, only socket units matching one of them are shown. Produces output similar to
LISTEN           UNIT                        ACTIVATES /dev/initctl     systemd-initctl.socket      systemd-initctl.service ... [::]:22          sshd.socket                 sshd.service kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
5 sockets listed.
Note: because the addresses might contains spaces, this output is not suitable for programmatic consumption.
Also see --show-types, --all, and --state=.
list-timers [PATTERN...] List timer units currently in memory, ordered by the time they elapse next. If one or more PATTERNs are specified, only units matching one of them are shown. Produces output similar to
NEXT                         LEFT          LAST                         PASSED     UNIT                         ACTIVATES n/a                          n/a           Thu 2017-02-23 13:40:29 EST  3 days ago ureadahead-stop.timer        ureadahead-stop.service Sun 2017-02-26 18:55:42 EST  1min 14s left Thu 2017-02-23 13:54:44 EST  3 days ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service Sun 2017-02-26 20:37:16 EST  1h 42min left Sun 2017-02-26 11:56:36 EST  6h ago     apt-daily.timer              apt-daily.service Sun 2017-02-26 20:57:49 EST  2h 3min left  Sun 2017-02-26 11:56:36 EST  6h ago     snapd.refresh.timer          snapd.refresh.service
NEXT shows the next time the timer will run.
LEFT shows how long till the next time the timer runs.
LAST shows the last time the timer ran.
PASSED shows how long has passed since the timer last ran.
UNIT shows the name of the timer
ACTIVATES shows the name the service the timer activates when it runs.
Also see --all and --state=.
is-active PATTERN... Check whether any of the specified units are active (i.e. running). Returns an exit code 0 if at least one is active, or non-zero otherwise. Unless --quiet is specified, this will also print the current unit state to standard output.
is-failed PATTERN... Check whether any of the specified units are in a "failed" state. Returns an exit code 0 if at least one has failed, non-zero otherwise. Unless --quiet is specified, this will also print the current unit state to standard output.
status [PATTERN...|PID...]] Show terse runtime status information about one or more units, followed by most recent log data from the journal. If no units are specified, show system status. If combined with --all, also show the status of all units (subject to limitations specified with -t). If a PID is passed, show information about the unit the process belongs to.
This function is intended to generate human-readable output. If you are looking for computer-parsable output, use show instead. By default, this function only shows 10 lines of output and ellipsizes lines to fit in the terminal window. This can be changed with --lines and --full, see above. In addition, journalctl --unit=NAME or journalctl --user-unit=NAME use a similar filter for messages and might be more convenient.
systemd implicitly loads units as necessary, so just running the status will attempt to load a file. The command is thus not useful for determining if something was already loaded or not. The units may possibly also be quickly unloaded after the operation is completed if there's no reason to keep it in memory thereafter.
Example 1. Example output from systemctl status
$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2017-01-04 13:54:04 EST; 1 weeks 0 days ago Docs: man:bluetoothd(8) Main PID: 930 (bluetoothd) Status: "Running" Tasks: 1 Memory: 648.0K CPU: 435ms CGroup: /system.slice/bluetooth.service └─930 /usr/lib/bluetooth/bluetoothd
Jan 12 10:46:45 example.com bluetoothd[8900]: Not enough free handles to register service Jan 12 10:46:45 example.com bluetoothd[8900]: Current Time Service could not be registered Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output error (5)
The dot ("●") uses color on supported terminals to summarize the unit state at a glance. Along with its color, its shape varies according to its state: "inactive" or "maintenance" is a white circle ("○"), "active" is a green dot ("●"), "deactivating" is a white dot, "failed" or "error" is a red cross ("×"), and "reloading" is a green clockwise circle arrow ("↻").
The "Loaded:" line in the output will show "loaded" if the unit has been loaded into memory. Other possible values for "Loaded:" include: "error" if there was a problem loading it, "not-found" if no unit file was found for this unit, "bad-setting" if an essential unit file setting could not be parsed and "masked" if the unit file has been masked. Along with showing the path to the unit file, this line will also show the enablement state. Enabled commands start at boot. See the full table of possible enablement states — including the definition of "masked" — in the documentation for the is-enabled command.
The "Active:" line shows active state. The value is usually "active" or "inactive". Active could mean started, bound, plugged in, etc depending on the unit type. The unit could also be in process of changing states, reporting a state of "activating" or "deactivating". A special "failed" state is entered when the service failed in some way, such as a crash, exiting with an error code or timing out. If the failed state is entered the cause will be logged for later reference.
show [PATTERN...|JOB...] Show properties of one or more units, jobs, or the manager itself. If no argument is specified, properties of the manager will be shown. If a unit name is specified, properties of the unit are shown, and if a job ID is specified, properties of the job are shown. By default, empty properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=. This command is intended to be used whenever computer-parsable output is required. Use status if you are looking for formatted human-readable output.
Many properties shown by systemctl show map directly to configuration settings of the system and service manager and its unit files. Note that the properties shown by the command are generally more low-level, normalized versions of the original configuration settings and expose runtime state in addition to configuration. For example, properties shown for service units include the service's current main process identifier as "MainPID" (which is runtime state), and time settings are always exposed as properties ending in the "...USec" suffix even if a matching configuration options end in "...Sec", because microseconds is the normalized time unit used internally by the system and service manager.
For details about many of these properties, see the documentation of the D-Bus interface backing these properties, see org.freedesktop.systemd1(5).
cat PATTERN... Show backing files of one or more units. Prints the "fragment" and "drop-ins" (source files) of units. Each file is preceded by a comment which includes the file name. Note that this shows the contents of the backing files on disk, which may not match the system manager's understanding of these units if any unit files were updated on disk and the daemon-reload command wasn't issued since.
help PATTERN...|PID... Show manual pages for one or more units, if available. If a PID is given, the manual pages for the unit the process belongs to are shown.
list-dependencies [UNIT...] Shows units required and wanted by the specified units. This recursively lists units following the Requires=, Requisite=, ConsistsOf=, Wants=, BindsTo= dependencies. If no units are specified, default.target is implied.
By default, only target units are recursively expanded. When --all is passed, all other units are recursively expanded as well.
Options --reverse, --after, --before may be used to change what types of dependencies are shown.
Note that this command only lists units currently loaded into memory by the service manager. In particular, this command is not suitable to get a comprehensive list at all reverse dependencies on a specific unit, as it won't list the dependencies declared by units currently not loaded.
start PATTERN... Start (activate) one or more units specified on the command line.
Note that unit glob patterns expand to names of units currently in memory. Units which are not active and are not in a failed state usually are not in memory, and will not be matched by any pattern. In addition, in case of instantiated units, systemd is often unaware of the instance name until the instance has been started. Therefore, using glob patterns with start has limited usefulness. Also, secondary alias names of units are not considered.
Option --all may be used to also operate on inactive units which are referenced by other loaded units. Note that this is not the same as operating on "all" possible units, because as the previous paragraph describes, such a list is ill-defined. Nevertheless, systemctl start --all GLOB may be useful if all the units that should match the pattern are pulled in by some target which is known to be loaded.
stop PATTERN... Stop (deactivate) one or more units specified on the command line.
This command will fail if the unit does not exist or if stopping of the unit is prohibited (see RefuseManualStop= in systemd.unit(5)). It will not fail if any of the commands configured to stop the unit (ExecStop=, etc.) fail, because the manager will still forcibly terminate the unit.