On 12/05/21 11:29 AM, Alex Griffin wrote:
> To get around the issue of bash interpreting your regex characters as
> something else, simply wrap the regex in single quotes:
>
> ./check_procs -w 25 -c 35 -m CPU -v --ereg-argument-array='^((?!john).)*$'
>
> Alex Griffin
Alex,
I already tried that and this was the error:
/usr/lib64/nagios/plugins/check_procs -w 25 -c 35 -m CPU -v
--ereg-argument-array='^((?!john).)*$'
PROCS UNKNOWN: Could not compile regular expression - Invalid preceding
regular expression
with the message on the web output being: PROCS UNKNOWN: Could not
compile regular expression - Invalid preceding regular expression
Best Regards,
Camron
--
Camron W. Fox
Hilo Office
High Performance Computing Group
Fujitsu Management Services of America, Inc.
E-mail: cw...@us.fujitsu.com
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users@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
