An example of this is the resmon main page. By default this check will look
at http://hostname:81/modulename/checkname which will output a single check.
However, this change lets you specify a custom URL which returns metrics for
multiple modules and it will find the correct one.

git-svn-id: https://labs.omniti.com/resmon/trunk@438 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@436 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@435 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

Core::BSD::Sensor for reading hardware sensors under OpenBSD (and maybe other BSDs as well.)  Based on CHECK_BSD_TEMP from resmon1.

git-svn-id: https://labs.omniti.com/resmon/trunk@434 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@433 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@432 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@431 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

(Reported by Bryan Horstmann-Allen)

git-svn-id: https://labs.omniti.com/resmon/trunk@429 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@428 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@427 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@426 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@425 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@423 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@422 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@421 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@420 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@419 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@418 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/trunk@417 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

It is used in the clean up function. Incidentally, this fixes a really
annoying issue where the check timeout functionality broken. The cause of the
check timeout functionality breaking was a scoping issue - the reader file
handle falls out of scope when the alarm fires and dies, and it waits until
the process finishes before passing control back to resmon. Storing the file
handle prevents it from being cleaned up until after we kill the process in
the clean_up function later on.

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@416 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

It's too much of a pain to have to change the built in versions of the modules
in the testmod script each time the resmon code changes, and it leads to odd
behavior with the testmod script that isn't present when run with resmon
itself.

The downside is that the testmod script is no longer standalone, and needs to
reference the resmon source code if it is moved out of the resmon tree. This
isn't as much of an issue as the testmod script by default is in the resources
directory of the resmon source and can be run direct from there.

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@415 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

The original intent was to fix bad behavior when a command doesn't exist. Upon
looking further into the implementation of the run_command function, I
realized that using open achieved the same effect (backticks but we get a
process id out of it) without a lot of code that didn't quite work when the
exec failed.

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@414 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55

git-svn-id: https://labs.omniti.com/resmon/branches/resmon2@413 8c0face9-b7db-6ec6-c4b3-d5f7145c7d55