diff options
| author | Neil Brown <neilb@suse.de> | 2002-05-20 13:17:18 +0200 |
|---|---|---|
| committer | Neil Brown <neilb@suse.de> | 2002-05-20 13:17:18 +0200 |
| commit | bd526cee922b8e2b279f04ca067f729e9b0ee723 (patch) | |
| tree | 24ebb244ddc6b5ecf9820d53517db288ff4b77a9 /mdadm.8 | |
| parent | mdadm-1.0.0 (diff) | |
| download | mdadm-bd526cee922b8e2b279f04ca067f729e9b0ee723.tar.xz mdadm-bd526cee922b8e2b279f04ca067f729e9b0ee723.zip | |
mdadm-1.0.1mdadm-1.0.1
Diffstat (limited to 'mdadm.8')
| -rw-r--r-- | mdadm.8 | 7 |
1 files changed, 6 insertions, 1 deletions
@@ -594,9 +594,14 @@ is given, then any other md devices that appear in will also be monitored. The result of monitoring the arrays is the generation of events. -These events are passed to a separate program (is specified) and may +These events are passed to a separate program (if specified) and may be mailed to a given E-mail address. +When passing event to program, the program is run once for each event +and is given 2 or 3 command-line arguements. The first is the +name of the event (see below). The second is the name of the +md device which is affected, and the third is the name of a related +device if relevant, such as a component device that has failed. If .B --scan |