mirror_zfs/cmd/zed/zed.d/all-debug.sh

#!/bin/sh
#
# Log all environment variables to ZED_DEBUG_LOG.
#
test -f "${ZED_SCRIPT_DIR}/zed.rc" && . "${ZED_SCRIPT_DIR}/zed.rc"

# Override the default umask to restrict access to a newly-created logfile.
umask 077

# Append stdout to the logfile after obtaining an advisory lock.
exec >> "${ZED_DEBUG_LOG:=/tmp/zed.debug.log}"
flock -x 1

printenv | sort
echo

exit 0
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 <cdunlap@llnl.gov> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue #2 2014-01-22 01:30:03 +04:00			`#!/bin/sh`
			`#`
			`# Log all environment variables to ZED_DEBUG_LOG.`
			`#`
			`test -f "${ZED_SCRIPT_DIR}/zed.rc" && . "${ZED_SCRIPT_DIR}/zed.rc"`

			`# Override the default umask to restrict access to a newly-created logfile.`
			`umask 077`

			`# Append stdout to the logfile after obtaining an advisory lock.`
			`exec >> "${ZED_DEBUG_LOG:=/tmp/zed.debug.log}"`
			`flock -x 1`

			`printenv \| sort`
			`echo`

			`exit 0`