neulab/tldr huggingface dataset:
chcpu -c|-d|-e|-g cpu-list
chcpu -p mode
chcpu -r|-h|-V
chcpu can modify the state of CPUs. It can enable or disable CPUs, scan for new CPUs, change the CPU dispatching mode of the underlying hypervisor, and request CPUs from the hypervisor (configure) or return CPUs to the hypervisor (deconfigure).
Some options have a cpu-list argument. Use this argument to specify a comma-separated list of CPUs. The list can contain individual CPU addresses or ranges of addresses. For example, 0,5,7,9-11 makes the command applicable to the CPUs with the addresses 0, 5, 7, 9, 10, and 11.
-c, --configure cpu-list Configure the specified CPUs. Configuring a CPU means that the hypervisor takes a CPU from the CPU pool and assigns it to the virtual hardware on which your kernel runs.
-d, --disable cpu-list Disable the specified CPUs. Disabling a CPU means that the kernel sets it offline.
-e, --enable cpu-list Enable the specified CPUs. Enabling a CPU means that the kernel sets it online. A CPU must be configured, see -c, before it can be enabled.
-g, --deconfigure cpu-list Deconfigure the specified CPUs. Deconfiguring a CPU means that the hypervisor removes the CPU from the virtual hardware on which the Linux instance runs and returns it to the CPU pool. A CPU must be offline, see -d, before it can be deconfigured.
-p, --dispatch mode Set the CPU dispatching mode (polarization). This option has an effect only if your hardware architecture and hypervisor support CPU polarization. Available modes are:
horizontal The workload is spread across all available CPUs.
vertical The workload is concentrated on few CPUs.
-r, --rescan Trigger a rescan of CPUs. After a rescan, the Linux kernel recognizes the new CPUs. Use this option on systems that do not automatically detect newly attached CPUs.
chcpu has the following exit status values:
0 success
64 partial success
Heiko Carstens <heiko.carstens@de.ibm.com>
Copyright IBM Corp. 2011
lscpu(1)
The chcpu command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
CP(1)                             User Commands                            CP(1)
cp - copy files and directories
cp [OPTION]... [-T] SOURCE DEST cp [OPTION]... SOURCE... DIRECTORY cp [OPTION]... -t DIRECTORY SOURCE...
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY.
-a, --archive same as -dR --preserve=all
--attributes-only don't copy the file data, just the attributes
--copy-contents copy contents of special files when recursive
-d     same as --no-dereference --preserve=links
-f, --force if an existing destination file cannot be opened, remove it and try again (this option is ignored when the -n option is also used)
-i, --interactive prompt before overwrite (overrides a previous -n option)
-H     follow command-line symbolic links in SOURCE
-l, --link hard link files instead of copying
-L, --dereference always follow symbolic links in SOURCE
-n, --no-clobber do not overwrite an existing file (overrides a previous -i option)
-P, --no-dereference never follow symbolic links in SOURCE
-p     same as --preserve=mode,ownership,timestamps
--preserve[=ATTR_LIST] preserve the specified attributes (default: mode,ownership,timestamps), if possible additional attributes: context, links, xattr, all
--no-preserve=ATTR_LIST don't preserve the specified attributes
--parents use full source file name under DIRECTORY
-R, -r, --recursive copy directories recursively
--reflink[=WHEN] control clone/CoW copies. See below
--remove-destination remove each existing destination file before attempting to open it (contrast with --force)
--sparse=WHEN control creation of sparse files. See below
--strip-trailing-slashes remove any trailing slashes from each SOURCE argument
-s, --symbolic-link make symbolic links instead of copying
-u, --update copy only when the SOURCE file is newer than the destination file or when the destination file is missing
-v, --verbose explain what is being done
-x, --one-file-system stay on this file system
-Z     set SELinux security context of destination file to default type
By default, sparse SOURCE files are detected by a crude heuristic and the corresponding DEST file is made sparse as well.  That is the behavior selected by --sparse=auto.  Specify --sparse=always to create a sparse DEST file whenever the SOURCE file contains a long enough sequence of zero bytes.  Use --sparse=never to inhibit creation of sparse files.
When --reflink[=always] is specified, perform a lightweight copy, where the data blocks are copied only when modified.  If this is not possible the copy fails, or if --reflink=auto is specified, fall back to a standard copy.  Use --reflink=never to ensure a standard copy is performed.
As a special case, cp makes a backup of SOURCE when the force and backup options are given and SOURCE and DEST are the same name for an existing, regular file.
Written by Torbjorn Granlund, David MacKenzie, and Jim Meyering.
Full documentation <https://www.gnu.org/software/coreutils/cp> or available locally via: info '(coreutils) cp invocation'
COMPOSER(1)                       User Commands                      COMPOSER(1)
composer - Composer command line interface
composer command [options] [arguments]
-h, --help Display this help message
-q, --quiet Do not output any message
-V, --version Display this application version
--ansi Force ANSI output
--no-ansi Disable ANSI output
-n, --no-interaction Do not ask any interactive question
--profile Display timing and memory usage information
--no-plugins Whether to disable plugins.
-d, --working-dir=WORKING-DIR If specified, use the given directory as working directory.
-v|vv|vvv, --verbose Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
Available commands: about  Shows the short information about Composer.
archive Creates an archive of this composer package.
browse [home] Opens the package's repository URL or homepage in your browser.
check-platform-reqs Check that platform requirements are satisfied.
clear-cache [clearcache] Clears composer's internal package cache.
config Sets config options.
create-project Creates new project from a package into given directory.
depends [why] Shows which packages cause the given package to be installed.
diagnose Diagnoses the system to identify common errors.
dump-autoload [dumpautoload] Dumps the autoloader.
exec   Executes a vendored binary/script.
global Allows running commands in the global composer dir ($COMPOSER_HOME).
help   Displays help for a command
init   Creates a basic composer.json file in current directory.
install [i] Installs the project dependencies from the composer.lock file if present, or falls back on the composer.json.
licenses Shows information about licenses of dependencies.
list   Lists commands
outdated Shows a list of installed packages that have updates available, including their latest version.
prohibits [why-not] Shows which packages prevent the given package from being installed.
remove Removes a package from the require or require-dev.
require Adds required packages to your composer.json and installs them.
run-script Runs the scripts defined in composer.json.
search Searches for packages.
show   [info] Shows information about packages.
status Shows a list of locally modified packages, for packages installed from source.
suggests Shows package suggestions.
update [u|upgrade] Upgrades your dependencies to the latest version according to composer.json, and updates the composer.lock file.
validate Validates a composer.json and composer.lock.
JOHN(8)                      System Manager's Manual                     JOHN(8)
john - a tool to find weak passwords of your users
john [options] password-files
This manual page documents briefly the john command.  This manual page was written for the Debian GNU/Linux distribution because the original program does not have a manual page.  john, better known as John the Ripper, is a tool to find weak passwords of users in a server. John can use a dictionary or some search pattern as well as a password file to check for passwords. John supports different cracking modes and understands many ciphertext formats, like several DES variants, MD5 and blowfish. It can also be used to extract AFS and Windows NT passwords.
To use John, you just need to supply it a password file and the desired options. If no mode is specified, john will try "single" first, then "wordlist" and finally "incremental".
Once John finds a password, it will be printed to the terminal and saved into a file called ~/.john/john.pot. John will read this file when it restarts so it doesn't try to crack already done passwords.
To see the cracked passwords, use
john -show passwd
Important: do this under the same directory where the password was cracked (when using the cronjob, /var/lib/john), otherwise it won't work.
While cracking, you can press any key for status, or Ctrl+C to abort the session, saving point information to a file ( ~/.john/john.rec by default). By the way, if you press Ctrl+C twice John will abort immediately without saving.  The point information is also saved every 10 minutes (configurable in the configuration file, ~/.john/john.ini or ~/.john/john.conf ) in case of a crash.
To continue an interrupted session, run:
john -restore
Now, you may notice that many accounts have a disabled shell, you can make John ignore these (assume that shell is called /etc/expired ):
john -show -shells:-/etc/expired passwd
You might want to mail all the users who got weak passwords, to tell them to change the passwords. It's not always a good idea though (unfortunately, lots of people seem to ignore such mail, it can be used as a hint for crackers, etc), but anyway, I'll assume you know what you're doing. Get a copy of the 'mailer' script supplied with John, so you won't change anything that's under /usr/sbin ; edit the message it sends, and possibly the mail command inside it (especially if the password file is from a different box than you got John running on). Then run:
./mailer passwd
Anyway, you probably should have a look at /usr/share/doc/john/OPTIONS for a list of all the command line options, and at /usr/share/doc/john/EXAMPLES for more John usage examples with other cracking modes.
All the options recognized by john start with a single dash (`-').  A summary of options is included below.
-external:MODE Enables an external mode, using external functions defined in ~/john.ini's [List.External:MODE] section.
-format:NAME Allows you to override the ciphertext format detection. Currently, valid format names are DES, BSDI, MD5, BF, AFS, LM. You can use this option when cracking or with '-test'. Note that John can't crack password files with different ciphertext formats at the same time.
-groups:[-]GID[,..] Tells John to load users of the specified group(s) only.
-incremental[:MODE] Enables the incremental mode, using the specified ~/john.ini definition (section [Incremental:MODE], or [Incremental:All] by default).
-makechars:FILE Generates a charset file, based on character frequencies from ~/.john/john.pot, for use with the incremental mode. The entire ~/.john/john.pot will be used for the charset file unless you specify some password files. You can also use an external filter() routine with this option.
-restore[:FILE] Continues an interrupted cracking session, reading point information from the specified file (~/.john/john.rec by default).
-rules Enables wordlist rules, that are read from [List.Rules:Wordlist] in /etc/john/john.conf (or the alternative configuration file you might specify on the command line). This option requires the -wordlist option to be passed as well.
-salts:[-]COUNT This feature sometimes allows you to achieve better performance. For example you can crack only some salts using '-salts:2' faster, and then crack the rest using '-salts:-2'. Total cracking time will be about the same, but you will get some passwords cracked earlier.
-savemem:LEVEL You might need this option if you don't have enough memory, or don't want John to affect other processes too much. Level 1 tells John not to waste memory on login names, so you won't see them while cracking. Higher levels have a performance impact: you should probably avoid using them unless John doesn't work or gets into swap otherwise.
-session:FILE Allows you to specify another point information file's name to use for this cracking session. This is useful for running multiple instances of John in parallel, or just to be able to recover an older session later, not always continue the latest one.
-shells:[-]SHELL[,..] This option is useful to load accounts with a valid shell only, or not to load accounts with a bad shell. You can omit the path before a shell name, so '-shells:csh' will match both '/bin/csh' and '/usr/bin/csh', while Â´-shells:/bin/csh' will only match '/bin/csh'.
-show  Shows the cracked passwords in a convenient form. You should also specify the password files. You can use this option while another John is cracking, to see what it did so far.
-single Enables the "single crack" mode, using rules from [List.Rules:Single].
-status[:FILE] Prints status of an interrupted or running session. To get an up to date status information of a detached running session, send that copy of John a SIGHUP before using this option.
-stdin These are used to enable the wordlist mode (reading from stdin).
-stdout[:LENGTH] When used with a cracking mode, except for "single crack", makes John print the words it generates to stdout instead of cracking. While applying wordlist rules, the significant password length is assumed to be LENGTH, or unlimited by default.
-test  Benchmarks all the enabled ciphertext format crackers, and tests them for correct operation at the same time. This option does not need any file passed as argument. Its only function is to benchmark the system john is running on.
-users:[-]LOGIN|UID[,..] Allows you to filter a few accounts for cracking, etc. A dash before the list can be used to invert the check (that is, load all the users that aren't listed).
-wordlist:FILE These are used to enable the wordlist mode, reading words from FILE.
John can work in the following modes:
Wordlist John will simply use a file with a list of words that will be checked against the passwords. See RULES for the format of wordlist files.
Single crack In this mode, john will try to crack the password using the login/GECOS information as passwords.
Incremental This is the most powerful mode. John will try any character combination to resolve the password.  Details about these modes can be found in the MODES file in john's documentation, including how to define your own cracking methods.
/etc/john/john.conf is where you configure how john will behave.
/etc/john/john-mail.msg has the message sent to users when their passwords are successfully cracked.
/etc/john/john-mail.conf is used to configure how john will send messages to users that had their passwords cracked.
mailer(8), unafs(8), unique(8), unshadow(8),
The programs and the configuration files are documented fully by John's documentation, which should be available in /usr/share/doc/john or other location, depending on your system.
This manual page was written by Jordi Mallach <jordi@debian.org> and Jeronimo  Pellegrini <pellegrini@mpcnet.com.br>, for the Debian GNU/Linux system (but may be used by others). John the Ripper was written by Solar Designer <solar@openwall.com>.  The complete list of contributors can be found in the CREDITS file in the documentation directory.
sstat(1)                         Slurm Commands                         sstat(1)
sstat - Display various status information of a running job/step.
sstat [OPTIONS...]
Status information for running jobs invoked with Slurm.
The sstat command displays job status information for your analysis.  The sstat command displays information pertaining to CPU, Task, Node, Resident Set Size (RSS) and Virtual Memory (VM).  You can tailor the output with the use of the --fields= option to specify the fields to be shown.
For the root user, the sstat command displays job status data for any job running on the system.
For the non-root user, the sstat output is limited to the user's jobs.
NOTE:  The sstat command requires that the jobacct_gather plugin be installed and operational.
NOTE:  The sstat command is not supported on Cray ALPS.
-a, --allsteps Print all steps for the given job(s) when no step is specified.
-e, --helpformat Print a list of fields that can be specified with the '--format' option.
-i, --pidformat Predefined format to list the pids running for each job step. (JobId,Nodes,Pids)
-j, --jobs Format is <job(.step)>. Stat this job step or comma-separated list of job steps. This option is required.  The step portion will default to the lowest numbered (not batch, extern, etc) step running if not specified, unless the --allsteps flag is set where not specifying a step will result in all running steps to be displayed.  NOTE: A step id of 'batch' will display the information about the batch step.  NOTE: A step id of 'extern' will display the information about the extern step.  This step is only available when using PrologFlags=contain
-o, --format, --fields Comma separated list of fields.  (use '--helpformat' for a list of available fields).
i.e. format=name%30 will print 30 characters of field name right justified.  A -30 will print 30 characters left justified.
--usage Display a command usage summary.
Job Status Fields The following are the field options:
AveCPU Average (system + user) CPU time of all tasks in job.
AvePages Average number of page faults of all tasks in job.
AveRSS Average resident set size of all tasks in job.
JobID  The number of the job or job step.  It is in the form: job.jobstep.
MaxPages Maximum number of page faults of all tasks in job.
MaxRSS Maximum resident set size of all tasks in job.
MaxVMSizeNode The node on which the maxvsize occurred.
MaxVMSizeTask The task ID where the maxvsize occurred.
MinCPU Minimum (system + user) CPU time of all tasks in job.
NTasks Total number of tasks in a job or step.
ReqCPUFreq Requested CPU frequency for the step, in kHz.
Executing sstat sends a remote procedure call to slurmctld. If enough calls from sstat 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 sstat 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 sstat to the minimum necessary for the information you are trying to gather.
Some sstat options may be set via environment variables. These environment variables, along with their corresponding options, are listed below.  (Note: commandline options will always override these settings)
sstat --format=AveCPU,AvePages,AveRSS,AveVMSize,JobID -j 11 25:02.000  0K         1.37M      5.93M      9.0
sstat -p --format=AveCPU,AvePages,AveRSS,AveVMSize,JobID -j 11 25:02.000|0K|1.37M|5.93M|9.0|
Copyright (C) 2009 Lawrence Livermore National Security.  Produced at Lawrence Livermore National Laboratory (cf, DISCLAIMER). Copyright (C) 2010-2013 SchedMD LLC.
sacct(1)
DOT(1)                       General Commands Manual                      DOT(1)
dot - filter for drawing directed graphs neato - filter for drawing undirected graphs twopi - filter for radial layouts of graphs circo - filter for circular layout of graphs fdp - filter for drawing undirected graphs sfdp - filter for drawing large undirected graphs patchwork - filter for squarified tree maps osage - filter for array-based layouts
dot [options] [files] neato [options] [files] twopi [options] [files] circo [options] [files] fdp [options] [files] sfdp [options] [files] patchwork [options] [files] osage [options] [files]
These are a collection of programs for drawing graphs.  There is actually only one main program; the specific layout algorithms are implemented as plugins. Thus, they largely share all of the same command-line options.
dot draws directed graphs.  It works well on directed acyclic graphs and other graphs that can be drawn as hierarchies or have a natural ``flow.''
neato draws undirected graphs using a ``spring'' model and reducing the related energy (see Kamada and Kawai, Information Processing Letters 31:1, April 1989).
twopi draws graphs using a radial layout (see G. Wills, Symposium on Graph Drawing GD'97, September, 1997).  Basically, one node is chosen as the center and put at the origin.  The remaining nodes are placed on a sequence of concentric circles centered about the origin, each a fixed radial distance from the previous circle.  All nodes distance 1 from the center are placed on the first circle; all nodes distance 1 from a node on the first circle are placed on the second circle; and so forth.
circo draws graphs using a circular layout (see Six and Tollis, GD '99 and ALENEX '99, and Kaufmann and Wiese, GD '02.)  The tool identifies biconnected components and draws the nodes of the component on a circle. The block‐cutpoint tree is then laid out using a recursive radial algorithm. Edge crossings within a circle are minimized by placing as many edges on the circle's perimeter as possible.  In particular, if the component is outerplanar, the component will have a planar layout.  If a node belongs to multiple non‐trivial biconnected components, the layout puts the node in one of them. By default, this is the first non‐trivial component found in the search from the root component.
fdp draws undirected graphs using a ``spring'' model. It relies on a force‐directed approach in the spirit of Fruchterman and Reingold (cf. Software‐Practice & Experience 21(11), 1991, pp. 1129‐1164).
sfdp also draws undirected graphs using the ``spring'' model described above, but it uses a multi-scale approach to produce layouts of large graphs in a reasonably short time.
patchwork draws the graph as a squarified treemap (see M. Bruls et al., ``Squarified treemaps'', Proc. Joint Eurographics and IEEE TCVG Symp. on Visualization, 2000, pp. 33-42). The clusters of the graph are used to specify the tree.
osage draws the graph using its cluster structure. For a given cluster, each of its subclusters is laid out internally.  Then the subclusters, plus any remaining nodes, are repositioned based on the cluster's pack and packmode attributes.
Graphviz uses an extensible plugin mechanism for its output renderers, so to see what output formats your installation of dot supports you can use ``dot -T:'' and check the warning message.  Also, The plugin mechanism supports multiple implementations of the output formats, allowing variations in the renderers and formatters.  To see what variants are available for a particular output format, use, for example: ``dot -Tpng:'' and to force a particular variant, use, for example: ``dot -Tpng:gd''
Traditionally, Graphviz supports the following: -Tdot (Dot format containing layout information), -Txdot (Dot format containing complete layout information), -Tps (PostScript), -Tpdf (PDF), -Tsvg -Tsvgz (Structured Vector Graphics), -Tfig (XFIG graphics), -Tpng (png bitmap graphics), -Tgif (gif bitmap graphics), -Tjpg -Tjpeg (jpeg bitmap graphics), -Tjson (xdot information encoded in JSON), -Timap (imagemap files for httpd servers for each node or edge that has a non‐null href attribute.), -Tcmapx (client‐side imagemap for use in html and xhtml). Additional less common or more special‐purpose output formats can be found at https://www.graphviz.org/doc/info/output.html.
The -P switch can be used to produce a graph of all output variants supported by plugins in the local installation of graphviz.
[strict] (graph|digraph) name { statement‐list } is the top‐level graph. If the graph is strict, then multiple edges are not allowed between the same pairs of nodes.  If it is a directed graph, indicated by digraph, then the edgeop must be "->". If it is an undirected graph then the edgeop must be "--".
Statements may be:
The language accepts both C‐style comments /*C...*/ or //...
A more complete description of the language can be found at https://www.graphviz.org/doc/info/lang.html.
GRAPH, NODE AND EDGE ATTRIBUTES Graphviz uses the name=value attributes, attached to graphs, subgraphs, nodes and edges, to tailor the layout and rendering. We list the more prominent attributes below. The complete list is available at https://www.graphviz.org/doc/info/attrs.html.
Attributes Common to Nodes, Edges, Clusters and Graphs href=url the default url for image map files; in PostScript files, the base URL for all relative URLs, as recognized by Acrobat Distiller 3.0 and up.
URL=url (``URL'' is a synonym for ``href.'')
A colorvalue may be "h,s,v" (hue, saturation, brightness) floating point numbers between 0 and 1, or an X11 color name such as white, black, red, green, blue, yellow, magenta, or cyan, or a "#rrggbb" (red, green, blue, 2 hex characters each) value.  See https://www.graphviz.org/doc/info/attrs.html#k:color and https://www.graphviz.org/doc/info/colors.html for further details.
label=text where text may include escaped newlines \n, \l, or \r for center, left, and right justified lines.  The string '\G' value will be replaced by the graph name.  For node labels, the string '\N' value will be replaced by the node name.  For edges, if the substring '\T' is found in a label, it will be replaced by the name of the tail node; if the substring '\H' is found in a label, it will be replaced by the name of the head node; if the substring '\E' value is found in a label it will be replaced by: tail_node_name->head_node_name or by: tail_node_name--head_node_name for undirected graphs.
Graphviz also supports special HTML-like labels for constructing complex node content. A full‐description of these is given at https://www.graphviz.org/doc/info/shapes.html#html.
If a node has shape=record, the label may contain recursive box lists delimited by { | }.  Port identifiers in labels are set off by angle brackets < >.
Graph Attributes size="x,y" specifies the maximum bounding box of drawing in inches.
layout=engine indicates the preferred layout engine (dot, neato, fdp, etc.) overriding the default from the basename of the command or the -K commandline option.
margin=f sets the page margin (included in the page size).
ordering=out constrains order of out‐edges in a subgraph according to their file sequence.
overlap=mode. This specifies what algorithm should do if any nodes overlap. If mode is false, the program uses the Prism algorithm to adjust the nodes to eliminate overlaps. If mode is scale, the layout is uniformly scaled up, preserving node sizes, until nodes no longer overlap. The latter technique removes overlaps while preserving symmetry and structure, while the former removes overlaps more compactly but destroys symmetries.  If mode is true (the default), no repositioning is done.  Since the dot algorithm always produces a layout with no node overlaps, this attribute is only useful with other layouts.
splines If set to true, edges are drawn as splines.  If set to polyline, edges are drawn as polylines.  If set to ortho, edges are drawn as orthogonal polylines.  In all of these cases, the nodes must not overlap. If splines=false or splines=line, edges are drawn as line segments.  The default is true for dot, and false for all other layouts.
(dot‐specific attributes)
nodesep=f sets the minimum separation between nodes.
ranksep=f sets the minimum separation between ranks.
rankdir=LR|RL|BT requests a left‐to‐right, right‐to‐left, or bottom‐to‐ top, drawing.
rank=same (or min or max) in a subgraph constrains the rank assignment of its nodes.   If a subgraph's name has the prefix cluster, its nodes are drawn in a distinct rectangle of the layout.  Clusters may be nested.
(neato‐specific attributes) mode=val.  Algorithm for minimizing energy in the layout. By default, neato uses stress majorization. If mode=KK, it uses a version of gradient descent.
model=val.  The neato model computes the desired distances between all pairs of vertices. By default, it uses the length of the shortest path. If model is set to circuit, a circuit-resistance model is used.  If model is set to subset, it uses a model whereby the edge length is the number of nodes that are neighbors of exactly one of the edge's vertices.
start=val.  Requests random initial placement and seeds the random number generator.  If val is not an integer, the process ID or current time is used as the seed.
epsilon=n.  Sets the cutoff for the solver.  The default is 0.1.
(twopi‐specific attributes) root=ctr. This specifies the node to be used as the center of the layout. If not specified, twopi will randomly pick one of the nodes that are furthest from a leaf node, where a leaf node is a node of degree 1. If no leaf nodes exists, an arbitrary node is picked as center.
ranksep=val. Specifies the radial distance in inches between the sequence of rings. The default is 0.75.
(circo‐specific attributes) root=nodename. Specifies the name of a node occurring in the root block. If the graph is disconnected, the root node attribute can be used to specify additional root blocks.
mindist=value. Sets the minimum separation between all nodes. If not specified then circo uses a default value of 1.0.
(fdp‐specific attributes) K=val. Sets the default ideal node separation in the layout.
maxiter=val. Sets the maximum number of iterations used to layout the graph.
start=val. Adjusts the random initial placement of nodes with no specified position.  If val is an integer, it is used as the seed for the random number generator.  If val is not an integer, a random system‐ generated integer, such as the process ID or current time, is used as the seed.
Node Attributes height=d or width=d sets minimum height or width.  Adding fixedsize=true forces these to be the actual size (text labels are ignored).
shape=builtin_polygon record epsf builtin_polygon can be such values as plaintext, ellipse, oval, circle, egg, triangle, box, diamond, trapezium, parallelogram, house, hexagon, octagon, note, tab, box3d, or component,, among others.  (Polygons are defined or modified by the following node attributes: regular, peripheries, sides, orientation, distortion and skew.)  epsf uses the node's shapefile attribute as the path name of an external EPSF file to be automatically loaded for the node shape.
See https://www.graphviz.org/doc/info/shapes.html for a complete description of node shapes.
style=filled solid dashed dotted bold invis
xlabel="text" specifies a label that will be place near, but outside, of a node. The normal label string is placed within the node shape.
tooltip="text" is a tooltip string for client‐side imagemaps and SVG, effective when nodes have a URL.  The tooltip string defaults to be the same as the label string, but this attribute permits nodes without labels to still have tooltips thus permitting denser graphs.  The substrings '\N' and '\G' are substituted in the same manner as for the node label attribute.  Additionally the substring '\L' is substituted with the node label string.
(circo‐specific attributes) root=true/false. This specifies that the block containing the given node be treated as the root of the spanning tree in the layout.
(neato‐ and fdp‐specific attributes) pin=val. If val is true, the node will remain at its initial position.
Edge Attributes weight=val where val is the cost of the edge.  For dot, weights must be non-negative integers.  Values greater than 1 tend to shorten the edge; weight 0 flat edges are ignored for ordering nodes.  In twopi, a weight of 0 will cause the edge to be ignored in constructing the underlying spanning tree. For neato and fdp, a heavier weight will put more emphasis on the algorithm achieving an edge length closer to that specified by the edge's len attribute.
target="text" is a target string for client‐side imagemaps and SVG, effective when edges have a URL.  If the target string is empty, the default, then no target attribute is included in the output.  The substrings '\T', '\H', '\E' and '\G' are substituted in the same manner as for the edge label attribute.  Additionally the substring '\L' is substituted with the edge label string.
tooltip="text" is a tooltip string for client‐side imagemaps effective when edges have a URL.  The tooltip string defaults to be the same as the edge label string.  The substrings '\T', '\H', '\E' and '\G' are substituted in the same manner as for the edge label attribute. Additionally the substring '\L' is substituted with the edge label string.
arrowhead,arrowtail=none, normal, inv, dot, odot, invdot, invodot, tee, empty, invempty, open, halfopen, diamond, odiamond, box, obox, crow. Specifies the shape of the glyph occurring where the edge touches the head or tail node, respectively. Note that this only specifies the shape. The dir attribute determines whether or not the glyph is drawn.
arrowsize=val specifies a multiplicative scale factor for the size of the arrowhead.  inv_length=6,inv_width=7,dot_radius=2)
headlabel,taillabel=text for labels appearing near the head and tail nodes of an edge.  labelfontcolor, labelfontname, labelfontsize for head and tail labels.  The substrings '\T', '\H', '\E' and '\G' are substituted in the same manner as for the edge label attribute. Additionally the substring '\L' is substituted with the edge label string.
headURL="url" (headURL is a synonym for headhref.)
tailURL="url" (tailURL is a synonym for tailhref.)
labeldistance and labelangle (in degrees CCW) specify the placement of head and tail labels.
(dot‐specific attributes) constraint=false causes an edge to be ignored for rank assignment.
minlen=n where n is an integer factor that applies to the edge length (ranks for normal edges, or minimum node separation for flat edges).
xlabel="text" Edge labels in dot are treated as special types of nodes, with space allocated for them during node layout. This can sometimes deform the edge routing. If an xlabel is used instead, the label is placed after all nodes and edges have been positioned. In turn, this may mean that there is some overlap among the labels.
(neato and fdp‐specific attributes) len=f sets the optimal length of an edge.  The default is 1.0.
COMMAND‐LINE OPTIONS -G sets a default graph attribute. -N sets a default node attribute. -E sets a default edge attribute.  Example: -Gsize="7,8" -Nshape=box -Efontsize=8
-n[1|2] (no‐op) If set, neato assumes nodes have already been positioned and all nodes have a pos attribute giving the positions.  It then performs an optional adjustment to remove node‐node overlap, depending on the value of the overlap attribute, computes the edge layouts, depending on the value of the splines attribute, and emits the graph in the appropriate format.  If num is supplied, the following actions occur: num = 1 Equivalent to -n. num > 1 Use node positions as specified, with no adjustment to remove node‐node overlaps, and use any edge layouts already specified by the pos attribute.  neato computes an edge layout for any edge that does not have a pos attribute.  As usual, edge layout is guided by the splines attribute.
-Klayout override the default layout engine implied by the command name.
-P generate a graph of the currently available plugins.
-c configure plugins.
-m memory test (observe no growth with top, kill when done).
-qlevel set level of message suppression. The default is 1.
-sfscale scale input by fscale, the default is 72.
-y invert y coordinate in output.
A complete description of the available command‐line options can be found at https://www.graphviz.org/doc/info/command.html.
digraph test123 { a -> b -> c; a -> {x y}; b [shape=box]; c [label="hello\nworld",color=blue,fontsize=24, fontname="Palatino-Italic",fontcolor=red,style=filled]; a -> z [label="hi", weight=100]; x -> z [label="multi-line\nlabel"]; edge [style=dashed,color=red]; b -> x; {rank=same; b x} }
graph test123 { a -- b -- c; a -- {x y}; x -- c [w=10.0]; x -- y [w=5.0,len=3]; }
Edge splines can overlap unintentionally.
Flat edge labels are slightly broken.  Intercluster edge labels are totally broken.
Because unconstrained optimization is employed, node boxes can possibly overlap or touch unrelated edges.  All existing spring embedders seem to have this limitation.
Apparently reasonable attempts to pin nodes or adjust edge lengths and weights can cause instability.
Stephen C. North <north@research.att.com> Emden R. Gansner <erg@graphviz.org> John C. Ellson <ellson@research.att.com> Yifan Hu <yifanhu@yahoo.com>
The bitmap driver (PNG, GIF etc) is by Thomas Boutell, <http://www.boutell.com/gd>
The Truetype font renderer is from the Freetype Project (David Turner, Robert Wilhelm, and Werner Lemberg) (who can be contacted at freetype-devel@lists.lrz-muenchen.de).
dotty(1) tcldot(n) xcolors(1) libcgraph(3)
E. R. Gansner, S. C. North,  K. P. Vo, "DAG ‐ A Program to Draw Directed Graphs", Software ‐ Practice and Experience 17(1), 1988, pp. 1047‐1062. E. R. Gansner, E. Koutsofios, S. C. North,  K. P. Vo, "A Technique for Drawing Directed Graphs," IEEE Trans. on Soft. Eng. 19(3), 1993, pp. 214‐230. S. North and E. Koutsofios, "Applications of graph visualization", Graphics Interface 94, pp. 234‐245. E. R. Gansner and E. Koutsofios and S. C. North, "Drawing Graphs with dot," Available at https://www.graphviz.org/pdf/dotguide.pdf. S. C. North, "NEATO User's Manual".  Available https://www.graphviz.org/pdf/neatoguide.pdf. E. R. Gansner and Y. Hu, "Efficient, Proximity-Preserving Node Overlap Removal", J. Graph Algorithms Appl., 14(1) pp. 53‐74, 2010.
DIFFSTAT(1)                  General Commands Manual                 DIFFSTAT(1)
diffstat - make histogram from diff-output
diffstat [options] [file-specifications]
This program reads the output of diff and displays a histogram of the insertions, deletions, and modifications per-file.  Diffstat is a program that is useful for reviewing large, complex patch files.  It reads from one or more input files which contain output from diff, producing a histogram of the total lines changed for each file referenced.
If the input filename ends with “.bz2”, “.gz”, “.lzma”, “.xz”, “.z” or “.Z”, diffstat will read the uncompressed data via a pipe from the corresponding program.  It also can infer the compression type from files piped via the standard input.
Diffstat recognizes the most popular types of output from diff:
unified preferred by the patch utility.
context best for readability, but not very compact.
default not good for much, but simple to generate.
Diffstat detects the lines that are output by diff to tell which files are compared, and then counts the markers in the first column that denote the type of change (insertion, deletion or modification).  These are shown in the histogram as "+", "-" and "!" characters.
If no filename is given on the command line, diffstat reads the differences from the standard input.
-b     ignore lines matching "Binary files XXX and YYY differ" in the diff
-c     prefix each line of output with "#", making it a comment-line for shell scripts.
-C     add SGR color escape sequences to highlight the histogram.
-D destination specify a directory containing files which can be referred to as the result of applying the differences.  diffstat will count the lines in the corresponding files (after adjusting the names by the -p option) to obtain the total number of lines in each file.
The remainder, after subtracting modified and deleted lines, is shown as "unchanged lines".
-d     The debug prints a lot of information.  It is normally compiled- in, but can be suppressed.
-e file redirect standard error to file.
-E     strip out ANSI escape sequences on each line before parsing the differences.  This allows diffstat to be used with colordiff.
-f format specify the format of the histogram.
0  for concise, which shows only the value and a single histogram code for each of insert (+), delete (-) or modify (!)
1  for normal output,
2  to fill in the histogram with dots,
4  to print each value with the histogram.
Any nonzero value gives a histogram.  The dots and individual values can be combined, e.g., -f6 gives both.
-h     prints the usage message and exits.
-k     suppress the merging of filenames in the report.
-K     attempt to improve the annotation of "only" files by looking for a match in the resulting set of files and inferring whether the file was added or removed.
This does not currently work in combination with -R because diffstat maintains only the resulting set of files.
-l     lists only the filenames.  No histogram is generated.
-m     merge insert/delete counts from each "chunk" of the patch file to approximate a count of the modified lines.
-n number specify the minimum width used for filenames.  If you do not specify this, diffstat uses the length of the longest filename, after stripping common prefixes.
-N number specify the maximum width used for filenames.  Names longer than this limit are truncated on the left.  If you do not specify this, diffstat next checks the -n option.
-o file redirect standard output to file.
-p number override the logic that strips common pathnames, simulating the patch "-p" option.
If you do not give a -p option, diffstat examines the differences and strips the common prefix from the pathnames.  This is not what patch does.
-q     suppress the "0 files changed" message for empty diffs.
-r  code provides optional rounding of the data shown in histogram, rather than truncating with error adjustments.
0  is the default.  No rounding is performed, but accumulated errors are added to following columns.
1  rounds the data
2  rounds the data and adjusts the histogram to ensure that it displays something if there are any differences even if those would normally be rounded to zero.
-R     Assume patch was created with old and new files swapped.
-s     show only the summary line, e.g., number of insertions and deletions.
-S source this is like the -D option, but specifies a location where the original files (before applying differences) can be found.
-t     overrides the histogram, generates output of comma separated values for the number of changed lines found in the differences for each file: inserted, deleted and modified.
If -S or -D options are given, the number of unchanged lines precedes the number of changes.
-T     prints the numbers that the -t option would show, between the pathname and histogram.
The width of the number of changes is determined by the largest value (but at least 3).  The width given in the -w option is separate from the width of these numbers.
-u     suppress the sorting of filenames in the report.
-v     show progress, e.g., if the output is redirected to a file, write progress messages to the standard error.
-V     prints the current version number and exits.
-w number specify the maximum width of the histogram.  The histogram will never be shorter than 10 columns, just in case the filenames get too large.
The default is 80 columns, unless the output is to a terminal.  In that case, the default width is the terminal's width.
Diffstat runs in a POSIX environment.
You can override the compiled-in paths of programs used for decompressing input files by setting environment variables corresponding to their name:
DIFFSTAT_BZCAT_PATH DIFFSTAT_BZIP2_PATH DIFFSTAT_COMPRESS_PATH DIFFSTAT_GZIP_PATH DIFFSTAT_LZCAT_PATH DIFFSTAT_PCAT_PATH DIFFSTAT_UNCOMPRESS_PATH DIFFSTAT_XZ_PATH DIFFSTAT_ZCAT_PATH
However, diffstat assumes that the resulting program uses the same command-line options, e.g., "-c" to decompress to the standard output.
Diffstat is a single binary module, which uses no auxiliary files.
Diffstat makes a lot of assumptions about the format of diff's output.
There is no way to obtain a filename from the standard diff between two files with no options.  Context diffs work, as well as unified diffs.
There's no easy way to determine the degree of overlap between the "before" and "after" displays of modified lines.  diffstat simply counts the number of inserted and deleted lines to approximate modified lines for the -m option.
diff(1), patch(1).
Thomas Dickey <dickey@invisible-island.net>.
HAXELIB(1)                   General Commands Manual                  HAXELIB(1)
haxelib - Haxe Library Manager
haxelib [command] [options...]
haxelib is a command-line tool to manage both the global repository and your local repository of Haxe libraries and projects.
install library [version] Install a given library from the global repository.  Once a project is installed, you can simply use haxe -lib library ... to be able to use it from your application.  By default, this is the current version of the project that is used.  If you want to use a specific version of the project, use haxe -lib library:version ...
list   List all installed libraries and their versions.
upgrade Upgrade all installed libraries to their latest version.
remove library [version] Remove a given library.
set library [version] Set the current version for a library. The version must be already installed.
search word List global libraries matching a word.
info library List information on a given library.
user library List information on a given user on the global repository.
register name Register a new user in the global repository.
submit library Submit or update a library to the global repository.
setup  Set the haxelib repository path.
config library Print the local repository path.
path libraries... List the path to the given libraries.
run library [arguments...] Run the specified library with arguments if it provides a run script. Be careful about trusting libraries this way since the script can damage your system.
test library install the specified library locally.
dev    Set the development directory for a given project.
Haxe is currently maintained by the Haxe Foundation.  It was originally written by Nicolas Cannasse for Motion-Twin.
haxe(1).
https://haxe.org/.
CKSUM(1)                          User Commands                         CKSUM(1)
cksum - compute and verify file checksums
cksum [OPTION]... [FILE]...
Print or verify checksums.  By default use the 32 bit CRC algorithm.
-a, --algorithm=TYPE select the digest type to use.  See DIGEST below.
-l, --length=BITS digest length in bits; must not exceed the max for the blake2 algorithm and must be a multiple of 8
--tag  create a BSD-style checksum (the default)
--untagged create a reversed style checksum, without digest type
--debug indicate which implementation used
DIGEST determines the digest algorithm and default output format: sysv   (equivalent to sum -s)
bsd    (equivalent to sum -r)
crc    (equivalent to cksum)
md5    (equivalent to md5sum)
sha1   (equivalent to sha1sum)
sha224 (equivalent to sha224sum)
sha256 (equivalent to sha256sum)
sha384 (equivalent to sha384sum)
sha512 (equivalent to sha512sum)
blake2b (equivalent to b2sum)
sm3    (only available through cksum)
When checking, the input should be a former output of this program, or equivalent standalone program.
Written by Padraig Brady and Q. Frank Xia.
Full documentation <https://www.gnu.org/software/coreutils/cksum> or available locally via: info '(coreutils) cksum invocation'
TCPKILL(8)                   System Manager's Manual                  TCPKILL(8)
tcpkill - kill TCP connections on a LAN
tcpkill [-i interface] [-1...9] expression
tcpkill kills specified in-progress TCP connections (useful for libnids- based applications which require a full TCP 3-whs for TCB creation).
-i interface Specify the interface to listen on.
-1...9 Specify the degree of brute force to use in killing a connection. Fast connections may require a higher number in order to land a RST in the moving receive window. Default is 3.
expression Specify a tcpdump(8) filter expression to select the connections to kill.
dsniff(8), tcpnice(8)
Dug Song <dugsong@monkey.org>
man(08 August 2015)                                          man(08 August 2015)
nudoku - ncurses based sudoku game
nudoku [OPTIONS]
nudoku is a ncurses based sudoku game. Perfect to relax a little or just waste some time when you are on the console.
Keybindings For navigation use vi-keybindings (hjkl) or arrow keys.  Pressing a number will put it in a field. Pressing delete, backspace or x will delete it.
Some keys need to be typed uppercase to prevent pressing them accidentally.
Q Quit nudoku.
r Redraw screen. In case you resized your terminal this will come handy.
c Gives feedback whether your solution is right. If you think you finished your sudoku press this key to make sure it is. You can also use this during the game to check if you have made any mistakes.
N Create a new puzzle.
S Let the computer solve the puzzle.