Diff for /embedaddon/smartmontools/smartd.8.in between versions 1.1.1.2 and 1.1.1.3

version 1.1.1.2, 2012/10/09 09:36:45 version 1.1.1.3, 2013/07/22 01:17:36
Line 1 Line 1
 .ig  .ig
 Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>  Copyright (C) 2002-10 Bruce Allen <smartmontools-support@lists.sourceforge.net>
 Copyright (C) 2004-13 Christian Franke <smartmontools-support@lists.sourceforge.net>
 
 $Id$  $Id$
   
 This program is free software; you can redistribute it and/or modify  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  it under the terms of the GNU General Public License as published by
 the Free Software Foundation; either version 2, or (at your option)  the Free Software Foundation; either version 2, or (at your option)
 any later version.  any later version.
 
You should have received a copy of the GNU General Public License (forYou should have received a copy of the GNU General Public License
example COPYING); if not, write to the Free Software Foundation, Inc.,(for example COPYING); If not, see <http://www.gnu.org/licenses/>.
675 Mass Ave, Cambridge, MA 02139, USA.
 This code was originally developed as a Senior Thesis by Michael Cornwell
This code was originally developed as a Senior Thesis by Michaelat the Concurrent Systems Laboratory (now part of the Storage Systems
Cornwell at the Concurrent Systems Laboratory (now part of the StorageResearch Center), Jack Baskin School of Engineering, University of
Systems Research Center), Jack Baskin School of Engineering,California, Santa Cruz. http://ssrc.soe.ucsc.edu/
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 CURRENT_SVN_DATE
 .SH NAME  .SH NAME
Line 38  CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV Line 39  CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV
 .\"! It does not contain info specific to other platforms.]  .\"! It does not contain info specific to other platforms.]
 .\"! .PP  .\"! .PP
 .\" %ENDIF NOT OS ALL  .\" %ENDIF NOT OS ALL
\fBsmartd\fP is a daemon that monitors the Self-Monitoring, Analysis\fBsmartd\fP is a daemon that monitors the Self-Monitoring, Analysis and
and Reporting Technology (SMART) system built into many ATA-3 andReporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS
later ATA, IDE and SCSI-3 hard drives. The purpose of SMART is tohard drives and solid-state drives.
monitor the reliability of the hard drive and predict drive failures,The purpose of SMART is to monitor the reliability of the hard drive
and to carry out different types of drive self-tests.  This version ofand predict drive failures, and to carry out different types of drive
\fBsmartd\fP is compatible with ATA/ATAPI-7 and earlier standards (seeself-tests.
\fBREFERENCES\fP below).This version of \fBsmartd\fP is compatible with
 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  \fBsmartd\fP will attempt to enable SMART monitoring on ATA devices
 (equivalent to \fBsmartctl -s on\fP) and polls these and SCSI devices  (equivalent to \fBsmartctl -s on\fP) and polls these and SCSI devices
Line 57  command-line option described below. Line 60  command-line option described below.
   
 In addition to logging to a file, \fBsmartd\fP can also be configured  In addition to logging to a file, \fBsmartd\fP can also be configured
 to send email warnings if problems are detected.  Depending upon the  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 uptype 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  the disk, replace the disk, or use a manufacturer\'s utility to force
 reallocation of bad or unreadable disk sectors.  If disk problems are  reallocation of bad or unreadable disk sectors.  If disk problems are
 detected, please see the \fBsmartctl\fP manual page and the  detected, please see the \fBsmartctl\fP manual page and the
Line 89  the contents of the (faulty) configuration file, as if Line 92  the contents of the (faulty) configuration file, as if
 signal had never been received.  signal had never been received.
   
 When \fBsmartd\fP is running in debug mode, the \fBINT\fP signal  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  same way as a \fBHUP\fP signal: it makes \fBsmartd\fP reload its
 configuration file. To exit \fBsmartd\fP use CONTROL-\e  configuration file. To exit \fBsmartd\fP use CONTROL-\e
 .\" %IF OS Windows  .\" %IF OS Windows
(Windows: CONTROL\-Break).(Windows: CONTROL-Break).
 .\" %ENDIF OS Windows  .\" %ENDIF OS Windows
   
 On startup, in the absence of the configuration file  On startup, in the absence of the configuration file
