neulab/tldr huggingface dataset:
Some capabilities are only put into the $TERMCAP variable of the virtual terminal if they can be efficiently implemented by the physical terminal. For instance, `dl' (delete line) is only put into the $TERMCAP variable if the terminal supports either delete line itself or scrolling regions. Note that this may provoke confusion, when the session is reattached on a different terminal, as the value of $TERMCAP cannot be modified by parent processes.
The "alternate screen" capability is not enabled by default.  Set the altscreen .screenrc command to enable it.
The following is a list of control sequences recognized by screen.  "(V)" and "(A)" indicate VT100-specific and ANSI- or ISO-specific functions, respectively.
ESC E                      Next Line
ESC D                      Index
ESC M                      Reverse Index
ESC H                      Horizontal Tab Set
ESC Z                      Send VT100 Identification String
ESC 7                 (V)  Save Cursor and Attributes
ESC 8                 (V)  Restore Cursor and Attributes
ESC [s                (A)  Save Cursor and Attributes
ESC [u                (A)  Restore Cursor and Attributes
ESC c                      Reset to Initial State
ESC g                      Visual Bell
ESC Pn p                   Cursor Visibility (97801)
Pn = 6                     Invisible
Pn = 7                     Visible
ESC =                 (V)  Application Keypad Mode
ESC >                 (V)  Numeric Keypad Mode
ESC # 8               (V)  Fill Screen with E's
ESC \                 (A)  String Terminator
ESC ^                 (A)  Privacy Message String (Message Line)
ESC !                      Global Message String (Message Line)
ESC k                      A.k.a. Definition String
ESC P                 (A)  Device Control String.  Outputs a string directly to the host terminal without interpretation.
ESC _                 (A)  Application Program Command (Hardstatus)
ESC ] 0 ; string ^G   (A)  Operating System Command (Hardstatus, xterm title hack)
ESC ] 83 ; cmd ^G     (A)  Execute screen command. This only works if multi-user support is compiled into screen. The pseudo-user ":window:" is used to check the access control list. Use "addacl :window: -rwx #?" to create a user with no rights and allow only the needed commands.
Control-N             (A)  Lock Shift G1 (SO)
Control-O             (A)  Lock Shift G0 (SI)
ESC n                 (A)  Lock Shift G2
ESC o                 (A)  Lock Shift G3
ESC N                 (A)  Single Shift G2
ESC O                 (A)  Single Shift G3
ESC ( Pcs             (A)  Designate character set as G0
ESC ) Pcs             (A)  Designate character set as G1
ESC * Pcs             (A)  Designate character set as G2
ESC + Pcs             (A)  Designate character set as G3
ESC [ Pn ; Pn H            Direct Cursor Addressing
ESC [ Pn ; Pn f            same as above
ESC [ Pn J                 Erase in Display
Pn = None or 0             From Cursor to End of Screen
Pn = 1                     From Beginning of Screen to Cursor
Pn = 2                     Entire Screen
ESC [ Pn K                 Erase in Line
Pn = None or 0             From Cursor to End of Line
Pn = 1                     From Beginning of Line to Cursor
Pn = 2                     Entire Line
ESC [ Pn X                 Erase character
ESC [ Pn A                 Cursor Up
ESC [ Pn B                 Cursor Down
ESC [ Pn C                 Cursor Right
ESC [ Pn D                 Cursor Left
ESC [ Pn E                 Cursor next line
ESC [ Pn F                 Cursor previous line
ESC [ Pn G                 Cursor horizontal position
ESC [ Pn `                 same as above
ESC [ Pn d                 Cursor vertical position
ESC [ Ps ;...; Ps m        Select Graphic Rendition
Ps = None or 0             Default Rendition
Ps = 1                     Bold
Ps = 2                (A)  Faint
Ps = 3                (A)  Standout Mode (ANSI: Italicized)
Ps = 4                     Underlined
Ps = 5                     Blinking
Ps = 7                     Negative Image
Ps = 22               (A)  Normal Intensity
Ps = 23               (A)  Standout Mode off (ANSI: Italicized off)
Ps = 24               (A)  Not Underlined
Ps = 25               (A)  Not Blinking
Ps = 27               (A)  Positive Image
Ps = 30               (A)  Foreground Black
Ps = 31               (A)  Foreground Red
Ps = 32               (A)  Foreground Green
Ps = 33               (A)  Foreground Yellow
Ps = 34               (A)  Foreground Blue
Ps = 35               (A)  Foreground Magenta
Ps = 36               (A)  Foreground Cyan
Ps = 37               (A)  Foreground White
Ps = 39               (A)  Foreground Default
Ps = 40               (A)  Background Black
Ps = ...
Ps = 49               (A)  Background Default
ESC [ Pn g                 Tab Clear
Pn = None or 0             Clear Tab at Current Position
Pn = 3                     Clear All Tabs
ESC [ Pn ; Pn r       (V)  Set Scrolling Region
ESC [ Pn I            (A)  Horizontal Tab
ESC [ Pn Z            (A)  Backward Tab
ESC [ Pn L            (A)  Insert Line
ESC [ Pn M            (A)  Delete Line
ESC [ Pn @            (A)  Insert Character
ESC [ Pn P            (A)  Delete Character
ESC [ Pn S                 Scroll Scrolling Region Up
ESC [ Pn T                 Scroll Scrolling Region Down
ESC [ Pn ^                 same as above
ESC [ Ps ;...; Ps h        Set Mode
ESC [ Ps ;...; Ps l        Reset Mode
Ps = 4                (A)  Insert Mode
Ps = 20               (A)  Automatic Linefeed Mode
Ps = 34                    Normal Cursor Visibility
Ps = ?1               (V)  Application Cursor Keys
Ps = ?3               (V)  Change Terminal Width to 132 columns
Ps = ?5               (V)  Reverse Video
Ps = ?6               (V)  Origin Mode
Ps = ?7               (V)  Wrap Mode
Ps = ?9                    X10 mouse tracking
Ps = ?25              (V)  Visible Cursor
Ps = ?47                   Alternate Screen (old xterm code)
Ps = ?1000            (V)  VT200 mouse tracking
Ps = ?1047                 Alternate Screen (new xterm code)
Ps = ?1049                 Alternate Screen (new xterm code)
ESC [ 5 i             (A)  Start relay to printer (ANSI Media Copy)
ESC [ 4 i             (A)  Stop relay to printer (ANSI Media Copy)
ESC [ 8 ; Ph ; Pw t        Resize the window to `Ph' lines and `Pw' columns (SunView special)
ESC [ c                    Send VT100 Identification String
ESC [ x                    Send Terminal Parameter Report
ESC [ > c                  Send VT220 Secondary Device Attributes String
ESC [ 6 n                  Send Cursor Position Report
In order to do a full VT100 emulation screen has to detect that a sequence of characters in the input stream was generated by a keypress on the user's keyboard and insert the VT100 style escape sequence. Screen has a very flexible way of doing this by making it possible to map arbitrary commands on arbitrary sequences of characters. For standard VT100 emulation the command will always insert a string in the input buffer of the window (see also command stuff in the command table). Because the sequences generated by a keypress can change after a reattach from a different terminal type, it is possible to bind commands to the termcap name of the keys.  Screen will insert the correct binding after each reattach. See the bindkey command for further details on the syntax and examples.
Here is the table of the default key bindings. The fourth is what command is executed if the keyboard is switched into application mode.
The following table describes all terminal capabilities that are recognized by screen and are not in the termcap(5) manual.  You can place these capabilities in your termcap entries (in `/etc/termcap') or use them with the commands `termcap', `terminfo' and `termcapinfo' in your screenrc files. It is often not possible to place these capabilities in the terminfo database.
LP   (bool)  Terminal has VT100 style margins (`magic margins'). Note that this capability is obsolete because screen uses the standard 'xn' instead.
Z0   (str)   Change width to 132 columns.
Z1   (str)   Change width to 80 columns.
WS   (str)   Resize display. This capability has the desired width and height as arguments. SunView(tm) example: '\E[8;%d;%dt'.
NF   (bool)  Terminal doesn't need flow control. Send ^S and ^Q direct to the application. Same as 'flow off'. The opposite of this capability is 'nx'.
G0   (bool)  Terminal can deal with ISO 2022 font selection sequences.
S0   (str)   Switch charset 'G0' to the specified charset. Default is '\E(%.'.
E0   (str)   Switch charset 'G0' back to standard charset. Default is '\E(B'.
C0   (str)   Use the string as a conversion table for font '0'. See the 'ac' capability for more details.
CS   (str)   Switch cursor-keys to application mode.
CE   (str)   Switch cursor-keys back to normal mode.
AN   (bool)  Turn on autonuke. See the 'autonuke' command for more details.
OL   (num)   Set the output buffer limit. See the 'obuflimit' command for more details.
KJ   (str)   Set the encoding of the terminal. See the 'encoding' command for valid encodings.
AF   (str)   Change character foreground color in an ANSI conform way. This capability will almost always be set to '\E[3%dm' ('\E[3%p1%dm' on terminfo machines).
AB   (str)   Same as 'AF', but change background color.
AX   (bool)  Does understand ANSI set default fg/bg color (\E[39m / \E[49m).
XC   (str)   Describe a translation of characters to strings depending on the current font. More details follow in the next section.
XT   (bool)  Terminal understands special xterm sequences (OSC, mouse tracking).
C8   (bool)  Terminal needs bold to display high-intensity colors (e.g. Eterm).
TF   (bool)  Add missing capabilities to the termcap/info entry. (Set by default).
Screen has a powerful mechanism to translate characters to arbitrary strings depending on the current font and terminal type.  Use this feature if you want to work with a common standard character set (say ISO8851-latin1) even on terminals that scatter the more unusual characters over several national language font pages.
Syntax: XC=<charset-mapping>{,,<charset-mapping>} <charset-mapping> := <designator><template>{,<mapping>} <mapping> := <char-to-be-mapped><template-arg>
The things in braces may be repeated any number of times.
A <charset-mapping> tells screen how to map characters in font <designator> ('B': Ascii, 'A': UK, 'K': German, etc.)  to strings. Every <mapping> describes to what string a single character will be translated. A template mechanism is used, as most of the time the codes have a lot in common (for example strings to switch to and from another charset). Each occurrence of '%' in <template> gets substituted with the <template-arg> specified together with the character. If your strings are not similar at all, then use '%' as a template and place the full string in <template- arg>. A quoting mechanism was added to make it possible to use a real '%'. The '\' character quotes the special characters '\', '%', and ','.
termcap hp700 'XC=B\E(K%\E(B,\304[,\326\\\\,\334]'
This tells screen how to translate ISOlatin1 (charset 'B') upper case umlaut characters on a hp700 terminal that has a German charset. '\304' gets translated to '\E(K[\E(B' and so on.  Note that this line gets parsed *three* times before the internal lookup table is built, therefore a lot of quoting is needed to create a single '\'.
Another extension was added to allow more emulation: If a mapping translates the unquoted '%' char, it will be sent to the terminal whenever screen switches to the corresponding <designator>. In this special case the template is assumed to be just '%' because the charset switch sequence and the character mappings normally haven't much in common.
This example shows one use of the extension:
termcap xterm 'XC=K%,%\E(B,[\304,\\\\\326,]\334'
Here, a part of the German ('K') charset is emulated on an xterm.  If screen has to change to the 'K' charset, '\E(B' will be sent to the terminal, i.e. the ASCII charset is used instead. The template is just '%', so the mapping is straightforward: '[' to '\304', '\' to '\326', and ']' to '\334'.
COLUMNS        Number of columns on the terminal (overrides termcap entry). HOME           Directory in which to look for .screenrc. LINES          Number of lines on the terminal (overrides termcap entry). LOCKPRG        Screen lock program. NETHACKOPTIONS Turns on nethack option. PATH           Used for locating programs to run. SCREENCAP      For customizing a terminal's TERMCAP value. SCREENDIR      Alternate socket directory. SCREENRC       Alternate user screenrc file. SHELL          Default shell program for opening windows (default "/bin/sh").  See also "shell" .screenrc command. STY            Alternate socket name. SYSSCREENRC    Alternate system screenrc file. TERM           Terminal name. TERMCAP        Terminal description. WINDOW         Window number of a window (at creation time).
.../screen-4.?.??/etc/screenrc .../screen-4.?.??/etc/etcscreenrc Examples in the screen distribution package for private and global initialization files. $SYSSCREENRC /usr/local/etc/screenrc           screen initialization commands $SCREENRC $HOME/.screenrc                   Read in after /usr/local/etc/screenrc $SCREENDIR/S-<login> /local/screens/S-<login>          Socket directories (default) /usr/tmp/screens/S-<login>        Alternate socket directories. <socket directory>/.termcap       Written by the "termcap" output function /usr/tmp/screens/screen-exchange  or /tmp/screen-exchange              screen `interprocess communication buffer' hardcopy.[0-9]                    Screen images created by the hardcopy function screenlog.[0-9]                   Output log files created by the log function /usr/lib/terminfo/?/*             or /etc/termcap                      Terminal capability databases /etc/utmp                         Login records $LOCKPRG                          Program that locks a terminal.
termcap(5), utmp(5), vi(1), captoinfo(1), tic(1)
Originally created by Oliver Laumann. For a long time maintained and developed by Juergen Weigert, Michael Schroeder, Micah Cowan and Sadrul Habib Chowdhury. Since 2015 maintained and developed by Amadeusz Slawinski <amade@asmblr.net> and Alexander Naumov <alexander_naumov@opensuse.org>.
Copyright (c) 2018-2020 Alexander Naumov <alexander_naumov@opensuse.org> Amadeusz Slawinski <amade@asmblr.net> Copyright (c) 2015-2017 Juergen Weigert <jnweiger@immd4.informatik.uni-erlangen.de> Alexander Naumov <alexander_naumov@opensuse.org> Amadeusz Slawinski <amade@asmblr.net> Copyright (c) 2010-2015 Juergen Weigert <jnweiger@immd4.informatik.uni-erlangen.de> Sadrul Habib Chowdhury <sadrul@users.sourceforge.net> Copyright (c) 2008, 2009 Juergen Weigert <jnweiger@immd4.informatik.uni-erlangen.de> Michael Schroeder <mlschroe@immd4.informatik.uni-erlangen.de> Micah Cowan <micah@cowan.name> Sadrul Habib Chowdhury <sadrul@users.sourceforge.net> Copyright (C) 1993-2003 Juergen Weigert <jnweiger@immd4.informatik.uni-erlangen.de> Michael Schroeder <mlschroe@immd4.informatik.uni-erlangen.de> Copyright (C) 1987 Oliver Laumann This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (see the file COPYING); if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Maarten ter Huurne <maarten@treewalker.org>, Jussi Kukkonen <jussi.kukkonen@intel.com>, Eric S. Raymond <esr@thyrsus.com>, Thomas Renninger <treen@suse.com>, Axel Beckert <abe@deuxchevaux.org>, Ken Beal <kbeal@amber.ssd.csd.harris.com>, Rudolf Koenig <rfkoenig@immd4.informatik.uni-erlangen.de>, Toerless Eckert <eckert@immd4.informatik.uni-erlangen.de>, Wayne Davison <davison@borland.com>, Patrick Wolfe <pat@kai.com, kailand!pat>, Bart Schaefer <schaefer@cse.ogi.edu>, Nathan Glasser <nathan@brokaw.lcs.mit.edu>, Larry W. Virden <lvirden@cas.org>, Howard Chu <hyc@hanauma.jpl.nasa.gov>, Tim MacKenzie <tym@dibbler.cs.monash.edu.au>, Markku Jarvinen <mta@{cc,cs,ee}.tut.fi>, Marc Boucher <marc@CAM.ORG>, Doug Siebert <dsiebert@isca.uiowa.edu>, Ken Stillson <stillson@tsfsrv.mitre.org>, Ian Frechett <frechett@spot.Colorado.EDU>, Brian Koehmstedt <bpk@gnu.ai.mit.edu>, Don Smith <djs6015@ultb.isc.rit.edu>, Frank van der Linden <vdlinden@fwi.uva.nl>, Martin Schweikert <schweik@cpp.ob.open.de>, David Vrona <dave@sashimi.lcu.com>, E. Tye McQueen <tye%spillman.UUCP@uunet.uu.net>, Matthew Green <mrg@eterna.com.au>, Christopher Williams <cgw@pobox.com>, Matt Mosley <mattm@access.digex.net>, Gregory Neil Shapiro <gshapiro@wpi.WPI.EDU>, Johannes Zellner <johannes@zellner.org>, Pablo Averbuj <pablo@averbuj.com>.
The latest official release of screen available via anonymous ftp from ftp.gnu.org/gnu/screen/ or any other GNU distribution site. The home site of screen is savannah.gnu.org/projects/screen/. If you want to help, send a note to screen-devel@gnu.org.
•  `dm' (delete mode) and `xs' are not handled correctly (they are ignored). `xn' is treated as a magic-margin indicator.
•  Screen has no clue about double-high or double-wide characters.  But this is the only area where vttest is allowed to fail.
•  It is not possible to change the environment variable $TERMCAP when reattaching under a different terminal type.
•  The support of terminfo based systems is very limited. Adding extra capabilities to $TERMCAP may not have any effects.
•  Screen does not make use of hardware tabs.
•  Screen must be installed as set-uid with owner root on most systems in order to be able to correctly change the owner of the tty device file for each window.  Special permission may also be required to write the file "/etc/utmp".
•  Entries in "/etc/utmp" are not removed when screen is killed with SIGKILL.  This will cause some programs (like "w" or "rwho") to advertise that a user is logged on who really isn't.
•  Screen may give a strange warning when your tty has no utmp entry.
•  When the modem line was hung up, screen may not automatically detach (or quit) unless the device driver is configured to send a HANGUP signal.  To detach a screen session use the -D or -d command line option.
•  If a password is set, the command line options -d and -D still detach a session without asking.
•  Both "breaktype" and "defbreaktype" change the break generating method used by all terminal devices. The first should change a window specific setting, where the latter should change only the default for new windows.
•  When attaching to a multiuser session, the user's .screenrc file is not sourced. Each user's personal settings have to be included in the .screenrc file from which the session is booted, or have to be changed manually.
•  A weird imagination is most useful to gain full advantage of all the features.
•  Send bug-reports, fixes, enhancements, t-shirts, money, beer & pizza to screen-devel@gnu.org.
SUPERVISORCTL(1)                   Supervisor                   SUPERVISORCTL(1)
supervisorctl - supervisorctl Documentation
Supervisor is a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems.
It shares some of the same goals of programs like launchd, daemontools, and runit. Unlike some of these programs, it is not meant to be run as a substitute for init as "process id 1". Instead it is meant to be used to control processes related to a project or a customer, and is meant to start like any other program at boot time.
Supervisor Components supervisorctl The command-line client piece of the supervisor is named supervisorctl.  It provides a shell-like interface to the features provided by supervisord.  From supervisorctl, a user can connect to different supervisord processes, get status on the subprocesses controlled by, stop and start subprocesses of, and get lists of running processes of a supervisord.
The command-line client talks to the server across a UNIX domain socket or an internet (TCP) socket.  The server can assert that the user of a client should present authentication credentials before it allows him to perform commands.  The client process typically uses the same configuration file as the server but any configuration file with a [supervisorctl] section in it will work.
Running Supervisor This section makes reference to a BINDIR when explaining how to run the supervisord and supervisorctl commands.  This is the "bindir" directory that your Python installation has been configured with.  For example, for an installation of Python installed via ./configure --prefix=/usr/local/py; make; make install, BINDIR would be /usr/local/py/bin. Python interpreters on different platforms use a different BINDIR.  Look at the output of setup.py install if you can't figure out where yours is.
supervisorctl Command-Line Options -c, --configuration Configuration file path (default /etc/supervisord.conf)
-h, --help Print usage message and exit
-i, --interactive Start an interactive shell after executing commands
-s,--serverurl URL URL on which supervisord server is listening (default "‐ http://localhost:9001").
-u, --username Username to use for authentication with server
-p, --password Password to use for authentication with server
-r, --history-file Keep a readline history (if readline is available)
action [arguments]
Actions are commands like "tail" or "stop".  If -i is specified or no action is specified on the command line, a "shell" interpreting actions typed interactively is started.  Use the action "help" to find out about available actions.
Running supervisorctl To start supervisorctl, run $BINDIR/supervisorctl.  A shell will be presented that will allow you to control the processes that are currently managed by supervisord.  Type "help" at the prompt to get information about the supported commands.
The supervisorctl executable may be invoked with "one time" commands when invoked with arguments from a command line.  An example: supervisorctl stop all.  If arguments are present on the command-line, it will prevent the interactive shell from being invoked.  Instead, the command will be executed and supervisorctl will exit.
If supervisorctl is invoked in interactive mode against a supervisord that requires authentication, you will be asked for authentication credentials.
Glossary daemontools A process control system by D.J. Bernstein.
launchd A process control system used by Apple as process 1 under Mac OS X.
runit  A process control system.
Superlance A package which provides various event listener implementations that plug into Supervisor which can help monitor process memory usage and crash status: http://pypi.python.org/pypi/superlance.
umask  Abbreviation of user mask: sets the file mode creation mask of the current process.  See http://en.wikipedia.org/wiki/Umask.
This man page was created by Orestis Ioannou <orestis@oioannou.com> using the official documentation.
2004-2015, Agendaless Consulting and Contributors
IP-NEIGHBOUR(8)                       Linux                      IP-NEIGHBOUR(8)
ip-neighbour - neighbour/arp tables management.
ip [ OPTIONS ] neigh  { COMMAND | help }
ip neigh { add | del | change | replace } { ADDR [ lladdr LLADDR ] [ nud STATE ] | proxy ADDR } [ dev DEV ] [ router ] [ extern_learn ]
ip neigh { show | flush } [ proxy ] [ to PREFIX ] [ dev DEV ] [ nud STATE ] [ vrf NAME ]
ip neigh get ADDR dev DEV
STATE := { permanent | noarp | stale | reachable | none | incomplete | delay | probe | failed }
The ip neigh command manipulates neighbour objects that establish bindings between protocol addresses and link layer addresses for hosts sharing the same link.  Neighbour entries are organized into tables. The IPv4 neighbour table is also known by another name - the ARP table.
The corresponding commands display neighbour bindings and their properties, add new neighbour entries and delete old ones.
ip neighbour add add a new neighbour entry
ip neighbour change change an existing entry
ip neighbour replace add a new entry or change an existing one
These commands create new neighbour records or update existing ones.
to ADDRESS (default) the protocol address of the neighbour. It is either an IPv4 or IPv6 address.
dev NAME the interface to which this neighbour is attached.
proxy  indicates whether we are proxying for this neighbour entry
router indicates whether neighbour is a router
extern_learn this neigh entry was learned externally. This option can be used to indicate to the kernel that this is a controller learnt dynamic entry.  Kernel will not gc such an entry.
lladdr LLADDRESS the link layer address of the neighbour.  LLADDRESS can also be null.
nud STATE the state of the neighbour entry.  nud is an abbreviation for 'Neighbour Unreachability Detection'.  The state can take one of the following values:
permanent the neighbour entry is valid forever and can be only be removed administratively.
noarp  the neighbour entry is valid. No attempts to validate this entry will be made but it can be removed when its lifetime expires.
reachable the neighbour entry is valid until the reachability timeout expires.
stale  the neighbour entry is valid but suspicious.  This option to ip neigh does not change the neighbour state if it was valid and the address is not changed by this command.
none   this is a pseudo state used when initially creating a neighbour entry or after trying to remove it before it becomes free to do so.
incomplete the neighbour entry has not (yet) been validated/resolved.
delay  neighbor entry validation is currently delayed.
probe  neighbor is being probed.
failed max number of probes exceeded without success, neighbor validation has ultimately failed.
ip neighbour delete delete a neighbour entry
The arguments are the same as with ip neigh add, except that lladdr and nud are ignored.
Warning: Attempts to delete or manually change a noarp entry created by the kernel may result in unpredictable behaviour. Particularly, the kernel may try to resolve this address even on a NOARP interface or if the address is multicast or broadcast.
ip neighbour show list neighbour entries
to ADDRESS (default) the prefix selecting the neighbours to list.
dev NAME only list the neighbours attached to this device.
vrf NAME only list the neighbours for given VRF.
proxy  list neighbour proxies.
unused only list neighbours which are not currently in use.
nud STATE only list neighbour entries in this state.  NUD_STATE takes values listed below or the special value all which means all states. This option may occur more than once.  If this option is absent, ip lists all entries except for none and noarp.
ip neighbour flush flush neighbour entries This command has the same arguments as show.  The differences are that it does not run when no arguments are given, and that the default neighbour states to be flushed do not include permanent and noarp.
With the -statistics option, the command becomes verbose. It prints out the number of deleted neighbours and the number of rounds made to flush the neighbour table. If the option is given twice, ip neigh flush also dumps all the deleted neighbours.
ip neigh get lookup a neighbour entry to a destination given a device
proxy  indicates whether we should lookup a proxy neighbour entry
to ADDRESS (default) the prefix selecting the neighbour to query.
dev NAME get neighbour entry attached to this device.
ip neighbour Shows the current neighbour table in kernel.
ip neigh flush dev eth0 Removes entries in the neighbour table on device eth0.
ip neigh get 10.0.1.10 dev eth0 Performs a neighbour lookup in the kernel and returns a neighbour entry.
IWCONFIG(8)                 Linux Programmer's Manual                IWCONFIG(8)
iwconfig - configure a wireless network interface
iwconfig [interface] iwconfig interface [essid X] [nwid N] [mode M] [freq F] [channel C][sens S ][ap A ][nick NN ] [rate R] [rts RT] [frag FT] [txpower T] [enc E] [key K] [power P] [retry R] [modu M] [commit] iwconfig --help iwconfig --version
Iwconfig is similar to ifconfig(8), but is dedicated to the wireless interfaces. It is used to set the parameters of the network interface which are specific to the wireless operation (for example : the frequency).  Iwconfig may also be used to display those parameters, and the wireless statistics (extracted from /proc/net/wireless).
All these parameters and statistics are device dependent. Each driver will provide only some of them depending on hardware support, and the range of values may change. Please refer to the man page of each device for details.
essid  Set the ESSID (or Network Name - in some products it may also be called Domain ID). The ESSID is used to identify cells which are part of the same virtual network. As opposed to the AP Address or NWID which define a single cell, the ESSID defines a group of cells connected via repeaters or infrastructure, where the user may roam transparently. With some cards, you may disable the ESSID checking (ESSID promiscuous) with off or any (and on to reenable it). If the ESSID of your network is one of the special keywords (off, on or any), you should use -- to escape it. Examples : iwconfig eth0 essid any iwconfig eth0 essid "My Network" iwconfig eth0 essid -- "ANY"
nwid   Set the Network ID. As all adjacent wireless networks share the same medium, this parameter is used to differentiate them (create logical colocated networks) and identify nodes belonging to the same cell. This parameter is only used for pre-802.11 hardware, the 802.11 protocol uses the ESSID and AP Address for this function. With some cards, you may disable the Network ID checking (NWID promiscuous) with off (and on to reenable it). Examples : iwconfig eth0 nwid AB34 iwconfig eth0 nwid off
nick[name] Set the nickname, or the station name. Some 802.11 products do define it, but this is not used as far as the protocols (MAC, IP, TCP) are concerned and completely useless as far as configuration goes. Only some wireless diagnostic tools may use it. Example : iwconfig eth0 nickname "My Linux Node"
mode   Set the operating mode of the device, which depends on the network topology. The mode can be Ad-Hoc (network composed of only one cell and without Access Point), Managed (node connects to a network composed of many Access Points, with roaming), Master (the node is the synchronisation master or acts as an Access Point), Repeater (the node forwards packets between other wireless nodes), Secondary (the node acts as a backup master/repeater), Monitor (the node is not associated with any cell and passively monitor all packets on the frequency) or Auto. Example : iwconfig eth0 mode Managed iwconfig eth0 mode Ad-Hoc
freq/channel Set the operating frequency or channel in the device. A value below 1000 indicates a channel number, a value greater than 1000 is a frequency in Hz. You may append the suffix k, M or G to the value (for example, "2.46G" for 2.46 GHz frequency), or add enough '0'. Channels are usually numbered starting at 1, and you may use iwlist(8) to get the total number of channels, list the available frequencies, and display the current frequency as a channel. Depending on regulations, some frequencies/channels may not be available. When using Managed mode, most often the Access Point dictates the channel and the driver may refuse the setting of the frequency. In Ad-Hoc mode, the frequency setting may only be used at initial cell creation, and may be ignored when joining an existing cell. You may also use off or auto to let the card pick up the best channel (when supported). Examples : iwconfig eth0 freq 2422000000 iwconfig eth0 freq 2.422G iwconfig eth0 channel 3 iwconfig eth0 channel auto
ap     Force the card to register to the Access Point given by the address, if it is possible. This address is the cell identity of the Access Point, as reported by wireless scanning, which may be different from its network MAC address. If the wireless link is point to point, set the address of the other end of the link. If the link is ad-hoc, set the cell identity of the ad-hoc network. When the quality of the connection goes too low, the driver may revert back to automatic mode (the card selects the best Access Point in range). You may also use off to re-enable automatic mode without changing the current Access Point, or you may use any or auto to force the card to reassociate with the currently best Access Point. Example : iwconfig eth0 ap 00:60:1D:01:23:45 iwconfig eth0 ap any iwconfig eth0 ap off
rate/bit[rate] For cards supporting multiple bit rates, set the bit-rate in b/s. The bit-rate is the speed at which bits are transmitted over the medium, the user speed of the link is lower due to medium sharing and various overhead. You may append the suffix k, M or G to the value (decimal multiplier : 10^3, 10^6 and 10^9 b/s), or add enough '0'. Values below 1000 are card specific, usually an index in the bit-rate list. Use auto to select automatic bit-rate mode (fallback to lower rate on noisy channels), which is the default for most cards, and fixed to revert back to fixed setting. If you specify a bit-rate value and append auto, the driver will use all bit-rates lower and equal than this value. Examples : iwconfig eth0 rate 11M iwconfig eth0 rate auto iwconfig eth0 rate 5.5M auto
txpower For cards supporting multiple transmit powers, sets the transmit power in dBm. If W is the power in Watt, the power in dBm is P = 30 + 10.log(W).  If the value is postfixed by mW, it will be automatically converted to dBm. In addition, on and off enable and disable the radio, and auto and fixed enable and disable power control (if those features are available). Examples : iwconfig eth0 txpower 15 iwconfig eth0 txpower 30mW iwconfig eth0 txpower auto iwconfig eth0 txpower off
sens   Set the sensitivity threshold. This define how sensitive is the card to poor operating conditions (low signal, interference). Positive values are assumed to be the raw value used by the hardware or a percentage, negative values are assumed to be dBm. Depending on the hardware implementation, this parameter may control various functions. On modern cards, this parameter usually control handover/roaming threshold, the lowest signal level for which the hardware remains associated with the current Access Point. When the signal level goes below this threshold the card starts looking for a new/better Access Point. Some cards may use the number of missed beacons to trigger this. For high density of Access Points, a higher threshold make sure the card is always associated with the best AP, for low density of APs, a lower threshold minimise the number of failed handoffs. On more ancient card this parameter usually controls the defer threshold, the lowest signal level for which the hardware considers the channel busy. Signal levels above this threshold make the hardware inhibits its own transmission whereas signals weaker than this are ignored and the hardware is free to transmit. This is usually strongly linked to the receive threshold, the lowest signal level for which the hardware attempts packet reception. Proper setting of these thresholds prevent the card to waste time on background noise while still receiving weak transmissions. Modern designs seems to control those thresholds automatically. Example : iwconfig eth0 sens -80 iwconfig eth0 sens 2
retry  Most cards have MAC retransmissions, and some allow to set the behaviour of the retry mechanism. To set the maximum number of retries, enter limit `value'.  This is an absolute value (without unit), and the default (when nothing is specified).  To set the maximum length of time the MAC should retry, enter lifetime `value'.  By defaults, this value is in seconds, append the suffix m or u to specify values in milliseconds or microseconds. You can also add the short, long, min and max modifiers. If the card supports automatic mode, they define the bounds of the limit or lifetime. Some other cards define different values depending on packet size, for example in 802.11 min limit is the short retry limit (non RTS/CTS packets). Examples : iwconfig eth0 retry 16 iwconfig eth0 retry lifetime 300m iwconfig eth0 retry short 12 iwconfig eth0 retry min limit 8
rts[_threshold] RTS/CTS adds a handshake before each packet transmission to make sure that the channel is clear. This adds overhead, but increases performance in case of hidden nodes or a large number of active nodes. This parameter sets the size of the smallest packet for which the node sends RTS ; a value equal to the maximum packet size disables the mechanism. You may also set this parameter to auto, fixed or off. Examples : iwconfig eth0 rts 250 iwconfig eth0 rts off
frag[mentation_threshold] Fragmentation allows to split an IP packet in a burst of smaller fragments transmitted on the medium. In most cases this adds overhead, but in a very noisy environment this reduces the error penalty and allow packets to get through interference bursts. This parameter sets the maximum fragment size which is always lower than the maximum packet size. This parameter may also control Frame Bursting available on some cards, the ability to send multiple IP packets together. This mechanism would be enabled if the fragment size is larger than the maximum packet size. You may also set this parameter to auto, fixed or off. Examples : iwconfig eth0 frag 512 iwconfig eth0 frag off
key/enc[ryption] Used to manipulate encryption or scrambling keys and security mode. To set the current encryption key, just enter the key in hex digits as XXXX-XXXX-XXXX-XXXX or XXXXXXXX.  To set a key other than the current key, prepend or append [index] to the key itself (this won't change which is the active key). You can also enter the key as an ASCII string by using the s: prefix. Passphrase is currently not supported. To change which key is the currently active key, just enter [index] (without entering any key value). off and on disable and reenable encryption. The security mode may be open or restricted, and its meaning depends on the card used. With most cards, in open mode no authentication is used and the card may also accept non-encrypted sessions, whereas in restricted mode only encrypted sessions are accepted and the card will use authentication if available. If you need to set multiple keys, or set a key and change the active key, you need to use multiple key directives. Arguments can be put in any order, the last one will take precedence. Examples : iwconfig eth0 key 0123-4567-89 iwconfig eth0 key [3] 0123-4567-89 iwconfig eth0 key s:password [2] iwconfig eth0 key [2] iwconfig eth0 key open iwconfig eth0 key off iwconfig eth0 key restricted [3] 0123456789 iwconfig eth0 key 01-23 key 45-67 [4] key [4]
power  Used to manipulate power management scheme parameters and mode. To set the period between wake ups, enter period `value'.  To set the timeout before going back to sleep, enter timeout `value'.  To set the generic level of power saving, enter saving `value'.  You can also add the min and max modifiers. By default, those values are in seconds, append the suffix m or u to specify values in milliseconds or microseconds. Sometimes, those values are without units (number of beacon periods, dwell, percentage or similar). off and on disable and reenable power management. Finally, you may set the power management mode to all (receive all packets), unicast (receive unicast packets only, discard multicast and broadcast) and multicast (receive multicast and broadcast only, discard unicast packets). Examples : iwconfig eth0 power period 2 iwconfig eth0 power 500m unicast iwconfig eth0 power timeout 300u all iwconfig eth0 power saving 3 iwconfig eth0 power off iwconfig eth0 power min period 2 power max period 4
modu[lation] Force the card to use a specific set of modulations. Modern cards support various modulations, some which are standard, such as 802.11b or 802.11g, and some proprietary. This command force the card to only use the specific set of modulations listed on the command line. This can be used to fix interoperability issues. The list of available modulations depend on the card/driver and can be displayed using iwlist modulation.  Note that some card/driver may not be able to select each modulation listed independently, some may come as a group. You may also set this parameter to auto let the card/driver do its best. Examples : iwconfig eth0 modu 11g iwconfig eth0 modu CCK OFDMa iwconfig eth0 modu auto
commit Some cards may not apply changes done through Wireless Extensions immediately (they may wait to aggregate the changes or apply it only when the card is brought up via ifconfig).  This command (when available) forces the card to apply all pending changes. This is normally not needed, because the card will eventually apply the changes, but can be useful for debugging.
For each device which supports wireless extensions, iwconfig will display the name of the MAC protocol used (name of device for proprietary protocols), the ESSID (Network Name), the NWID, the frequency (or channel), the sensitivity, the mode of operation, the Access Point address, the bit-rate, the RTS threshold, the fragmentation threshold, the encryption key and the power management settings (depending on availability).
The parameters displayed have the same meaning and values as the parameters you can set, please refer to the previous part for a detailed explanation of them. Some parameters are only displayed in short/abbreviated form (such as encryption). You may use iwlist(8) to get all the details. Some parameters have two modes (such as bitrate). If the value is prefixed by `=', it means that the parameter is fixed and forced to that value, if it is prefixed by `:', the parameter is in automatic mode and the current value is shown (and may change).
Access Point/Cell An address equal to 00:00:00:00:00:00 means that the card failed to associate with an Access Point (most likely a configuration issue). The Access Point parameter will be shown as Cell in ad-hoc mode (for obvious reasons), but otherwise works the same.
If /proc/net/wireless exists, iwconfig will also display its content. Note that those values will depend on the driver and the hardware specifics, so you need to refer to your driver documentation for proper interpretation of those values.
Link quality Overall quality of the link. May be based on the level of contention or interference, the bit or frame error rate, how good the received signal is, some timing synchronisation, or other hardware metric. This is an aggregate value, and depends totally on the driver and hardware.
Signal level Received signal strength (RSSI - how strong the received signal is). May be arbitrary units or dBm, iwconfig uses driver meta information to interpret the raw value given by /proc/net/wireless and display the proper unit or maximum value (using 8 bit arithmetic). In Ad-Hoc mode, this may be undefined and you should use iwspy.
Noise level Background noise level (when no packet is transmitted). Similar comments as for Signal level.
Rx invalid nwid Number of packets received with a different NWID or ESSID. Used to detect configuration problems or adjacent network existence (on the same frequency).
Rx invalid crypt Number of packets that the hardware was unable to decrypt. This can be used to detect invalid encryption settings.
Rx invalid frag Number of packets for which the hardware was not able to properly re-assemble the link layer fragments (most likely one was missing).
Tx excessive retries Number of packets that the hardware failed to deliver. Most MAC protocols will retry the packet a number of times before giving up.
Invalid misc Other packets lost in relation with specific wireless operations.
Missed beacon Number of periodic beacons from the Cell or the Access Point we have missed. Beacons are sent at regular intervals to maintain the cell coordination, failure to receive them usually indicates that the card is out of range.
Jean Tourrilhes - jt@hpl.hp.com
/proc/net/wireless
ifconfig(8), iwspy(8), iwlist(8), iwevent(8), iwpriv(8), wireless(7).
minetest(6)                                                          minetest(6)
minetest, minetestserver - Multiplayer infinite-world block sandbox
minetest [--server SERVER OPTIONS | CLIENT OPTIONS] [COMMON OPTIONS] [WORLD PATH]
minetestserver [SERVER OPTIONS] [COMMON OPTIONS] [WORLD PATH]
Minetest is one of the first InfiniMiner/Minecraft(/whatever) inspired games (started October 2010), with a goal of taking the survival multiplayer gameplay in a slightly different direction.
The main design philosophy is to keep it technically simple, stable and portable. It will be kept lightweight enough to run on fairly old hardware.
--help Print allowed options and exit
--version Print version information and exit
--config <value> Load configuration from specified file
--logfile <value> Set logfile path ('' for no logging)
--info Print more information to console
--verbose Print even more information to console
--trace Print enormous amounts of information to console
--quiet Print only errors to console
--color <value> Colorize the logs ('always', 'never' or 'auto'), defaults to 'auto'
--gameid <value> | list Set gameid or list available ones
--worldname <value> Set world path by name
--world <value> Set world path
--worldlist path | name | both Get list of worlds ('path' lists paths, 'name' lists names, 'both' lists both)
--map-dir <value> Same as --world (deprecated)
--port <value> Set network port (UDP) to use
--run-unittests Run unit tests and exit
--address <value> Address to connect to
--go   Disable main menu
--name <value> Set player name
--password <value> Set password
--password-file <value> Set password from contents of file
--random-input Enable random user input, for testing (client only)
--videomodes List available video modes (client only)
--speedtests Run speed tests
--migrate <value> Migrate from current map backend to another. Possible values are sqlite3, leveldb, redis, postgresql, and dummy.
--migrate-auth <value> Migrate from current auth backend to another. Possible values are sqlite3, leveldb, and files.
--migrate-players <value> Migrate from current players backend to another. Possible values are sqlite3, leveldb, postgresql, dummy, and files.
--terminal Display an interactive terminal over ncurses during execution.
MINETEST_SUBGAME_PATH Colon delimited list of directories to search for games.
Please report all bugs at https://github.com/minetest/minetest/issues.
Perttu Ahola <celeron55@gmail.com> and contributors.
This man page was originally written by Juhani Numminen <juhaninumminen0@gmail.com>.
http://www.minetest.net/
NOKOGIRI(1)                                                          NOKOGIRI(1)
nokogiri - an HTML, XML, SAX, and Reader parser
Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among Nokogiri’s many features is the ability to search documents via XPath or CSS3 selectors.  The nokogiri command parses a document, and launches an interactive ruby session (irb(1)), allowing one to analysing the result interactively.
nokogiri <uri|path> [options]
--type [TYPE] Set the type of the document to be parsed
-E, --encoding encoding Set the encoding of the document
-e command Specifies script from command-line
--rng <uri|path> Validate using this rng file
-?, --help Show a message very similar to this man page
-v, --version Show the version of the program
nokogiri http://www.ruby-lang.org/
nokogiri ./public/index.html
curl -s http://nokogiri.org | nokogiri -e'p $_.css("h1").length'
CPULIMIT(1)                       User commands                      CPULIMIT(1)
cpulimit -- limits the CPU usage of a process
cpulimit [TARGET] [OPTIONS...] [ -- PROGRAM]
TARGET must be exactly one of these:
-p, --pid=N pid of the process
-e, --exe=FILE name of the executable program file
-P, --path=PATH absolute path name of the executable program file
-b, --background run cpulimit in the background, freeing up the terminal
-f, --foreground run cpulimit in foreground while waiting for launched process to finish
-c, --cpu specify the number of CPU cores available. Usually this is detected for us.
-l, --limit=N percentage of CPU allowed from 1 up. Usually 1 - 100, but can be higher on multi-core CPUs. (mandatory)
-q, --quiet Runs in quiet mode, avoids writing update messages to console.
-k, --kill kill target process instead of throttling its CPU usage