neulab/tldr huggingface dataset:
For the above source file, ctags tags point and x by default.  If the qualified extra is enabled from the command line (--extras=+q), then point.x is also tagged even though the string "point.x" is not in the source code.
$ ctags --fields=+K -uo - qualified.java point   qualified.java  /^class point {$/;"     class x       qualified.java  /^      double x;$/;"   field   class:point $ ctags --fields=+K --extras=+q -uo - qualified.java point   qualified.java  /^class point {$/;"     class x       qualified.java  /^      double x;$/;"   field   class:point point.x qualified.java  /^      double x;$/;"   field   class:point
reference/r Include reference tags. See "TAG ENTRIES" about reference tags.
The following example demonstrates the reference extra tag.
#include <stdio.h> #include "utils.h" #define X #undef X
The roles:system or roles:local fields will be added depending on whether the include file name begins with '<' or not.
"#define X" emits a definition tag. On the other hand "#undef X" emits a reference tag.
$ ctags --fields=+EKr -uo - inc.c X       inc.c   /^#define X$/;" macro   file:   roles:def       extras:fileScope $ ctags --fields=+EKr --extras=+r -uo - inc.c stdio.h inc.c   /^#include <stdio.h>/;" header  roles:system    extras:reference utils.h inc.c   /^#include "utils.h"/;" header  roles:local     extras:reference X       inc.c   /^#define X$/;" macro   file:   roles:def       extras:fileScope X       inc.c   /^#undef X$/;"  macro   file:   roles:undef     extras:fileScope,reference
Language-specific fields and extras Exuberant Ctags has the concept of fields and extras. They are common between parsers of different languages. Universal Ctags extends this concept by providing language-specific fields and extras.
vi(1) will, by default, expect a tag file by the name tags in the current directory. Once the tag file is built, the following commands exercise the tag indexing feature:
vi -t tag Start vi and position the cursor at the file and line where tag is defined.
:ta tag Find a tag.
Ctrl-] Find the tag under the cursor.
Ctrl-T Return to previous location before jump to tag (not widely implemented).
emacs(1) will, by default, expect a tag file by the name TAGS in the current directory. Once the tag file is built, the following commands exercise the tag indexing feature:
M-x visit-tags-table <RET> FILE <RET> Select the tag file, FILE, to use.
M-. [TAG] <RET> Find the first definition of TAG. The default tag is the identifier under the cursor.
M-*    Pop back to where you previously invoked M-..
C-u M-. Find the next definition for the last tag.
For more commands, see the Tags topic in the Emacs info document.
NEdit version 5.1 and later can handle the new extended tag file format (see --format).
• To make NEdit use the tag file, select "File->Load Tags File".
• To jump to the definition for a tag, highlight the word, then press Ctrl-D.
NEdit 5.1 can read multiple tag files from different directories. Setting the X resource nedit.tagFile to the name of a tag file instructs NEdit to automatically load that tag file at startup time.
Because ctags is neither a preprocessor nor a compiler, use of preprocessor macros can fool ctags into either missing tags or improperly generating inappropriate tags. Although ctags has been designed to handle certain common cases, this is the single biggest cause of reported problems. In particular, the use of preprocessor constructs which alter the textual syntax of C can fool ctags. You can work around many such problems by using the -I option.
Note that since ctags generates patterns for locating tags (see the --excmd option), it is entirely possible that the wrong line may be found by your editor if there exists another source line which is identical to the line containing the tag. The following example demonstrates this condition:
int variable;
/* ... */ void foo(variable) int variable; { /* ... */ }
Depending upon which editor you use and where in the code you happen to be, it is possible that the search pattern may locate the local parameter declaration before it finds the actual global variable definition, since the lines (and therefore their search patterns) are identical.
This can be avoided by use of the --excmd=n option.
ctags has more options than ls(1).
ctags assumes the input file is written in the correct grammar. Otherwise output of ctags is undefined. In other words it has garbage in, garbage out (GIGO) feature.
When parsing a C++ member function definition (e.g. className::function), ctags cannot determine whether the scope specifier is a class name or a namespace specifier and always lists it as a class name in the scope portion of the extension fields. Also, if a C++ function is defined outside of the class declaration (the usual case), the access specification (i.e. public, protected, or private) and implementation information (e.g. virtual, pure virtual) contained in the function declaration are not known when the tag is generated for the function definition. It will, however be available for prototypes (e.g. --kinds-c++=+p).
No qualified tags are generated for language objects inherited into a class.
TMPDIR On Unix-like hosts where mkstemp(3) is available, the value of this variable specifies the directory in which to place temporary files.  This can be useful if the size of a temporary file becomes too large to fit on the partition holding the default temporary directory defined at compilation time.
ctags creates temporary files only if either (1) an emacs-style tag file is being generated, (2) the tag file is being sent to standard output, or (3) the program was compiled to use an internal sort algorithm to sort the tag files instead of the sort(1) utility of the operating system.  If the sort(1) utility of the operating system is being used, it will generally observe this variable also.
Note that if ctags is setuid, the value of TMPDIR will be ignored.
tags   The default tag file created by ctags.
TAGS   The default tag file created by etags.
$XDG_CONFIG_HOME/ctags/*.ctags, or $HOME/.config/ctags/*.ctags if $XDG_CONFIG_HOME is not defined (on other than MS Windows)
$HOME/.ctags.d/*.ctags
$HOMEDRIVE$HOMEPATH/ctags.d/*.ctags (on MS Windows only)
.ctags.d/*.ctags
ctags.d/*.ctags If any of these configuration files exist, each will be expected to contain a set of default options which are read in the order listed when ctags starts, but before any command line options are read. This makes it possible to set up personal or project-level defaults.
It is possible to compile ctags to read an additional configuration file before any of those shown above, which will be indicated if the output produced by the --version option lists the custom-conf feature.
Options appearing on the command line will override options specified in these files. Only options will be read from these files.
Note that the option files are read in line-oriented mode in which spaces are significant (since shell quoting is not possible) but spaces at the beginning of a line are ignored. Each line of the file is read as one command line parameter (as if it were quoted with single quotes).  Therefore, use new lines to indicate separate command-line arguments.
A line starting with '#' is treated as a comment.
*.ctags files in a directory are loaded in alphabetical order.
See ctags-optlib(7) for defining (or extending) a parser in a configuration file.
See tags(5) for the format of tag files.
See ctags-incompatibilities(7) about known incompatible changes with Exuberant Ctags.
See ctags-client-tools(7) if you are interested in writing a tool for processing tags files.
See ctags-lang-python(7) about python input specific notes.
See readtags(1) about a client tool for binary searching a name in a sorted tags file.
The official Universal Ctags web site at: https://ctags.io/
Also ex(1), vi(1), elvis(1), or, better yet, vim(1), the official editor of ctags.  For more information on vim(1), see the Vim web site at: https://www.vim.org/
Universal Ctags project https://ctags.io/
Darren Hiebert <dhiebert@users.sourceforge.net> http://DarrenHiebert.com/
"Think ye at all times of rendering some service to every member of the human race."
"All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity."
-- From the Baha'i Writings
This version of ctags (Universal Ctags) derived from the repository, known as fishman-ctags, started by Reza Jelveh.
The fishman-ctags was derived from Exuberant Ctags.
Some parsers are taken from tagmanager of the Geany (‐ https://www.geany.org/) project.
Exuberant Ctags was originally derived from and inspired by the ctags program by Steve Kirkendall <kirkenda@cs.pdx.edu> that comes with the Elvis vi clone (though virtually none of the original code remains).
Credit is also due Bram Moolenaar <Bram@vim.org>, the author of vim, who has devoted so much of his time and energy both to developing the editor as a service to others, and to helping the orphans of Uganda.
The section entitled "HOW TO USE WITH GNU EMACS" was shamelessly stolen from the info page for GNU etags.
CALIBRE-SERVER(1)                    calibre                   CALIBRE-SERVER(1)
calibre-server - calibre-server
calibre-server [options] [path to library folder...]
Start the calibre Content server. The calibre Content server exposes your calibre libraries over the internet. You can specify the path to the library folders as arguments to calibre-server. If you do not specify any paths, all the libraries that the main calibre program knows about will be used.
Whenever you pass arguments to calibre-server that have spaces in them, enclose the arguments in quotation marks. For example: "/some path/with spaces"
[OPTIONS] --access-log Path to the access log file. This log contains information about clients connecting to the server and making requests. By default no access logging is done.
--ajax-timeout Time (in seconds) to wait for a response from the server when making queries.
--auth-mode Choose the type of authentication used.     Set the HTTP authentication mode used by the server. Set to "basic" if you are putting this server behind an SSL proxy. Otherwise, leave it as "auto", which will use "basic" if SSL is configured otherwise it will use "digest".
--auto-reload Automatically reload server when source code changes. Useful for development. You should also specify a small value for the shutdown timeout.
--ban-after Number of login failures for ban.   The number of login failures after which an IP address is banned
--ban-for Ban IP addresses that have repeated login failures. Temporarily bans access for IP addresses that have repeated login failures for the specified number of minutes. Useful to prevent attempts at guessing passwords. If set to zero, no banning is done.
--book-list-mode Choose the default book list mode.  Set the default book list mode that will be used for new users. Individual users can override the default in their own settings. The default is to use a cover grid.
--compress-min-size Minimum size for which responses use data compression (in bytes).
--custom-list-template Path to a JSON file containing a template for the custom book list mode. The easiest way to create such a template file is to go to Preferences-> Sharing over the net-> Book list template in calibre, create the template and export it.
--daemonize Run process in background as a daemon (Linux only).
--displayed-fields Restrict displayed user-defined fields.     Comma separated list of user-defined metadata fields that will be displayed by the Content server in the /opds and /mobile views. If you specify this option, any fields not in this list will not be displayed. For example: my_rating,my_tags
--enable-allow-socket-preallocation, --disable-allow-socket-preallocation Socket pre-allocation, for example, with systemd socket activation. By default, this option is enabled.
--enable-auth, --disable-auth Password based authentication to access the server. Normally, the server is unrestricted, allowing anyone to access it. You can restrict access to predefined users with this option. By default, this option is disabled.
--enable-fallback-to-detected-interface, --disable-fallback-to-detected-interface Fallback to auto-detected interface.        If for some reason the server is unable to bind to the interface specified in the listen_on option, then it will try to detect an interface that connects to the outside world and bind to that. By default, this option is enabled.
--enable-local-write, --disable-local-write Allow un-authenticated local connections to make changes. Normally, if you do not turn on authentication, the server operates in read-only mode, so as to not allow anonymous users to make changes to your calibre libraries. This option allows anybody connecting from the same computer as the server is running on to make changes. This is useful if you want to run the server without authentication but still use calibredb to make changes to your calibre libraries. Note that turning on this option means any program running on the computer can make changes to your calibre libraries. By default, this option is disabled.
--enable-log-not-found, --disable-log-not-found Log HTTP 404 (Not Found) requests.  Normally, the server logs all HTTP requests for resources that are not found. This can generate a lot of log spam, if your server is targeted by bots. Use this option to turn it off. By default, this option is enabled.
--enable-use-bonjour, --disable-use-bonjour Advertise OPDS feeds via BonJour.   Advertise the OPDS feeds via the BonJour service, so that OPDS based reading apps can detect and connect to the server automatically. By default, this option is enabled.
--enable-use-sendfile, --disable-use-sendfile Zero copy file transfers for increased performance.         This will use zero-copy in-kernel transfers when sending files over the network, increasing performance. However, it can cause corrupted file transfers on some broken filesystems. If you experience corrupted file transfers, turn it off. By default, this option is enabled.
--ignored-fields Ignored user-defined metadata fields.       Comma separated list of user-defined metadata fields that will not be displayed by the Content server in the /opds and /mobile views. For example: my_rating,my_tags
--listen-on The interface on which to listen for connections.   The default is to listen on all available IPv4 interfaces. You can change this to, for example, "127.0.0.1" to only listen for connections from the local machine, or to "::" to listen to all incoming IPv6 and IPv4 connections.
--log  Path to log file for server log. This log contains server information and errors, not access logs. By default it is written to stdout.
--manage-users Manage the database of users allowed to connect to this server. You can use it in automated mode by adding a --. See calibre-server --manage-users -- help for details. See also the --userdb option.
--max-header-line-size Max. size of single HTTP header (in KB).
--max-job-time Maximum time for worker processes.  Maximum amount of time worker processes are allowed to run (in minutes). Set to zero for no limit.
--max-jobs Maximum number of worker processes.         Worker processes are launched as needed and used for large jobs such as preparing a book for viewing, adding books, converting, etc. Normally, the max. number of such processes is based on the number of CPU cores. You can control it by this setting.
--max-log-size Max. log file size (in MB).         The maximum size of log files, generated by the server. When the log becomes larger than this size, it is automatically rotated. Set to zero to disable log rotation.
--max-opds-items Maximum number of books in OPDS feeds.      The maximum number of books that the server will return in a single OPDS acquisition feed.
--max-opds-ungrouped-items Maximum number of ungrouped items in OPDS feeds.    Group items in categories such as author/tags by first letter when there are more than this number of items. Set to zero to disable.
--max-request-body-size Max. allowed size for files uploaded to the server (in MB).
--num-per-page Number of books to show in a single page.   The number of books to show in a single page in the browser.
--pidfile Write process PID to the specified file
--port The port on which to listen for connections.
--search-the-net-urls Path to a JSON file containing URLs for the "Search the internet" feature. The easiest way to create such a file is to go to Preferences-> Sharing over the net->Search the internet in calibre, create the URLs and export them.
--shutdown-timeout Total time in seconds to wait for clean shutdown.
--ssl-certfile Path to the SSL certificate file.
--ssl-keyfile Path to the SSL private key file.
--timeout Time (in seconds) after which an idle connection is closed.
--trusted-ips Allow un-authenticated connections from specific IP addresses to make changes.      Normally, if you do not turn on authentication, the server operates in read-only mode, so as to not allow anonymous users to make changes to your calibre libraries. This option allows anybody connecting from the specified IP addresses to make changes. Must be a comma separated list of address or network specifications. This is useful if you want to run the server without authentication but still use calibredb to make changes to your calibre libraries. Note that turning on this option means anyone connecting from the specified IP addresses can make changes to your calibre libraries.
--url-prefix A prefix to prepend to all URLs.    Useful if you wish to run this server behind a reverse proxy. For example use, /calibre as the URL prefix.
--userdb Path to the user database to use for authentication. The database is a SQLite file. To create it use --manage-users. You can read more about managing users at: https://manual.calibre-ebook.com/server.html#managing-user-accounts-from-the-command-line-only
--worker-count Number of worker threads used to process requests.
SMARTCTL(8)                  SMART Monitoring Tools                  SMARTCTL(8)
smartctl - Control and Monitor Utility for SMART Disks
smartctl [options] device
[This man page is generated for the Linux version of smartmontools.  It does not contain info specific to other platforms.]
smartctl controls the Self-Monitoring, Analysis and Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS hard drives and solid-state drives.  The purpose of SMART is to monitor the reliability of the hard drive and predict drive failures, and to carry out different types of drive self-tests.  smartctl also supports some features not related to SMART.  This version of smartctl is compatible with ACS-3, ACS-2, ATA8-ACS, ATA/ATAPI-7 and earlier standards (see REFERENCES below).
smartctl also provides support for polling TapeAlert messages from SCSI tape drives and changers.
The user must specify the device to be controlled or interrogated as the final argument to smartctl.  The command set used by the device is often derived from the device path but may need help with the '-d' option (for more information see the section on "ATA, SCSI command sets and SAT" below).  Device paths are as follows:
LINUX:   Use the forms "/dev/sd[a-z]" for ATA/SATA and SCSI/SAS devices. For SCSI Tape Drives and Changers with TapeAlert support use the devices "/dev/nst*" and "/dev/sg*".  For disks behind 3ware controllers you may need "/dev/sd[a-z]" or "/dev/twe[0-9]", "/dev/twa[0-9]" or "/dev/twl[0-9]": see details below.  For disks behind HighPoint RocketRAID controllers you may need "/dev/sd[a-z]".  For disks behind Areca SATA RAID controllers, you need "/dev/sg[2-9]" (note that smartmontools interacts with the Areca controllers via a SCSI generic device which is different than the SCSI device used for reading and writing data)!  For HP Smart Array RAID controllers, there are three currently supported drivers: cciss, hpsa, and hpahcisr.  For disks accessed via the cciss driver the device nodes are of the form "/dev/cciss/c[0-9]d0".  For disks accessed via the hpahcisr and hpsa drivers, the device nodes you need are "/dev/sg[0-9]*". ("lsscsi -g" is helpful in determining which scsi generic device node corresponds to which device.)  Use the nodes corresponding to the RAID controllers, not the nodes corresponding to logical drives.  See the -d option below, as well.  Use the forms "/dev/nvme[0-9]" (broadcast namespace) or "/dev/nvme[0-9]n[1-9]" (specific namespace 1-9) for NVMe devices.
if '-' is specified as the device path, smartctl reads and interprets it's own debug output from standard input.  See '-r ataioctl' below for details.
smartctl guesses the device type if possible.  If necessary, the '-d' option can be used to override this guess.
Note that the printed output of smartctl displays most numerical values in base 10 (decimal), but some values are displayed in base 16 (hexadecimal).  To distinguish them, the base 16 values are always displayed with a leading "0x", for example: "0xff".  This man page follows the same convention.
The options are grouped below into several categories.  smartctl will execute the corresponding commands in the order: INFORMATION, ENABLE/DISABLE, DISPLAY DATA, RUN/ABORT TESTS.
SHOW INFORMATION OPTIONS:
-h, --help, --usage Prints a usage message to STDOUT and exits.
-V, --version, --copyright, --license Prints version, copyright, license, home page and SVN revision information for your copy of smartctl to STDOUT and then exits.
-i, --info Prints the device model number, serial number, firmware version, and ATA Standard version/revision information.  Says if the device supports SMART, and if so, whether SMART support is currently enabled or disabled.  If the device supports Logical Block Address mode (LBA mode) print current user drive capacity in bytes.  (If drive has a user protected area reserved, or is "clipped", this may be smaller than the potential maximum drive capacity.) Indicates if the drive is in the smartmontools database (see '-v' options below).  If so, the drive model family may also be printed.  If '-n' (see below) is specified, the power mode of the drive is printed.
[NVMe] For NVMe devices the information is obtained from the Identify Controller and the Identify Namespace data structure.
--identify[=[w][nvb]] [ATA only] Prints an annotated table of the IDENTIFY DEVICE data. By default, only valid words (words not equal to 0x0000 or 0xffff) and nonzero bits and bit fields are printed.  This can be changed by the optional argument which consists of one or two characters from the set 'wnvb'.  The character 'w' enables printing of all 256 words.  The character 'n' suppresses printing of bits, 'v' enables printing of all bits from valid words, 'b' enables printing of all bits.  For example '--identify=n' (valid words, no bits) produces the shortest output and '--identify=wb' (all words, all bits) produces the longest output.
-a, --all Prints all SMART information about the disk, or TapeAlert information about the tape drive or changer.  For ATA devices this is equivalent to '-H -i -c -A -l error -l selftest -l selective' and for SCSI, this is equivalent to '-H -i -A -l error -l selftest'. For NVMe, this is equivalent to '-H -i -c -A -l error'. Note that for ATA disks this does not enable the non-SMART options and the SMART options which require support for 48-bit ATA commands.
-x, --xall Prints all SMART and non-SMART information about the device.  For ATA devices this is equivalent to '-H -i -g all -g wcreorder -c -A -f brief -l xerror,error -l xselftest,selftest -l selective -l directory -l scttemp -l scterc -l devstat -l defects -l sataphy'. and for SCSI, this is equivalent to '-H -i -g all -A -l error -l selftest -l background -l sasphy'. For NVMe, this is equivalent to '-H -i -c -A -l error'.
--scan Scans for devices and prints each device name, device type and protocol ([ATA] or [SCSI]) info.  May be used in conjunction with '-d TYPE' to restrict the scan to a specific TYPE.  See also info about platform specific device scan and the DEVICESCAN directive on smartd(8) man page.
--scan-open Same as --scan, but also tries to open each device before printing device info.  The device open may change the device type due to autodetection (see also '-d test').
This option can be used to create a draft smartd.conf file.  All options after '--' are appended to each output line.  For example: smartctl --scan-open -- -a -W 4,45,50 -m admin@work > smartd.conf
Multiple '-d TYPE' options may be specified with '--scan[-open]' to combine the scan results of more than one TYPE.
-g NAME, --get=NAME Get non-SMART device settings.  See '-s, --set' below for further info.
RUN-TIME BEHAVIOR OPTIONS:
-j, --json[=cgiosuvy] Enables JSON or YAML output mode.
The output could be modified or enhanced by the optional argument which consists of one or more characters from the set 'cgiosuvy': 'c': Outputs compact format without extra spaces and newlines.  By default, output is pretty-printed.  If used with YAML format, the indentation of arrays is reduced. 'g': Outputs JSON structure as single assignments to allow the usage of grep.  Each assignment reflects the absolute path of a value.  The syntax is compatible with gron: 'json.KEY1[INDEX2].KEY3 = VALUE;'. 'o': Includes the full original plaintext output of smartctl as a JSON array 'smartctl.output[]'. 's': Outputs JSON object elements sorted by key.  By default, object elements are ordered as generated internally. 'v': Enables verbose output of possible unsafe integers.  If specified, values which may exceed JSON safe integer (53-bit) range are always output as a number (with some 'KEY') and a string ('KEY_s'), regardless of the actual value.  Values which may exceed 64-bit range are also output as a little endian byte array ('KEY_le').  By default, the additional elements are only output if the value actually exceeds the range. 'y': [NEW EXPERIMENTAL SMARTCTL FEATURE] Outputs in YAML format.
The following two arguments are primarily indented for development: 'i': Includes lines from the plaintext output which print info already implemented for JSON output.  The lines appear as strings with key 'smartctl_NNNN_i'. 'u': Includes lines from the plaintext output which print info still unimplemented for JSON output.  The lines appear as strings with key 'smartctl_NNNN_u'.
-q TYPE, --quietmode=TYPE Specifies that smartctl should run in one of the quiet modes described here.  The valid arguments to this option are:
errorsonly - only print: For the '-l error' option, if nonzero, the number of errors recorded in the SMART error log and the power-on time when they occurred; For the '-l selftest' option, errors recorded in the device self-test log; For the '-H' option, SMART "disk failing" status or device Attributes (pre-failure or usage) which failed either now or in the past; For the '-A' option, device Attributes (pre-failure or usage) which failed either now or in the past.
silent - print no output.  The only way to learn about what was found is to use the exit status of smartctl (see EXIT STATUS below).
noserial - Do not print the serial number of the device.
-d TYPE, --device=TYPE Specifies the type of the device.  The valid arguments to this option are:
auto - attempt to guess the device type from the device name or from controller type info provided by the operating system or from a matching USB ID entry in the drive database.  This is the default.
test - prints the guessed TYPE, then opens the device and prints the (possibly changed) TYPE name and then exits without performing any further commands.
ata - the device type is ATA.  This prevents smartctl from issuing SCSI commands to an ATA device.
scsi - the device type is SCSI.  This prevents smartctl from issuing ATA commands to a SCSI device.
nvme[,NSID] - the device type is NVM Express (NVMe).  The optional parameter NSID specifies the namespace id (in hex) passed to the driver.  Use 0xffffffff for the broadcast namespace id.  The default for NSID is the namespace id addressed by the device name.
sat[,auto][,N] - the device type is SCSI to ATA Translation (SAT). This is for ATA disks that have a SCSI to ATA Translation Layer (SATL) between the disk and the operating system.  SAT defines two ATA PASS THROUGH SCSI commands, one 12 bytes long and the other 16 bytes long.  The default is the 16 byte variant which can be overridden with either '-d sat,12' or '-d sat,16'.
If '-d sat,auto' is specified, device type SAT (for ATA/SATA disks) is only used if the SCSI INQUIRY data reports a SATL (VENDOR: "ATA     ").  Otherwise device type SCSI (for SCSI/SAS disks) is used.
usbcypress - this device type is for ATA disks that are behind a Cypress USB to PATA bridge.  This will use the ATACB proprietary scsi pass through command.  The default SCSI operation code is 0x24, but although it can be overridden with '-d usbcypress,0xN', where N is the scsi operation code, you're running the risk of damage to the device or filesystems on it.
usbjmicron[,p][,x][,PORT] - this device type is for SATA disks that are behind a JMicron USB to PATA/SATA bridge.  The 48-bit ATA commands (required e.g. for '-l xerror', see below) do not work with all of these bridges and are therefore disabled by default. These commands can be enabled by '-d usbjmicron,x'.  If two disks are connected to a bridge with two ports, an error message is printed if no PORT is specified.  The port can be specified by '-d usbjmicron[,x],PORT' where PORT is 0 (master) or 1 (slave).  This is not necessary if the device uses a port multiplier to connect multiple disks to one port.  The disks appear under separate /dev/ice names then.  CAUTION: Specifying ',x' for a device which does not support it results in I/O errors and may disconnect the drive.  The same applies if the specified PORT does not exist or is not connected to a disk.
The Prolific PL2507/3507 USB bridges with older firmware support a pass-through command similar to JMicron and work with '-d usbjmicron,0'.  Newer Prolific firmware requires a modified command which can be selected by '-d usbjmicron,p'.  Note that this does not yet support the SMART status command.
usbprolific - this device type is for SATA disks that are behind a Prolific PL2571/2771/2773/2775 USB to SATA bridge.
usbsunplus - this device type is for SATA disks that are behind a SunplusIT USB to SATA bridge.
sntjmicron[,NSID] - this device type is for NVMe disks that are behind a JMicron USB to NVMe bridge.  The optional parameter NSID specifies the namespace id (in hex) passed to the driver.  The default namespace id is the broadcast namespace id (0xffffffff).
sntrealtek - [NEW EXPERIMENTAL SMARTCTL FEATURE] this device type is for NVMe disks that are behind a Realtek USB to NVMe bridge.
marvell - [Linux only] interact with SATA disks behind Marvell chip-set controllers (using the Marvell rather than libata driver).
megaraid,N - [Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller.  The non- negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored.  Use syntax such as: smartctl -a -d megaraid,2 /dev/sda smartctl -a -d megaraid,0 /dev/sdb smartctl -a -d megaraid,0 /dev/bus/0 This interface will also work for Dell PERC controllers.  It is possible to set RAID device name as /dev/bus/N, where N is a SCSI bus number.
The following entry in /proc/devices must exist: For PERC2/3/4 controllers: megadevN For PERC5/6 controllers: megaraid_sas_ioctlN
aacraid,H,L,ID - [Linux, Windows and Cygwin only] the device consists of one or more SCSI/SAS or SATA disks connected to an AacRaid controller.  The non-negative integers H,L,ID (Host number, Lun, ID) denote which disk on the controller is monitored. Use syntax such as: smartctl -a -d aacraid,0,0,2 /dev/sda smartctl -a -d aacraid,1,0,4 /dev/sdb
Option '-d sat,auto+...' is implicitly enabled to detect SATA disks.  Use '-d scsi+aacraid,H,L,ID' to disable it.
On Linux, the following entry in /proc/devices must exist: aac. Character device nodes /dev/aacH (H=Host number) are created if required.
3ware,N - [FreeBSD and Linux only] the device consists of one or more ATA disks connected to a 3ware RAID controller.  The non- negative integer N (in the range from 0 to 127 inclusive) denotes which disk on the controller is monitored.  Use syntax such as: smartctl -a -d 3ware,2 /dev/sda  [Linux only] smartctl -a -d 3ware,0 /dev/twe0 smartctl -a -d 3ware,1 /dev/twa0 smartctl -a -d 3ware,1 /dev/twl0 [Linux only] smartctl -a -d 3ware,1 /dev/tws0 [FreeBSD only] The first two forms, which refer to devices /dev/sda-z (deprecated) and /dev/twe0-15, may be used with 3ware series 6000, 7000, and 8000 series controllers that use the 3x-xxxx driver. The devices /dev/twa0-15, must be used with 3ware 9000 series controllers, which use the 3w-9xxx driver.  The devices /dev/twl0-15 [Linux] or /dev/tws0-15 [FreeBSD] must be used with the 3ware/LSI 9750 series controllers which use the 3w-sas driver.
Note that if the special character device nodes /dev/tw[ls]?, /dev/twa?  and /dev/twe? do not exist, or exist with the incorrect major or minor numbers, smartctl will recreate them on the fly.
areca,N - [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA disks connected to an Areca SATA RAID controller.  The positive integer N (in the range from 1 to 24 inclusive) denotes which disk on the controller is monitored.  On Linux use syntax such as: smartctl -a -d areca,2 /dev/sg2 smartctl -a -d areca,3 /dev/sg3 The first line above addresses the second disk on the first Areca RAID controller.  The second line addresses the third disk on the second Areca RAID controller.  To help identify the correct device on Linux, use the command: cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices to show the SCSI generic devices (one per line, starting with /dev/sg0).  The correct SCSI generic devices to address for smartmontools are the ones with the type field equal to 3.  If the incorrect device is addressed, please read the warning/error messages carefully.  They should provide hints about what devices to use.
Important: the Areca controller must have firmware version 1.46 or later.  Lower-numbered firmware versions will give (harmless) SCSI error messages and no SMART information.
areca,N/E - [FreeBSD, Linux, Windows and Cygwin only] the device consists of one or more SATA or SAS disks connected to an Areca SAS RAID controller.  The integer N (range 1 to 128) denotes the channel (slot) and E (range 1 to 8) denotes the enclosure. Important: This requires Areca SAS controller firmware version 1.51 or later.
cciss,N - [FreeBSD and Linux only] the device consists of one or more SCSI/SAS or SATA disks connected to a cciss RAID controller. The non-negative integer N (in the range from 0 to 15 inclusive) denotes which disk on the controller is monitored.
Option '-d sat,auto+...' is implicitly enabled to detect SATA disks.  Use '-d scsi+cciss,N' to disable it.
To look at disks behind HP Smart Array controllers, use syntax such as: smartctl -a -d cciss,0 /dev/cciss/c0d0    (cciss driver under Linux) smartctl -a -d cciss,0 /dev/sg2    (hpsa or hpahcisr drivers under Linux)
hpt,L/M/N - [FreeBSD and Linux only] the device consists of one or more ATA disks connected to a HighPoint RocketRAID controller. The integer L is the controller id, the integer M is the channel number, and the integer N is the PMPort number if it is available. The allowed values of L are from 1 to 4 inclusive, M are from 1 to 128 inclusive and N from 1 to 4 if PMPort available.  And also these values are limited by the model of the HighPoint RocketRAID controller.  Use syntax such as: smartctl -a -d hpt,1/3 /dev/sda    (under Linux) smartctl -a -d hpt,1/2/3 /dev/sda    (under Linux) Note that the /dev/sda-z form should be the device node which stands for the disks derived from the HighPoint RocketRAID controllers under Linux and under FreeBSD, it is the character device which the driver registered (eg, /dev/hptrr, /dev/hptmv6).
intelliprop,N[+TYPE] - the device consists of multiple ATA disks connected to an Intelliprop controller.  The integer N is the port number from 0 to 3 of the ATA drive to be targeted.  The TYPE can be ata(default), sat, or a USB controller listed above.  Note: if a type of ATA does not work, try a type of sat.  Use syntax such as: smartctl -a -d intelliprop,1 /dev/sda    (under Linux) smartctl -a -d intelliprop,1+sat /dev/sda    (under Linux) WARNING: The disks are selected by write commands to the ATA Device Vendor Specific Log at address 0xc0.  Using this option with other devices may have undesirable side effects.
jmb39x[-q],N[,sLBA][,force][+TYPE] - [NEW EXPERIMENTAL SMARTCTL FEATURE] the device consists of multiple SATA disks connected to a JMicron JMB39x RAID port multiplier.  The suffix '-q' selects a slightly different command variant used by some QNAP NAS devices. The integer N is the port number from 0 to 4. WARNING: The ATA pass-through commands are issued via READ/WRITE commands to LBA 33 of the RAID volume.  Using this option with other devices may overwrite this sector. The LBA could be selected in the range 33 (last sector of a GPT) to 62 (last sector of traditional boot area). By default, access to the device is refused if the selected sector is not zero filled.  The 'force' flag disables this check. WARNING: Original sector data is not written back if smartctl is aborted with a signal.
jms56x,N[,sLBA][,force][+TYPE] - [NEW EXPERIMENTAL SMARTCTL FEATURE] the device consists of multiple SATA disks connected to a JMicron JMS56x USB to SATA RAID bridge.  See 'jmb39x...' above for valid arguments.
-T TYPE, --tolerance=TYPE [ATA only] Specifies how tolerant smartctl should be of ATA and SMART command failures.
The behavior of smartctl depends upon whether the command is "optional" or "mandatory".  Here "mandatory" means "required by the ATA Specification if the device implements the SMART command set" and "optional" means "not required by the ATA Specification even if the device implements the SMART command set."  The "mandatory" ATA and SMART commands are: (1) ATA IDENTIFY DEVICE, (2) SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE, (3) SMART ENABLE/DISABLE, and (4) SMART RETURN STATUS.
The valid arguments to this option are:
normal - exit on failure of any mandatory SMART command, and ignore all failures of optional SMART commands.  This is the default.  Note that on some devices, issuing unimplemented optional SMART commands doesn't cause an error.  This can result in misleading smartctl messages such as "Feature X not implemented", followed shortly by "Feature X: enabled".  In most such cases, contrary to the final message, Feature X is not enabled.
conservative - exit on failure of any optional SMART command.
permissive - ignore failure(s) of mandatory SMART commands.  This option may be given more than once.  Each additional use of this option will cause one more additional failure to be ignored.  Note that the use of this option can lead to messages like "Feature X not supported", followed shortly by "Feature X enable failed".  In a few such cases, contrary to the final message, Feature X is enabled.
verypermissive - equivalent to giving a large number of '-T permissive' options: ignore failures of any number of mandatory SMART commands.  Please see the note above.
-b TYPE, --badsum=TYPE [ATA only] Specifies the action smartctl should take if a checksum error is detected in the: (1) Device Identity Structure, (2) SMART Self-Test Log Structure, (3) SMART Attribute Value Structure, (4) SMART Attribute Threshold Structure, or (5) ATA Error Log Structure.
warn - report the incorrect checksum but carry on in spite of it. This is the default.
exit - exit smartctl.
ignore - continue silently without issuing a warning.
-r TYPE, --report=TYPE Intended primarily to help smartmontools developers understand the behavior of smartmontools on non-conforming or poorly conforming hardware.  This option reports details of smartctl transactions with the device.  The option can be used multiple times.  When used just once, it shows a record of the ioctl() transactions with the device.  When used more than once, the detail of these ioctl() transactions are reported in greater detail.  The valid arguments to this option are:
ioctl - report all ioctl() transactions.
ataioctl - report only ioctl() transactions with ATA devices.
scsiioctl - report only ioctl() transactions with SCSI devices. Invoking this once shows the SCSI commands in hex and the corresponding status.  Invoking it a second time adds a hex listing of the first 64 bytes of data send to, or received from the device.
nvmeioctl - report only ioctl() transactions with NVMe devices.
Any argument may include a positive integer to specify the level of detail that should be reported.  The argument should be followed by a comma then the integer with no spaces.  For example, ataioctl,2 The default level is 1, so '-r ataioctl,1' and '-r ataioctl' are equivalent.
For testing purposes, the output of '-r ataioctl,2' can later be parsed by smartctl itself if '-' is used as device path argument. The ATA command input parameters, sector data and return values are reconstructed from the debug report read from stdin.  Then smartctl internally simulates an ATA device with the same behaviour.  This is does not work for SCSI devices yet.
-n POWERMODE[,STATUS], --nocheck=POWERMODE[,STATUS] [ATA] [SCSI: NEW EXPERIMENTAL SMARTCTL FEATURE] Specifies if smartctl should exit before performing any checks when the device is in a low-power mode.  It may be used to prevent a disk from being spun-up by smartctl.  The power mode is ignored by default.
Note: If this option is used it may also be necessary to specify the device type with the '-d' option.  Otherwise the device may spin up due to commands issued during device type autodetection.
By default, exit status 2 is returned if the device is in one of the specified low-power modes.  This status is also returned if the device open or identification failed (see EXIT STATUS below). The optional STATUS parameter allows to override this default. STATUS is an integer in the range from 0 to 255 inclusive.  For example use '-n standby,0' to return success if a device is in SLEEP or STANDBY mode.  Use '-n standby,3' to return a unique exit status in this case.
never - check the device always, but print the power mode if '-i' is specified.
sleep[,STATUS] - check the device unless it is in SLEEP mode.
standby[,STATUS] - check the device unless it is in SLEEP or STANDBY mode.  In these modes most disks are not spinning, so if you want to prevent a disk from spinning up, this is probably what you want.
idle[,STATUS] - check the device unless it is in SLEEP, STANDBY or IDLE mode.  In the IDLE state, most disks are still spinning, so this is probably not what you want.
SMART FEATURE ENABLE/DISABLE COMMANDS:
Note: if multiple options are used to both enable and disable a feature, then both the enable and disable commands will be issued. The enable command will always be issued before the corresponding disable command.
-s VALUE, --smart=VALUE Enables or disables SMART on device.  The valid arguments to this option are on and off.
[ATA] Note that the ATA commands SMART ENABLE/DISABLE OPERATIONS were declared obsolete in ATA ACS-4 Revision 10 (Nov 2015).
[SCSI tape drive or changer] It is not necessary (or useful) to enable SMART to see the TapeAlert messages.
-o VALUE, --offlineauto=VALUE [ATA only] Enables or disables SMART automatic offline test, which scans the drive every four hours for disk defects.  This command can be given during normal system operation.  The valid arguments to this option are on and off.
Note that the SMART automatic offline test command is listed as "Obsolete" in every version of the ATA and ATA/ATAPI Specifications.  It was originally part of the SFF-8035i Revision 2.0 specification, but was never part of any ATA specification. However it is implemented and used by many vendors.  You can tell if automatic offline testing is supported by seeing if this command enables and disables it, as indicated by the 'Auto Offline Data Collection' part of the SMART capabilities report (displayed with '-c').
SMART provides three basic categories of testing.  The first category, called "online" testing, has no effect on the performance of the device.  It is turned on by the '-s on' option.
The second category of testing is called "offline" testing.  This type of test can, in principle, degrade the device performance. The '-o on' option causes this offline testing to be carried out, automatically, on a regular scheduled basis.  Normally, the disk will suspend offline testing while disk accesses are taking place, and then automatically resume it when the disk would otherwise be idle, so in practice it has little effect.  Note that a one-time offline test can also be carried out immediately upon receipt of a user command.  See the '-t offline' option below, which causes a one-time offline test to be carried out immediately.
The choice (made by the SFF-8035i and ATA specification authors) of the word testing for these first two categories is unfortunate, and often leads to confusion.  In fact these first two categories of online and offline testing could have been more accurately described as online and offline data collection.
The results of this automatic or immediate offline testing (data collection) are reflected in the values of the SMART Attributes. Thus, if problems or errors are detected, the values of these Attributes will go below their failure thresholds; some types of errors may also appear in the SMART error log.  These are visible with the '-A' and '-l error' options respectively.
Some SMART attribute values are updated only during off-line data collection activities; the rest are updated during normal operation of the device or during both normal operation and off- line testing.  The Attribute value table produced by the '-A' option indicates this in the UPDATED column.  Attributes of the first type are labeled "Offline" and Attributes of the second type are labeled "Always".
The third category of testing (and the only category for which the word 'testing' is really an appropriate choice) is "self" testing. This third type of test is only performed (immediately) when a command to run it is issued.  The '-t' and '-X' options can be used to carry out and abort such self-tests; please see below for further details.
Any errors detected in the self testing will be shown in the SMART self-test log, which can be examined using the '-l selftest' option.
Note: in this manual page, the word "Test" is used in connection with the second category just described, e.g. for the "offline" testing.  The words "Self-test" are used in connection with the third category.
-S VALUE, --saveauto=VALUE [ATA] Enables or disables SMART autosave of device vendor-specific Attributes.  The valid arguments to this option are on and off. Note that this feature is preserved across disk power cycles, so you should only need to issue it once.
The ATA standard does not specify a method to check whether SMART autosave is enabled.  Unlike SCSI (below), smartctl is unable to print a warning if autosave is disabled.
Note that the ATA commands SMART ENABLE/DISABLE AUTOSAVE were declared obsolete in ATA ACS-4 Revision 10 (Nov 2015).
[SCSI] For SCSI devices this toggles the value of the Global Logging Target Save Disabled (GLTSD) bit in the Control Mode Page. Some disk manufacturers set this bit by default.  This prevents error counters, power-up hours and other useful data from being placed in non-volatile storage, so these values may be reset to zero the next time the device is power-cycled.  If the GLTSD bit is set then 'smartctl -a' will issue a warning.  Use on to clear the GLTSD bit and thus enable saving counters to non-volatile storage.  For extreme streaming-video type applications you might consider using off to set the GLTSD bit.
-g NAME, --get=NAME, -s NAME[,VALUE], --set=NAME[,VALUE] Gets/sets non-SMART device settings.  Note that the '--set' option shares its short option '-s' with '--smart'.  Valid arguments are:
all - Gets all values.  This is equivalent to '-g aam -g apm -g lookahead -g security -g wcache -g rcache -g dsn'
aam[,N|off] - [ATA only] Gets/sets the Automatic Acoustic Management (AAM) feature (if supported).  A value of 128 sets the most quiet (slowest) mode and 254 the fastest (loudest) mode, 'off' disables AAM.  Devices may support intermediate levels. Values below 128 are defined as vendor specific (0) or retired (1 to 127).  Note that the AAM feature was declared obsolete in ATA ACS-2 Revision 4a (Dec 2010).