9e246ac3d8
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 <cdunlap@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue #2
29 lines
757 B
Plaintext
29 lines
757 B
Plaintext
# zed.rc
|
|
|
|
# Absolute path to the debug output file.
|
|
#ZED_DEBUG_LOG="/tmp/zed.debug.log"
|
|
|
|
# Email address of the zpool administrator.
|
|
# Email will only be sent if ZED_EMAIL is defined.
|
|
#ZED_EMAIL="root"
|
|
|
|
# Email verbosity.
|
|
# If set to 0, suppress email if the pool is healthy.
|
|
# If set to 1, send email regardless of pool health.
|
|
#ZED_EMAIL_VERBOSE=0
|
|
|
|
# Minimum number of seconds between emails sent for a similar event.
|
|
#ZED_EMAIL_INTERVAL_SECS="3600"
|
|
|
|
# Default directory for zed lock files.
|
|
#ZED_LOCKDIR="/var/lock"
|
|
|
|
# Default directory for zed state files.
|
|
#ZED_RUNDIR="/var/run"
|
|
|
|
# The syslog priority (eg, specified as a "facility.level" pair).
|
|
#ZED_SYSLOG_PRIORITY="daemon.notice"
|
|
|
|
# The syslog tag for marking zed events.
|
|
#ZED_SYSLOG_TAG="zed"
|