BUG/MEDIUM: Consistently use 'check' in process_chk

I am not entirely sure that this is a bug, but it seems
to me that it may cause a problem if there agent-check is
configured and there is some kind of error making a connection for it.

Signed-off-by: Simon Horman <horms@verge.net.au>
This commit is contained in:
Simon Horman 2014-06-20 12:29:47 +09:00 committed by Willy Tarreau
parent 15480d7250
commit ccaabcdfca

View File

@ -1541,7 +1541,7 @@ static struct task *process_chk(struct task *t)
* First, let's check whether there was an uncaught error, * First, let's check whether there was an uncaught error,
* which can happen on connect timeout or error. * which can happen on connect timeout or error.
*/ */
if (s->check.result == CHK_RES_UNKNOWN) { if (check->result == CHK_RES_UNKNOWN) {
/* good connection is enough for pure TCP check */ /* good connection is enough for pure TCP check */
if ((conn->flags & CO_FL_CONNECTED) && !check->type) { if ((conn->flags & CO_FL_CONNECTED) && !check->type) {
if (check->use_ssl) if (check->use_ssl)