Lakshmi, it isn't an issue and doesn't need to be taken care of -- it works as it's meant to. It is meant to be an integer, not a range.
Sent from a phone. On Mar 28, 2015, at 1:28 PM, lakshmi narayanan sadagopan <laxmynar...@gmail.com<mailto:laxmynar...@gmail.com>> wrote: Hi, Would you know if you have a patch or update to take care of this issue? Regards Lakshmi On Wed, Mar 25, 2015 at 4:19 PM, lakshmi narayanan sadagopan <laxmynar...@gmail.com<mailto:laxmynar...@gmail.com>> wrote: Hi, I was going over the check_http writeup you have at https://www.monitoring-plugins.org/doc/man/check_http.html . I am able to use check_http to trigger a WARNING state based on a single expiry day threshold but not for a range. So, for example This works check_http -H www.verisign.com<http://www.verisign.com> -C 14 but this doesn't. check_http -H www.verisign.com<http://www.verisign.com> -C 30,14 Would you know how I can get around this? Your help is much appreciated. Regards Lakshmi
