Permalink
Browse files

fix typos

  • Loading branch information...
1 parent 44e8a3a commit f219667755bbcc97df4233f6a052a465b0e71a65 @datamuc committed Sep 28, 2013
Showing with 3 additions and 3 deletions.
  1. +3 −3 lib/Nagios/Passive/BulkResult.pm
View
6 lib/Nagios/Passive/BulkResult.pm
@@ -80,14 +80,14 @@ Nagios::Passive::BulkResult - submit passive check results to nagios' checkresul
Submitting a huge amount of results with L<Nagios::Passive::ResultPath> has some
limits. Typically a checkresult has a size of 200 bytes or so. But the blocksize
-of most filesystems is about 4K. So a file takes at least 4K of disk space.
+of most filesystems is about 4K. Therefore a file takes at least 4K of disk space.
Well, disk space is cheap and nagios deletes the file again after it has
processed it, but most of the time the checkresults_dir is a memory filesystem.
And suddenly you waste a lot of RAM. Also reading one large file is faster than
reading thousands of small files.
Nagios can handle multiple check results within one file. This is what this
-Module provides. You just create a Nagios::Passive objects with an undefined
-checkresults_dir and add that object to the BulkResult container. When you
+module provides. You just create Nagios::Passive objects with an undefined
+checkresults_dir and add these to the BulkResult container. When you
are done, just call C<-E<gt>submit> on the container and one big file is created.

0 comments on commit f219667

Please sign in to comment.