Fix invalid range for trusty nagios check_procs.

This apparently worked on precise (because it alerted often enough)
possibly due to input scrubbing. Was definitely wrong though.

Trusty package spits out some extra noise too, but the nagios exit
code appears correct... so...

Change-Id: Ic8efe935301f70576f57d29f3847ed7533c3b597