summaryrefslogtreecommitdiff
path: root/doc/mmsnmptrapd.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/mmsnmptrapd.html')
-rw-r--r--doc/mmsnmptrapd.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/mmsnmptrapd.html b/doc/mmsnmptrapd.html
index 699049d..fb50f6c 100644
--- a/doc/mmsnmptrapd.html
+++ b/doc/mmsnmptrapd.html
@@ -34,8 +34,8 @@ The following logic is applied to all message being processed:
snmptrapd/severity/hostname. A configurable mapping table will be used to drive a new
severity value from that severity string. If no mapping has been defined, the original
severity is not changed.
-<li>It replaces the "FromHost" value with the derived value from step2
-<li>It replaces the "Severity" value with the derived value from step 3
+<li>It replaces the "FromHost" value with the derived value from step 2
+<li>It replaces the "Severity" value with the derived value from step 3
</ol>
<p>Note that the placement of this module inside the configuration is important. All actions
before this modules is called will work on the unmodified message. All messages after it's call
@@ -55,11 +55,11 @@ tells the module which start string inside the tag to look for. The default is
matching incoming messages. It MUST not be given, except if two slashes are required
for whatever reasons (so "tag/" results in a check for "tag//" at the start of
the tag field).
-<li><b>$mmsnmptrapdSeverityMapping</b> [severtiymap]<br>
+<li><b>$mmsnmptrapdSeverityMapping</b> [severitymap]<br>
This specifies the severity mapping table. It needs to be specified as a list. Note that
due to the current config system <b>no whitespace</b> is supported inside the list, so be
sure not to use any whitespace inside it.<br>
-The list is constructed of Severtiy-Name/Severity-Value pairs, delimited by comma.
+The list is constructed of Severity-Name/Severity-Value pairs, delimited by comma.
Severity-Name is a case-sensitive string, e.g. "warning" and an associated
numerical value (e.g. 4).
Possible values are in the rage 0..7 and are defined in RFC5424, table 2. The