X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;f=smartd.8.in;h=38fcfaf23eb217649948fb703f1c0551e80130ce;hb=7af9336546f5d8f23d8760b67b3d835773e52f04;hp=d725f67018b54e29dcef899f724069076916b4dc;hpb=d008864df4d33c3dba4fd61cef8ea0ef9c944851;p=mirror_smartmontools-debian.git diff --git a/smartd.8.in b/smartd.8.in index d725f67..38fcfaf 100644 --- a/smartd.8.in +++ b/smartd.8.in @@ -1,50 +1,45 @@ .ig -Copyright (C) 2002-10 Bruce Allen - -$Id: smartd.8.in 3497 2011-12-13 20:17:08Z chrfranke $ +Copyright (C) 2002-10 Bruce Allen +Copyright (C) 2004-15 Christian Franke + +$Id: smartd.8.in 4120 2015-08-27 16:12:21Z samm2 $ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. - -You should have received a copy of the GNU General Public License (for -example COPYING); if not, write to the Free Software Foundation, Inc., -675 Mass Ave, Cambridge, MA 02139, USA. - -This code was originally developed as a Senior Thesis by Michael -Cornwell at the Concurrent Systems Laboratory (now part of the Storage -Systems Research Center), Jack Baskin School of Engineering, -University of California, Santa Cruz. http://ssrc.soe.ucsc.edu/ + +You should have received a copy of the GNU General Public License +(for example COPYING); If not, see . + +This code was originally developed as a Senior Thesis by Michael Cornwell +at the Concurrent Systems Laboratory (now part of the Storage Systems +Research Center), Jack Baskin School of Engineering, University of +California, Santa Cruz. http://ssrc.soe.ucsc.edu/ + .. -.TH SMARTD 8 CURRENT_SVN_DATE CURRENT_SVN_VERSION CURRENT_SVN_DATE +.TH SMARTD 8 "CURRENT_SVN_DATE" "CURRENT_SVN_VERSION" "SMART Monitoring Tools" .SH NAME \fBsmartd\fP \- SMART Disk Monitoring Daemon .SH SYNOPSIS .B smartd [options] -.\" %IF NOT OS Windows -.SH FULL PATH -.B /usr/local/sbin/smartd - -.\" %ENDIF NOT OS Windows -.SH PACKAGE VERSION -CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV - .SH DESCRIPTION .\" %IF NOT OS ALL .\"! [This man page is generated for the OS_MAN_FILTER version of smartmontools. .\"! It does not contain info specific to other platforms.] .\"! .PP .\" %ENDIF NOT OS ALL -\fBsmartd\fP is a daemon that monitors the Self-Monitoring, Analysis -and Reporting Technology (SMART) system built into many ATA-3 and -later ATA, IDE and SCSI-3 hard 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. This version of -\fBsmartd\fP is compatible with ATA/ATAPI-7 and earlier standards (see -\fBREFERENCES\fP below). +\fBsmartd\fP is a daemon that monitors 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. +This version of \fBsmartd\fP is compatible with +ACS-3, ACS-2, ATA8-ACS, ATA/ATAPI-7 and earlier standards +(see \fBREFERENCES\fP below). \fBsmartd\fP will attempt to enable SMART monitoring on ATA devices (equivalent to \fBsmartctl -s on\fP) and polls these and SCSI devices @@ -57,7 +52,7 @@ command-line option described below. In addition to logging to a file, \fBsmartd\fP can also be configured to send email warnings if problems are detected. Depending upon the -type of problem, you may want to run self\-tests on the disk, back up +type of problem, you may want to run self-tests on the disk, back up the disk, replace the disk, or use a manufacturer\'s utility to force reallocation of bad or unreadable disk sectors. If disk problems are detected, please see the \fBsmartctl\fP manual page and the @@ -73,9 +68,9 @@ file \fB/usr/local/etc/smartd.conf\fP (Windows: \fBEXEDIR/smartd.conf\fP). If the configuration file is subsequently modified, \fBsmartd\fP can be told to re-read the configuration file by sending it a \fBHUP\fP signal, for example with the command: -.fi +.br \fBkillall -HUP smartd\fP. -.fi +.br .\" %IF OS Windows (Windows: See NOTES below.) .\" %ENDIF OS Windows @@ -89,11 +84,11 @@ the contents of the (faulty) configuration file, as if the \fBHUP\fP signal had never been received. When \fBsmartd\fP is running in debug mode, the \fBINT\fP signal -(normally generated from a shell with CONTROL\-C) is treated in the +(normally generated from a shell with CONTROL-C) is treated in the same way as a \fBHUP\fP signal: it makes \fBsmartd\fP reload its configuration file. To exit \fBsmartd\fP use CONTROL-\e .\" %IF OS Windows -(Windows: CONTROL\-Break). +(Windows: CONTROL-Break). .\" %ENDIF OS Windows On startup, in the absence of the configuration file @@ -103,11 +98,13 @@ devices that support SMART. The scanning is done as follows: .IP \fBLINUX:\fP 9 Examine all entries \fB"/dev/hd[a-t]"\fP for IDE/ATA devices, and \fB"/dev/sd[a-z]"\fP, \fB"/dev/sd[a-c][a-z]"\fP -for SCSI or SATA devices. +for ATA/SATA or SCSI/SAS devices. +Disks behind RAID controllers are not included. .\" %ENDIF OS Linux .\" %IF OS FreeBSD .IP \fBFREEBSD:\fP 9 Authoritative list of disk devices is obtained from SCSI (CAM) and ATA subsystems. +Disks behind RAID controllers are not included. .\" %ENDIF OS FreeBSD .\" %IF OS NetBSD OpenBSD .IP \fBNETBSD/OPENBSD:\fP 9 @@ -116,57 +113,43 @@ Authoritative list of disk devices is obtained from sysctl .\" %ENDIF OS NetBSD OpenBSD .\" %IF OS Solaris .IP \fBSOLARIS:\fP 9 -Examine all entries \fB"/dev/rdsk/c?t?d?s?"\fP for IDE/ATA and SCSI disk +Examine all entries \fB"/dev/rdsk/*s0"\fP for IDE/ATA and SCSI disk devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape devices. .\" %ENDIF OS Solaris .\" %IF OS Darwin .IP \fBDARWIN:\fP 9 The IOService plane is scanned for ATA block storage devices. .\" %ENDIF OS Darwin -.\" %IF OS Windows -.IP \fBWINDOWS\ 9x/ME\fP: 9 -Examine all entries \fB"/dev/hd[a-d]"\fP (bitmask -from "\\\\.\\SMARTVSD") for IDE/ATA devices. -Examine all entries \fB"/dev/scsi[0\-9][0\-f]"\fP for SCSI devices -on ASPI adapter 0\-9, ID 0\-15. -.\" %ENDIF OS Windows .\" %IF OS Windows Cygwin -.IP \fBWINDOWS\ NT4/2000/XP/2003/Vista/Win7/2008\fP: 9 -Examine all entries \fB"/dev/sd[a-j]"\fP ("\\\\.\\PhysicalDrive[0-9]") -for IDE/(S)ATA and SCSI disk devices +.IP \fBWINDOWS\fP: 9 +Examine all entries \fB"/dev/sd[a\-z]"\fP, \fB"/dev/sd[a\-c][a\-z]"\fP +and \fB"/dev/sdd[a\-x]"\fP ("\\\\.\\PhysicalDrive[0\-127]") for +IDE/(S)ATA and SCSI disk devices. If a 3ware 9000 controller is installed, examine all entries \fB"/dev/sdX,N"\fP for the first logical drive (\'unit\' \fB"/dev/sdX"\fP) and all physical disks (\'ports\' \fB",N"\fP) detected behind this controller. Same for a second controller if present. -[NEW EXPERIMENTAL SMARTD FEATURE] If directive \'\-d csmi\' is specified, -examine all entries \fB"/dev/csmi[0\-9],N"\fP for drives behind Intel -Matrix RAID driver. +If directive \'\-d csmi\' or no \'\-d\' directive is specified, +examine all entries \fB"/dev/csmi[0\-9],N"\fP for drives behind an Intel +ICHxR controller with RST driver. + +Disks behind Areca RAID controllers are not included. .\" %ENDIF OS Windows Cygwin -.\" %IF OS Cygwin -.IP \fBCYGWIN\fP: 9 -See "WINDOWS NT4/2000/XP/2003/Vista/Win7/2008" above. -.\" %ENDIF OS Cygwin -.\" %IF OS OS2 -.IP \fBOS/2,eComStation\fP: 9 -Use the form \fB"/dev/hd[a\-z]"\fP for IDE/ATA devices. -.\" %ENDIF OS OS2 .PP \fBsmartd\fP then monitors for \fIall\fP possible SMART errors (corresponding to the \fB\'\-a\'\fP -Directive in the configuration file; see \fBCONFIGURATION FILE\fP -below). - -.SH -OPTIONS +Directive in the configuration file; see the \fBsmartd.conf\fP(5) man page). +.SH OPTIONS .TP .B \-A PREFIX, \-\-attributelog=PREFIX -[ATA only] Writes \fBsmartd\fP attribute information (normalized and raw -attribute values) to files \'PREFIX\'\'MODEL\-SERIAL.ata.csv\'. At each +Writes \fBsmartd\fP attribute information (normalized and raw +attribute values) to files \'PREFIX\'\'MODEL\-SERIAL.ata.csv\' or \'PREFIX\'\'VENDOR\-MODEL\-SERIAL.scsi.csv\'. At each check cycle attributes are logged as a line of semicolon separated triplets of the form "attribute-ID;attribute-norm-value;attribute-raw-value;". +For SCSI devices error counters and temperature recorded in the form "counter-name;counter-value;" Each line is led by a date string of the form "yyyy-mm-dd HH:MM:SS" (in UTC). .\" %IF ENABLE_ATTRIBUTELOG @@ -200,13 +183,14 @@ can be used to verify the existence of the default configuration file. By using \'\-\' for FILE, the configuration is read from standard input. This is useful for commands like: .nf -.B echo /dev/hdb \-m user@home \-M test | smartd \-c \- \-q onecheck +.B echo /dev/sdb \-m user@home \-M test | smartd \-c \- \-q onecheck .fi to perform quick and simple checks without a configuration file. .\" %IF ENABLE_CAPABILITIES .TP .B \-C, \-\-capabilities -Use \fBcapabilities(7)\fP. +[Linux only] Use libcap-ng to drop unneeded Linux process \fBcapabilities\fP(7). +The following capabilities are kept: CAP_SYS_ADMIN, CAP_SYS_RAWIO, CAP_MKNOD. Warning: Mail notification does not work when used. .\" %ENDIF ENABLE_CAPABILITIES @@ -214,16 +198,16 @@ Warning: Mail notification does not work when used. .B \-d, \-\-debug Runs \fBsmartd\fP in "debug" mode. In this mode, it displays status information to STDOUT rather than logging it to SYSLOG and does not -\fBfork(2)\fP into the background and detach from the controlling +\fBfork\fP(2) into the background and detach from the controlling terminal. In this mode, \fBsmartd\fP also prints more verbose information about what it is doing than when operating in "daemon" -mode. In this mode, the \fBQUIT\fP signal (normally generated from a -terminal with CONTROL\-C) makes \fBsmartd\fP reload its configuration +mode. In this mode, the \fBINT\fP signal (normally generated from a +terminal with CONTROL-C) makes \fBsmartd\fP reload its configuration file. Please use CONTROL-\e to exit .\" %IF OS Windows -(Windows: CONTROL\-Break). +(Windows: CONTROL-Break). -Windows only: The "debug" mode can be toggled by the command +[Windows only] The "debug" mode can be toggled by the command \fBsmartd sigusr2\fP. A new console for debug output is opened when debug mode is enabled. .\" %ENDIF OS Windows @@ -231,8 +215,8 @@ debug mode is enabled. .B \-D, \-\-showdirectives Prints a list (to STDOUT) of all the possible Directives which may appear in the configuration file /usr/local/etc/smartd.conf, and then exits. -These Directives are also described later in this man page. They may -appear in the configuration file following the device name. +These Directives are described in the \fBsmartd.conf\fP(5) man page. +They may appear in the configuration file following the device name. .TP .B \-h, \-\-help, \-\-usage Prints usage message to STDOUT and exits. @@ -255,7 +239,7 @@ also use: .B killall -USR1 smartd .fi for the same purpose. -.fi +.br .\" %IF OS Windows (Windows: See NOTES below.) .\" %ENDIF OS Windows @@ -268,35 +252,14 @@ then by default messages from \fBsmartd\fP are logged to the facility \fIdaemon\fP. If you would like to have \fBsmartd\fP messages logged somewhere other -than the default location, this can typically be accomplished with -(for example) the following steps: -.RS 7 -.IP \fB[1]\fP 4 -Modify the script that starts \fBsmartd\fP to include the \fBsmartd\fP -command-line argument \'\-l local3\'. This tells \fBsmartd\fP to log its -messages to facility \fBlocal3\fP. -.IP \fB[2]\fP 4 -Modify the \fBsyslogd\fP configuration file (typically -\fB/etc/syslog.conf\fP) by adding a line of the form: -.nf -\fBlocal3.* /var/log/smartd.log\fP -.fi -This tells \fBsyslogd\fP to log all the messages from facility \fBlocal3\fP to -the designated file: /var/log/smartd.log. -.IP \fB[3]\fP 4 -Tell \fBsyslogd\fP to re-read its configuration file, typically by -sending the \fBsyslogd\fP process a \fBSIGHUP\fP hang-up signal. -.IP \fB[4]\fP 4 -Start (or restart) the \fBsmartd\fP daemon. -.RE -.\" The following two lines are a workaround for a man2html bug. Please leave them. -.\" They define a non-existent option; useful because man2html can't correctly reset the margins. -.TP -.B \& +than the default location, include (for example) \'\-l local3\' in its +start up argument list. +Tell the syslog daemon to log all messages from facility \fBlocal3\fP +to (for example) \'/var/log/smartd.log\'. + For more detailed information, please refer to the man pages for -\fBsyslog.conf\fP, \fBsyslogd\fP, and \fBsyslog\fP. You may also want -to modify the log rotation configuration files; see the man pages for -\fBlogrotate\fP and examine your system\'s /etc/logrotate.conf file. +the local syslog daemon, typically \fBsyslogd\fP(8), \fBsyslog-ng\fP(8) +or \fBrsyslogd\fP(8). .\" %IF OS Cygwin Cygwin: If no \fBsyslogd\fP is running, the \'\-l\' option has no effect. @@ -308,23 +271,17 @@ Windows: Some \fBsyslog\fP functionality is implemented internally in \fBsmartd\fP as follows: If no \'\-l\' option (or \'\-l daemon\') is specified, messages are written to Windows event log or to file \fB./smartd.log\fP if event log is not available -(Win9x/ME or access denied). By specifying other values of FACILITY, +(access denied). By specifying other values of FACILITY, log output is redirected as follows: \'\-l local0\' to file \fB./smartd.log\fP, \'\-l local1\' to standard output (redirect with \'>\' to any file), \'\-l local2\' to standard error, \'\-l local[3-7]\': to file \fB./smartd[1-5].log\fP. - -When using the event log, the enclosed utility \fBsyslogevt.exe\fP -should be registered as an event message file to avoid error -messages from the event viewer. Use \'\fBsyslogevt -r smartd\fP\' -to register, \'\fBsyslogevt -u smartd\fP\' to unregister and -\'\fBsyslogevt\fP\' for more help. .\" %ENDIF OS Windows .TP .B \-n, \-\-no\-fork Do not fork into background; this is useful when executed from modern -init methods like initng, minit or supervise. +init methods like initng, minit, supervise or systemd. .\" %IF OS Cygwin On Cygwin, this allows running \fBsmartd\fP as service via cygrunsrv, @@ -392,7 +349,7 @@ a list of future scheduled self tests to stdout, and then exit with zero exit status if all of these steps worked correctly. Device's SMART status is not checked. -This option is intended to test whether the '-s REGEX' directives in +This option is intended to test whether the '\-s REGEX' directives in smartd.conf will have the desired effect. The output lists the next test schedules, limited to 5 tests per type and device. This is followed by a summary of all tests of each device within the next 90 days. @@ -427,17 +384,19 @@ The default level is 1, so \'\-r ataioctl,1\' and \'\-r ataioctl\' are equivalent. .TP .B \-s PREFIX, \-\-savestates=PREFIX -[ATA only] Reads/writes \fBsmartd\fP state information from/to files -\'PREFIX\'\'MODEL\-SERIAL.ata.state\'. This preserves SMART attributes, drive -min and max temperatures (\-W directive), info about last sent warning email +Reads/writes \fBsmartd\fP state information from/to files +\'PREFIX\'\'MODEL\-SERIAL.ata.state\' or \'PREFIX\'\'VENDOR\-MODEL\-SERIAL.scsi.state\'. +This preserves SMART attributes, drive min and max temperatures (\-W directive), +info about last sent warning email (\-m directive), and the time of next check of the self-test REGEXP (\-s directive) across boot cycles. .\" %IF ENABLE_SAVESTATES If this option is not specified, state information is maintained in files -\'/usr/local/var/lib/smartmontools/smartd.MODEL\-SERIAL.ata.state\'. +\'/usr/local/var/lib/smartmontools/smartd.MODEL\-SERIAL.ata.state\' for ATA devices and +\'/usr/local/var/lib/smartmontools/smartd.VENDOR\-MODEL\-SERIAL.scsi.state\' for SCSI devices. To disable state files, specify this option with an empty string -argument: \'-s ""\'. +argument: \'\-s ""\'. .\" %ENDIF ENABLE_SAVESTATES MODEL and SERIAL are build from drive identify information, invalid characters are replaced by underline. @@ -453,10 +412,25 @@ always (re)written after reading the configuration file, before rereading the configuration file (SIGHUP), before smartd shutdown, and after a check forced by SIGUSR1. After a normal check cycle, a file is only rewritten if an important change (which usually results in a SYSLOG output) occurred. +.TP +.B \-w PATH, \-\-warnexec=PATH +Run the executable PATH instead of the default script when smartd +needs to send warning messages. PATH must point to an executable binary +file or script. +The default script is +.\" %IF NOT OS Windows +\fB/usr/local/etc/smartd_warning.sh\fP. +.\" %ENDIF NOT OS Windows +.\" %IF OS ALL +(Windows: EXEDIR/smartd_warning.cmd) +.\" %ENDIF OS ALL +.\" %IF OS Windows +.\"! \fBEXEDIR/smartd_warning.cmd\fP. +.\" %ENDIF OS Windows .\" %IF OS Windows .TP .B \-\-service -Windows only: Enables \fBsmartd\fP to run as a Windows service. +[Windows only] Enables \fBsmartd\fP to run as a Windows service. The option must be specified in the service command line as the first argument. It should not be used from console. See NOTES below for details. @@ -468,30 +442,26 @@ information for your copy of \fBsmartd\fP to STDOUT and then exits. Please include this information if you are reporting bugs or problems. .SH EXAMPLES - -.B -smartd -.fi +.B smartd +.br Runs the daemon in forked mode. This is the normal way to run \fBsmartd\fP. Entries are logged to SYSLOG. -.B -smartd -d -i 30 -.fi +.B smartd -d -i 30 +.br Run in foreground (debug) mode, checking the disk status every 30 seconds. -.B -smartd -q onecheck -.fi +.B smartd -q onecheck +.br Registers devices, and checks the status of the devices exactly -once. The exit status (the bash +once. The exit status (the shell .B $? variable) will be zero if all went well, and nonzero if no devices were detected or some other problem was encountered. -.fi +.\" %IF ENABLE_INITSCRIPT Note that \fBsmartmontools\fP provides a start-up script in \fB/usr/local/etc/rc.d/init.d/smartd\fP which is responsible for starting and stopping the daemon via the normal init interface. Using this script, @@ -503,8 +473,11 @@ and stop it by using the command: .nf .B /usr/local/etc/rc.d/init.d/smartd stop .fi + +.\" %ENDIF ENABLE_INITSCRIPT .SH CONFIGURATION -The syntax of the smartd.conf(5) file is discussed separately. +The syntax of the \fBsmartd.conf\fP(5) file is discussed separately. + .SH NOTES \fBsmartd\fP will make log entries at loglevel @@ -515,7 +488,7 @@ or .B \'\-u\' Directives. For example: .nf -.B \'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93\' +.B \'Device: /dev/sda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93\' .fi Note that in this message, the value given is the \'Normalized\' not the \'Raw\' Attribute value (the disk temperature in this case is about 22 @@ -526,7 +499,7 @@ and Directives modify this behavior, so that the information is printed with the Raw values as well, for example: .nf -.B \'Device: /dev/hda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]\' +.B \'Device: /dev/sda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]\' .fi Here the Raw values are the actual disk temperatures in Celsius. The way in which the Raw values are printed, and the names under which the @@ -544,7 +517,7 @@ will make log entries at loglevel .B LOG_CRIT if a SMART Attribute has failed, for example: .nf -.B \'Device: /dev/hdc, Failed SMART Attribute: 5 Reallocated_Sector_Ct\' +.B \'Device: /dev/sdc, Failed SMART Attribute: 5 Reallocated_Sector_Ct\' .fi This loglevel is used for reporting enabled by the .B \'\-H\', \-f\', \'\-l\ selftest\', @@ -570,24 +543,27 @@ to read: ...;daemon.info;... /var/adm/messages .fi Alternatively, you can use a local facility to log messages: please -see the \fBsmartd\fP '-l' command-line option described above. +see the \fBsmartd\fP '\-l' command-line option described above. .\" %ENDIF OS Solaris .\" %IF OS Cygwin The Cygwin Version of \fBsmartd\fP can be run as a service via the -cygrunsrv tool. The start-up script provides Cygwin-specific commands -to install and remove the service: +cygrunsrv tool. +.\" %IF ENABLE_INITSCRIPT +The start-up script provides Cygwin-specific commands to install and +remove the service: .nf .B /usr/local/etc/rc.d/init.d/smartd install [options] .B /usr/local/etc/rc.d/init.d/smartd remove .fi The service can be started and stopped by the start-up script as usual (see \fBEXAMPLES\fP above). +.\" %ENDIF ENABLE_INITSCRIPT .\" %ENDIF OS Cygwin .\" %IF OS Windows On Windows, the log messages are written to the event log or to a file. -See documentation of the '-l FACILITY' option above for details. +See documentation of the '\-l FACILITY' option above for details. On Windows, the following built-in commands can be used to control \fBsmartd\fP, if running as a daemon: @@ -609,22 +585,24 @@ The Windows Version of \fBsmartd\fP has buildin support for services: \'\fBsmartd install [options]\fP\' installs a service named "smartd" (display name "SmartD Service") using the command line \'/INSTALLPATH/smartd.exe \-\-service [options]\'. +This also installs smartd.exe as a event message file for the Windows +event viewer. -\'\fBsmartd remove\fP\' can later be used to remove the service entry -from registry. +\'\fBsmartd remove\fP\' can later be used to remove the service and +event message entries from the registry. Upon startup, the smartd service changes the working directory to its own installation path. If smartd.conf and blat.exe are stored in this directory, no \'-c\' option and \'-M exec\' directive is needed. -The debug mode (\'-d\', \'-q onecheck\') does not work if smartd is +The debug mode (\'\-d\', \'\-q onecheck\') does not work if smartd is running as service. The service can be controlled as usual with Windows commands \'net\' or \'sc\' (\'\fBnet start smartd\fP\', \'\fBnet stop smartd\fP\'). Pausing the service (\'\fBnet pause smartd\fP\') sets the interval between -disk checks (\'-i N\') to infinite. +disk checks (\'\-i N\') to infinite. Continuing the paused service (\'\fBnet continue smartd\fP\') resets the interval and rereads the configuration file immediately (like \fBSIGHUP\fP): @@ -635,25 +613,21 @@ checks disks immediately (like \fBSIGUSR1\fP). .\" %ENDIF OS Windows .SH LOG TIMESTAMP TIMEZONE - When \fBsmartd\fP makes log entries, these are time-stamped. The time stamps are in the computer's local time zone, which is generally set using either the environment variable \'\fBTZ\fP\' or using a time-zone file such as \fB/etc/localtime\fP. You may wish to change the timezone while \fBsmartd\fP is running (for example, if you carry a laptop to a new time-zone and don't reboot it). Due to a bug in the -\fBtzset(3)\fP function of many unix standard C libraries, the +\fBtzset\fP(3) function of many unix standard C libraries, the time-zone stamps of \fBsmartd\fP might not change. For some systems, \fBsmartd\fP will work around this problem \fIif\fP the time-zone is set using \fB/etc/localtime\fP. The work-around \fIfails\fP if the time-zone is set using the \'\fBTZ\fP\' variable (or a file that it points to). - -.SH RETURN VALUES -The return value (exit status) of -\fBsmartd\fP -can have the following values: +.SH EXIT STATUS +The exit status (return value) of \fBsmartd\fP can have the following values: .TP .B 0: Daemon startup successful, or \fBsmartd\fP was killed by a SIGTERM (or in debug mode, a SIGQUIT). @@ -671,7 +645,7 @@ Forking the daemon failed. Couldn\'t create PID file. .TP .B 5: -Config file does not exist (only returned in conjunction with the \'-c\' option). +Config file does not exist (only returned in conjunction with the \'\-c\' option). .TP .B 6: Config file exists, but cannot be read. @@ -680,16 +654,11 @@ Config file exists, but cannot be read. \fBsmartd\fP ran out of memory during startup. .TP -.B 9: -A compile time constant of\fB smartd\fP was too small. This can be caused by an -excessive number of disks, or by lines in \fB /usr/local/etc/smartd.conf\fP that are too long. -Please report this problem to \fB smartmontools-support@lists.sourceforge.net\fP. -.TP -.B 10 +.B 10: An inconsistency was found in \fBsmartd\fP\'s internal data structures. This should never happen. It must be due to either a coding or compiler bug. \fIPlease\fP report such failures to -smartmontools-support@lists.sourceforge.net. +smartmontools developers, see REPORTING BUGS below. .TP .B 16: A device explicitly listed in @@ -715,77 +684,88 @@ status is then 128 plus the signal number. For example if \fBsmartd\fP is killed by SIGKILL (signal 9) then the exit status is 137. -.PP -.SH AUTHOR -\fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net -.fi -University of Wisconsin \- Milwaukee Physics Department - -.PP -.SH CONTRIBUTORS -The following have made large contributions to smartmontools: -.nf -\fBCasper Dik\fP (Solaris SCSI interface) -\fBChristian Franke\fP (Windows interface, C++ redesign, USB support, ...) -\fBDouglas Gilbert\fP (SCSI subsystem) -\fBGuido Guenther\fP (Autoconf/Automake packaging) -\fBGeoffrey Keating\fP (Darwin ATA interface) -\fBEduard Martinescu\fP (FreeBSD interface) -\fBFr\['e]d\['e]ric L. W. Meunier\fP (Web site and Mailing list) -\fBGabriele Pohl\fP (Web site and Wiki, conversion from CVS to SVN) -\fBKeiji Sawada\fP (Solaris ATA interface) -\fBManfred Schwarb\fP (Drive database) -\fBSergey Svishchev\fP (NetBSD interface) -\fBDavid Snyder and Sergey Svishchev\fP (OpenBSD interface) -\fBPhil Williams\fP (User interface and drive database) -\fBShengfeng Zhou\fP (Linux/FreeBSD HighPoint RocketRAID interface) -.fi -Many other individuals have made smaller contributions and corrections. - -.PP -.SH CREDITS -.fi -This code was derived from the smartsuite package, written by Michael -Cornwell, and from the previous UCSC smartsuite package. It extends -these to cover ATA\-5 disks. This code was originally developed as a -Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory -(now part of the Storage Systems Research Center), Jack Baskin School -of Engineering, University of California, Santa -Cruz. \fBhttp://ssrc.soe.ucsc.edu/\fP . -.SH -HOME PAGE FOR SMARTMONTOOLS: -.fi -Please see the following web site for updates, further documentation, bug -reports and patches: \fBhttp://smartmontools.sourceforge.net/\fP +.\" %IF NOT OS Windows +.SH FILES +.TP +.B /usr/local/sbin/smartd +full path of this executable. +.TP +.B /usr/local/etc/smartd.conf +configuration file (see \fBsmartd.conf\fP(5) man page). +.TP +.B /usr/local/etc/smartd_warning.sh +script run on warnings (see \'\-M exec\' directive on +\fBsmartd.conf\fP(5) man page). +.\" %IF ENABLE_SMARTDPLUGINDIR +.TP +.B /usr/local/etc/smartd_warning.d/ +plugin directory for smartd warning script (see \'\-m\' directive on +\fBsmartd.conf\fP(5) man page). +.\" %ENDIF ENABLE_SMARTDPLUGINDIR +.\" %IF ENABLE_DRIVEDB +.TP +.B /usr/local/share/smartmontools/drivedb.h +drive database (see \'\-B\' option). +.\" %ENDIF ENABLE_DRIVEDB +.TP +.B /usr/local/etc/smart_drivedb.h +optional local drive database (see \'\-B\' option). -.SH -SEE ALSO: -\fBsmartd.conf\fP(5), \fBsmartctl\fP(8), \fBsyslogd\fP(8), -\fBsyslog.conf\fP(5), \fBbadblocks\fP(8), \fBide\-smart\fP(8), \fBregex\fP(7). +.\" %ENDIF NOT OS Windows +.SH AUTHORS +\fBBruce Allen\fP (project initiator), +.br +\fBChristian Franke\fP (project manager, Windows port and all sort of things), +.br +\fBDouglas Gilbert\fP (SCSI subsystem), +.br +\fBVolker Kuhlmann\fP (moderator of support and database mailing list), +.br +\fBGabriele Pohl\fP (wiki & development team support), +.br +\fBAlex Samorukov\fP (FreeBSD port and more, new Trac wiki). + +Many other individuals have made contributions and corrections, +see AUTHORS, ChangeLog and repository files. + +The first smartmontools code was derived from the smartsuite package, +written by Michael Cornwell and Andre Hedrick. + +.SH REPORTING BUGS +To submit a bug report, create a ticket in smartmontools wiki: +.br +<\fBhttp://www.smartmontools.org/\fP>. +.br +Alternatively send the info to the smartmontools support mailing list: +.br +<\fBhttps://lists.sourceforge.net/lists/listinfo/smartmontools-support\fB>. + +.SH SEE ALSO +\fBsmartd.conf\fP(5), \fBsmartctl\fP(8), \fBupdate-smart-drivedb\fP(8). + +.SH REFERENCES +Please see the following web site for more info: +\fBhttp://www.smartmontools.org/\fP -.SH -REFERENCES FOR SMART -.fi An introductory article about smartmontools is \fIMonitoring Hard Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004, -pages 74\-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP +pages 74-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP online. If you would like to understand better how SMART works, and what it does, a good place to start is with Sections 4.8 and 6.54 of the first -volume of the \'AT Attachment with Packet Interface\-7\' (ATA/ATAPI\-7) +volume of the \'AT Attachment with Packet Interface-7\' (ATA/ATAPI-7) specification Revision 4b. This documents the SMART functionality which the \fBsmartmontools\fP utilities provide access to. -.fi -The functioning of SMART was originally defined by the SFF\-8035i -revision 2 and the SFF\-8055i revision 1.4 specifications. These are +The functioning of SMART was originally defined by the SFF-8035i +revision 2 and the SFF-8055i revision 1.4 specifications. These are publications of the Small Form Factors (SFF) Committee. Links to these and other documents may be found on the Links page of the -\fBsmartmontools\fP Wiki at -\fBhttp://sourceforge.net/apps/trac/smartmontools/wiki/Links\fP . +\fBsmartmontools\fP Wiki at \fBhttp://www.smartmontools.org/wiki/Links\fP . -.SH -SVN ID OF THIS PAGE: -$Id: smartd.8.in 3497 2011-12-13 20:17:08Z chrfranke $ +.SH PACKAGE VERSION +CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV +.br +$Id: smartd.8.in 4120 2015-08-27 16:12:21Z samm2 $