neulab/tldr huggingface dataset:
-S     use standard averaging to calculate power consumption instead of using a 120 second rolling average of capacity samples. This is only useful if the battery reports just capacity values and is an alternative method of calculating the power consumption based on the start and current battery capacity.
-t     gather temperatures from all the available thermal zones on the device. If there are no thermal zones available then nothing will be displayed.
-z     forcibly ignore zero power rate readings from the battery. Use this to gather other statistics (for example when using -c, -f, -t options) if powerstat cannot measure power (not discharging or no RAPL interface).
Measure power with the default of 10 samples with an interval of 10 seconds powerstat
Measure power with 60 samples with an interval of 1 second powerstat 1 60
Measure power and redo sampling if we are not idle and we detect fork()/exec()/exit() activity sudo powerstat -r
Measure power using the Intel RAPL interface: powerstat -R
Measure power using the Intel RAPL interface and show extra RAPL domain power readings and power measurement histogram at end of the run powerstat -RDH
Measure power and redo sampling if less that 95% idle powerstat -i 95
Wait to settle for 1 minute then measure power every 20 seconds and show any fork()/exec()/exit() activity at end of the measuring powerstat -d 60 -s 20
Measure temperature, CPU frequencies, C-states, power via RAPL domains, produce histograms, don't print repeated headings and measure every 0.5 seconds powerstat -tfcRHn 0.5
vmstat(8), powertop(8), power-calibrate(8)
powerstat was written by Colin Ian King <colin.i.king@gmail.com>
This manual page was written by Colin Ian King <colin.i.king@gmail.com>, for the Ubuntu project (but may be used by others).
Copyright Â© 2011-2021 Canonical Ltd. Copyright Colin Ian King This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
ICEWEASEL(1)                   Linux User's Manual                  ICEWEASEL(1)
iceweasel - a Web browser for X11 derived from the Mozilla browser
iceweasel [OPTIONS] [URL]
/usr/lib/iceweasel/firefox-bin [OPTIONS] [URL]
Iceweasel is an open-source web browser, designed for standards compliance, performance and portability.
iceweasel is a simple shell script that will set up the environment for the actual executable, firefox-bin.  If there is a Iceweasel browser already running, iceweasel will arrange for it to create a new browser window; otherwise it will start the Iceweasel application.
A summary of the options supported by iceweasel is included below.
GTK options --gdk-debug=FLAGS Gdk debugging flags to set
--gdk-no-debug=FLAGS Gdk debugging flags to unset
--gtk-debug=FLAGS Gtk+ debugging flags to set
--gtk-no-debug=FLAGS Gtk+ debugging flags to unset
--gtk-module=MODULE Load an additional Gtk module
--no-xshm Don't use X shared memory extension
--xim-preedit=STYLE
--xim-status=STYLE
Mozilla options -height value Set height of startup window to value pixels.
-h, -help Show summary of options.
-installer Start with Mozilla 4.x migration window.
-width value Set width of startup window to value pixels.
-v, -version Print Iceweasel version.
-no-remote Don't connect to a running iceweasel instance.
-a application-id Check for a running Iceweasel started with the specified application-id.  When iceweasel is invoked for the first time with a particular application-id, a new Iceweasel application is started; subsequent invocations of iceweasel with the same application-id will cause the already-running Iceweasel to bring up a new window.
The default is -a iceweasel.
-CreateProfile profile Create profile.  Implies -a iceweasel--profile, or -a default if profile is default.
-P profile Start with profile.  Implies -a iceweasel--profile, or -a default if profile is default.
-ProfileManager Start with profile manager.  Implies -a with a fresh unique application-id.
-UILocale locale Start with locale resources as User Interface locale. By default, it is guessed from environment and available locales for Iceweasel.
-contentLocale locale Start with locale resources as content locale. By default, it is guessed from environment and available locales for Iceweasel.
-new-window URL Open URL in a new window in an already running Iceweasel process. -new-tab URL Open URL in a new tab in an already running Iceweasel process.
-jsconsole Start with Javascript Console
-chrome url Load the specified chrome.
-safe-mode Starts Iceweasel in safe mode, that is disabling all extensions and showing a bit more debugging messages.
Debugger options -g, -debug Starts Iceweasel through a debugger (gdb by default).
--debugger program Use program as a debugger for Iceweasel. Implies -debug.
ICEWEASEL_DSP - configures the /dev/dsp wrapper to use. Accepted values are "auto", "artsdsp", "esddsp", "aoss" or "none" (default).
/usr/bin/iceweasel - shell script wrapping firefox-bin
/usr/lib/iceweasel/firefox-bin - iceweasel executable
/etc/iceweasel/iceweaselrc - file containing environment variables to be passed to Iceweasel.
${HOME}/.mozilla/firefox/rc - file containing environment variables to be passed to Iceweasel. Overrides /etc/iceweasel/iceweaselrc
To report a bug, please visit http://bugzilla.mozilla.org/
mozilla(1)
LVREDUCE(8)                  System Manager's Manual                 LVREDUCE(8)
lvreduce â€” Reduce the size of a logical volume
lvreduce option_args position_args [ option_args ]
lvreduce reduces the size of an LV. The freed logical extents are returned to the VG to be used by other LVs. A copy-on-write snapshot LV can also be reduced if less space is needed to hold COW blocks. Use lvconvert(8) to change the number of data images in a RAID or mirrored LV.
Be careful when reducing an LV's size, because data in the reduced area is lost. Ensure that any file system on the LV is resized before running lvreduce so that the removed extents are not in use by the file system.
Sizes will be rounded if necessary. For example, the LV size must be an exact number of extents, and the size of a striped segment must be a multiple of the number of stripes.
lvreduce -L|--size [-]Size[m|UNIT] LV [ -l|--extents [-]Number[PERCENT] ] [ -A|--autobackup y|n ] [ -f|--force ] [ -n|--nofsck ] [ -r|--resizefs ] [    --noudevsync ] [    --reportformat basic|json ] [ COMMON_OPTIONS ]
-l|--extents [-]Number[PERCENT] Specifies the new size of the LV in logical extents.  The --size and --extents options are alternate methods of specifying size. The total number of physical extents used will be greater when redundant data is needed for RAID levels.  An alternate syntax allows the size to be determined indirectly as a percentage of the size of a related VG, LV, or set of PVs. The suffix %VG denotes the total size of the VG, the suffix %FREE the remaining free space in the VG, and the suffix %PVS the free space in the specified PVs.  For a snapshot, the size can be expressed as a percentage of the total size of the origin LV with the suffix %ORIGIN (100%ORIGIN provides space for the whole origin).  When expressed as a percentage, the size defines an upper limit for the number of logical extents in the new LV. The precise number of logical extents in the new LV is not determined until the command has completed.  When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
-L|--size [-]Size[m|UNIT] Specifies the new size of the LV.  The --size and --extents options are alternate methods of specifying size.  The total number of physical extents used will be greater when redundant data is needed for RAID levels.  When the plus + or minus - prefix is used, the value is not an absolute size, but is relative and added or subtracted from the current size.
Reduce the size of an LV by 3 logical extents: lvreduce -l -3 vg00/lvol1
CARGO-DOC(1)                 General Commands Manual                CARGO-DOC(1)
cargo-doc - Build a package's documentation
cargo doc [options]
Build the documentation for the local package and all dependencies. The output is placed in target/doc in rustdoc's usual format.
Documentation Options --open Open the docs in a browser after building them. This will use your default browser unless you define another one in the BROWSER environment variable or use the doc.browser <https://doc.rust-lang.org/cargo/reference/config.html#docbrowser> configuration option.
--no-deps Do not build documentation for dependencies.
--document-private-items Include non-public items in the documentation. This will be enabled by default if documenting a binary target.
-p spec..., --package spec... Document only the specified packages. See cargo-pkgid(1) for the SPEC format. This flag may be specified multiple times and supports common Unix glob patterns like *, ? and []. However, to avoid your shell accidentally expanding glob patterns before Cargo handles them, you must use single quotes or double quotes around each pattern.
--workspace Document all members in the workspace.
Target Selection When no target selection options are given, cargo doc will document all binary and library targets of the selected package. The binary will be skipped if its name is the same as the lib target. Binaries are skipped if they have required-features that are missing.
The default behavior can be changed by setting doc = false for the target in the manifest settings. Using target selection options will ignore the doc flag and will always document the given target.
--lib Document the package's library.
--bin name... Document the specified binary. This flag may be specified multiple times and supports common Unix glob patterns.
--bins Document all binary targets.
--example name... Document the specified example. This flag may be specified multiple times and supports common Unix glob patterns.
--examples Document all example targets.
Compilation Options --target triple Document for the given architecture. The default is the host architecture. The general format of the triple is <arch><sub>-<vendor>-<sys>-<abi>. Run rustc --print target-list for a list of supported targets.
--release Document optimized artifacts with the release profile. See also the --profile option for choosing a specific profile by name.
--profile name Document with the given profile. See the the reference <https://doc.rust-lang.org/cargo/reference/profiles.html> for more details on profiles.
--ignore-rust-version Document the target even if the selected Rust compiler is older than the required Rust version as configured in the project's rust-version field.
1. Build the local package documentation and its dependencies and output to target/doc.
cargo doc
cargo(1), cargo-rustdoc(1), rustdoc(1)
IPERF(1)                          User Manuals                          IPERF(1)
iperf - perform network throughput tests
iperf -s [options]
iperf -c server [options]
iperf -u -s [options]
iperf -u -c server [options]
iperf is a tool for performing network throughput measurements.  It can test either TCP or UDP throughput.  To perform an iperf test the user must establish both a server (to discard traffic) and a client (to generate traffic).
-b, --bandwidth set the target bandwidth and optional standard devation per <mean>,[<stdev>] (See NOTES for suffixes)
-e, --enhanced Display enhanced output in reports otherwise use legacy report (ver 2.0.5) formatting (see notes)
-f, --format [abkmgBKMG] format to report: adaptive, bits, Bytes, Kbits, Mbits, Gbits, KBytes, MBytes, GBytes (see NOTES for more)
-h, --help print a help synopsis
-i, --interval n pause n seconds between periodic bandwidth reports
-l, --len n[kmKM] set read/write buffer size (TCP) or length (UDP) to n (TCP default 128K, UDP default 1470)
--l2checks perform layer 2 length checks on received UDP packets (requires systems that support packet sockets, e.g. Linux)
-m, --print_mss print TCP maximum segment size (MTU - TCP/IP header)
-o, --output filename output the report or error message to this specified file
-p, --port n set server port to listen on/connect to to n (default 5001)
-u, --udp use UDP rather than TCP
-w, --window n[kmKM] TCP window size (socket buffer size)
-z, --realtime Request real-time scheduler, if supported.
-B, --bind host bind to host, ip address or multicast address and optional port (see notes)
-C, --compatibility for use with older versions does not sent extra msgs
-M, --mss n set TCP maximum segment size (MTU - 40 bytes)
-N, --nodelay set TCP no delay, disabling Nagle's Algorithm
-v, --version print version information and quit
-x, --reportexclude [CDMSV] exclude C(connection) D(data) M(multicast) S(settings) V(server) reports
-y, --reportstyle C|c if set to C or c report results as CSV (comma separated values)
-b, --bandwidth n[kmgKMG] set target read rate to n bits/sec. TCP only for the server.
-s, --server run in server mode
--udp-histogram[=binwidth[u],bincount,[lowerci],[upperci]] output UDP latency histograms, bin width (default 1 millisecond, append u for microseconds,) bincount is total bins (default 1000), ci is confidence interval between 0-100% (default lower 5%, upper 95%)
-B, --bind ip | ip%device bind src ip addr and optional src device for receiving
-D, --daemon run the server as a daemon.  On Windows this will run the specified command-line under the IPerfService, installing the service if necessary.  Note the service is not configured to auto- start or restart - if you need a self-starting service you will need to create an init script or use Windows "sc" commands.
-H, --ssm-host host Set the source host (ip addr) per SSM multicast, i.e. the S of the S,G
-R, --remove remove the IPerfService (Windows only).
-U, --single_udp run in single threaded UDP mode
-V, --ipv6_domain Enable IPv6 reception by setting the domain and socket to AF_INET6 (Can receive on both IPv4 and IPv6)
-b, --bandwidth n[kmgKMG] | npps set target bandwidth to n bits/sec (default 1 Mbit/sec) or n packets per sec.  This may be used with TCP or UDP.  For variable loads use format mean,standard deviation
-c, --client host run in client mode, connecting to host
-d, --dualtest Do a bidirectional test simultaneously.
--fq-rate n[kmgKMG] Set a rate to be used with fair-queueing based socket-level pacing, in bytes or bits per second. Only available on platforms supporting the SO_MAX_PACING_RATE socket option. (Note: Here the suffixes indicate bytes/sec or bits/sec per use of uppercase or lowercase, respectively)
--incr-dstip increment the destination ip address when using the parallel (-P) option
--ipg n set the interpacket gap to n (units of milliseconds) for packets within an isochronous frame (burst), requires --isochronous
--isochronous[=fps:mean,stdev] send isochronous traffic with frequency frames per second and load defined by mean and standard deviation using a log normal distribution, defaults to 60:20m,0.  (Note: Here the suffixes indicate bytes/sec or bits/sec per use of uppercase or lowercase, respectively)
-n, --num n[kmKM] number of bytes to transmit (instead of -t)
-r, --tradeoff Do a bidirectional test individually - client-to-server, followed by a reversed test, server-to-client
-t, --time n time in seconds to listen for new traffic connections, receive traffic or transmit traffic (Defaults: transmit is 10 secs while listen and receive are indefinite)
--trip-time request the server to report the total trip time, i.e from the client's 3WHS done to client's (fin, fin-ack or socket close) (requires synchronized clocks)
--txstart-time n.n set the txstart-time to n.n using unix or epoch time format (supports nanonsecond resolution, e.g 1536014418.839992457)
-B, --bind ip | ip:port | ipv6 -V | [ipv6]:port -V bind src ip addr and optional port as the source of traffic (see notes)
-F, --fileinput name input the data to be transmitted from a file
-I, --stdin input the data to be transmitted from stdin
-L, --listenport n port to recieve bidirectional tests back on
-P, --parallel n number of parallel client threads to run
-R, --reverse reverse the traffic flow after header exchange, useful for testing through firewalls
-S, --tos set the socket's IP_TOS (byte) field
-T, --ttl n time-to-live, for multicast (default 1) -V, --ipv6_domain Set the domain to IPv6 (send packets over IPv6)
-X, --peerdetect run server version detection prior to traffic.
-Z, --linux-congestion algo set TCP congestion control algorithm (Linux only)
TCP tests (client)
iperf -c <host> -e -i 1 ------------------------------------------------------------ Client connecting to <host>, TCP port 5001 with pid 5149 Write buffer size:  128 KByte TCP window size:  340 KByte (default) ------------------------------------------------------------ [  3] local 45.56.85.133 port 49960 connected with 45.33.58.123 port 5001 (ct=3.23 ms) [ ID] Interval        Transfer    Bandwidth       Write/Err  Rtry Cwnd/RTT        NetPwr [  3] 0.00-1.00 sec   126 MBytes  1.05 Gbits/sec  1006/0          0 56K/626 us  210636.47 [  3] 1.00-2.00 sec   138 MBytes  1.15 Gbits/sec  1100/0        299 483K/3884 us  37121.32 [  3] 2.00-3.00 sec   137 MBytes  1.15 Gbits/sec  1093/0         24 657K/5087 us  28162.31 [  3] 3.00-4.00 sec   126 MBytes  1.06 Gbits/sec  1010/0        284 294K/2528 us  52366.58 [  3] 4.00-5.00 sec   117 MBytes   980 Mbits/sec  935/0        373 487K/2025 us  60519.66 [  3] 5.00-6.00 sec   144 MBytes  1.20 Gbits/sec  1149/0          2 644K/3570 us  42185.36 [  3] 6.00-7.00 sec   126 MBytes  1.06 Gbits/sec  1011/0        112 582K/5281 us  25092.56 [  3] 7.00-8.00 sec   110 MBytes   922 Mbits/sec  879/0         56 279K/1957 us  58871.89 [  3] 8.00-9.00 sec   127 MBytes  1.06 Gbits/sec  1014/0         46 483K/3372 us  39414.89 [  3] 9.00-10.00 sec   132 MBytes  1.11 Gbits/sec  1054/0          0 654K/3380 us  40872.75 [  3] 0.00-10.00 sec  1.25 GBytes  1.07 Gbits/sec  10251/0       1196 -1K/3170 us  42382.03
where (per -e,) ct= TCP connect time (or three way handshake time 3WHS) Write/Err Total number of successful socket writes. Total number of non-fatal socket write errors Rtry Total number of TCP retries Cwnd/RTT (*nix only) TCP congestion window and round trip time (sampled) NetPwr (*nix only) Network power defined as (throughput / RTT)
TCP tests (server)
iperf -s -e -i 1 -l 8K ------------------------------------------------------------ Server listening on TCP port 5001 with pid 13430 Read buffer size: 8.00 KByte TCP window size: 85.3 KByte (default) ------------------------------------------------------------ [  4] local 45.33.58.123 port 5001 connected with 45.56.85.133 port 49960 [ ID] Interval        Transfer    Bandwidth       Reads   Dist(bin=1.0K) [  4] 0.00-1.00 sec   124 MBytes  1.04 Gbits/sec  22249 798:2637:2061:767:2165:1563:589:11669 [  4] 1.00-2.00 sec   136 MBytes  1.14 Gbits/sec  24780 946:3227:2227:790:2427:1888:641:12634 [  4] 2.00-3.00 sec   137 MBytes  1.15 Gbits/sec  24484 1047:2686:2218:810:2195:1819:728:12981 [  4] 3.00-4.00 sec   126 MBytes  1.06 Gbits/sec  20812 863:1353:1546:614:1712:1298:547:12879 [  4] 4.00-5.00 sec   117 MBytes   984 Mbits/sec  20266 769:1886:1828:589:1866:1350:476:11502 [  4] 5.00-6.00 sec   143 MBytes  1.20 Gbits/sec  24603 1066:1925:2139:822:2237:1827:744:13843 [  4] 6.00-7.00 sec   126 MBytes  1.06 Gbits/sec  22635 834:2464:2249:724:2269:1646:608:11841 [  4] 7.00-8.00 sec   110 MBytes   921 Mbits/sec  21107 842:2437:2747:592:2871:1903:496:9219 [  4] 8.00-9.00 sec   126 MBytes  1.06 Gbits/sec  22804 1038:1784:2639:656:2738:1927:573:11449 [  4] 9.00-10.00 sec   133 MBytes  1.11 Gbits/sec  23091 1088:1654:2105:710:2333:1928:723:12550 [  4] 0.00-10.02 sec  1.25 GBytes  1.07 Gbits/sec  227306 9316:22088:21792:7096:22893:17193:6138:120790
where (per -e,) Reads Total number of socket reads Dist(bin=size) Eight bin histogram of the socket reads returned byte count.  Bin width is set per size.  Bins are separated by a colon.  In the example, the bins are 0-1K, 1K-2K, .., 7K-8K.
UDP tests (client)
iperf -c <host> -e -i 1 -u -b 10m ------------------------------------------------------------ Client connecting to <host>, UDP port 5001 with pid 5169 Sending 1470 byte datagrams, IPG target: 1176.00 us (kalman adjust) UDP buffer size:  208 KByte (default) ------------------------------------------------------------ [  3] local 45.56.85.133 port 32943 connected with 45.33.58.123 port 5001 [ ID] Interval        Transfer     Bandwidth      Write/Err  PPS [  3] 0.00-1.00 sec  1.19 MBytes  10.0 Mbits/sec  852/0      851 pps [  3] 1.00-2.00 sec  1.19 MBytes  10.0 Mbits/sec  850/0      850 pps [  3] 2.00-3.00 sec  1.19 MBytes  10.0 Mbits/sec  850/0      850 pps [  3] 3.00-4.00 sec  1.19 MBytes  10.0 Mbits/sec  851/0      850 pps [  3] 4.00-5.00 sec  1.19 MBytes  10.0 Mbits/sec  850/0      850 pps [  3] 5.00-6.00 sec  1.19 MBytes  10.0 Mbits/sec  850/0      850 pps [  3] 6.00-7.00 sec  1.19 MBytes  10.0 Mbits/sec  851/0      850 pps [  3] 7.00-8.00 sec  1.19 MBytes  10.0 Mbits/sec  850/0      850 pps [  3] 8.00-9.00 sec  1.19 MBytes  10.0 Mbits/sec  851/0      850 pps [  3] 0.00-10.00 sec  11.9 MBytes  10.0 Mbits/sec  8504/0      850 pps [  3] Sent 8504 datagrams [  3] Server Report: [  3] 0.00-10.00 sec  11.9 MBytes  10.0 Mbits/sec   0.047 ms    0/ 8504 (0%)  0.537/ 0.392/23.657/ 0.497 ms  850 pps  2329.37
where (per -e,) Write/Err Total number of successful socket writes. Total number of non-fatal socket write errors PPS Transmit packet rate in packets per second
UDP tests (server)
iperf -s -e -i 1 -u ------------------------------------------------------------ Server listening on UDP port 5001 with pid 13496 Receiving 1470 byte datagrams UDP buffer size:  208 KByte (default) ------------------------------------------------------------ [  3] local 45.33.58.123 port 5001 connected with 45.56.85.133 port 32943 [ ID] Interval        Transfer     Bandwidth        Jitter   Lost/Total Latency avg/min/max/stdev PPS  NetPwr [  3] 0.00-1.00 sec  1.19 MBytes  10.0 Mbits/sec   0.057 ms    0/  851 (0%)  0.475/ 0.408/ 1.898/ 0.090 ms  851 pps  2633.56 [  3] 1.00-2.00 sec  1.19 MBytes  10.0 Mbits/sec   0.039 ms    0/  851 (0%)  0.669/ 0.405/16.256/ 1.375 ms  850 pps  1869.32 [  3] 2.00-3.00 sec  1.19 MBytes  10.0 Mbits/sec   0.038 ms    0/  850 (0%)  0.795/ 0.395/23.657/ 2.138 ms  850 pps  1572.05 [  3] 3.00-4.00 sec  1.19 MBytes  10.0 Mbits/sec   0.045 ms    0/  850 (0%)  0.475/ 0.403/ 3.477/ 0.148 ms  850 pps  2628.58 [  3] 4.00-5.00 sec  1.19 MBytes  10.0 Mbits/sec   0.043 ms    0/  851 (0%)  0.463/ 0.400/ 1.458/ 0.068 ms  850 pps  2699.88 [  3] 5.00-6.00 sec  1.19 MBytes  10.0 Mbits/sec   0.032 ms    0/  850 (0%)  0.486/ 0.404/ 2.658/ 0.154 ms  850 pps  2572.21 [  3] 6.00-7.00 sec  1.19 MBytes  10.0 Mbits/sec   0.055 ms    0/  850 (0%)  0.469/ 0.404/ 2.768/ 0.108 ms  850 pps  2664.82 [  3] 7.00-8.00 sec  1.19 MBytes  10.0 Mbits/sec   0.039 ms    0/  851 (0%)  0.571/ 0.400/12.452/ 0.855 ms  850 pps  2192.68 [  3] 8.00-9.00 sec  1.19 MBytes  10.0 Mbits/sec   0.083 ms    0/  850 (0%)  0.475/ 0.392/ 3.702/ 0.196 ms  850 pps  2628.29 [  3] 9.00-10.00 sec  1.19 MBytes  10.0 Mbits/sec   0.047 ms    0/  850 (0%)  0.493/ 0.396/ 6.010/ 0.343 ms  850 pps  2534.89 [  3] 0.00-10.00 sec  11.9 MBytes  10.0 Mbits/sec   0.047 ms    0/ 8504 (0%)  0.537/ 0.392/23.657/ 0.867 ms  850 pps  2329.37
where (per -e,) Latency End to end latency in mean/minimum/maximum/standard deviation format (Note: requires the client's and server's system clocks to be synchronized to a common reference, e.g. using precision time protocol PTP.  A GPS disciplined OCXO is a recommended reference.) PPS Received packet rate in packets per second NetPwr Network power defined as (throughput / latency)
Isochronous UDP tests (client)
iperf -c 192.168.100.33 -u -e -i 1 --isochronous=60:100m,10m --realtime ------------------------------------------------------------ Client connecting to 192.168.100.33, UDP port 5001 with pid 14971 UDP isochronous: 60 frames/sec mean= 100 Mbit/s, stddev=10.0 Mbit/s, Period/IPG=16.67/0.005 ms UDP buffer size:  208 KByte (default) ------------------------------------------------------------ [  3] local 192.168.100.76 port 42928 connected with 192.168.100.33 port 5001 [ ID] Interval        Transfer     Bandwidth      Write/Err  PPS frames:tx/missed/slips [  3] 0.00-1.00 sec  12.0 MBytes   101 Mbits/sec  8615/0     8493 pps 62/0/0 [  3] 1.00-2.00 sec  12.0 MBytes   100 Mbits/sec  8556/0     8557 pps 60/0/0 [  3] 2.00-3.00 sec  12.0 MBytes   101 Mbits/sec  8586/0     8586 pps 60/0/0 [  3] 3.00-4.00 sec  12.1 MBytes   102 Mbits/sec  8687/0     8687 pps 60/0/0 [  3] 4.00-5.00 sec  11.8 MBytes  99.2 Mbits/sec  8468/0     8468 pps 60/0/0 [  3] 5.00-6.00 sec  11.9 MBytes  99.8 Mbits/sec  8519/0     8520 pps 60/0/0 [  3] 6.00-7.00 sec  12.1 MBytes   102 Mbits/sec  8694/0     8694 pps 60/0/0 [  3] 7.00-8.00 sec  12.1 MBytes   102 Mbits/sec  8692/0     8692 pps 60/0/0 [  3] 8.00-9.00 sec  11.9 MBytes   100 Mbits/sec  8537/0     8537 pps 60/0/0 [  3] 9.00-10.00 sec  11.8 MBytes  99.0 Mbits/sec  8450/0     8450 pps 60/0/0 [  3] 0.00-10.01 sec   120 MBytes   100 Mbits/sec  85867/0     8574 pps 602/0/0 [  3] Sent 85867 datagrams [  3] Server Report: [  3] 0.00-9.98 sec   120 MBytes   101 Mbits/sec   0.009 ms  196/85867 (0.23%)  0.665/ 0.083/ 1.318/ 0.174 ms 8605 pps  18903.85
where (per -e,) frames:tx/missed/slips Total number of isochronous frames or bursts. Total number of frame ids not sent.  Total number of frame slips
Isochronous UDP tests (server)
iperf -s -e -u --udp-histogram=100u,2000 --realtime ------------------------------------------------------------ Server listening on UDP port 5001 with pid 5175 Receiving 1470 byte datagrams UDP buffer size:  208 KByte (default) ------------------------------------------------------------ [  3] local 192.168.100.33 port 5001 connected with 192.168.100.76 port 42928 isoch (peer 2.0.13-alpha) [ ID] Interval        Transfer     Bandwidth        Jitter   Lost/Total Latency avg/min/max/stdev PPS  NetPwr  Frames/Lost [  3] 0.00-9.98 sec   120 MBytes   101 Mbits/sec   0.010 ms  196/85867 (0.23%)  0.665/ 0.083/ 1.318/ 0.284 ms 8585 pps  18903.85  601/1 [  3] 0.00-9.98 sec T8(f)-PDF: bin(w=100us):cnt(85671)=1:2,2:844,3:10034,4:8493,5:8967,6:8733,7:8823,8:9023,9:8901,10:8816,11:7730,12:4563,13:741,14:1 (5.00/95.00%=3/12,Outliers=0,obl/obu=0/0) [  3] 0.00-9.98 sec F8(f)-PDF: bin(w=100us):cnt(598)=15:2,16:1,17:27,18:68,19:125,20:136,21:103,22:83,23:22,24:23,25:5,26:3 (5.00/95.00%=17/24,Outliers=0,obl/obu=0/0)
where, Frames/lost Total number of frames (or bursts) received.  Total number of bursts lost or errored T8-PDF(f) Latency histogram for packets F8-PDF(f) Latency histogram for frames
Note:  The environment variable option settings haven't been maintained well.  See the source code if these are of interest.
Some numeric options support format characters per '<value>c' (e.g. 10M) where the c format characters are k,m,g,K,M,G.  Lowercase format characters are 10^3 based and uppercase are 2^n based, e.g. 1k = 1000, 1K = 1024, 1m = 1,000,000 and 1M = 1,048,576
The -b option supports variable offered loads through the <mean>,<standard deviation> format, e.g. -b 100m,10m on the client.  The distribution used is log normal.  Similar for the isochronous option.
The -e or --enhanced latency output on the UDP servers assumes the clients' and servers' system clocks are synchronized.  Network Time Protocol (NTP) or Precision Time Protocol (PTP) are commonly used for this.  The reference clock(s) or oscillator's error will also affect the accuracy of UDP latency measurements.
The -B option affects the bind() system call.  This is typically used to bind to a particular IP address. Only packets destined to that IP address will be received while any transmitted packets will carry that IP address as their source. The bind() does not control anything about the routing of transmitted packets. So, for example, if the IP address of eth0 is used for -B and the routing table for the destination IP address (per -c) resolves the ouput interface to be eth1, then the host will send the packet out device eth1 with the source IP address of eth0.  To affect the physical output interface (e.g. dual homed systems) the host's routing table(s) need to be configured, e.g. configure policy routing per each -B source address.
The TCP connect time (or three way handshake) can be seen on the iperf client when the -e (--enhancedreports) option is set. Look for the ct=<value> in the connected message, e.g.in '[ 3] local 192.168.1.4 port 48736 connected with 192.168.1.1 port 5001 (ct=1.84 ms)' shows the 3WHS took 1.84 milliseconds.
The network power (NetPwr) metric is experimental.  It's a convenience function defined as throughput/delay.  For TCP, the delay is the sampled RTT times.  For UDP the delay is the end/end latency.  Don't confuse this with the physics definition of power (delta energy/delta time) but more of a measure of a desireable property divided by an undesireable property.  Also note, one must use -i interval with TCP to get this as that's what sets the RTT sampling rate.  The metric is scaled to assist with human readability.  (Note: if this metric goes beyond the experimental state we'll consider a supporting and RTT sampling rate independent of the -i interval.)
This section needs to be filled in.
See https://sourceforge.net/p/iperf2/tickets/
Iperf2, based from iperf (originally written by Mark Gates and Alex Warshavsky), has a goal of maintainence with some feature enhancement. Other contributions from Ajay Tirumala, Jim Ferguson, Jon Dugan <jdugan at x1024 dot net>, Feng Qin, Kevin Gibbs, John Estabrook <jestabro at ncsa.uiuc.edu>, Andrew Gallatin <gallatin at gmail.com>, Stephen Hemminger <shemminger at linux-foundation.org>, Tim Auckland <tim.auckland at gmail.com>, Robert J. McMahon <rjmcmahon at rjmcmahon.com>
http://sourceforge.net/projects/iperf2/
ncc(1)                       General Commands Manual                      ncc(1)
ncc - nesC compiler for TinyOS
ncc [-target=pc|mica|mica2|mica2dot|...] [-tossim] [-board=micasb|basicsb|micawb|...] [-tosdir=dir] [-tosscheduler=...] [-nostdinc] [--version] [-print-tosdir] [-print-platforms] [-print-target] [any nescc option] [any gcc option] files...
ncc is an extension to nescc that knows how to compile nesC applications for a TinyOS environment. If invoked on regular C files, it behaves like gcc. When invoked on a nesC component or interface (.nc extension) file it compiles and links (except if the usual -c, -S, -E or -fsyntax-only options are used) that component with the other files specified on the command line.
ncc just invokes nescc with extra options based on the selected platform and sensorboard(s). And nescc itself just invokes gcc. Thus, for a full understanding of possible ncc options you should read the nescc and gcc man pages.
ncc accepts all gcc and nescc options, and some additional TinyOS specific options:
-target=X Specify the target architecture for this compilation. If -tossim is also specified, the compilation uses the tossim environment and produces a locally executable file. The default target is specified in the .default-platform file in your TinyOS directory (see -tosdir option), and defaults to mica if that file is absent. A platform that is not in the TinyOS distribution can be used if its directory is specified with an explicit -I directive (the platform name is taken from the directory's name, platform directories are recognised by the presence of a .platform file).
-tosdir=dir Specify the location of TinyOS. This location can also be specified with the TOSDIR environment variable. If the variable and the option are both given, ncc uses the value specified with the option. If neither the environment variable or option are specified, ncc uses its compiled-in TinyOS directory.
-tosscheduler=component,unique-string,interface-name,interface- definition,run-event,post-command By  default,  nesC  compiles uses of task void taskname() ... to void taskname(), and post taskname() to TOS_post(taskname).
With this option, each task gets  its  own  interface-definition interface, the task implementation is transformed into a run-event event and posts becomes a call to the post-command  command.  This per-task interface is automatically connected to the parameterised interface-name interface of scheduler component component.  The parameter id for the connection is chosen with unique("unique- string").
If this option is not set explicity, its parameters are assigned by default as follows:
-tosscheduler=TinySchedulerC,TinySchedulerC.TaskBasic,TaskBasic,TaskBasic,runTask,postTask
-tossim Compile for the TOSSIM environment rather than a native platform. Every directory in the search path will be duplicated, with the first copy having /sim appended to it.
-print-tosdir Print the TinyOS directory to be used and exit, taking into account the -tosdir option and TOSDIR environment variable. No compilation occurs when -print-tosdir is used.
-print-platforms Print the valid TinyOS platforms, including those made available by explicit -I directives (see -target option).
-print-target Print the name of the selected target. Most useful when -target is not specified.
-nostdinc Do not automatically include the TinyOS directories in the search path. See the discussion of search paths below for more details.
-board=Y Specify one (or more) sensor boards. This effects the search path and preprocessor symbols. The set of boards is set by the TinyOS distribution (see the tos/sensorboards directory). As with targets, a sensorboard directory can be made available via an explicit -I directive (sensorboard directories are recognised by the presence of a .sensor file).
--version Print the version of ncc, nescc and of the gcc compiler used for the selected target.
If you wish to compile a component Bar.nc to a C file, you can do:
ncc -c -o /dev/null -fnesc-cfile=Bar.c Bar.nc
ncc performs the following substitutions on the directories specified with the -I option: %T is replaced by the TinyOS directory, %p is replaced by the selected target, %P is replaced by the target's platform directory, %% is replaced by %.
Except when -nostdinc is specified, the search path for nesC components is as follows, where tosdir is the TinyOS directory requested and target is the selected target:
*      The current directory
*      -I directives (in option order)
*      %T/sensorboards/boardname, for each -board=boardname option specified (in option order) - except if the sensorboard was found via an explicit -I directive
*      %T/platform/%p  - except if the platform was found via an explicit -I directive
*      Additional directories requested by the selected target (e.g., %T/platform/avrmote for the mica target)
*      %T/interfaces
*      %T/system
*      %T/lib
*      NESCPATH environment variable directories (note that %T and %p subsitution is not performed on these directories).
When -nostdinc is specified, the search path is simply:
*      -I directives
*      NESCPATH environment variable directories
In addition to the preprocessor symbols defined by gcc and nescc, ncc defines:
PLATFORM_target where target is the selected target name, converted to upper case
BOARD_boardname for each -board=boardname option (the boardname is converted to upper case)
TOSDIR If the -tosdir=dir option is not used, the TOSDIR environment variable specifies the location of TinyOS.
gcc(1), platform-specific gcc, nescc(1)
ncc is built over nescc, which handles the non-TinyOS-specific functionality of ncc. Users of nesC in a non-TinyOS context may prefer to use nescc (see the source code of ncc and nescc for details).
ZLESS(1)                     General Commands Manual                    ZLESS(1)
zless - file perusal filter for crt viewing of compressed text
zless [ name ...  ]
The zless command is a filter which allows examination of compressed or plain text files one screenful at a time on a soft-copy terminal.  It is the equivalent of setting the environment variable LESSOPEN to '|gzip -cdfq -- %s', and the environment variable LESSMETACHARS to '<space><tab><newline>;*?"()<>[|&^`#\$%=~', and then running less. However, enough people seem to think that having the command zless available is important to be worth providing it.
zmore(1), less(1)
The zless command does not work with compressed data that is piped to it via standard input; it requires that input files be specified as arguments.  To read compressed data from a pipe, you can use ...|gunzip|less instead of ...|zless.
Copyright © 2006-2007, 2015-2021 Free Software Foundation, Inc. Copyright © 1992, 1993 Jean-loup Gailly
JEKYLL(1)                         User Commands                        JEKYLL(1)
Jekyll - is a blogaware, static site generator.
jekyll # . -> ./_site
jekyll <path to write generated site> # . -> <path>
jekyll <path to source> <path to write generated site> # <path> -> <path>
jekyll import <importer name> <options> # imports posts using named import script
Configuration is read from '<source>/_config.yml' but can be overridden using the following options:
--file [PATH] File to import from
--dbname [TEXT] DB to import from
--user [TEXT] Username to use when importing
--pass [TEXT] Password to use when importing
--host [HOST ADDRESS] Host to import from
--site [SITE NAME] Site to import from
--[no-]safe Safe mode (default unsafe)
--[no-]auto Auto-regenerate
--server [PORT] Start web server (default port 4000)
--no-server Do not start a web server
--base-url [BASE_URL] Serve website from a given base URL (default '/'
--[no-]lsi Use LSI for better related posts
--[no-]pygments Use pygments to highlight code
--rdiscount Use rdiscount gem for Markdown
--redcarpet Use redcarpet gem for Markdown
--kramdown Use kramdown gem for Markdown
--time [TIME] Time to generate the site for
--[no-]future Render future dated posts
--permalink [TYPE] Use 'date' (default) for YYYY/MM/DD
--paginate [POSTS_PER_PAGE] Paginate a blog's posts
--limit_posts [MAX_POSTS] Limit the number of posts to publish
--url [URL] Set custom site.url
--version Display current version
This manual page was written by Youhei SASAKI <uwabami@gfd-dennou.org>, for the Debian GNU/Linux system(but may be used by others).
SQLITE3(1)                   General Commands Manual                  SQLITE3(1)
sqlite3 - A command line interface for SQLite version 3
sqlite3 [options] [databasefile] [SQL]
sqlite3 is a terminal-based front-end to the SQLite library that can evaluate queries interactively and display the results in multiple formats.  sqlite3 can also be used within shell scripts and other applications to provide batch processing features.
To start a sqlite3 interactive session, invoke the sqlite3 command and optionally provide the name of a database file.  If the database file does not exist, it will be created.  If the database file does exist, it will be opened.
For example, to create a new database file named "mydata.db", create a table named "memos" and insert a couple of records into that table:
$ sqlite3 mydata.db SQLite version 3.8.8 Enter ".help" for instructions sqlite> create table memos(text, priority INTEGER); sqlite> insert into memos values('deliver project description', 10); sqlite> insert into memos values('lunch with Christine', 100); sqlite> select * from memos; deliver project description|10 lunch with Christine|100 sqlite>
If no database name is supplied, the ATTACH sql command can be used to attach to existing or create new database files.  ATTACH can also be used to attach to multiple databases within the same interactive session. This is useful for migrating data between databases, possibly changing the schema along the way.
Optionally, a SQL statement or set of SQL statements can be supplied as a single argument.  Multiple statements should be separated by semi-colons.
$ sqlite3 -line mydata.db 'select * from memos where priority > 20;' text = lunch with Christine priority = 100
SQLITE META-COMMANDS The interactive interpreter offers a set of meta-commands that can be used to control the output format, examine the currently attached database files, or perform administrative operations upon the attached databases (such as rebuilding indices).   Meta-commands are always prefixed with a dot (.).
A list of available meta-commands can be viewed at any time by issuing the '.help' command.  For example:
sqlite> .help .backup ?DB? FILE      Backup DB (default "main") to FILE .bail on|off           Stop after hitting an error.  Default OFF .clone NEWDB           Clone data into NEWDB from the existing database .databases             List names and files of attached databases .dump ?TABLE? ...      Dump the database in an SQL text format If TABLE specified, only dump tables matching LIKE pattern TABLE. .echo on|off           Turn command echo on or off .eqp on|off            Enable or disable automatic EXPLAIN QUERY PLAN .exit                  Exit this program .explain ?on|off?      Turn output mode suitable for EXPLAIN on or off. With no args, it turns EXPLAIN on. .fullschema            Show schema and the content of sqlite_stat tables .headers on|off        Turn display of headers on or off .help                  Show this message .import FILE TABLE     Import data from FILE into TABLE .indices ?TABLE?       Show names of all indices If TABLE specified, only show indices for tables matching LIKE pattern TABLE. .load FILE ?ENTRY?     Load an extension library .log FILE|off          Turn logging on or off.  FILE can be stderr/stdout .mode MODE ?TABLE?     Set output mode where MODE is one of: csv      Comma-separated values column   Left-aligned columns.  (See .width) html     HTML <table> code insert   SQL insert statements for TABLE line     One value per line list     Values delimited by .separator string tabs     Tab-separated values tcl      TCL list elements .nullvalue STRING      Use STRING in place of NULL values .once FILENAME         Output for the next SQL command only to FILENAME .open ?FILENAME?       Close existing database and reopen FILENAME .output ?FILENAME?     Send output to FILENAME or stdout .print STRING...       Print literal STRING .prompt MAIN CONTINUE  Replace the standard prompts .quit                  Exit this program .read FILENAME         Execute SQL in FILENAME .restore ?DB? FILE     Restore content of DB (default "main") from FILE .save FILE             Write in-memory database into FILE .schema ?TABLE?        Show the CREATE statements If TABLE specified, only show tables matching LIKE pattern TABLE. .separator STRING ?NL? Change separator used by output mode and .import NL is the end-of-line mark for CSV .shell CMD ARGS...     Run CMD ARGS... in a system shell .show                  Show the current values for various settings .stats on|off          Turn stats on or off .system CMD ARGS...    Run CMD ARGS... in a system shell .tables ?TABLE?        List names of tables If TABLE specified, only list tables matching LIKE pattern TABLE. .timeout MS            Try opening locked tables for MS milliseconds .timer on|off          Turn SQL timer on or off .trace FILE|off        Output each SQL statement as it is run .vfsname ?AUX?         Print the name of the VFS stack .width NUM1 NUM2 ...   Set column widths for "column" mode Negative values right-justify sqlite>
sqlite3 has the following options:
-bail  Stop after hitting an error.
-batch Force batch I/O.
-column Query results will be displayed in a table like form, using whitespace characters to separate the columns and align the output.
-cmd command run command before reading stdin
-csv   Set output mode to CSV (comma separated values).
-echo  Print commands before execution.
-init file Read and execute commands from file , which can contain a mix of SQL statements and meta-commands.
-[no]header Turn headers on or off.
-help  Show help on options and exit.
-html  Query results will be output as simple HTML tables.
-interactive Force interactive I/O.
-line  Query results will be displayed with one value per line, rows separated by a blank line.  Designed to be easily parsed by scripts or other programs
-list  Query results will be displayed with the separator (|, by default) character between each field value.  The default.
-mmap N Set default mmap size to N
-nullvalue string Set string used to represent NULL values.  Default is '' (empty string).
-separator separator Set output field separator.  Default is '|'.
-stats Print memory stats before each finalize.
-version Show SQLite version.
-vfs name Use name as the default VFS.
sqlite3 reads an initialization file to set the configuration of the interactive environment.  Throughout initialization, any previously specified setting can be overridden.  The sequence of initialization is as follows:
o The default configuration is established as follows:
mode            = LIST separator       = "|" main prompt     = "sqlite> " continue prompt = "   ...> "
o If the file ~/.sqliterc exists, it is processed first.  can be found in the user's home directory, it is read and processed.  It should generally only contain meta-commands.
o If the -init option is present, the specified file is processed.
o All other command line options are processed.
http://www.sqlite.org/cli.html The sqlite3-doc package.
This manual page was originally written by Andreas Rottmann <rotty@debian.org>, for the Debian GNU/Linux system (but may be used by others). It was subsequently revised by Bill Bumgarner <bbum@mac.com> and further updated by Laszlo Boszormenyi <gcs@debian.hu> .
SVGO(1)                           User Commands                          SVGO(1)
svgo – nodejs-based tool for optimizing SVG vector graphics files
svgo [options] [INPUT...]
Arguments INPUT  Alias to --input
Options -v, --version output the version number
-i, --input <INPUT...> Input files, ”-“ for STDIN
-s, --string <STRING> Input SVG data string
-f, --folder <FOLDER> Input folder, optimize and rewrite all *.svg files
-o, --output <OUTPUT...> Output file or folder (by default the same as the input), ”-“ for STDOUT
-p, --precision <INTEGER> Set number of digits in the fractional part, overrides plugins params
--config <CONFIG> Custom config file, only .js is supported
--datauri <FORMAT> Output as Data URI string (base64), URI encoded (enc) or unencoded (unenc)
--multipass Pass over SVGs multiple times to ensure all optimizations are applied
--pretty Make SVG pretty printed
--indent <INTEGER> Indent number when pretty printing SVGs
--eol <EOL> Line break to use when outputting SVG: lf, crlf.  If unspecified, uses platform default.
--final-newline Ensure SVG ends with a line break
-r, --recursive Use with --folder.  Optimizes *.svg files in folders recursively.
--exclude <PATTERN...> Use with --folder.  Exclude files matching regular expression pattern.
-q, --quiet Only output error messages, not regular status messages
--show-plugins Show available plugins and exit
--no-color Output plain text without color
-h, --help Display help for command
GRUB-INSTALL(8)          System Administration Utilities         GRUB-INSTALL(8)
grub-install - install GRUB to a device
grub-install [OPTION...] [OPTION] [INSTALL_DEVICE]
Install GRUB on your drive.
--compress=no|xz|gz|lzo compress GRUB files [optional]
--disable-shim-lock disable shim_lock verifier
--dtb=FILE embed a specific DTB
-d, --directory=DIR use images and modules under DIR [default=/usr/lib/grub/<platform>]
--fonts=FONTS install FONTS [default=unicode]
--install-modules=MODULES install only MODULES and their dependencies [default=all]
-k, --pubkey=FILE embed FILE as public key for signature checking
--locale-directory=DIR use translations under DIR [default=/usr/share/locale]
--locales=LOCALES install only LOCALES [default=all]
--modules=MODULES pre-load specified modules MODULES
--sbat=FILE SBAT metadata
--themes=THEMES install THEMES [default=starfield]
-v, --verbose print verbose messages.
--allow-floppy make the drive also bootable as floppy (default for fdX devices). May break on some BIOSes.
--boot-directory=DIR install GRUB images under the directory DIR/grub instead of the /boot/grub directory
--bootloader-id=ID the ID of bootloader. This option is only available on EFI and Macs.
--core-compress=xz|none|auto choose the compression to use for core image
--disk-module=MODULE disk module to use (biosdisk or native). This option is only available on BIOS target.
--efi-directory=DIR use DIR as the EFI System Partition root.
--force install even if problems are detected
--force-file-id use identifier file even if UUID is available
--label-bgcolor=COLOR use COLOR for label background
--label-color=COLOR use COLOR for label
--label-font=FILE use FILE as font for label
--macppc-directory=DIR use DIR for PPC MAC install.
--no-bootsector do not install bootsector
--no-nvram don't update the `boot-device'/`Boot*' NVRAM variables. This option is only available on EFI and IEEE1275 targets.