neulab/tldr huggingface dataset:
If you encounter any problems, please contact us and supply backuplog.txt, writelog.txt and restorelog.txt. See section BUGS for contact info.
flashrom exits with 0 on success, 1 on most failures but with 3 if a call to mmap() fails.
flashrom needs different access permissions for different programmers.
internal needs raw memory access, PCI configuration space access, raw I/O port access (x86) and MSR access (x86).
atavia needs PCI configuration space access.
nic3com, nicrealtek and nicnatsemi need PCI configuration space read access and raw I/O port access.
atahpt needs PCI configuration space access and raw I/O port access.
gfxnvidia, drkaiser and it8212 need PCI configuration space access and raw memory access.
rayer_spi needs raw I/O port access.
satasii, nicintel, nicintel_eeprom and nicintel_spi need PCI configuration space read access and raw memory access.
satamv and atapromise need PCI configuration space read access, raw I/O port access and raw memory access.
serprog needs TCP access to the network or userspace access to a serial port.
buspirate_spi needs userspace access to a serial port.
ft2232_spi, usbblaster_spi and pickit2_spi need access to the respective USB device via libusb API version 0.1.
ch341a_spi and dediprog need access to the respective USB device via libusb API version 1.0.
dummy needs no access permissions at all.
internal, nic3com, nicrealtek, nicnatsemi, gfxnvidia, drkaiser, satasii, satamv, atahpt, atavia and atapromise have to be run as superuser/root, and need additional raw access permission.
serprog, buspirate_spi, dediprog, usbblaster_spi, ft2232_spi, pickit2_spi, ch341a_spi and digilent_spi can be run as normal user on most operating systems if appropriate device permissions are set.
ogp needs PCI configuration space read access and raw memory access.
On OpenBSD, you can obtain raw access permission by setting securelevel=-1 in /etc/rc.securelevel and rebooting, or rebooting into single user mode.
Please report any bugs to the flashrom mailing list ⟨flashrom@flashrom.org⟩.
We recommend to subscribe first at https://flashrom.org/mailman/listinfo/flashrom.
Many of the developers communicate via the #flashrom IRC channel on chat.freenode.net.  If you don't have an IRC client, you can use the freenode webchat ⟨http://webchat.freenode.net/?channels=flashrom⟩.  You are welcome to join and ask questions, send us bug and success reports there too. Please provide a way to contact you later (e.g. a mail address) and be patient if there is no immediate reaction. Also, we provide a pastebin service ⟨https://paste.flashrom.org⟩ that is very useful when you want to share logs etc. without spamming the channel.
Laptops Using flashrom on older laptops is dangerous and may easily make your hardware unusable. flashrom will attempt to detect if it is running on a susceptible laptop and restrict flash-chip probing for safety reasons. Please see the detailed discussion of this topic and associated flashrom options in the Laptops paragraph in the internal programmer subsection of the PROGRAMMER-SPECIFIC INFORMATION section and the information in our wiki ⟨https://flashrom.org/Laptops⟩.
One-time programmable (OTP) memory and unique IDs Some flash chips contain OTP memory often denoted as "security registers".  They usually have a capacity in the range of some bytes to a few hundred bytes and can be used to give devices unique IDs etc. flashrom is not able to read or write these memories and may therefore not be able to duplicate a chip completely. For chip types known to include OTP memories a warning is printed when they are detected.
Similar to OTP memories are unique, factory programmed, unforgeable IDs. They are not modifiable by the user at all.
flashrom is covered by the GNU General Public License (GPL), version 2. Some files are additionally available under any later version of the GPL.
Please see the individual files.
Andrew Morgan Carl-Daniel Hailfinger Claus Gindhart David Borg David Hendricks Dominik Geyer Edward O'Callaghan Eric Biederman Giampiero Giancipoli Helge Wagner Idwer Vollering Joe Bao Joerg Fischer Joshua Roys Kyösti Mälkki Luc Verhaegen Li-Ta Lo Mark Marshall Markus Boas Mattias Mattsson Michael Karcher Nikolay Petukhov Patrick Georgi Peter Lemenkov Peter Stuge Reinder E.N. de Haan Ronald G. Minnich Ronald Hoogenboom Sean Nelson Stefan Reinauer Stefan Tauner Stefan Wildemann Stephan Guilloux Steven James Urja Rannikko Uwe Hermann Wang Qingpei Yinghai Lu some others, please see the flashrom svn changelog for details. All still active authors can be reached via the mailing list ⟨flashrom@flashrom.org⟩.
This manual page was written by Uwe Hermann ⟨uwe@hermann-uwe.de⟩, Carl- Daniel Hailfinger, Stefan Tauner and others.  It is licensed under the terms of the GNU GPL (version 2 or later).
GO-FMT(1)                    General Commands Manual                   GO-FMT(1)
go-fmt - gofmt (reformat) package sources
go fmt [-n] [-x] [packages]
Fmt runs the command 'gofmt -l -w' on the packages named by the import paths.  It prints the names of the files that are modified.
For more about gofmt, see 'go doc cmd/gofmt'. For more about specifying packages, see go-packages(7).
-n     The -n flag prints commands that would be executed.
-x     The -x flag prints commands as they are executed.
-mod   The -mod flag's value sets which module download mode to use: readonly or vendor. See 'go help modules' for more.
To run gofmt with specific options, run gofmt itself.
go-fix(1), go-vet(1).
This manual page was written by Michael Stapelberg <stapelberg@debian.org> and is maintained by the Debian Go Compiler Team <team+go-compiler@tracker.debian.org> based on the output of 'go help fmt' for the Debian project (and may be used by others).
RADEONTOP(1)                                                        RADEONTOP(1)
radeontop - tool to show GPU utilization
radeontop [-chmv] [-b bus] [-d file] [-l limit] [-i secs] [-p device] [-t ticks]
RadeonTop shows the utilization of your GPU, both in general and by blocks.
Supported cards are R600 and up.
-b, --bus bus If you have multiple cards, use this parameter to select a specific one. For lspci output 01:00.0 VGA compatible controller, bus would be 1.
-c, --color Enables colorized output.
-d, --dump file Instead of displaying the data, dump it to file. Use - for stdout. The file is appended to, so itâ€™s safe to specify the same filename for consecutive runs.
Use SIGTERM or SIGINT for graceful termination.
-h, --help Displays help.
-i, --dump-interval seconds Wait for N seconds between data output.
-l, --limit limit Quit after dumping limit lines. Only valid in dump mode. Default is to dump until terminated; use SIGTERM or SIGINT for graceful termination.
-m, --mem Forces the use of the /dev/mem path, in case autodetection fails. Useful for the proprietary driver.
-p, --path device Open the DRM device node specified by device path. Usually it is located at /dev/dri/card0 or /dev/drm0. If this option used, --bus and --mem are ignored.
-t, --ticks ticks How many times per second to sample the data. The default is 120. Higher numbers mean more accurate output and more overhead.
-v, --version Displays the program version.
C, c Toggle colorized output.
Q, q Quit.
See http://github.com/clbr/radeontop
apport-bug(1)                General Commands Manual               apport-bug(1)
apport-bug, apport-collect - file a bug report using Apport, or update an existing report
apport-bug
apport-bug symptom | pid | package | program path | .apport/.crash file
apport-collect report-number
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your system to help the developers to fix the problem and avoid unnecessary question/answer turnarounds.
You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most useful bug reports.
If there is no matching symptom, you need to determine the affected program or package yourself. You can provide a package name or program name to apport-bug, e. g.:
apport-bug firefox apport-bug /usr/bin/unzip
In order to add more information to the bug report that could help the developers to fix the problem, you can also specify a process ID instead:
$ pidof gnome-terminal 5139 $ apport-bug 5139
As a special case, to report a bug against the Linux kernel, you do not need to use the full package name (such as linux-image-2.6.28-4-generic); you can just use
apport-bug linux
to report a bug against the currently running kernel.
Finally, you can use this program to report a previously stored crash or bug report:
apport-bug /var/crash/_bin_bash.1000.crash apport-bug /tmp/apport.firefox.332G9t.apport
Bug reports can be written to a file by using the --save option  or by using apport-cli.
apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session does not run under X11, it calls apport-cli for a command-line client.
apport-collect collects the same information as apport-bug, but adds it to an already reported problem you have submitted. This is useful if the report was not originally filed through Apport, and the developers ask you to attach information from your system.
Please see the apport-cli(1) manpage for possible options.
APPORT_IGNORE_OBSOLETE_PACKAGES Apport refuses to create bug reports if the package or any dependency is not current. If this environment variable is set, this check is waived. Experts who will thoroughly check the situation before filing a bug report can define this in their ~/.bashrc or temporarily on the command line when calling apport-bug.
apport crash files are written in to /var/crash by default, named uniquely per binary name and user id.  They are not deleted after being sent to the bug tracker (but from cron when they get older than 7 days). You can extract the core file (if any) and other information using apport-unpack.
apport-cli(1), apport-unpack(1)
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.
LAST(1)                           User Commands                          LAST(1)
last, lastb - show a listing of last logged in users
last [options] [username...] [tty...]
lastb [options] [username...] [tty...]
last searches back through the /var/log/wtmp file (or the file designated by the -f option) and displays a list of all users logged in (and out) since that file was created. One or more usernames and/or ttys can be given, in which case last will show only the entries matching those arguments. Names of ttys can be abbreviated, thus last 0 is the same as last tty0.
When catching a SIGINT signal (generated by the interrupt key, usually control-C) or a SIGQUIT signal, last will show how far it has searched through the file; in the case of the SIGINT signal last will then terminate.
The pseudo user reboot logs in each time the system is rebooted. Thus last reboot will show a log of all the reboots since the log file was created.
lastb is the same as last, except that by default it shows a log of the /var/log/btmp file, which contains all the bad login attempts.
-a, --hostlast Display the hostname in the last column. Useful in combination with the --dns option.
-d, --dns For non-local logins, Linux stores not only the host name of the remote host, but its IP number as well. This option translates the IP number back into a hostname.
-f, --file file Tell last to use a specific file instead of /var/log/wtmp. The --file option can be given multiple times, and all of the specified files will be processed.
-F, --fulltimes Print full login and logout times and dates.
-i, --ip Like --dns , but displays the host’s IP number instead of the name.
-number; -n, --limit number Tell last how many lines to show.
-p, --present time Display the users who were present at the specified time. This is like using the options --since and --until together with the same time.
-R, --nohostname Suppresses the display of the hostname field.
-s, --since time Display the state of logins since the specified time. This is useful, e.g., to easily determine who was logged in at a particular time. The option is often combined with --until.
-t, --until time Display the state of logins until the specified time.
--time-format format Define the output timestamp format to be one of notime, short, full, or iso. The notime variant will not print any timestamps at all, short is the default, and full is the same as the --fulltimes option. The iso variant will display the timestamp in ISO-8601 format. The ISO format contains timezone information, making it preferable when printouts are investigated outside of the system.
-w, --fullnames Display full user names and domain names in the output.
-x, --system Display the system shutdown entries and run level changes.
The options that take the time argument understand the following formats:
┌────────────────────┬─────────────────────────────┐ │                    │                             │ │YYYYMMDDhhmmss      │                             │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │YYYY-MM-DD hh:mm:ss │                             │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │YYYY-MM-DD hh:mm    │ (seconds will be set to 00) │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │YYYY-MM-DD          │ (time will be set to        │ │                    │ 00:00:00)                   │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │hh:mm:ss            │ (date will be set to today) │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │hh:mm               │ (date will be set to today, │ │                    │ seconds to 00)              │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │now                 │                             │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │yesterday           │ (time is set to 00:00:00)   │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │today               │ (time is set to 00:00:00)   │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │tomorrow            │ (time is set to 00:00:00)   │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │+5min               │                             │ ├────────────────────┼─────────────────────────────┤ │                    │                             │ │-5days              │                             │ └────────────────────┴─────────────────────────────┘
/var/log/wtmp, /var/log/btmp
The files wtmp and btmp might not be found. The system only logs information in these files if they are present. This is a local configuration issue. If you want the files to be used, they can be created with a simple touch(1) command (for example, touch /var/log/wtmp).
Miquel van Smoorenburg <miquels@cistron.nl>
login(1), wtmp(5), init(8), shutdown(8)
The last command is part of the util-linux package which can be downloaded from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils/util-linux/>.
OPTIPNG(1)                   General Commands Manual                  OPTIPNG(1)
OptiPNG - Optimize Portable Network Graphics files
optipng [-? | -h | -help] optipng [options...] files...
The OptiPNG program shall attempt to optimize PNG files, i.e. reduce their size to a minimum, without losing semantic information. In addition, this program shall perform a suite of auxiliary functions like integrity checks, metadata recovery and pixmap-to-PNG conversion.
The optimization attempts are not guaranteed to succeed. Valid PNG files that cannot be optimized by this program are normally left intact; their size will not grow. The user may request to override this default behavior.
The input files are raster image files encoded either in PNG format (the native format), or in an external format. The currently supported external formats are GIF, BMP, PNM and TIFF.
OptiPNG processes each image file given in the command line as follows:
- If the image is in PNG format:
Attempts to optimize the given file in-place. If optimization is successful, or if the option -force is enabled, replaces the original file with its optimized version. The original file is backed up if the option -keep is enabled.
- If the image is in an external format:
Creates an optimized PNG version of the given file. The output file name is composed from the original file name and the .png extension.
Existing files are not overwritten, unless the option -clobber is enabled.
General options -?, -h, -help Show a complete summary of options.
-backup, -keep Keep a backup of the modified files.
-clobber Overwrite the existing output and backup files. Under this option, if the option -backup is not enabled, the old backups of the overwritten files are deleted.
-dir directory Write the output files to directory.
-fix   Enable error recovery. This option has no effect on valid input files. The program will spend a reasonable amount of effort to recover as much data as possible, without increasing the output file size, but the success cannot be generally guaranteed. The program may even increase the file size, e.g., by reconstructing missing critical data. Under this option, integrity shall take precedence over file size. When this option is not used, the invalid input files are left unprocessed.
-force Enforce writing of a new output file. This option overrides the program's decision not to write such file, e.g. when the PNG input is digitally signed (using dSIG), or when the PNG output becomes larger than the PNG input.
-log file Log messages to file.  For safety reasons, file must have the extension .log. This option is deprecated and will be removed eventually. Use shell redirection.
-out file Write output file to file.  The command line must contain exactly one input file.
-preserve Preserve file attributes (time stamps, file access rights, etc.) where applicable.
-quiet, -silent Run in quiet mode. The messages are still written to the log file if the option -log is enabled.
-simulate Run in simulation mode: perform the trials, but do not create output files.
-v     Enable the options -verbose and -version.
-verbose Run in verbose mode.
-version Show copyright, version and build info.
--     Stop option switch parsing.
PNG encoding and optimization options -o level Select the optimization level. The optimization level 0 enables a set of optimization operations that require minimal effort. There will be no changes to image attributes like bit depth or color type, and no recompression of existing IDAT datastreams. The optimization level 1 enables a single IDAT compression trial. The trial chosen is what OptiPNG thinks it's probably the most effective. The optimization levels 2 and higher enable multiple IDAT compression trials; the higher the level, the more trials. The behavior and the default value of this option may change across different program versions. Use the option -h to see the details pertaining to your specific version.
-f filters Select the PNG delta filters. The filters argument is specified as a rangeset (e.g. -f0-5), and the default filters value depends on the optimization level set by the option -o. The filter values 0, 1, 2, 3 and 4 indicate static filtering, and correspond to the standard PNG filter codes (None, Left, Up, Average and Paeth, respectively). The filter value 5 indicates adaptive filtering, whose effect is defined by the libpng(3) library used by OptiPNG.
-full  Produce a full report on IDAT.  This option might slow down the trials.
-i type Select the interlace type (0-1). If the interlace type 0 is selected, the output image shall be non-interlaced (i.e. progressive-scanned). If the interlace type 1 is selected, the output image shall be interlaced using the Adam7 method. By default, the output shall have the same interlace type as the input.
-nb    Do not apply bit depth reduction.
-nc    Do not apply color type reduction.
-np    Do not apply palette reduction.
-nx    Do not apply any lossless image reduction: enable the options -nb, -nc and -np.
-nz    Do not recode IDAT datastreams. The IDAT optimization operations that do not require recoding (e.g. IDAT chunk concatenation) are still performed. This option has effect on PNG input files only.
-zc levels Select the zlib compression levels used in IDAT compression. The levels argument is specified as a rangeset (e.g. -zc6-9), and the default levels value depends on the optimization level set by the option -o. The effect of this option is defined by the zlib(3) library used by OptiPNG.
-zm levels Select the zlib memory levels used in IDAT compression. The levels argument is specified as a rangeset (e.g. -zm8-9), and the default levels value depends on the optimization level set by the option -o. The effect of this option is defined by the zlib(3) library used by OptiPNG.
-zs strategies Select the zlib compression strategies used in IDAT compression. The strategies argument is specified as a rangeset (e.g. -zs0-3), and the default strategies value depends on the optimization level set by the option -o. The effect of this option is defined by the zlib(3) library used by OptiPNG.
-zw size Select the zlib window size (32k,16k,8k,4k,2k,1k,512,256) used in IDAT compression. The size argument can be specified either in bytes (e.g. 16384) or kilobytes (e.g. 16k). The default size value is set to the lowest window size that yields an IDAT output as big as if yielded by the value 32768. The effect of this option is defined by the zlib(3) library used by OptiPNG.
Editing options -snip  Cut one image out of multi-image, animation or video files. Depending on the input format, this may be either the first or the most relevant (e.g. the largest) image.
-strip objects Strip metadata objects from a PNG file. PNG metadata is the information stored in any ancillary chunk except tRNS.  (tRNS represents the alpha channel, which, even if ignored in rendering, is still a proper image channel in the RGBA color space.) The only option currently supported is -strip all.
Notes Options may come in any order (except for --), before, after, or alternating with file names. Option names are case-insensitive and may be abbreviated to their shortest unique prefix.
Some options may have arguments that follow the option name, separated by whitespace or the equal sign ('='). If the option argument is a number or a rangeset, the separator may be omitted. For example:
-out newfile.png  <=>  -out=newfile.png -o3  <=>  -o 3  <=>  -o=3 -f0,3-5  <=>  -f 0,3-5  <=>  -f=0,3-5
Rangeset arguments are cumulative; e.g.
-f0 -f3-5  <=>  -f0,3-5 -zs0 -zs1 -zs2-3  <=>  -zs0,1,2,3  <=>  -zs0-3
The PNG optimization algorithm consists of the following steps:
1.  Reduce the bit depth, the color type and the color palette of the image.  This step may reduce the size of the uncompressed image, which, indirectly, may reduce the size of the compressed image (i.e. the size of the output PNG file).
2.  Run a suite of compression methods and strategies and select the compression parameters that yield the smallest output file.
3.  Store all IDAT contents into a single chunk, eliminating the overhead incurred by repeated IDAT headers and CRCs.
4.  Set the zlib window size inside IDAT to a mininum that does not affect the compression ratio, reducing the memory requirements of PNG decoders.
Not all of the above steps need to be executed. The behavior depends on the actual input files and user options.
Step 1 may be customized via the no-reduce options -nb, -nc, -np and -nx. Step 2 may be customized via the -o option, and may be fine-tuned via the options -zc, -zm, -zs and -zw. Step 3 is always executed. Step 4 is executed only if a new IDAT is being created, and may be fine-tuned via the option -zw.
Extremely exhaustive searches are not generally expected to yield significant improvements in compression ratio, and are recommended to advanced users only.
optipng file.png      # default speed optipng -o5 file.png  # slow optipng -o7 file.png  # very slow
Lossless image reductions are not completely implemented.  (This does not affect the integrity of the output files.)  Here are the missing pieces:
- The color palette reductions are implemented only partially. - The bit depth reductions below 8, for grayscale images, are not implemented yet.
Encoding of images whose total IDAT size exceeds 2GB is not supported.
TIFF support is limited to uncompressed, PNG-compatible (grayscale, RGB and RGBA) images.
Metadata is not imported from the external image formats.
There is no support for pipes, streams, extended file attributes or access control lists.
png(5), libpng(3), zlib(3), pngcrush(1), pngrewrite(1).
The files produced by OptiPNG are compliant with PNG-2003: Glenn Randers-Pehrson et al.  Portable Network Graphics (PNG) Specification, Second Edition. W3C Recommendation 10 November 2003; ISO/IEC IS 15948:2003 (E). http://www.w3.org/TR/PNG/
OptiPNG is written and maintained by Cosmin Truta.
This manual page was originally written by Nelson A. de Oliveira for the Debian Project. It was later updated by Cosmin Truta, and is now part of the OptiPNG distribution.
SCREENKEY(1)                  screenkey User Manual                 SCREENKEY(1)
screenkey - screencast tool to display your keystrokes
screenkey
screenkey is a screencast tool to display your keys inspired by Screenflick for Mac OS and based initially on key-mon project.
It’s useful to create screencasts and is also a powerful teaching tool.
screenkey --help gives all options with their explanations.
Georges Khaznadar <georgesk@debian.org> Wrote this manpage for the Debian system.
Copyright © 2012-2017 Georges Khaznadar
This manual page was written for the Debian system (and may be used by others).
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation.
IEX(1)                     BSD General Commands Manual                    IEX(1)
iex â€” The Elixir shell
iex [OPTIONS]
The interactive shell is used for evaluation, debugging and introspection of the Elixir runtime system. It is also possible to use the program for testing the work of small pieces of code escaping the stage of saving the code in a file.
Note that many of the options mentioned here were borrowed from the Erlang shell, therefore erl(1) can be used as an additional source of information on the options.
-h, --help Displays the help message to the standard error (stderr) and exits.
-v, --version Displays the Elixir version to the standard output (stdout) and exits.
-e, --eval expression Evaluates the specified expression (see the --rpc-eval option).
-r file Requires the specified file. In other words, the file is checked for existence at the start of iex.
-S script Runs the specified script.
-pa directory Adds the specified directory to the beginning of the code path. If the directory already exists, it will be removed from its old position and put to the beginning.
See also the function Code.prepend_path/1.
-pr file Does the same thing as -r (see above) but in parallel.
-pz directory Adds the specified directory to the end of the code path. If the directory already exists, it will be neither removed from its old position nor put to the end.
See also the function Code.append_path/1.
--app application Starts the specified application and all its dependencies.
--boot file Specifies the name of the boot file, file.boot, which is used to start the system. Unless File contains an absolute path, the system searches for file.boot in the current and $ROOT/bin directories.
Defaults to $ROOT/bin/start.boot.
The option is equivalent to Erlang's -boot.
--boot-var var dir If the boot script contains a path variable var other than $ROOT, this variable is expanded to dir.  Used when applications are installed in another directory than $ROOT/lib.
The option is equivalent to Erlang's -boot_var.
See also the function :systools.make_script/1,2 in SASL.
--erl parameters Serves the same purpose as ELIXIR_ERL_OPTIONS (see the ENVIRONMENT section)
--erl-config file Specifies the name of a configuration file, file.config, which is used to configure applications. Note that the configuration file must be written in Erlang.
The option is equivalent to Erlang's -config.
--cookie value Specifies the magic cookie value. If the value isn't specified via the option when the node starts, it will be taken from the file ~/.erlang.cookie (see the FILES section).  Distributed nodes can interact with each other only when their magic cookies are equal.
See also the function Node.set_cookie/2.
--hidden Starts a hidden node.
Connections between nodes are transitive. For example, if node A is connected to node B, and node B is connected to node C, then node A is connected to node C. The option --hidden allows creating a node which can be connected to another node, escaping redundant connections.
The function Node.list/0 allows getting the list of nodes connected to the target node, however the list won't include hidden nodes. Depending on the input parameter, the function Node.list/1 allows getting the list which contains only hidden nodes (the parameter :hidden) or both hidden and not hidden nodes (the parameter :connected).
--logger-otp-reports val Enables or disables OTP reporting (val can be either true or false).
--logger-sasl-reports val Enables or disables SASL reporting (val can be either true or false).
--sname name Gives a node a short name and starts it. Short names take the form of name@host, where host is the name of the target host (hostname(1)) which runs the node. The nodes with short names can interact with each other only in the same local network.
--name name Gives a node a long name and starts it. Long names take the form of name@host, where host is the IP address of the host which runs the node. In contrast to the nodes with short names, the nodes with long names aren't limited by boundaries of a local network (see above).
--pipe-to pipedir logdir Starts the Erlang VM as a named pipedir and logdir (only for Unix-like operating systems).
--rpc-eval node expression Evaluates the specified expression on the specified node (see the --eval option).
--vm-args file Reads the command-line arguments from file and passes them to the Erlang VM.
The option is equivalent to Erlang's -args_file.
--werl  Uses Erlang's Windows shell GUI (only for Windows).
--dot-iex file Loads the specified file instead of .iex.exs (see the FILES section).
--remsh node Connects to the specified node which was started with the --sname or --name options (see above).
--      Separates the options passed to the compiler from the options passed to the executed code.
The following options can be given more than once: --boot-var, --erl-config, --eval, --rpc-eval.
ELIXIR_ERL_OPTIONS Allows passing parameters to the Erlang runtime.
~/.erlang.cookie Stores the magic cookie value which is used only when it wasn't specified via the option --cookie (see above).  If the file doesn't exist when a node starts, it will be created.
.iex.exs After iex starts, it seeks the file .iex.exs and, in a case of success, executes the code from the file in the context of the shell. At first the search starts in the current working directory; then, if necessary, it continues in the home directory.
elixir(1), elixirc(1), mix(1)
Elixir is maintained by the Elixir Core Team.
This manual page was contributed by Evgeny Golyshev.
Copyright (c) 2012 Plataformatec.
Main website: https://elixir-lang.org
Documentation: https://elixir-lang.org/docs.html
TIMEDATECTL(1)                     timedatectl                    TIMEDATECTL(1)
timedatectl - Control the system time and date
timedatectl [OPTIONS...] {COMMAND}
timedatectl may be used to query and change the system clock and its settings, and enable or disable time synchronization services.
Use systemd-firstboot(1) to initialize the system time zone for mounted (but not booted) system images.
timedatectl may be used to show the current status of time synchronization services, for example systemd-timesyncd.service(8).
The following commands are understood:
status Show current settings of the system clock and RTC, including whether network time synchronization is active. If no command is specified, this is the implied default.
show Show the same information as status, but in machine readable form. This command is intended to be used whenever computer-parsable output is required. Use status if you are looking for formatted human-readable output.
By default, empty properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=.
set-time [TIME] Set the system clock to the specified time. This will also update the RTC time accordingly. The time may be specified in the format "2012-10-30 18:17:16".
set-timezone [TIMEZONE] Set the system time zone to the specified value. Available timezones can be listed with list-timezones. If the RTC is configured to be in the local time, this will also update the RTC time. This call will alter the /etc/localtime symlink. See localtime(5) for more information.
list-timezones List available time zones, one per line. Entries from the list can be set as the system timezone with set-timezone.
set-local-rtc [BOOL] Takes a boolean argument. If "0", the system is configured to maintain the RTC in universal time. If "1", it will maintain the RTC in local time instead. Note that maintaining the RTC in the local timezone is not fully supported and will create various problems with time zone changes and daylight saving adjustments. If at all possible, keep the RTC in UTC mode. Note that invoking this will also synchronize the RTC from the system clock, unless --adjust-system-clock is passed (see above). This command will change the 3rd line of /etc/adjtime, as documented in hwclock(8).
set-ntp [BOOL] Takes a boolean argument. Controls whether network time synchronization is active and enabled (if available). If the argument is true, this enables and starts the first existing network synchronization service. If the argument is false, then this disables and stops the known network synchronization services. The way that the list of services is built is described in systemd- timedated.service(8).
systemd-timesyncd Commands The following commands are specific to systemd-timesyncd.service(8).
timesync-status Show current status of systemd-timesyncd.service(8). If --monitor is specified, then this will monitor the status updates.
show-timesync Show the same information as timesync-status, but in machine readable form. This command is intended to be used whenever computer-parsable output is required. Use timesync-status if you are looking for formatted human-readable output.
ntp-servers INTERFACE SERVER... Set the interface specific NTP servers. This command can be used only when the interface is managed by systemd-networkd.
revert INTERFACE Revert the interface specific NTP servers. This command can be used only when the interface is managed by systemd-networkd.
--no-ask-password Do not query the user for authentication for privileged operations.
--adjust-system-clock If set-local-rtc is invoked and this option is passed, the system clock is synchronized from the RTC again, taking the new setting into account. Otherwise, the RTC is synchronized from the system clock.
--monitor If timesync-status is invoked and this option is passed, then timedatectl monitors the status of systemd-timesyncd.service(8) and updates the outputs. Use Ctrl+C to terminate the monitoring.
-a, --all When showing properties of systemd-timesyncd.service(8), show all properties regardless of whether they are set or not.
-p, --property= When showing properties of systemd-timesyncd.service(8), limit display to certain properties as specified as argument. If not specified, all set properties are shown. The argument should be a property name, such as "ServerName". If specified more than once, all properties with the specified names are shown.
--value When printing properties with show-timesync, only print the value, and skip the property name and "=".
-H, --host= Execute the operation remotely. Specify a hostname, or a username and hostname separated by "@", to connect to. The hostname may optionally be suffixed by a port ssh is listening on, separated by ":", and then a container name, separated by "/", which connects directly to a specific container on the specified host. This will use SSH to talk to the remote machine manager instance. Container names may be enumerated with machinectl -H HOST. Put IPv6 addresses in brackets.
-M, --machine= Execute operation on a local container. Specify a container name to connect to, optionally prefixed by a user name to connect as and a separating "@" character. If the special string ".host" is used in place of the container name, a connection to the local system is made (which is useful to connect to a specific user's user bus: "--user --machine=lennart@.host"). If the "@" syntax is not used, the connection is made as root user. If the "@" syntax is used either the left hand side or the right hand side may be omitted (but not both) in which case the local user name and ".host" are implied.
--version Print a short version string and exit.
--no-pager Do not pipe output into a pager.
$SYSTEMD_LOG_LEVEL The maximum log level of emitted messages (messages with a higher log level, i.e. less important ones, will be suppressed). Either one of (in order of decreasing importance) emerg, alert, crit, err, warning, notice, info, debug, or an integer in the range 0...7. See syslog(3) for more information.
$SYSTEMD_LOG_COLOR A boolean. If true, messages written to the tty will be colored according to priority.
This setting is only useful when messages are written directly to the terminal, because journalctl(1) and other tools that display logs will color messages based on the log level on their own.
$SYSTEMD_LOG_TIME A boolean. If true, console log messages will be prefixed with a timestamp.
This setting is only useful when messages are written directly to the terminal or a file, because journalctl(1) and other tools that display logs will attach timestamps based on the entry metadata on their own.
$SYSTEMD_LOG_LOCATION A boolean. If true, messages will be prefixed with a filename and line number in the source code where the message originates.
Note that the log location is often attached as metadata to journal entries anyway. Including it directly in the message text can nevertheless be convenient when debugging programs.
$SYSTEMD_LOG_TID A boolean. If true, messages will be prefixed with the current numerical thread ID (TID).
Note that the this information is attached as metadata to journal entries anyway. Including it directly in the message text can nevertheless be convenient when debugging programs.
$SYSTEMD_LOG_TARGET The destination for log messages. One of console (log to the attached tty), console-prefixed (log to the attached tty but with prefixes encoding the log level and "facility", see syslog(3), kmsg (log to the kernel circular log buffer), journal (log to the journal), journal-or-kmsg (log to the journal if available, and to kmsg otherwise), auto (determine the appropriate log target automatically, the default), null (disable log output).
$SYSTEMD_PAGER Pager to use when --no-pager is not given; overrides $PAGER. If neither $SYSTEMD_PAGER nor $PAGER are set, a set of well-known pager implementations are tried in turn, including less(1) and more(1), until one is found. If no pager implementation is discovered no pager is invoked. Setting this environment variable to an empty string or the value "cat" is equivalent to passing --no-pager.
$SYSTEMD_LESS Override the options passed to less (by default "FRSXMK").
Users might want to change two options in particular:
K This option instructs the pager to exit immediately when Ctrl+C is pressed. To allow less to handle Ctrl+C itself to switch back to the pager command prompt, unset this option.
If the value of $SYSTEMD_LESS does not include "K", and the pager that is invoked is less, Ctrl+C will be ignored by the executable, and needs to be handled by the pager.
X This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal. It is set by default to allow command output to remain visible in the terminal even after the pager exits. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse.
See less(1) for more discussion.
$SYSTEMD_LESSCHARSET Override the charset passed to less (by default "utf-8", if the invoking terminal is determined to be UTF-8 compatible).
$SYSTEMD_PAGERSECURE Takes a boolean argument. When true, the "secure" mode of the pager is enabled; if false, disabled. If $SYSTEMD_PAGERSECURE is not set at all, secure mode is enabled if the effective UID is not the same as the owner of the login session, see geteuid(2) and sd_pid_get_owner_uid(3). In secure mode, LESSSECURE=1 will be set when invoking the pager, and the pager shall disable commands that open or create new files or start new subprocesses. When $SYSTEMD_PAGERSECURE is not set at all, pagers which are not known to implement secure mode will not be used. (Currently only less(1) implements secure mode.)
Note: when commands are invoked with elevated privileges, for example under sudo(8) or pkexec(1), care must be taken to ensure that unintended interactive features are not enabled. "Secure" mode for the pager may be enabled automatically as describe above. Setting SYSTEMD_PAGERSECURE=0 or not removing it from the inherited environment allows the user to invoke arbitrary commands. Note that if the $SYSTEMD_PAGER or $PAGER variables are to be honoured, $SYSTEMD_PAGERSECURE must be set too. It might be reasonable to completely disable the pager using --no-pager instead.
$SYSTEMD_COLORS Takes a boolean argument. When true, systemd and related utilities will use colors in their output, otherwise the output will be monochrome. Additionally, the variable can take one of the following special values: "16", "256" to restrict the use of colors to the base 16 or 256 ANSI colors, respectively. This can be specified to override the automatic decision based on $TERM and what the console is connected to.
$SYSTEMD_URLIFY The value must be a boolean. Controls whether clickable links should be generated in the output for terminal emulators supporting this. This can be specified to override the decision that systemd makes based on $TERM and other conditions.
Show current settings:
$ timedatectl Local time: Thu 2017-09-21 16:08:56 CEST Universal time: Thu 2017-09-21 14:08:56 UTC RTC time: Thu 2017-09-21 14:08:56 Time zone: Europe/Warsaw (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no
Enable network time synchronization:
$ timedatectl set-ntp true ==== AUTHENTICATING FOR org.freedesktop.timedate1.set-ntp === Authentication is required to control whether network time synchronization shall be enabled. Authenticating as: user Password: ******** ==== AUTHENTICATION COMPLETE ===
$ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled) Active: active (running) since Mo 2015-03-30 14:20:38 CEST; 5s ago Docs: man:systemd-timesyncd.service(8) Main PID: 595 (systemd-timesyn) Status: "Using Time Server 216.239.38.15:123 (time4.google.com)." CGroup: /system.slice/systemd-timesyncd.service └─595 /usr/lib/systemd/systemd-timesyncd ...
Show current status of systemd-timesyncd.service(8):
$ timedatectl timesync-status Server: 216.239.38.15 (time4.google.com) Poll interval: 1min 4s (min: 32s; max 34min 8s) Leap: normal Version: 4 Stratum: 1 Reference: GPS Precision: 1us (-20) Root distance: 335us (max: 5s) Offset: +316us Delay: 349us Jitter: 0 Packet count: 1 Frequency: -8.802ppm
systemd(1), hwclock(8), date(1), localtime(5), systemctl(1), systemd- timedated.service(8), systemd-timesyncd.service(8), systemd-firstboot(1)
KUBERNETES(1)(kubernetes)                              KUBERNETES(1)(kubernetes)
Eric Paris Jan 2015
kubectl logs - Print the logs for a container in a pod
kubectl logs [OPTIONS]
Print the logs for a container in a pod or specified resource. If the pod has only one container, the container name is optional.
--all-containers=false      Get all containers' logs in the pod(s).
-c, --container=""      Print the logs of this container
-f, --follow=false      Specify if the logs should be streamed.
--ignore-errors=false      If watching / following pod logs, allow for any errors that occur to be non-fatal
--insecure-skip-tls-verify-backend=false      Skip verifying the identity of the kubelet that logs are requested from.  In theory, an attacker could provide invalid log content back. You might want to use this if your kubelet serving certificates have expired.
--limit-bytes=0      Maximum bytes of logs to return. Defaults to no limit.
--max-log-requests=5      Specify maximum number of concurrent logs to follow when using by a selector. Defaults to 5.
--pod-running-timeout=20s      The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running
--prefix=false      Prefix each log line with the log source (pod name and container name)
-p, --previous=false      If true, print the logs for the previous instance of the container in a pod if it exists.
-l, --selector=""      Selector (label query) to filter on.
--since=0s      Only return logs newer than a relative duration like 5s, 2m, or 3h. Defaults to all logs. Only one of since-time / since may be used.
--since-time=""      Only return logs after a specific date (RFC3339). Defaults to all logs. Only one of since-time / since may be used.
--tail=-1      Lines of recent log file to display. Defaults to -1 with no selector, showing all log lines otherwise 10, if a selector is provided.
--timestamps=false      Include timestamps on each line in the log output
--add-dir-header=false      If true, adds the file directory to the header of the log messages
--alsologtostderr=false      log to standard error as well as files
--application-metrics-count-limit=100      Max number of application metrics to store (per container)
--as=""      Username to impersonate for the operation
--as-group=[]      Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
--azure-container-registry-config=""      Path to the file containing Azure container registry configuration information.
--boot-id-file="/proc/sys/kernel/random/boot_id"      Comma-separated list of files to check for boot-id. Use the first one that exists.
--cache-dir="/build/.kube/cache"      Default cache directory
--certificate-authority=""      Path to a cert file for the certificate authority
--client-certificate=""      Path to a client certificate file for TLS
--client-key=""      Path to a client key file for TLS
--cloud-provider-gce-l7lb-src-cidrs=130.211.0.0/22,35.191.0.0/16 CIDRs opened in GCE firewall for L7 LB traffic proxy  health checks
--cloud-provider-gce-lb-src-cidrs=130.211.0.0/22,209.85.152.0/22,209.85.204.0/22,35.191.0.0/16 CIDRs opened in GCE firewall for L4 LB traffic proxy  health checks
--cluster=""      The name of the kubeconfig cluster to use
--container-hints="/etc/cadvisor/container_hints.json"      location of the container hints file
--containerd="/run/containerd/containerd.sock"      containerd endpoint
--containerd-namespace="k8s.io"      containerd namespace
--context=""      The name of the kubeconfig context to use
--default-not-ready-toleration-seconds=300      Indicates the tolerationSeconds of the toleration for notReady:NoExecute that is added by default to every pod that does not already have such a toleration.
--default-unreachable-toleration-seconds=300      Indicates the tolerationSeconds of the toleration for unreachable:NoExecute that is added by default to every pod that does not already have such a toleration.
--disable-root-cgroup-stats=false      Disable collecting root Cgroup stats
--docker="unix:///var/run/docker.sock"      docker endpoint