rec 1.3.4 → 1.3.5

data/EXAMPLES

@@ -24,7 +24,7 @@ If we see that happen 3 times (+threshold+) within a minute (+lifespan+), alert
   }
 
 When we see the first event, a state is created with title "Failed sudo password for user richard".
-The second event has not effect, beyond automatically incrementing the count.
+The second event has no effect, beyond automatically incrementing the count.
 When we see the third event, an output message is generated and logged, and then the generated
 message is also sent via IM to the administrator. Alternatively:
 
@@ -59,7 +59,7 @@ for a fixed 5 minutes.
 == Adding a final block
 If we want to see one message when the user first has trouble, then another message
 after he has decided to stop trying, the format is a little different. The block
-given is previous examples is stored in the +params+ as +action+.
+given in previous examples is stored in the +params+ as +action+.
 
 Instead, the +action+ block may be specified directly as a member of the params hash,
 and the +final+ must be specified in this way if it is to be used.

data/README

@@ -55,7 +55,7 @@ There are several alternatives to REC which may suit your needs better:
 * scalextreme.com[www.scalextreme.com]
 
 While I like these options, I find they take a lot of configuring.
-They also has some dependencies that make them a bit heavier than you may want.
+They also have some dependencies that make them a bit heavier than you may want.
 If you just want to keep track of a few kinds of events, want a lot of flexibility
 and control without too much effort, then REC may be of some value.
 
@@ -85,7 +85,7 @@ We can also 'swallow' all of the rest of the "host terra is down" events because
 This <em>event compression</em> means the administrator gets one important message, and not 27
 distracting alerts.
 
-A notifcation can be sent by email or IM, depending on your preferences and working hours.
+A notification can be sent by email or instant message, depending on your preferences and working hours.
 The destinations and credentials are supplied to your ruleset:
   # For better security, move the next few lines into a file readable only by
   # the user running this script eg. /home/rec/alert.conf
@@ -154,7 +154,7 @@ The sequence of captures is as specified for ruby Regexps.
   :pattern => /\w+ sudo\:  (\w+) \: (\d) incorrect password attempts/,
   :details => ["userid", "failures"],
 The names chosen for captured values are used as keys to store the values in the same
-hash that stores the parameters, so do *not* choose words like +pattern+, +details+,
+hash that stores the parameters, so do *not* choose the following keywords: +pattern+, +details+,
 +message+, +threshold+, +lifespan+, +alert+, +capture+, +continue+, or +action+.
 
 === message
@@ -179,7 +179,7 @@ minutes longer at each request.
 This is a string template used to generate an output log message (the timestamp will be
 prefixed automatically to complete the log entry).
   :alert => "'Too much sudo activity' userid=%userid$s attempts=%count$d dur=%dur$0.3fs ",
-By convention, we make out log messages very easy to parse by creating name=value pairs,
+By convention, we make our log messages very easy to parse by creating name=value pairs,
 and single-quoting strings containing spaces, in case the output will be processed further.
 
 If no +alert+ is provided, it will default to +message+.

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: rec
 version: !ruby/object:Gem::Version 
-  hash: 19
+  hash: 17
   prerelease: 
   segments: 
   - 1
   - 3
-  - 4
-  version: 1.3.4
+  - 5
+  version: 1.3.5
 platform: ruby
 authors: 
 - Richard Kernahan
@@ -15,7 +15,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2013-03-26 00:00:00 Z
+date: 2013-10-10 00:00:00 Z
 dependencies: 
 - !ruby/object:Gem::Dependency 
   name: xmpp4r
@@ -32,7 +32,11 @@ dependencies:
         version: "0.5"
   type: :runtime
   version_requirements: *id001
-description: "\t\tSifts through your log files in real time, using stateful intelligence to determine\n\
+description: "\t\tDeprecated. \n\
+  \t\tI'm planning to discontinue this gem. Although it has enormous flexibility and power, \n\
+  \t\tit is in my view too complex. 80% of requirements can be met through custom shell scripts\n\
+  \t\twhich are much simpler to write and maintain. \n\n\
+  \t\tSifts through your log files in real time, using stateful intelligence to determine\n\
   \t\twhat is really important. REC can alert you (by email or IM) or it can simply condense\n\
   \t\ta large log file into a much shorter and more meaningful log.\n\
   \t\tREC is inspired by Risto Vaarandi's brilliant *sec* (simple-evcorr.sourceforge.net)\n\