check_procs don't see some process
Jan Scholten
Jan.Scholten at iconz.net
Sun Oct 17 22:49:21 CEST 2004
On Sat, 16 Oct 2004 08:56:07 +0200, Julien TOUCHE
<julien.touche at lycos.com> wrote:
> Jan Scholten a écrit :
>> ./check_procs --help
>> [..]
>> -a, --argument-array=STRING
>> Only scan for processes with args that contain STRING.
>
> args is not the same than command, maybe i misunderstood it as i check it
yeah i know but it seems like it runs some kind of grep over the ps
output.
The helpfile from check_proc out of the 1.4.1 alpaha package is somewhat
better (it didn't seem to change his behavior):
Examples:
check_procs -w 2:2 -c 2:1024 -C portsentry
Warning if not two processes with command name portsentry. Critical
if < 2 or > 1024 processes
check_procs -w 10 -a '/usr/local/bin/perl' -u root
Warning alert if > 10 processes with command arguments containing
'/usr/local/bin/perl' and owned by root
check_procs -w 50000 -c 100000 --metric=VSZ
Alert if vsz of any processes over 50K or 100K
check_procs -w 10 -c 20 --metric=CPU
Alert if cpu of any processes over 101001145700r 20%
--
Jan Scholten
Research and Development Intern
Iconz.co.nz
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list