2 Copyright (C) 2002-10 Bruce Allen
3 Copyright (C) 2004-16 Christian Franke
5 $Id: smartd.8.in 4299 2016-04-16 19:45:57Z chrfranke $
7 This program is free software; you can redistribute it and/or modify
8 it under the terms of the GNU General Public License as published by
9 the Free Software Foundation; either version 2, or (at your option)
12 You should have received a copy of the GNU General Public License
13 (for example COPYING); If not, see <http://www.gnu.org/licenses/>.
15 This code was originally developed as a Senior Thesis by Michael Cornwell
16 at the Concurrent Systems Laboratory (now part of the Storage Systems
17 Research Center), Jack Baskin School of Engineering, University of
18 California, Santa Cruz. http://ssrc.soe.ucsc.edu/
21 .TH SMARTD 8 "CURRENT_SVN_DATE" "CURRENT_SVN_VERSION" "SMART Monitoring Tools"
23 \fBsmartd\fP \- SMART Disk Monitoring Daemon
30 .\"! [This man page is generated for the OS_MAN_FILTER version of smartmontools.
31 .\"! It does not contain info specific to other platforms.]
34 \fBsmartd\fP is a daemon that monitors the Self-Monitoring, Analysis and
35 Reporting Technology (SMART) system built into most ATA/SATA and SCSI/SAS
36 hard drives and solid-state drives.
37 The purpose of SMART is to monitor the reliability of the hard drive
38 and predict drive failures, and to carry out different types of drive
40 This version of \fBsmartd\fP is compatible with
41 ACS-3, ACS-2, ATA8-ACS, ATA/ATAPI-7 and earlier standards
42 (see \fBREFERENCES\fP below).
44 \fBsmartd\fP will attempt to enable SMART monitoring on ATA devices
45 (equivalent to \fBsmartctl -s on\fP) and polls these and SCSI devices
46 every 30 minutes (configurable), logging SMART errors and changes of
47 SMART Attributes via the SYSLOG interface. The default location for
48 these SYSLOG notifications and warnings is system-dependent
49 (typically \fB/var/log/messages\fP or \fB/var/log/syslog\fP).
50 To change this default location, please see the \fB\'-l\'\fP
51 command-line option described below.
53 In addition to logging to a file, \fBsmartd\fP can also be configured
54 to send email warnings if problems are detected. Depending upon the
55 type of problem, you may want to run self-tests on the disk, back up
56 the disk, replace the disk, or use a manufacturer\'s utility to force
57 reallocation of bad or unreadable disk sectors. If disk problems are
58 detected, please see the \fBsmartctl\fP manual page and the
59 \fBsmartmontools\fP web page/FAQ for further guidance.
61 If you send a \fBUSR1\fP signal to \fBsmartd\fP it will immediately
62 check the status of the disks, and then return to polling the disks
63 every 30 minutes. See the \fB\'\-i\'\fP option below for additional
66 \fBsmartd\fP can be configured at start-up using the configuration
67 file \fB/usr/local/etc/smartd.conf\fP (Windows: \fBEXEDIR/smartd.conf\fP).
68 If the configuration file is subsequently modified, \fBsmartd\fP
69 can be told to re-read the configuration file by sending it a
70 \fBHUP\fP signal, for example with the command:
72 \fBkillall -HUP smartd\fP.
75 (Windows: See NOTES below.)
78 On startup, if \fBsmartd\fP finds a syntax error in the configuration
79 file, it will print an error message and then exit. However if
80 \fBsmartd\fP is already running, then is told with a \fBHUP\fP signal
81 to re-read the configuration file, and then find a syntax error in
82 this file, it will print an error message and then continue, ignoring
83 the contents of the (faulty) configuration file, as if the \fBHUP\fP
84 signal had never been received.
86 When \fBsmartd\fP is running in debug mode, the \fBINT\fP signal
87 (normally generated from a shell with CONTROL-C) is treated in the
88 same way as a \fBHUP\fP signal: it makes \fBsmartd\fP reload its
89 configuration file. To exit \fBsmartd\fP use CONTROL-\e
91 (Windows: CONTROL-Break).
94 On startup, in the absence of the configuration file
95 \fB/usr/local/etc/smartd.conf\fP, the \fBsmartd\fP daemon first scans for all
96 devices that support SMART. The scanning is done as follows:
99 Examine all entries \fB"/dev/hd[a-t]"\fP for IDE/ATA
100 devices, and \fB"/dev/sd[a-z]"\fP, \fB"/dev/sd[a-c][a-z]"\fP
101 for ATA/SATA or SCSI/SAS devices.
102 Disks behind RAID controllers are not included.
104 [NEW EXPERIMENTAL SMARTD FEATURE]
105 If directive \'\-d nvme\'
106 .\" %IF ENABLE_NVME_DEVICESCAN
107 or no \'\-d\' directive
108 .\" %ENDIF ENABLE_NVME_DEVICESCAN
109 is specified, examine all entries \fB"/dev/nvme[0-99]"\fP for NVMe devices.
113 Authoritative list of disk devices is obtained from SCSI (CAM) and ATA subsystems.
114 Disks behind RAID controllers are not included.
115 .\" %ENDIF OS FreeBSD
116 .\" %IF OS NetBSD OpenBSD
117 .IP \fBNETBSD/OPENBSD:\fP 9
118 Authoritative list of disk devices is obtained from sysctl
120 .\" %ENDIF OS NetBSD OpenBSD
123 Examine all entries \fB"/dev/rdsk/*s0"\fP for IDE/ATA and SCSI disk
124 devices, and entries \fB"/dev/rmt/*"\fP for SCSI tape devices.
125 .\" %ENDIF OS Solaris
128 The IOService plane is scanned for ATA block storage devices.
130 .\" %IF OS Windows Cygwin
132 Examine all entries \fB"/dev/sd[a\-z]"\fP, \fB"/dev/sd[a\-c][a\-z]"\fP
133 and \fB"/dev/sdd[a\-x]"\fP ("\\\\.\\PhysicalDrive[0\-127]") for
134 IDE/(S)ATA and SCSI disk devices.
136 If a 3ware 9000 controller is installed, examine all entries
137 \fB"/dev/sdX,N"\fP for the first logical drive (\'unit\'
138 \fB"/dev/sdX"\fP) and all physical disks (\'ports\' \fB",N"\fP)
139 detected behind this controller. Same for a second controller if present.
141 If directive \'\-d csmi\' or no \'\-d\' directive is specified,
142 examine all entries \fB"/dev/csmi[0\-9],N"\fP for drives behind an Intel
143 ICHxR controller with RST driver.
145 Disks behind Areca RAID controllers are not included.
147 [NEW EXPERIMENTAL SMARTD FEATURE]
148 If directive \'\-d nvme\'
149 .\" %IF ENABLE_NVME_DEVICESCAN
150 or no \'\-d\' directive
151 .\" %ENDIF ENABLE_NVME_DEVICESCAN
152 is specified, examine all entries \fB"/dev/nvme[0-9]"\fP for NVMe devices.
153 .\" %ENDIF OS Windows Cygwin
155 \fBsmartd\fP then monitors
156 for \fIall\fP possible SMART errors (corresponding to the \fB\'\-a\'\fP
157 Directive in the configuration file; see the \fBsmartd.conf\fP(5) man page).
161 .B \-A PREFIX, \-\-attributelog=PREFIX
162 Writes \fBsmartd\fP attribute information (normalized and raw
163 attribute values) to files \'PREFIX\'\'MODEL\-SERIAL.ata.csv\' or \'PREFIX\'\'VENDOR\-MODEL\-SERIAL.scsi.csv\'. At each
164 check cycle attributes are logged as a line of semicolon separated triplets
165 of the form "attribute-ID;attribute-norm-value;attribute-raw-value;".
166 For SCSI devices error counters and temperature recorded in the form "counter-name;counter-value;"
167 Each line is led by a date string of the form "yyyy-mm-dd HH:MM:SS" (in UTC).
169 .\" %IF ENABLE_ATTRIBUTELOG
170 If this option is not specified, attribute information is written to files
171 \'/usr/local/var/lib/smartmontools/attrlog.MODEL\-SERIAL.ata.csv\'.
172 To disable attribute log files, specify this option with an empty string
174 .\" %ENDIF ENABLE_ATTRIBUTELOG
175 MODEL and SERIAL are build from drive identify information, invalid
176 characters are replaced by underline.
178 If the PREFIX has the form \'/path/dir/\' (e.g. \'/var/lib/smartd/\'), then
179 files \'MODEL\-SERIAL.ata.csv\' are created in directory \'/path/dir\'.
180 If the PREFIX has the form \'/path/name\' (e.g. \'/var/lib/misc/attrlog\-\'),
181 then files 'nameMODEL\-SERIAL.ata.csv' are created in directory '/path/'.
182 The path must be absolute, except if debug mode is enabled.
184 .B \-B [+]FILE, \-\-drivedb=[+]FILE
185 [ATA only] Read the drive database from FILE. The new database replaces
186 the built in database by default. If \'+\' is specified, then the new entries
187 prepend the built in entries.
188 Please see the \fBsmartctl\fP(8) man page for further details.
190 .B \-c FILE, \-\-configfile=FILE
191 Read \fBsmartd\fP configuration Directives from FILE, instead of from
192 the default location \fB/usr/local/etc/smartd.conf\fP (Windows: \fBEXEDIR/smartd.conf\fP).
193 If FILE does \fBnot\fP exist, then \fBsmartd\fP will print an error
194 message and exit with nonzero status. Thus, \'\-c /usr/local/etc/smartd.conf\'
195 can be used to verify the existence of the default configuration file.
197 By using \'\-\' for FILE, the configuration is read from standard
198 input. This is useful for commands like:
200 .B echo /dev/sdb \-m user@home \-M test | smartd \-c \- \-q onecheck
202 to perform quick and simple checks without a configuration file.
203 .\" %IF ENABLE_CAPABILITIES
205 .B \-C, \-\-capabilities
206 [Linux only] Use libcap-ng to drop unneeded Linux process \fBcapabilities\fP(7).
207 The following capabilities are kept: CAP_SYS_ADMIN, CAP_SYS_RAWIO, CAP_MKNOD.
209 Warning: Mail notification does not work when used.
210 .\" %ENDIF ENABLE_CAPABILITIES
213 Runs \fBsmartd\fP in "debug" mode. In this mode, it displays status
214 information to STDOUT rather than logging it to SYSLOG and does not
215 \fBfork\fP(2) into the background and detach from the controlling
216 terminal. In this mode, \fBsmartd\fP also prints more verbose
217 information about what it is doing than when operating in "daemon"
218 mode. In this mode, the \fBINT\fP signal (normally generated from a
219 terminal with CONTROL-C) makes \fBsmartd\fP reload its configuration
220 file. Please use CONTROL-\e to exit
222 (Windows: CONTROL-Break).
224 [Windows only] The "debug" mode can be toggled by the command
225 \fBsmartd sigusr2\fP. A new console for debug output is opened when
226 debug mode is enabled.
227 .\" %ENDIF OS Windows
229 .B \-D, \-\-showdirectives
230 Prints a list (to STDOUT) of all the possible Directives which may
231 appear in the configuration file /usr/local/etc/smartd.conf, and then exits.
232 These Directives are described in the \fBsmartd.conf\fP(5) man page.
233 They may appear in the configuration file following the device name.
235 .B \-h, \-\-help, \-\-usage
236 Prints usage message to STDOUT and exits.
238 .B \-i N, \-\-interval=N
239 Sets the interval between disk checks to \fIN\fP seconds, where
240 \fIN\fP is a decimal integer. The minimum allowed value is ten and
241 the maximum is the largest positive integer that can be represented on
242 your system (often 2^31-1). The default is 1800 seconds.
244 Note that the superuser can make \fBsmartd\fP check the status of the
245 disks at any time by sending it the \fBSIGUSR1\fP signal, for example
248 .B kill -SIGUSR1 <pid>
250 where \fB<pid>\fP is the process id number of \fBsmartd\fP. One may
253 .B killall -USR1 smartd
255 for the same purpose.
258 (Windows: See NOTES below.)
259 .\" %ENDIF OS Windows
261 .B \-l FACILITY, \-\-logfacility=FACILITY
262 Uses syslog facility FACILITY to log the messages from \fBsmartd\fP.
263 Here FACILITY is one of \fIlocal0\fP, \fIlocal1\fP, ..., \fIlocal7\fP,
264 or \fIdaemon\fP [default]. If this command-line option is not used,
265 then by default messages from \fBsmartd\fP are logged to the facility
268 If you would like to have \fBsmartd\fP messages logged somewhere other
269 than the default location, include (for example) \'\-l local3\' in its
270 start up argument list.
271 Tell the syslog daemon to log all messages from facility \fBlocal3\fP
272 to (for example) \'/var/log/smartd.log\'.
274 For more detailed information, please refer to the man pages for
275 the local syslog daemon, typically \fBsyslogd\fP(8), \fBsyslog-ng\fP(8)
276 or \fBrsyslogd\fP(8).
279 Cygwin: If no \fBsyslogd\fP is running, the \'\-l\' option has no effect.
280 In this case, all \fBsyslog\fP messages are written to Windows event log.
284 Windows: Some \fBsyslog\fP functionality is implemented
285 internally in \fBsmartd\fP as follows: If no \'\-l\' option
286 (or \'\-l daemon\') is specified, messages are written to Windows
287 event log or to file \fB./smartd.log\fP if event log is not available
288 (access denied). By specifying other values of FACILITY,
289 log output is redirected as follows:
290 \'\-l local0\' to file \fB./smartd.log\fP,
291 \'\-l local1\' to standard output (redirect with \'>\' to any file),
292 \'\-l local2\' to standard error,
293 \'\-l local[3-7]\': to file \fB./smartd[1-5].log\fP.
294 .\" %ENDIF OS Windows
297 Do not fork into background; this is useful when executed from modern
298 init methods like initng, minit, supervise or systemd.
301 On Cygwin, this allows running \fBsmartd\fP as service via cygrunsrv,
306 On Windows, this option is not available, use \'\-\-service\' instead.
307 .\" %ENDIF OS Windows
309 .B \-p NAME, \-\-pidfile=NAME
310 Writes pidfile \fINAME\fP containing the \fBsmartd\fP Process ID
311 number (PID). To avoid symlink attacks make sure the directory to
312 which pidfile is written is only writable for root. Without this
313 option, or if the \-\-debug option is given, no PID file is written on
314 startup. If \fBsmartd\fP is killed with a maskable signal then the
317 .B \-q WHEN, \-\-quit=WHEN
318 Specifies when, if ever, \fBsmartd\fP should exit. The valid
319 arguments are to this option are:
322 \- Exit if there are no devices to monitor, or if any errors are found
323 at startup in the configuration file. This is the default.
326 \- Exit if there are no devices to monitor, or if any errors are found
327 in the configuration file /usr/local/etc/smartd.conf at startup or whenever it
331 \- Exit if there are no devices to monitor at startup. But continue
332 to run if no devices are found whenever the configuration file is
336 \- Only exit if a fatal error occurs (no remaining system memory,
337 invalid command line arguments). In this mode, even if there are no
338 devices to monitor, or if the configuration file
339 \fB/usr/local/etc/smartd.conf\fP has errors, \fBsmartd\fP will continue to run,
340 waiting to load a configuration file listing valid devices.
343 \- Start \fBsmartd\fP in debug mode, then register devices, then check
344 device\'s SMART status once, and then exit with zero exit status if all
345 of these steps worked correctly.
347 This last option is intended for \'distribution-writers\' who want to
348 create automated scripts to determine whether or not to automatically
349 start up \fBsmartd\fP after installing smartmontools. After starting
350 \fBsmartd\fP with this command-line option, the distribution\'s install
351 scripts should wait a reasonable length of time (say ten seconds). If
352 \fBsmartd\fP has not exited with zero status by that time, the script
353 should send \fBsmartd\fP a SIGTERM or SIGKILL and assume that
354 \fBsmartd\fP will not operate correctly on the host. Conversely, if
355 \fBsmartd\fP exits with zero status, then it is safe to run
356 \fBsmartd\fP in normal daemon mode. If \fBsmartd\fP is unable to
357 monitor any devices or encounters other problems then it will return
358 with non-zero exit status.
361 \- Start \fBsmartd\fP in debug mode, then register devices, then write
362 a list of future scheduled self tests to stdout, and then exit with zero
363 exit status if all of these steps worked correctly.
364 Device's SMART status is not checked.
366 This option is intended to test whether the '\-s REGEX' directives in
367 smartd.conf will have the desired effect. The output lists the next test
368 schedules, limited to 5 tests per type and device. This is followed by a
369 summary of all tests of each device within the next 90 days.
371 .B \-r TYPE, \-\-report=TYPE
372 Intended primarily to help
374 developers understand the behavior of
376 on non-conforming or poorly-conforming hardware. This option reports
379 transactions with the device. The option can be used multiple times.
380 When used just once, it shows a record of the ioctl() transactions
381 with the device. When used more than once, the detail of these ioctl()
382 transactions are reported in greater detail. The valid arguments to
386 \- report all ioctl() transactions.
389 \- report only ioctl() transactions with ATA devices.
392 \- report only ioctl() transactions with SCSI devices.
394 .\" %IF OS FreeBSD Linux Windows Cygwin
396 \- [FreeBSD, Linux, Windows and Cygwin only]
397 [NEW EXPERIMENTAL SMARTD FEATURE]
398 report only ioctl() transactions with NVMe devices.
400 .\" %ENDIF OS FreeBSD Linux Windows Cygwin
401 Any argument may include a positive integer to specify the level of
402 detail that should be reported. The argument should be followed by a
403 comma then the integer with no spaces. For example, \fIataioctl,2\fP
404 The default level is 1, so \'\-r ataioctl,1\' and \'\-r ataioctl\' are
407 .B \-s PREFIX, \-\-savestates=PREFIX
408 Reads/writes \fBsmartd\fP state information from/to files
409 \'PREFIX\'\'MODEL\-SERIAL.ata.state\' or \'PREFIX\'\'VENDOR\-MODEL\-SERIAL.scsi.state\'.
410 This preserves SMART attributes, drive min and max temperatures (\-W directive),
411 info about last sent warning email
412 (\-m directive), and the time of next check of the self-test REGEXP
413 (\-s directive) across boot cycles.
415 .\" %IF ENABLE_SAVESTATES
416 If this option is not specified, state information is maintained in files
417 \'/usr/local/var/lib/smartmontools/smartd.MODEL\-SERIAL.ata.state\' for ATA devices and
418 \'/usr/local/var/lib/smartmontools/smartd.VENDOR\-MODEL\-SERIAL.scsi.state\' for SCSI devices.
419 To disable state files, specify this option with an empty string
420 argument: \'\-s ""\'.
421 .\" %ENDIF ENABLE_SAVESTATES
422 MODEL and SERIAL are build from drive identify information, invalid
423 characters are replaced by underline.
425 If the PREFIX has the form \'/path/dir/\' (e.g. \'/var/lib/smartd/\'), then
426 files \'MODEL\-SERIAL.ata.state\' are created in directory \'/path/dir\'.
427 If the PREFIX has the form \'/path/name\' (e.g. \'/var/lib/misc/smartd\-\'),
428 then files 'nameMODEL\-SERIAL.ata.state' are created in directory '/path/'.
429 The path must be absolute, except if debug mode is enabled.
431 The state information files are read on smartd startup. The files are
432 always (re)written after reading the configuration file, before rereading
433 the configuration file (SIGHUP), before smartd shutdown, and after a check
434 forced by SIGUSR1. After a normal check cycle, a file is only rewritten if
435 an important change (which usually results in a SYSLOG output) occurred.
437 .B \-w PATH, \-\-warnexec=PATH
438 Run the executable PATH instead of the default script when smartd
439 needs to send warning messages. PATH must point to an executable binary
441 The default script is
442 .\" %IF NOT OS Windows
443 \fB/usr/local/etc/smartd_warning.sh\fP.
444 .\" %ENDIF NOT OS Windows
446 (Windows: EXEDIR/smartd_warning.cmd)
449 .\"! \fBEXEDIR/smartd_warning.cmd\fP.
450 .\" %ENDIF OS Windows
454 [Windows only] Enables \fBsmartd\fP to run as a Windows service.
455 The option must be specified in the service command line as the first
456 argument. It should not be used from console.
457 See NOTES below for details.
458 .\" %ENDIF OS Windows
460 .B \-V, \-\-version, \-\-license, \-\-copyright
461 Prints version, copyright, license, home page and SVN revision
462 information for your copy of \fBsmartd\fP to STDOUT and then exits.
463 Please include this information if you are reporting bugs or problems.
468 Runs the daemon in forked mode. This is the normal way to run
470 Entries are logged to SYSLOG.
474 Run in foreground (debug) mode, checking the disk status
477 .B smartd -q onecheck
479 Registers devices, and checks the status of the devices exactly
480 once. The exit status (the shell
482 variable) will be zero if all went well, and nonzero if no devices
483 were detected or some other problem was encountered.
485 .\" %IF ENABLE_INITSCRIPT
486 Note that \fBsmartmontools\fP provides a start-up script in
487 \fB/usr/local/etc/rc.d/init.d/smartd\fP which is responsible for starting and
488 stopping the daemon via the normal init interface. Using this script,
489 you can start \fBsmartd\fP by giving the command:
491 .B /usr/local/etc/rc.d/init.d/smartd start
493 and stop it by using the command:
495 .B /usr/local/etc/rc.d/init.d/smartd stop
498 .\" %ENDIF ENABLE_INITSCRIPT
500 The syntax of the \fBsmartd.conf\fP(5) file is discussed separately.
504 will make log entries at loglevel
506 if the Normalized SMART Attribute values have changed, as reported using the
510 Directives. For example:
512 .B \'Device: /dev/sda, SMART Attribute: 194 Temperature_Celsius changed from 94 to 93\'
514 Note that in this message, the value given is the \'Normalized\' not the \'Raw\'
515 Attribute value (the disk temperature in this case is about 22
520 Directives modify this behavior, so that the information is printed
521 with the Raw values as well, for example:
523 .B \'Device: /dev/sda, SMART Attribute: 194 Temperature_Celsius changed from 94 [Raw 22] to 93 [Raw 23]\'
525 Here the Raw values are the actual disk temperatures in Celsius. The
526 way in which the Raw values are printed, and the names under which the
527 Attributes are reported, is governed by the various
528 .B \'-v Num,Description\'
529 Directives described previously.
533 manual page for further explanation of the differences between
534 Normalized and Raw Attribute values.
537 will make log entries at loglevel
539 if a SMART Attribute has failed, for example:
541 .B \'Device: /dev/sdc, Failed SMART Attribute: 5 Reallocated_Sector_Ct\'
543 This loglevel is used for reporting enabled by the
544 .B \'\-H\', \-f\', \'\-l\ selftest\',
547 Directives. Entries reporting failure of SMART Prefailure Attributes
548 should not be ignored: they mean that the disk is failing. Use the
550 utility to investigate.
553 Under Solaris with the default \fB/etc/syslog.conf\fP configuration,
554 messages below loglevel \fBLOG_NOTICE\fP will \fBnot\fP be recorded.
555 Hence all \fBsmartd\fP messages with loglevel \fBLOG_INFO\fP will be
556 lost. If you want to use the existing daemon facility to log all
557 messages from \fBsmartd\fP, you should change \fB/etc/syslog.conf\fP
560 ...;daemon.notice;... /var/adm/messages
564 ...;daemon.info;... /var/adm/messages
566 Alternatively, you can use a local facility to log messages: please
567 see the \fBsmartd\fP '\-l' command-line option described above.
569 .\" %ENDIF OS Solaris
571 The Cygwin Version of \fBsmartd\fP can be run as a service via the
573 .\" %IF ENABLE_INITSCRIPT
574 The start-up script provides Cygwin-specific commands to install and
577 .B /usr/local/etc/rc.d/init.d/smartd install [options]
578 .B /usr/local/etc/rc.d/init.d/smartd remove
580 The service can be started and stopped by the start-up script as usual
581 (see \fBEXAMPLES\fP above).
582 .\" %ENDIF ENABLE_INITSCRIPT
586 On Windows, the log messages are written to the event log or to a file.
587 See documentation of the '\-l FACILITY' option above for details.
589 On Windows, the following built-in commands can be used to control
590 \fBsmartd\fP, if running as a daemon:
592 \'\fBsmartd status\fP\' \- check status
594 \'\fBsmartd stop\fP\' \- stop smartd
596 \'\fBsmartd reload\fP\' \- reread config file
598 \'\fBsmartd restart\fP\' \- restart smartd
600 \'\fBsmartd sigusr1\fP\' \- check disks now
602 \'\fBsmartd sigusr2\fP\' \- toggle debug mode
604 The Windows Version of \fBsmartd\fP has buildin support for services:
606 \'\fBsmartd install [options]\fP\' installs a service
607 named "smartd" (display name "SmartD Service") using the command line
608 \'/INSTALLPATH/smartd.exe \-\-service [options]\'.
609 This also installs smartd.exe as a event message file for the Windows
612 \'\fBsmartd remove\fP\' can later be used to remove the service and
613 event message entries from the registry.
615 Upon startup, the smartd service changes the working directory
616 to its own installation path. If smartd.conf and blat.exe are stored
617 in this directory, no \'-c\' option and \'-M exec\' directive is needed.
619 The debug mode (\'\-d\', \'\-q onecheck\') does not work if smartd is
622 The service can be controlled as usual with Windows commands \'net\'
623 or \'sc\' (\'\fBnet start smartd\fP\', \'\fBnet stop smartd\fP\').
625 Pausing the service (\'\fBnet pause smartd\fP\') sets the interval between
626 disk checks (\'\-i N\') to infinite.
628 Continuing the paused service (\'\fBnet continue smartd\fP\') resets the
629 interval and rereads the configuration file immediately (like \fBSIGHUP\fP):
631 Continuing a still running service (\'\fBnet continue smartd\fP\' without
632 preceding \'\fBnet pause smartd\fP\') does not reread configuration but
633 checks disks immediately (like \fBSIGUSR1\fP).
635 .\" %ENDIF OS Windows
636 .SH LOG TIMESTAMP TIMEZONE
637 When \fBsmartd\fP makes log entries, these are time-stamped. The time
638 stamps are in the computer's local time zone, which is generally set
639 using either the environment variable \'\fBTZ\fP\' or using a
640 time-zone file such as \fB/etc/localtime\fP. You may wish to change
641 the timezone while \fBsmartd\fP is running (for example, if you carry
642 a laptop to a new time-zone and don't reboot it). Due to a bug in the
643 \fBtzset\fP(3) function of many unix standard C libraries, the
644 time-zone stamps of \fBsmartd\fP might not change. For some systems,
645 \fBsmartd\fP will work around this problem \fIif\fP the time-zone is
646 set using \fB/etc/localtime\fP. The work-around \fIfails\fP if the
647 time-zone is set using the \'\fBTZ\fP\' variable (or a file that it
651 The exit status (return value) of \fBsmartd\fP can have the following values:
654 Daemon startup successful, or \fBsmartd\fP was killed by a SIGTERM (or in debug mode, a SIGQUIT).
657 Commandline did not parse.
660 There was a syntax error in the config file.
663 Forking the daemon failed.
666 Couldn\'t create PID file.
669 Config file does not exist (only returned in conjunction with the \'\-c\' option).
672 Config file exists, but cannot be read.
676 ran out of memory during startup.
679 An inconsistency was found in \fBsmartd\fP\'s internal data
680 structures. This should never happen. It must be due to either a
681 coding or compiler bug. \fIPlease\fP report such failures to
682 smartmontools developers, see REPORTING BUGS below.
685 A device explicitly listed in
686 .B /usr/local/etc/smartd.conf
691 didn\'t find any devices to monitor.
696 received a SIGINT or SIGQUIT. (Note that in debug mode, SIGINT has
697 the same effect as SIGHUP, and makes \fBsmartd\fP reload its
698 configuration file. SIGQUIT has the same effect as SIGTERM and causes
699 \fBsmartd\fP to exit with zero exit status.
703 was killed by a signal that is not explicitly listed above. The exit
704 status is then 128 plus the signal number. For example if
706 is killed by SIGKILL (signal 9) then the exit status is 137.
708 .\" %IF NOT OS Windows
711 .B /usr/local/sbin/smartd
712 full path of this executable.
714 .B /usr/local/etc/smartd.conf
715 configuration file (see \fBsmartd.conf\fP(5) man page).
717 .B /usr/local/etc/smartd_warning.sh
718 script run on warnings (see \'\-M exec\' directive on
719 \fBsmartd.conf\fP(5) man page).
720 .\" %IF ENABLE_SMARTDPLUGINDIR
722 .B /usr/local/etc/smartd_warning.d/
723 plugin directory for smartd warning script (see \'\-m\' directive on
724 \fBsmartd.conf\fP(5) man page).
725 .\" %ENDIF ENABLE_SMARTDPLUGINDIR
726 .\" %IF ENABLE_DRIVEDB
728 .B /usr/local/share/smartmontools/drivedb.h
729 drive database (see \'\-B\' option).
730 .\" %ENDIF ENABLE_DRIVEDB
732 .B /usr/local/etc/smart_drivedb.h
733 optional local drive database (see \'\-B\' option).
735 .\" %ENDIF NOT OS Windows
737 \fBBruce Allen\fP (project initiator),
739 \fBChristian Franke\fP (project manager, Windows port and all sort of things),
741 \fBDouglas Gilbert\fP (SCSI subsystem),
743 \fBVolker Kuhlmann\fP (moderator of support and database mailing list),
745 \fBGabriele Pohl\fP (wiki & development team support),
747 \fBAlex Samorukov\fP (FreeBSD port and more, new Trac wiki).
749 Many other individuals have made contributions and corrections,
750 see AUTHORS, ChangeLog and repository files.
752 The first smartmontools code was derived from the smartsuite package,
753 written by Michael Cornwell and Andre Hedrick.
756 To submit a bug report, create a ticket in smartmontools wiki:
758 <\fBhttp://www.smartmontools.org/\fP>.
760 Alternatively send the info to the smartmontools support mailing list:
762 <\fBhttps://lists.sourceforge.net/lists/listinfo/smartmontools-support\fB>.
765 \fBsmartd.conf\fP(5), \fBsmartctl\fP(8).
766 .\" %IF ENABLE_UPDATE_SMART_DRIVEDB
768 \fBupdate-smart-drivedb\fP(8).
769 .\" %ENDIF ENABLE_UPDATE_SMART_DRIVEDB
772 Please see the following web site for more info:
773 \fBhttp://www.smartmontools.org/\fP
775 An introductory article about smartmontools is \fIMonitoring Hard
776 Disks with SMART\fP, by Bruce Allen, Linux Journal, January 2004,
777 pages 74-77. This is \fBhttp://www.linuxjournal.com/article/6983\fP
780 If you would like to understand better how SMART works, and what it
781 does, a good place to start is with Sections 4.8 and 6.54 of the first
782 volume of the \'AT Attachment with Packet Interface-7\' (ATA/ATAPI-7)
783 specification Revision 4b. This documents the SMART functionality which the
784 \fBsmartmontools\fP utilities provide access to.
786 The functioning of SMART was originally defined by the SFF-8035i
787 revision 2 and the SFF-8055i revision 1.4 specifications. These are
788 publications of the Small Form Factors (SFF) Committee.
790 Links to these and other documents may be found on the Links page of the
791 \fBsmartmontools\fP Wiki at \fBhttp://www.smartmontools.org/wiki/Links\fP .
794 CURRENT_SVN_VERSION CURRENT_SVN_DATE CURRENT_SVN_REV
796 $Id: smartd.8.in 4299 2016-04-16 19:45:57Z chrfranke $