summaryrefslogtreecommitdiffstats
path: root/cmd/zed/zed.d/checksum-email.sh
diff options
context:
space:
mode:
authorChris Dunlap <[email protected]>2014-01-21 13:30:03 -0800
committerBrian Behlendorf <[email protected]>2014-04-02 13:10:03 -0700
commit9e246ac3d8ef9ff8aed86ecf277eea2cae3a79d3 (patch)
tree9ae68bdb5b532dd2d5fbb2bc0fcaf684fd78ea50 /cmd/zed/zed.d/checksum-email.sh
parent8c7aa0cfc47578d1d38f80ecb7c66eed7cde5c59 (diff)
Initial implementation of zed (ZFS Event Daemon)
zed monitors ZFS events. When a zevent is posted, zed will run any scripts that have been enabled for the corresponding zevent class. Multiple scripts may be invoked for a given zevent. The zevent nvpairs are passed to the scripts as environment variables. Events are processed synchronously by the single thread, and there is no maximum timeout for script execution. Consequently, a misbehaving script can delay (or forever block) the processing of subsequent zevents. Plans are to address this in future commits. Initial scripts have been developed to log events to syslog and send email in response to checksum/data/io errors and resilver.finish/scrub.finish events. By default, email will only be sent if the ZED_EMAIL variable is configured in zed.rc (which is serving as a config file of sorts until a proper configuration file is implemented). Signed-off-by: Chris Dunlap <[email protected]> Signed-off-by: Brian Behlendorf <[email protected]> Issue #2
Diffstat (limited to 'cmd/zed/zed.d/checksum-email.sh')
l---------cmd/zed/zed.d/checksum-email.sh1
1 files changed, 1 insertions, 0 deletions
diff --git a/cmd/zed/zed.d/checksum-email.sh b/cmd/zed/zed.d/checksum-email.sh
new file mode 120000
index 000000000..f95bec215
--- /dev/null
+++ b/cmd/zed/zed.d/checksum-email.sh
@@ -0,0 +1 @@
+io-email.sh \ No newline at end of file