Line 104  devices that support SMART.  The scanning is done as f Line 107  devices that support SMART.  The scanning is done as f
 Examine all entries \fB"/dev/hd[a-t]"\fP for IDE/ATA  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  devices, and \fB"/dev/sd[a-z]"\fP, \fB"/dev/sd[a-c][a-z]"\fP
 for SCSI or SATA devices.  for SCSI or SATA devices.
   Disks behind RAID controllers are not included.
 .\" %ENDIF OS Linux  .\" %ENDIF OS Linux
 .\" %IF OS FreeBSD  .\" %IF OS FreeBSD
 .IP \fBFREEBSD:\fP 9  .IP \fBFREEBSD:\fP 9
 Authoritative list of disk devices is obtained from SCSI (CAM) and ATA subsystems.  Authoritative list of disk devices is obtained from SCSI (CAM) and ATA subsystems.
   Disks behind RAID controllers are not included.
 .\" %ENDIF OS FreeBSD  .\" %ENDIF OS FreeBSD
 .\" %IF OS NetBSD OpenBSD  .\" %IF OS NetBSD OpenBSD
 .IP \fBNETBSD/OPENBSD:\fP 9  .IP \fBNETBSD/OPENBSD:\fP 9
Line 123  devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape  Line 128  devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape 
 .IP \fBDARWIN:\fP 9  .IP \fBDARWIN:\fP 9
 The IOService plane is scanned for ATA block storage devices.  The IOService plane is scanned for ATA block storage devices.
 .\" %ENDIF OS Darwin  .\" %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  .\" %IF OS Windows Cygwin
.IP \fBWINDOWS\ NT4/2000/XP/2003/Vista/Win7/2008\fP: 9.IP \fBWINDOWS\fP: 9
Examine all entries \fB"/dev/sd[a-j]"\fP ("\\\\.\\PhysicalDrive[0-9]")Examine all entries \fB"/dev/sd[a\-z]"\fP, \fB"/dev/sd[a\-c][a\-z]"\fP
for IDE/(S)ATA and SCSI disk devices 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  If a 3ware 9000 controller is installed, examine all entries
 \fB"/dev/sdX,N"\fP for the first logical drive (\'unit\'  \fB"/dev/sdX,N"\fP for the first logical drive (\'unit\'
Line 143  detected behind this controller. Same for a second con Line 142  detected behind this controller. Same for a second con
 If directive \'\-d csmi\' or no \'\-d\' directive is specified,  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  examine all entries \fB"/dev/csmi[0\-9],N"\fP for drives behind an Intel
 ICHxR controller with RST driver.  ICHxR controller with RST driver.
   
   Disks behind Areca RAID controllers are not included.
 .\" %ENDIF OS Windows Cygwin  .\" %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  .PP
 \fBsmartd\fP then monitors  \fBsmartd\fP then monitors
 for \fIall\fP possible SMART errors (corresponding to the \fB\'\-a\'\fP  for \fIall\fP possible SMART errors (corresponding to the \fB\'\-a\'\fP
Directive in the configuration file; see \fBCONFIGURATION FILE\fPDirective in the configuration file; see the \fBsmartd.conf\fP(5) man page).
below).  
   
 .SH   .SH 
 OPTIONS  OPTIONS
   
 .TP  .TP
 .B \-A PREFIX, \-\-attributelog=PREFIX  .B \-A PREFIX, \-\-attributelog=PREFIX
[ATA only] Writes \fBsmartd\fP attribute information (normalized and rawWrites \fBsmartd\fP attribute information (normalized and raw
attribute values) to files \'PREFIX\'\'MODEL\-SERIAL.ata.csv\'.  At eachattribute 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  check cycle attributes are logged as a line of semicolon separated triplets
 of the form "attribute-ID;attribute-norm-value;attribute-raw-value;".  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).  Each line is led by a date string of the form "yyyy-mm-dd HH:MM:SS" (in UTC).
   
 .\" %IF ENABLE_ATTRIBUTELOG  .\" %IF ENABLE_ATTRIBUTELOG
Line 218  information to STDOUT rather than logging it to SYSLOG Line 211  information to STDOUT rather than logging it to SYSLOG
 terminal.  In this mode, \fBsmartd\fP also prints more verbose  terminal.  In this mode, \fBsmartd\fP also prints more verbose
 information about what it is doing than when operating in "daemon"  information about what it is doing than when operating in "daemon"
 mode. In this mode, the \fBINT\fP signal (normally generated from a  mode. In this mode, the \fBINT\fP signal (normally generated from a
terminal with CONTROL\-C) makes \fBsmartd\fP reload its configurationterminal with CONTROL-C) makes \fBsmartd\fP reload its configuration
 file.  Please use CONTROL-\e to exit  file.  Please use CONTROL-\e to exit
 .\" %IF OS Windows  .\" %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  \fBsmartd sigusr2\fP. A new console for debug output is opened when
