neulab/tldr huggingface dataset:
archinstall.Partition(path: str, block_device: archinstall.lib.disk.BlockDevice, part_id=None, size=- 1, filesystem=None, mountpoint=None, encrypted=False, autodetect_filesystem=True)
archinstall.Filesystem(blockdevice, mode)
archinstall.device_state(name, *args, **kwargs)
archinstall.all_disks(*args, **kwargs)
LUKS (DISK ENCRYPTION) archinstall.luks2(partition, mountpoint, password, key_file=None, auto_unmount=False, *args, **kwargs)
archinstall.list_interfaces(skip_loopback=True)
archinstall.log(*args, **kwargs)
archinstall.locate_binary(name)
archinstall.RequirementError() Common base class for all exceptions
archinstall.DiskError() Common base class for all exceptions
archinstall.ProfileError() Common base class for all exceptions
archinstall.SysCallError(message, exit_code) Common base class for all exceptions
archinstall.ProfileNotFound() Common base class for all exceptions
archinstall.HardwareIncompatibilityError() Common base class for all exceptions
archinstall.UserError() Common base class for all exceptions
archinstall.ServiceException() Common base class for all exceptions
Anton Hvornum
2021, Anton Hvornum
MOST(1)                                                                  MOST(1)
most - browse or page through a text file
most [ -1 ] [ -b ] [ -C ] [ -c ] [ -d ] [ -M ] [ -r ] [ -s ] [ -t ] [ -u ] [ -v ] [ -w ] [ -z ] [ +/string ] [ +line-number ] [ +d ] [ +s ] [ +u ] [ file... ]
most is a paging program that displays, one windowful at a time, the contents of a file on a terminal.  It pauses after each windowful and prints on the window status line the screen the file name, current line number, and the percentage of the file so far displayed.
Unlike other paging programs, most is capable of displaying an arbitrary number of windows as long as each window occupies at least two screen lines.  Each window may contain the same file or a different file.  In addition, each window has its own mode.  For example, one window may display a file with its lines wrapped while another may be truncating the lines. Windows may be `locked' together in the sense that if one of the locked windows scrolls, all locked windows will scroll.  most is also capable of ignoring lines that are indented beyond a user specified value.  This is useful when viewing computer programs to pick out gross features of the code.  See the `:o' command for a description of this feature.
In addition to displaying ordinary text files, most can also display binary files as well as files with arbitrary ascii characters.  When a file is read into a buffer, most examines the first 32 bytes of the file to determine if the file is a binary file and then switches to the appropriate mode.  However, this feature may be disabled with the -k option.  See the description of the -b, -k, -v, and -t options for further details.
Text files may contain combinations of underscore and backspace characters causing a printer to underline or overstrike.  When most recognizes this, it inserts the appropriate escape sequences to achieve the desired effect.  In addition, some files cause the printer to overstrike some characters by embedding carriage return characters in the middle of a line.  When this occurs, most displays the overstruck character with a bold attribute.  This feature facilitates the reading of UNIX man pages or a document produced by runoff.  In particular, viewing this document with most should illustrate this behavior provided that the underline characters have not been stripped.  This may be turned off with the -v option.
By default, lines with more characters than the terminal width are not wrapped but are instead truncated. When truncation occurs, this is indicated by a `$' in the far right column of the terminal screen.  The RIGHT and LEFT arrow keys may be used to view lines which extend past the margins of the screen.  The -w option may be used to override this feature.  When a window is wrapped, the character `\' will appear at the right edge of the window.
Commands are listed below.
-1     VT100 mode.  This is meaningful only on VMS systems.  This option should be used if the terminal is strictly a VT100.  This implies that the terminal does not have the ability to delete and insert multiple lines.  VT102s and above have this ability.
-b     Binary mode.  Use this switch when you want to view files containing 8 bit characters.  most will display the file 16 bytes per line in hexadecimal notation. A typical line looks like:
01000000 40001575 9C23A020 4000168D     ....@..u.#. @...
When used with the -v option, the same line looks like:
^A^@^@^@  @^@^U u 9C #A0    @^@^V8D     ....@..u.#. @...
-C     Disable color support.
-c     Make searches case-sensitive
-d     Omit the backslash mark used to denote a wrapped line.
-M     Disable the use of mmap.
-r     Default to using regexp searches
-s     Squeeze-mode.  Replace multiple blank lines with a single blank line.
-t     Display tabs as ^I.  If this option is immediately followed by an integer, the integer sets the tab width, e.g., -t4
-u     Disable UTF-8 mode even if the locale dictates it
+u     Force UTF-8 mode.  By default most will use the current locale to determine if UTF-8 mode should be used.  The +u and -u switches allow the behavior to be overridden
-v     Display control characters as in `^A' for control A.  Normally most does not interpret control characters.
-w     Wrap lines
-z     Disable gunzip-on-the-fly
+/string Start up at the line containing the first occurrence of string
+lineno Start up at the specified line-number
+d     This switch should only be used if you want the option to delete a file while viewing it.  This makes it easier to clean unwanted files out of a directory. The file is deleted with the interactive key sequence `:D' and then confirming with `y'.
+s     Secure Mode-- no edit, cd, shell, and reading files not already listed on the command line.
The commands take effect immediately; it is not necessary to type a carriage return.  In the following commands, i is a numerical argument (1 by default).
SPACE, CTRL-D, NEXT_SCREEN Display another windowful, or jump i windowfuls if i is specified.
RETURN, DOWN_ARROW, V, CTRL-N Display another line, or i more lines, if specified.
UP_ARROW, ^, CTRL-P Display previous line, or i previous lines, if specified.
T, ESCAPE< Move to top of buffer.
B, ESCAPE> Move to bottom of buffer.
RIGHT_ARROW, TAB, > Scroll window left 60i columns to view lines that are beyond the right margin of the window.
LEFT_ARROW, CTRL-B, < Scroll window right 60i columns to view lines that are beyond the left margin of the window.
U, CTRL-U, DELETE, PREV_SCREEN Skip back i windowfuls and then print a windowful.
R, CTRL-R Redraw the window.
J, G   If  i  is  not  specified, then prompt for a line number then jump to that line otherwise just jump to line i.
%      If i is not specified, then prompt for a percent number then jump to that percent of the file otherwise just jump to i percent of the file.
W, w   If  the  current  screen  width  is 80, make it 132 and vice- versa.  For other values, this command is ignored.
Q, CTRL-X CTRL-C, CTRL-K E Exit from most.  On VMS, ^Z also exits.
h, CTRL-H, HELP, PF2 Help.  Give a description of all the most commands.  The most environment variable MOST_HELP must be set for this to be meaningful.
f, /, CTRL-F, FIND, GOLD PF3 Prompt  for  a  string  and search forward from the current line for ith distinct line containing the string.  CTRL-G aborts.
?      Prompt for a string and search backward for the ith distinct line containing the string.  CTRL-G aborts.
n      Search for the next i lines containing an occurrence of the last search string in the direction of the previous search.
m, SELECT, CTRL-@, CTRL-K M, PERIOD Set a mark on the current line for later reference.
INSERT_HERE, CTRL-X CTRL-X, COMMA, CTRL-K RETURN, GOLD PERIOD Set a mark on the current line but return to previous mark.  This allows the user to toggle back and forth between two positions in the file.
l, L   Toggle locking for this window.  The window is locked if there is a `*' at the left edge of the status line.  Windows locked together, scroll together.
CTRL-X 2, CTRL-W 2, GOLD X Split this window in half.
CTRL-X o, CTRL-W o, o, GOLDUP, GOLDDOWN Move to other window.
CTRL-X 0, CTRL-W 0, GOLD V Delete this window.
CTRL-X 1, CTRL-W 1, GOLD O Delete all other windows, leaving only one window.
E, e   Edit this file.
$, ESC $ This is system dependent.  On VMS, this causes most to spawn a subprocess.  When the user exits the process, most is resumed.  On UNIX systems, most simply suspends itself.
:n     Skip to the next filename given in the command line.  Use the arrow keys to scroll forward or backward through the file list. `Q' quits most and any other key selects the given file.
:c     Toggle case sensitive search.
:D     Delete current file.  This command is only meaningful with the +d switch.
:o, :O Toggle various options.  With this key sequence, most displays a prompt asking the user to hit one of: bdtvw.  The `b', `t', `v', and `w' options have the same meaning as the command line switches.  For example, the `w' option will toggle wrapping on and off for the current window.
The `d' option must be used with a prefix integer i.  All lines indented beyond i columns will not be displayed.  For example, consider the fragment:
int main(int argc, char **argv) { int i; for (i = 0; i < argc, i++) { fprintf(stdout,"%i: %s\n",i,argv[i]); } return 0; } The key sequence `1:od' will cause most to display the file ignoring all lines indented beyond the first column.  So for the example above, most would display:
int main(int argc, char **argv)... } where the `...' indicates lines that follow are not displayed.
CTRL-G aborts the commands requiring the user to type something in at a prompt.  The back-quote key has a special meaning here.  It is used to quote certain characters.  This is useful when search for the occurrence of a string with a control character or a string at the beginning of a line.  In the latter case, to find the occurrence of `The' at the beginning of a line, enter `^JThe where ` quotes the CTRL-J.
most uses the following environment variables:
MOST_SWITCHES This  variable  sets  commonly used switches.  For example, some people prefer to use most with the -s option so that excess blank lines are not displayed.  On VMS this is normally done done in the login.com through the line:
$ define MOST_SWITCHES "-s"
MOST_EDITOR, SLANG_EDITOR Either  of  these environment variables specify an editor for most to invoke to edit a file. The value can contain %s and %d formatting descriptors that represent the file name and line number, respectively.  For example, if JED is your editor, then set MOST_EDITOR to 'jed %s -g %d'.
MOST_HELP This variable may be used to specify an alternate help file.
MOST_INITFILE Set this variable to specify the initialization file to load during startup.  The default action is to load the system configuration file and then a personal configuration file called .mostrc on Unix, and most.rc on other systems.
When most starts up, it tries to read a system configuration file and then a personal configuration file. These files may be used to specify key-bindings and colors.
To bind a key to a particular function use the syntax:
setkey function-name key-sequence
The setkey command requires two arguments.  The function-name argument specifies the function that is to be executed as a response to the keys specified by the key-sequence argument are pressed.  For example,
setkey   "up"     "^P"
indicates that when Ctrl-P is pressed then the function up is to be executed.
Sometimes, it is necessary to first unbind a key-sequence before rebinding it in order via the unsetkey function:
unsetkey "^F"
Colors may be defined through the use of the color keyword in the the configuration file using the syntax:
color OBJECT-NAME FOREGROUND-COLOR BACKGROUND-COLOR
Here, OBJECT-NAME can be any one of the following items:
status           -- the status line underline        -- underlined text overstrike       -- overstruck text normal           -- anything else
See the sample configuration files for more information.
Almost all of the known bugs or limitations of most are due to a desire to read and interpret control characters in files.  One problem concerns the use of backspace characters to underscore or overstrike other characters.  most makes an attempt to use terminal escape sequences to simulate this behavior.  One side effect is the one does not always get what one expects when scrolling right and left through a file.  When in doubt, use the -v and -b options of most.
The regular-expression searches may fail to find strings that involve backspace/underscore used for highlighting.  The regular-expression syntax is described in the S-Lang Library documentation.
John E. Davis <jed@jedsoft.org>
Over the years, many people have contributed to most in one way or another, e.g., via code patches, bug-fixes, comments, or criticisms.  I am particularly grateful to the very early adopters of the program who took a chance with a fledgling software project headed by someone learning the underlying language.  These include:
Mats Akerberg, Henk D. Davids, Rex O. Livingston, and Mark Pizzolato contributed to the early VMS versions of most.  In particular, Mark worked on it to get it ready for DECUS.
Foteos Macrides adapted most for use in cswing and gopher.  A few features of the present version of most was inspired from his work.
I am grateful to Robert Mills for re-writing the search routines to use regular expressions.
Sven Oliver Moll came up with the idea of automatic detection of zipped files.
I would also like to thank Shinichi Hama for his valuable criticisms of most.
Javier Kohen was instrumental in the support for UTF-8.
Thanks to David W. Sanderson for adapting the early documentation to nroff man page source format.
promtool(1)                         2.24.1+ds                        promtool(1)
build user:       pkg-go-maintainers@lists.alioth.debian.org build date:       20210804-20:00:23 go version:       go1.15.9 platform:         linux/amd64 ""
promtool - Tooling for the Prometheus monitoring system
promtool [<flags>] <command> [<args> ...]
Tooling for the Prometheus monitoring system.
-h, --help Show context-sensitive help (also try --help-long and --help-man).
--version Show application version.
help [<command>...] Show help.
check config <config-files>... Check if the config files are valid or not.
check web-config <web-config-files>... Check if the web config files are valid or not.
check rules <rule-files>... Check if the rule files are valid or not.
check metrics Pass Prometheus metrics over stdin to lint them for consistency and correctness.
$ cat metrics.prom | promtool check metrics
$ curl -s http://localhost:9090/metrics | promtool check metrics
query instant [<flags>] <server> <expr> Run instant query.
--time=TIME Query evaluation time (RFC3339 or Unix timestamp).
query range [<flags>] <server> <expr> Run range query.
--header=HEADER Extra headers to send to server.
--start=START Query range start time (RFC3339 or Unix timestamp).
--end=END Query range end time (RFC3339 or Unix timestamp).
--step=STEP Query step size (duration).
query series --match=MATCH [<flags>] <server> Run series query.
--match=MATCH Series selector. Can be specified multiple times.
--start=START Start time (RFC3339 or Unix timestamp).
--end=END End time (RFC3339 or Unix timestamp).
query labels [<flags>] <server> <name> Run labels query.
debug pprof <server> Fetch profiling debug information.
debug metrics <server> Fetch metrics debug information.
debug all <server> Fetch all debug information.
test rules <test-rule-file>... Unit tests for rules.
tsdb bench write [<flags>] [<file*>] Run a write performance benchmark.
--out="benchout" Set the output path.
--metrics=10000 Number of metrics to read.
tsdb analyze [<flags>] [<db path*>] [<block id>] Analyze churn, label pair cardinality.
--limit=20 How many items to show in each list.
tsdb list [<flags>] [<db path*>] List tsdb blocks.
-r, --human-readable Print human readable values.
tsdb dump [<flags>] [<db path*>] Dump samples from a TSDB.
--min-time=-9223372036854775808 Minimum timestamp to dump.
--max-time=9223372036854775807 Maximum timestamp to dump.
tsdb create-blocks-from openmetrics <input file> [<output directory*>] Import samples from OpenMetrics input and produce TSDB blocks. Please refer to the storage docs for more details.
TRAP(1P)                    POSIX Programmer's Manual                   TRAP(1P)
trap — trap signals
trap n [condition...] trap [action condition...]
If the first operand is an unsigned decimal integer, the shell shall treat all operands as conditions, and shall reset each condition to the default value. Otherwise, if there are operands, the first is treated as an action and the remaining as conditions.
If action is '-', the shell shall reset each condition to the default value. If action is null (""), the shell shall ignore each specified condition if it arises. Otherwise, the argument action shall be read and executed by the shell when one of the corresponding conditions arises. The action of trap shall override a previous action (either default action or one explicitly set). The value of "$?" after the trap action completes shall be the value it had before trap was invoked.
The condition can be EXIT, 0 (equivalent to EXIT), or a signal specified using a symbolic name, without the SIG prefix, as listed in the tables of signal names in the <signal.h> header defined in the Base Definitions volume of POSIX.1‐2017, Chapter 13, Headers; for example, HUP, INT, QUIT, TERM. Implementations may permit names with the SIG prefix or ignore case in signal names as an extension. Setting a trap for SIGKILL or SIGSTOP produces undefined results.
The environment in which the shell executes a trap on EXIT shall be identical to the environment immediately after the last command executed before the trap on EXIT was taken.
Each time trap is invoked, the action argument shall be processed in a manner equivalent to:
eval action
Signals that were ignored on entry to a non-interactive shell cannot be trapped or reset, although no error need be reported when attempting to do so. An interactive shell may reset or catch signals ignored on entry. Traps shall remain in place for a given shell until explicitly changed with another trap command.
When a subshell is entered, traps that are not being ignored shall be set to the default actions, except in the case of a command substitution containing only a single trap command, when the traps need not be altered. Implementations may check for this case using only lexical analysis; for example, if `trap` and $( trap -- ) do not alter the traps in the subshell, cases such as assigning var=trap and then using $($var) may still alter them. This does not imply that the trap command cannot be used within the subshell to set new traps.
The trap command with no operands shall write to standard output a list of commands associated with each condition. If the command is executed in a subshell, the implementation does not perform the optional check described above for a command substitution containing only a single trap command, and no trap commands with operands have been executed since entry to the subshell, the list shall contain the commands that were associated with each condition immediately before the subshell environment was entered.  Otherwise, the list shall contain the commands currently associated with each condition. The format shall be:
"trap -- %s %s ...\n", <action>, <condition> ...
The shell shall format the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that achieve the same trapping results. For example:
save_traps=$(trap) ... eval "$save_traps"
XSI-conformant systems also allow numeric signal numbers for the conditions corresponding to the following signal names:
The trap special built-in shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
If the trap name or number is invalid, a non-zero exit status shall be returned; otherwise, zero shall be returned. For both interactive and non-interactive shells, invalid signal names or numbers shall not be considered a syntax error and do not cause the shell to abort.
Write out a list of all traps and actions:
Set a trap so the logout utility in the directory referred to by the HOME environment variable executes when the shell terminates:
trap '"$HOME"/logout' EXIT
trap '"$HOME"/logout' 0
Unset traps on INT, QUIT, TERM, and EXIT:
trap - INT QUIT TERM EXIT
Implementations may permit lowercase signal names as an extension. Implementations may also accept the names with the SIG prefix; no known historical shell does so. The trap and kill utilities in this volume of POSIX.1‐2017 are now consistent in their omission of the SIG prefix for signal names. Some kill implementations do not allow the prefix, and kill -l lists the signals without prefixes.
Trapping SIGKILL or SIGSTOP is syntactically accepted by some historical implementations, but it has no effect. Portable POSIX applications cannot attempt to trap these signals.
The output format is not historical practice. Since the output of historical trap commands is not portable (because numeric signal values are not portable) and had to change to become so, an opportunity was taken to format the output in a way that a shell script could use to save and then later reuse a trap if it wanted.
The KornShell uses an ERR trap that is triggered whenever set -e would cause an exit. This is allowable as an extension, but was not mandated, as other shells have not used it.
The text about the environment for the EXIT trap invalidates the behavior of some historical versions of interactive shells which, for example, close the standard input before executing a trap on 0. For example, in some historical interactive shell sessions the following trap on 0 would always print "--":
trap 'read foo; echo "-$foo-"' 0
trap 'eval " $cmd"' 0
causes the contents of the shell variable cmd to be executed as a command when the shell exits. Using:
trap '$cmd' 0
does not work correctly if cmd contains any special characters such as quoting or redirections. Using:
trap " $cmd" 0
also works (the leading <space> character protects against unlikely cases where cmd is a decimal integer or begins with '-'), but it expands the cmd variable when the trap command is executed, not when the exit action is executed.
The Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines, <signal.h>
JHSDB(1)                          JDK Commands                          JHSDB(1)
jhsdb - attach to a Java process or launch a postmortem debugger to analyze the content of a core dump from a crashed Java Virtual Machine (JVM)
jhsdb clhsdb [--pid pid | --exe executable --core coredump]
jhsdb hsdb [--pid pid | --exe executable --core coredump]
jhsdb debugd (--pid pid | --exe executable --core coredump) [options]
jhsdb jstack (--pid pid | --exe executable --core coredump | --connect [server-id@]debugd-host) [options]
jhsdb jmap (--pid pid | --exe executable --core coredump | --connect [server-id@]debugd-host) [options]
jhsdb jinfo (--pid pid | --exe executable --core coredump | --connect [server-id@]debugd-host) [options]
jhsdb jsnap (--pid pid | --exe executable --core coredump | --connect [server-id@]debugd-host) [options]
pid    The process ID to which the jhsdb tool should attach.  The process must be a Java process.  To get a list of Java processes running on a machine, use the ps command or, if the JVM processes are not running in a separate docker instance, the jps command.
executable The Java executable file from which the core dump was produced.
coredump The core file to which the jhsdb tool should attach.
[server-id@]debugd-host An optional server ID and the address of the remote debug server (debugd).
options The command-line options for a jhsdb mode.  See Options for the debugd Mode, Options for the jstack Mode, Options for the jmap Mode, Options for the jinfo Mode, and Options for the jsnap Mode.
Either the pid or the pair of executable and core files or the [server-id@]debugd-host must be provided for debugd, jstack, jmap, jinfo and jsnap modes.
You can use the jhsdb tool to attach to a Java process or to launch a postmortem debugger to analyze the content of a core-dump from a crashed Java Virtual Machine (JVM).  This command is experimental and unsupported.
Attaching the jhsdb tool to a live process will cause the process to hang and the process will probably crash when the debugger detaches.
The jhsdb tool can be launched in any one of the following modes:
jhsdb clhsdb Starts the interactive command-line debugger.
jhsdb hsdb Starts the interactive GUI debugger.
jhsdb debugd Starts the remote debug server.
jhsdb jstack Prints stack and locks information.
jhsdb jmap Prints heap information.
jhsdb jinfo Prints basic JVM information.
jhsdb jsnap Prints performance counter information.
jhsdb command --help Displays the options available for the command.
--serverid server-id An optional unique ID for this debug server.  This is required if multiple debug servers are run on the same machine.
--rmiport port Sets the port number to which the RMI connector is bound.  If not specified a random available port is used.
--registryport port Sets the RMI registry port.  This option overrides the system property 'sun.jvm.hotspot.rmi.port'.  If not specified, the system property is used.  If the system property is not set, the default port 1099 is used.
--hostname hostname Sets the hostname the RMI connector is bound.  The value could be a hostname or an IPv4/IPv6 address.  This option overrides the system property 'java.rmi.server.hostname'.  If not specified, the system property is used.  If the system property is not set, a system hostname is used.
--flags Prints the VM flags.
--sysprops Prints the Java system properties.
no option Prints the VM flags and the Java system properties.
no option Prints the same information as Solaris pmap.
--heap Prints the java heap summary.
--binaryheap Dumps the java heap in hprof binary format.
--dumpfile name The name of the dumpfile.
--histo Prints the histogram of java object heap.
--clstats Prints the class loader statistics.
--finalizerinfo Prints the information on objects awaiting finalization.
--locks Prints the java.util.concurrent locks information.
--mixed Attempts to print both java and native frames if the platform allows it.
--all  Prints all performance counters.
KJS::ScheduledAction(3)     Library Functions Manual     KJS::ScheduledAction(3)
KJS::ScheduledAction - An action (either function or string) to be executed after a specified time interval, either once or repeatedly.
#include <kjs_window.h>
Public Member Functions ScheduledAction (Object _func, List _args, bool _singleShot) ScheduledAction (QString _code, bool _singleShot) void execute (Window *window)
Public Attributes ObjectImp func List args QString code bool isFunction bool singleShot
Detailed Description An action (either function or string) to be executed after a specified time interval, either once or repeatedly.
Used for window.setTimeout() and window.setInterval()
Definition at line 159 of file kjs_window.h.
Author Generated automatically by Doxygen for khtml Library from the source code.
FOLD(1P)                    POSIX Programmer's Manual                   FOLD(1P)
fold — filter for folding lines
fold [-bs] [-w width] [file...]
The fold utility is a filter that shall fold lines from its input files, breaking the lines to have a maximum of width column positions (or bytes, if the -b option is specified). Lines shall be broken by the insertion of a <newline> such that each output line (referred to later in this section as a segment) is the maximum width possible that does not exceed the specified number of column positions (or bytes). A line shall not be broken in the middle of a character. The behavior is undefined if width is less than the number of columns any single character in the input would occupy.
If the <carriage-return>, <backspace>, or <tab> characters are encountered in the input, and the -b option is not specified, they shall be treated specially:
<backspace> The current count of line width shall be decremented by one, although the count never shall become negative. The fold utility shall not insert a <newline> immediately before or after any <backspace>, unless the following character has a width greater than 1 and would cause the line width to exceed width.
<carriage-return> The current count of line width shall be set to zero. The fold utility shall not insert a <newline> immediately before or after any <carriage-return>.
<tab>     Each <tab> encountered shall advance the column position pointer to the next tab stop. Tab stops shall be at each column position n such that n modulo 8 equals 1.
The fold utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
-b        Count width in bytes rather than column positions.
-s        If a segment of a line contains a <blank> within the first width column positions (or bytes), break the line after the last such <blank> meeting the width constraints. If there is no <blank> meeting the requirements, the -s option shall have no effect for that output segment of the input line.
-w width  Specify the maximum line length, in column positions (or bytes if -b is specified). The results are unspecified if width is not a positive decimal number. The default value shall be 80.
file      A pathname of a text file to be folded. If no file operands are specified, the standard input shall be used.
The standard input shall be used if no file operands are specified, and shall be used if a file operand is '-' and the implementation treats the '-' as meaning standard input.  Otherwise, the standard input shall not be used.  See the INPUT FILES section.
If the -b option is specified, the input files shall be text files except that the lines are not limited to {LINE_MAX} bytes in length. If the -b option is not specified, the input files shall be text files.
The following environment variables shall affect the execution of fold:
LC_CTYPE  Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files), and for the determination of the width in column positions each character would occupy on a constant-width font output device.
The standard output shall be a file containing a sequence of characters whose order shall be preserved from the input files, possibly with inserted <newline> characters.
The fold utility is frequently used to send text files to printers that truncate, rather than fold, lines wider than the printer is able to print (usually 80 or 132 column positions).
An example invocation that submits a file of possibly long lines to the printer (under the assumption that the user knows the line width of the printer to be assigned by lp):
fold -w 132 bigfile | lp
Although terminal input in canonical processing mode requires the erase character (frequently set to <backspace>) to erase the previous character (not byte or column position), terminal output is not buffered and is extremely difficult, if not impossible, to parse correctly; the interpretation depends entirely on the physical device that actually displays/prints/stores the output. In all known internationalized implementations, the utilities producing output for mixed column-width output assume that a <backspace> character backs up one column position and outputs enough <backspace> characters to return to the start of the character when <backspace> is used to provide local line motions to support underlining and emboldening operations. Since fold without the -b option is dealing with these same constraints, <backspace> is always treated as backing up one column position rather than backing up one character.
Historical versions of the fold utility assumed 1 byte was one character and occupied one column position when written out. This is no longer always true. Since the most common usage of fold is believed to be folding long lines for output to limited-length output devices, this capability was preserved as the default case. The -b option was added so that applications could fold files with arbitrary length lines into text files that could then be processed by the standard utilities. Note that although the width for the -b option is in bytes, a line is never split in the middle of a character.  (It is unspecified what happens if a width is specified that is too small to hold a single character found in the input followed by a <newline>.)
The tab stops are hardcoded to be every eighth column to meet historical practice. No new method of specifying other tab stops was invented.
PING(8)                              iputils                             PING(8)
ping - send ICMP ECHO_REQUEST to network hosts
ping [-aAbBdDfhLnOqrRUvV46] [-c count] [-F flowlabel] [-i interval] [-I interface] [-l preload] [-m mark] [-M pmtudisc_option] [-N nodeinfo_option] [-w deadline] [-W timeout] [-p pattern] [-Q tos] [-s packetsize] [-S sndbuf] [-t ttl] [-T timestamp option] [hop...] {destination}
ping uses the ICMP protocol's mandatory ECHO_REQUEST datagram to elicit an ICMP ECHO_RESPONSE from a host or gateway. ECHO_REQUEST datagrams (“pings”) have an IP and ICMP header, followed by a struct timeval and then an arbitrary number of “pad” bytes used to fill out the packet.
ping works with both IPv4 and IPv6. Using only one of them explicitly can be enforced by specifying -4 or -6.
ping can also send IPv6 Node Information Queries (RFC4620). Intermediate hops may not be allowed, because IPv6 source routing was deprecated (RFC5095).
-4 Use IPv4 only.
-6 Use IPv6 only.
-a Audible ping.
-A Adaptive ping. Interpacket interval adapts to round-trip time, so that effectively not more than one (or more, if preload is set) unanswered probe is present in the network. Minimal interval is 200msec unless super-user. On networks with low RTT this mode is essentially equivalent to flood mode.
-b Allow pinging a broadcast address.
-B Do not allow ping to change source address of probes. The address is bound to one selected when ping starts.
-c count Stop after sending count ECHO_REQUEST packets. With deadline option, ping waits for count ECHO_REPLY packets, until the timeout expires.
-d Set the SO_DEBUG option on the socket being used. Essentially, this socket option is not used by Linux kernel.
-D Print timestamp (unix time + microseconds as in gettimeofday) before each line.
-f Flood ping. For every ECHO_REQUEST sent a period “.” is printed, while for every ECHO_REPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. If interval is not given, it sets interval to zero and outputs packets as fast as they come back or one hundred times per second, whichever is more. Only the super-user may use this option with zero interval.
-F flow label IPv6 only. Allocate and set 20 bit flow label (in hex) on echo request packets. If value is zero, kernel allocates random flow label.
-h Show help.
-i interval Wait interval seconds between sending each packet. Real number allowed with dot as a decimal separator (regardless locale setup). The default is to wait for one second between each packet normally, or not to wait in flood mode. Only super-user may set interval to values less than 0.2 seconds.
-I interface interface is either an address, an interface name or a VRF name. If interface is an address, it sets source address to specified interface address. If interface is an interface name, it sets source interface to specified interface. If interface is a VRF name, each packet is routed using the corresponding routing table; in this case, the -I option can be repeated to specify a source address. NOTE: For IPv6, when doing ping to a link-local scope address, link specification (by the '%'-notation in destination, or by this option) can be used but it is no longer required.
-l preload If preload is specified, ping sends that many packets not waiting for reply. Only the super-user may select preload more than 3.
-L Suppress loopback of multicast packets. This flag only applies if the ping destination is a multicast address.
-N nodeinfo_option IPv6 only. Send ICMPv6 Node Information Queries (RFC4620), instead of Echo Request. CAP_NET_RAW capability is required.
help Show help for NI support.
name Queries for Node Names.
ipv6 Queries for IPv6 Addresses. There are several IPv6 specific flags.
ipv4 Queries for IPv4 Addresses. There is one IPv4 specific flag.
subject-name=nodename Subject name. If it contains more than one dot, fully-qualified domain name is assumed.
-n Numeric output only. No attempt will be made to lookup symbolic names for host addresses.
-O Report outstanding ICMP ECHO reply before sending next packet. This is useful together with the timestamp -D to log output to a diagnostic file and search for missing answers.
-p pattern You may specify up to 16 “pad” bytes to fill out the packet you send. This is useful for diagnosing data-dependent problems in a network. For example, -p ff will cause the sent packet to be filled with all ones.
-q Quiet output. Nothing is displayed except the summary lines at startup time and when finished.
-r Bypass the normal routing tables and send directly to a host on an attached interface. If the host is not on a directly-attached network, an error is returned. This option can be used to ping a local host through an interface that has no route through it provided the option -I is also used.
-R ping only. Record route. Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and displays the route buffer on returned packets. Note that the IP header is only large enough for nine such routes. Many hosts ignore or discard this option.
-s packetsize Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data.
-t ttl ping only. Set the IP Time to Live.
-U Print full user-to-user latency (the old behaviour). Normally ping prints network round trip time, which can be different f.e. due to DNS failures.
-v Verbose output. Do not suppress DUP replies when pinging multicast address.
-V Show version and exit.
-w deadline Specify a timeout, in seconds, before ping exits regardless of how many packets have been sent or received. In this case ping does not stop after count packet are sent, it waits either for deadline expire or until count probes are answered or for some error notification from network.
-W timeout Time to wait for a response, in seconds. The option affects only timeout in absence of any responses, otherwise ping waits for two RTTs. Real number allowed with dot as a decimal separator (regardless locale setup). 0 means infinite timeout.
When using ping for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running. Then, hosts and gateways further and further away should be “pinged”. Round-trip times and packet loss statistics are computed. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the minimum/average/maximum/mdev round-trip time numbers.
Population standard deviation (mdev), essentially an average of how far each ping RTT is from the mean RTT. The higher mdev is, the more variable the RTT is (over time). With a high RTT variability, you will have speed issues with bulk transfers (they will take longer than is strictly speaking necessary, as the variability will eventually cause the sender to wait for ACKs) and you will have middling to poor VoIP quality.
When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed. Shorter current statistics can be obtained without termination of process with signal SIGQUIT.
If ping does not receive any reply packets at all it will exit with code 1. If a packet count and deadline are both specified, and fewer than count packets are received by the time the deadline has arrived, it will also exit with code 1. On other error it exits with code 2. Otherwise it exits with code 0. This makes it possible to use the exit code to see if a host is alive or not.
This program is intended for use in network testing, measurement and management. Because of the load it can impose on the network, it is unwise to use ping during normal operations or from automated scripts.
An IP header without options is 20 bytes. An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth of ICMP header followed by an arbitrary amount of data. When a packetsize is given, this indicates the size of this extra piece of data (the default is 56). Thus the amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space (the ICMP header).
If the data space is at least of size of struct timeval ping uses the beginning bytes of this space to include a timestamp which it uses in the computation of round trip times. If the data space is shorter, no round trip times are given.
ping will report duplicate and damaged packets. Duplicate packets should never occur, and seem to be caused by inappropriate link-level retransmissions. Duplicates may occur in many situations and are rarely (if ever) a good sign, although the presence of low levels of duplicates may not always be cause for alarm.
The (inter)network layer should never treat packets differently depending on the data contained in the data portion. Unfortunately, data-dependent problems have been known to sneak into networks and remain undetected for long periods of time. In many cases the particular pattern that will have problems is something that doesn't have sufficient “transitions”, such as all ones or all zeros, or a pattern right at the edge, such as almost all zeros. It isn't necessarily enough to specify a data pattern of all zeros (for example) on the command line because the pattern that is of interest is at the data link level, and the relationship between what you type and what the controllers transmit can be complicated.
This means that if you have a data-dependent problem you will probably have to do a lot of testing to find it. If you are lucky, you may manage to find a file that either can't be sent across your network or that takes much longer to transfer than other similar length files. You can then examine this file for repeated patterns that you can test using the -p option of ping.
The TTL value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one.
The maximum possible value of this field is 255, and most Unix systems set the TTL field of ICMP ECHO_REQUEST packets to 255. This is why you will find you can “ping” some hosts, but not reach them with telnet(1) or ftp(1).
In normal operation ping prints the TTL value from the packet it receives. When a remote system receives a ping packet, it can do one of three things with the TTL field in its response:
• Set it to 255; this is what current Berkeley Unix systems do. In this case the TTL value in the received packet will be 255 minus the number of routers in the path from the remote system to the pinging host.
• The maximum IP header length is too small for options like RECORD_ROUTE to be completely useful. There's not much that can be done about this, however.
ip(8), ss(8).
As of version s20150815, the ping6 binary doesn't exist anymore. It has been merged into ping. Creating a symlink named ping6 pointing to ping will result in the same functionality as before.
ping requires CAP_NET_RAW capability to be executed 1) if the program is used for non-echo queries (See -N option), or 2) if kernel does not support non-raw ICMP sockets, or 3) if the user is not allowed to create an ICMP echo socket. The program may be used as set-uid root.
ping is part of iputils package.
CHECK-SUPPORT-STAT(1)                                      CHECK-SUPPORT-STAT(1)
check-support-status - check installed packages for security support (debian-security-support)
Version 2020.06.21~deb10u1
Search for packages whose support is limited, has already ended or will end earlier than the distribution’s end of life:
check-support-status
Search for packages with ended support from a custom list, reporting each package only once:
check-support-status \ --type ended \ --status-db /path/to/status-db \ --list /path/to/security-support-ended
--list FILE Use the given file as the database of packages whose support ends at a particular date or that is limited by specific conditions. The file format is plain text in columns, separated by one or more whitespace characters.
For --type earlyend:
•   source package name
•   last package version that will be supported
•   the date support will end
•   the rest (optional): details, and/or a URL for further information.
For --type ended:
•   last package version that is supported
•   the date support was ended
For --type limited:
If no "--list" is provided, the script is run for limited and date-defined end of support, using the lists shipped in the package.
By default, check-support-status evaluates the status of the packages according to the Debian version where it runs upon. This behavior can be modified using the DEBIAN_VERSION environment variable, e.g.
DEBIAN_VERSION=9 check-support-status
--no-heading Skips printing a headline.
--status-db FILE Use the given file to record alerts so each affected package is reported only once.
Default: No records, any affected package will be reported every time.
--except PACKAGES Do not alert for the given binary packages (comma-separated list).
Default: Alert for all packages (no exceptions).
--type TYPE One of the following:
•   "earlyend": Alert for packages whose support will end earlier than the distribution’s.
•   "ended": Alert for packages where security support has ended.
•   "limited": Alert for packages where security support is limited.
--version, --Version, -V Show the version number and exit.
Installations with mixed distributions like half-stable, half-testing are not supported.
Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
COPYRIGHT & LICENSE Copyright (C) 2014 Christoph Biedl <debian.axhn@manchmal.in-ulm.de>
This package is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License version 2 as published by the Free Software Foundation.
This package 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. If not, see <http://www.gnu.org/licenses/>
On Debian systems, the complete text of the GNU General Public License version 2 can be found in "/usr/share/common-licenses/GPL-2".
OCAMLOPT(1)                  General Commands Manual                 OCAMLOPT(1)
ocamlopt - The OCaml native-code compiler
ocamlopt [ options ] filename ...
ocamlopt.opt (same options)
The OCaml high-performance native-code compiler ocamlopt(1) compiles OCaml source files to native code object files and link these object files to produce standalone executables.
The ocamlopt(1) command has a command-line interface very close to that of ocamlc(1).  It accepts the same types of arguments and processes them sequentially, after all options have been processed:
Arguments ending in .mli are taken to be source files for compilation unit interfaces. Interfaces specify the names exported by compilation units: they declare value names with their types, define public data types, declare abstract data types, and so on. From the file x.mli, the ocamlopt(1) compiler produces a compiled interface in the file x.cmi. The interface produced is identical to that produced by the bytecode compiler ocamlc(1).