
SANtools® S.M.A.R.T. Disk Monitor (SMARTMon-UX)162
SANTOOLS® is registered in US Patent and Trademark Office No 3,107,854 All rights reserved.
# $$Y$$ - Instructs SMARTMon-UX to disable threshold monitoring for this parameter
# after invoking the script
# $$Z$$ - Instructs SMARTMon-UX to reset the threshold to current value + 1 after
# invoking the script. (Think of this as turning off the alarm)
#
# Example usage:
# echo $$D: $$12 is currently at $$V >> EventlogDev$$1:$$2.$$3
# will create individual event logs for specific devices on this threshold
#
Other rules apply:
· The action script will be interpreted literally. If you require special characters, spaces, double or single quotes, you
must supply them.
· The program will not attempt to interpret the action script or check it for validity. It will merely make optional field
substitutions and launch the routine. It is your responsibility to first test the script so that it has the desired effect.
· The action script utilizes the library call "system" which means the script will have all permissions, priority, and
environmental variables associated with the calling routine.
· SMARTMon-UX will suspend operations until the script has been completed. If you wish to run the script in the
background and have control passed back to SMARTMon-UX immediately, append an & to the end of the script.
(This is not supported by Windows).
· There is one important characteristic of log page parameters and thresholds in general. All values use 1 to 8 bytes
to store the data, and the SCSI specification does not provide a method to report an overflow or roll over.
Information is reported as an unsigned integer. This means if the parameter you are interested in contains FFFFh (
65535 in decimal), and it is increased by one, the value reported will be zero. That is because the maximum value
that can be stored in two bytes is 65535, so it just rolls over to zero. This will normally not be a problem, because
the device manufacturers and the ANSI specification typically assign a reasonable number of bytes to prevent an
overflow from happening. If you enter a number that is larger than the overflow value for the threshold,
SMARTMon-UX will alert you and tell you the maximum number you may use.
· You may edit this file manually, but once you go down that path, do not let SMARTMon-UX programmatically
manipulate the file. Your changes may be lost.
· Lines beginning with # are treated as comments.
· SMARTMon-UX currently allows a maximum of 1024 events.
· The action script is optional, but you must still reserve a line for it. Just leave the line blank.
· Note that substitution $$11 and $$1 are valid. SMARTMon-UX looks for $$11 first, then scans for $$1. This
prevents $$1 from being executed in the event that $$11 is defined.
· If you select the "A" option to add thresholds after some are already defined for the selected device, the program
will default to these values as you run through them again.
· You can not define more than one set of thresholds for the same device through the programmatic means
described in this section. If this is what you require, you must edit the configuration file manually. You may also just
launch multiple instances of the program with different configuration files.
Option V - View all defined thresholds
This displays all defined thresholds for all devices. The devices do not have to be on-line or attached to your system.
However, if they are not attached to your system, you will not be able to make any modifications to them.
Command (Enter ? for help): V
Pollable parameters for all devices:
Device Driver Description Threshold PollingSec Actions Description
0 \\.\SCSI2Port2Path0Target19Lun0 SEAGATE ST1181677FC 25 60 L Current
temperature +/- 3 degrees C
script->"echo "Smartmon-ux event @ $$D: $$12=$$V" >> logfile$$1-$$2.$$3.log"
1 \\.\SCSI2Port2Path0Target3Lun0 Unknown (offline) 25 60 L Current
temperature +/- 3 degrees C
script->"echo "Smartmon-ux event @ $$D: $$12=$$V" >> logfile$$1-$$2.$$3.log"
In the case above the first entry represents parameters for our Seagate disk, but the second entry is for something
that is offline. Note that this example provides a means to keep individual running temperature log files for the two
devices. The script works for both Windows and UNIX operating systems. Note also, if you wanted to keep a current
drive temperature file that could be read by an external application, you would script something like:
echo $$V > CurrentTemperature_SeagateAdapter.$$1ID$$2.txt
Comentarios a estos manuales