Line 308  Windows: Some \fBsyslog\fP functionality is implemente Line 301  Windows: Some \fBsyslog\fP functionality is implemente
 internally in \fBsmartd\fP as follows: If no \'\-l\' option  internally in \fBsmartd\fP as follows: If no \'\-l\' option
 (or \'\-l daemon\') is specified, messages are written to Windows  (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  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:  log output is redirected as follows:
 \'\-l local0\' to file \fB./smartd.log\fP,  \'\-l local0\' to file \fB./smartd.log\fP,
 \'\-l local1\' to standard output (redirect with \'>\' to any file),  \'\-l local1\' to standard output (redirect with \'>\' to any file),
 \'\-l local2\' to standard error,  \'\-l local2\' to standard error,
 \'\-l local[3-7]\': to file \fB./smartd[1-5].log\fP.  \'\-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  .\" %ENDIF OS Windows
 .TP  .TP
 .B \-n, \-\-no\-fork  .B \-n, \-\-no\-fork
Line 392  a list of future scheduled self tests to stdout, and t Line 379  a list of future scheduled self tests to stdout, and t
 exit status if all of these steps worked correctly.  exit status if all of these steps worked correctly.
 Device's SMART status is not checked.  Device's SMART status is not checked.
   
This option is intended to test whether the '-s REGEX' directives inThis option is intended to test whether the '\-s REGEX' directives in
 smartd.conf will have the desired effect. The output lists the next test  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  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.  summary of all tests of each device within the next 90 days.
Line 427  The default level is 1, so \'\-r ataioctl,1\' and \'\- Line 414  The default level is 1, so \'\-r ataioctl,1\' and \'\-
 equivalent.  equivalent.
 .TP  .TP
 .B \-s PREFIX, \-\-savestates=PREFIX  .B \-s PREFIX, \-\-savestates=PREFIX
[ATA only] Reads/writes \fBsmartd\fP state information from/to filesReads/writes \fBsmartd\fP state information from/to files
\'PREFIX\'\'MODEL\-SERIAL.ata.state\'. This preserves SMART attributes, drive\'PREFIX\'\'MODEL\-SERIAL.ata.state\' or \'PREFIX\'\'VENDOR\-MODEL\-SERIAL.scsi.state\'. 
min and max temperatures (\-W directive), info about last sent warning emailThis 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  (\-m directive), and the time of next check of the self-test REGEXP
 (\-s directive) across boot cycles.  (\-s directive) across boot cycles.
   
 .\" %IF ENABLE_SAVESTATES  .\" %IF ENABLE_SAVESTATES
 If this option is not specified, state information is maintained in files  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  To disable state files, specify this option with an empty string
argument: \'-s ""\'.argument: \'\-s ""\'.
 .\" %ENDIF ENABLE_SAVESTATES  .\" %ENDIF ENABLE_SAVESTATES
 MODEL and SERIAL are build from drive identify information, invalid  MODEL and SERIAL are build from drive identify information, invalid
 characters are replaced by underline.  characters are replaced by underline.
Line 453  always (re)written after reading the configuration fil Line 442  always (re)written after reading the configuration fil
 the configuration file (SIGHUP), before smartd shutdown, and after a check  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  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.  an important change (which usually results in a SYSLOG output) occurred.
   .TP
   .B \-w PATH, \-\-warnexec=PATH
   [NEW EXPERIMENTAL SMARTD FEATURE]
   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  .\" %IF OS Windows
   .\"! \fBEXEDIR/smartd_warning.cmd\fP.
   .\" %ENDIF OS Windows
   .\" %IF OS Windows
 .TP  .TP
 .B \-\-service  .B \-\-service
 [Windows only] Enables \fBsmartd\fP to run as a Windows service.  [Windows only] Enables \fBsmartd\fP to run as a Windows service.
Line 570  to read: Line 575  to read:
        ...;daemon.info;...          /var/adm/messages         ...;daemon.info;...          /var/adm/messages
 .fi  .fi
 Alternatively, you can use a local facility to log messages: please  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  .\" %ENDIF OS Solaris
 .\" %IF OS Cygwin  .\" %IF OS Cygwin
Line 587  The service can be started and stopped by the start-up Line 592  The service can be started and stopped by the start-up
 .\" %ENDIF OS Cygwin  .\" %ENDIF OS Cygwin
 .\" %IF OS Windows  .\" %IF OS Windows
 On Windows, the log messages are written to the event log or to a file.  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  On Windows, the following built-in commands can be used to control
 \fBsmartd\fP, if running as a daemon:  \fBsmartd\fP, if running as a daemon:
Line 609  The Windows Version of \fBsmartd\fP has buildin suppor Line 614  The Windows Version of \fBsmartd\fP has buildin suppor
 \'\fBsmartd install [options]\fP\' installs a service  \'\fBsmartd install [options]\fP\' installs a service
 named "smartd" (display name "SmartD Service") using the command line  named "smartd" (display name "SmartD Service") using the command line
 \'/INSTALLPATH/smartd.exe \-\-service [options]\'.  \'/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\'\fBsmartd remove\fP\' can later be used to remove the service and
from registry.event message entries from the registry.
   
 Upon startup, the smartd service changes the working directory  Upon startup, the smartd service changes the working directory
 to its own installation path. If smartd.conf and blat.exe are stored  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.  in this directory, no \'-c\' option and \'-M exec\' directive is needed.
   
The debug mode (\'-d\', \'-q onecheck\') does not work if smartd isThe debug mode (\'\-d\', \'\-q onecheck\') does not work if smartd is
 running as service.  running as service.
   
 The service can be controlled as usual with Windows commands \'net\'  The service can be controlled as usual with Windows commands \'net\'
 or \'sc\' (\'\fBnet start smartd\fP\', \'\fBnet stop smartd\fP\').  or \'sc\' (\'\fBnet start smartd\fP\', \'\fBnet stop smartd\fP\').
   
 Pausing the service (\'\fBnet pause smartd\fP\') sets the interval between  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  Continuing the paused service (\'\fBnet continue smartd\fP\') resets the
 interval and rereads the configuration file immediately (like \fBSIGHUP\fP):  interval and rereads the configuration file immediately (like \fBSIGHUP\fP):
Line 671  Forking the daemon failed. Line 678  Forking the daemon failed.
 Couldn\'t create PID file.  Couldn\'t create PID file.
 .TP  .TP
 .B 5:  .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  .TP
 .B 6:  .B 6:
 Config file exists, but cannot be read.  Config file exists, but cannot be read.
Line 716  status is then 128 plus the signal number.  For exampl Line 723  status is then 128 plus the signal number.  For exampl
 is killed by SIGKILL (signal 9) then the exit status is 137.  is killed by SIGKILL (signal 9) then the exit status is 137.
   
 .PP  .PP
.SH AUTHOR.SH AUTHORS
\fBBruce Allen\fP smartmontools\-support@lists.sourceforge.net\fBBruce Allen\fP
.fi.br
 University of Wisconsin \- Milwaukee Physics Department  University of Wisconsin \- Milwaukee Physics Department
   .br
   \fBChristian Franke\fP (Windows interface, C++ redesign, most enhancements
   since 2009)
   .br
   \fBsmartmontools\-support@lists.sourceforge.net\fP
   
 .PP  .PP
 .SH CONTRIBUTORS  .SH CONTRIBUTORS
 The following have made large contributions to smartmontools:  The following have made large contributions to smartmontools:
 .nf  .nf
 \fBCasper Dik\fP (Solaris SCSI interface)  \fBCasper Dik\fP (Solaris SCSI interface)
 \fBChristian Franke\fP (Windows interface, C++ redesign, USB support, ...)  
 \fBDouglas Gilbert\fP (SCSI subsystem)  \fBDouglas Gilbert\fP (SCSI subsystem)
 \fBGuido Guenther\fP (Autoconf/Automake packaging)  \fBGuido Guenther\fP (Autoconf/Automake packaging)
 \fBGeoffrey Keating\fP (Darwin ATA interface)  \fBGeoffrey Keating\fP (Darwin ATA interface)
Line 747  Many other individuals have made smaller contributions Line 758  Many other individuals have made smaller contributions
 .fi  .fi
 This code was derived from the smartsuite package, written by Michael  This code was derived from the smartsuite package, written by Michael
 Cornwell, and from the previous UCSC smartsuite package.  It extends  Cornwell, and from the previous UCSC smartsuite package.  It extends
these to cover ATA\-5 disks.  This code was originally developed as athese to cover ATA-5 disks.  This code was originally developed as a
 Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory  Senior Thesis by Michael Cornwell at the Concurrent Systems Laboratory
 (now part of the Storage Systems Research Center), Jack Baskin School  (now part of the Storage Systems Research Center), Jack Baskin School
 of Engineering, University of California, Santa  of Engineering, University of California, Santa
Line 768  REFERENCES FOR SMART Line 779  REFERENCES FOR SMART
 .fi  .fi
 An introductory article about smartmontools is \fIMonitoring Hard  An introductory article about smartmontools is \fIMonitoring Hard
 Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,  Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,
pages 74\-77. This is \fBhttp://www.linuxjournal.com/article/6983\fPpages 74-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP
 online.  online.
   
 If you would like to understand better how SMART works, and what it  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  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  specification Revision 4b.  This documents the SMART functionality which the
 \fBsmartmontools\fP utilities provide access to.  \fBsmartmontools\fP utilities provide access to.
   
 .fi  .fi
The functioning of SMART was originally defined by the SFF\-8035iThe functioning of SMART was originally defined by the SFF-8035i
revision 2 and the SFF\-8055i revision 1.4 specifications.  These arerevision 2 and the SFF-8055i revision 1.4 specifications.  These are
 publications of the Small Form Factors (SFF) Committee.  publications of the Small Form Factors (SFF) Committee.
   
 Links to these and other documents may be found on the Links page of the  Links to these and other documents may be found on the Links page of the

Removed from v.1.1.1.2  
changed lines
  Added in v.1.1.1.3


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>