[PATCH] BUG/MINOR: frontend: fix frontend start status (9 replies)

Hi,
I ran into a bug when using the 'disabled' keyword for frontends -
currently it is not possible to enable such frontend later.
The correponding patch file follows.

Regards,

Ondrej Stumpf
---------------------------------------

From 34fa61371d5c80e5cc2d92142e15baad0eb28d80 Mon Sep 17 00:00:00 2001
From: Ondrej Stumpf <ondrej.stumpf@gooddata.com>
Date: Mon, 25 Apr 2016 11:54:36 +0200
Subject: [PATCH] BUG/MINOR: frontend: fix frontend start status
When the 'disabled' keyword is used in config file for a frontend, the
frontend starts
with PAUSED status rather than STOPPED to make it enablable in the future.
---
src/cfgparse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/cfgparse.c b/src/cfgparse.c
index 2400559..0c069f6 100644
--- a/src/cfgparse.c
+++ b/src/cfgparse.c
@@ -3267,7 +3267,7 @@ int cfg_parse_listen(const char *file, int linenum,
char **args, int kwm)
else if (!strcmp(args[0], "disabled")) { /* disables this proxy */
if (alertif_too_many_args(0, file, linenum, args, &err_code))
goto out;
- curproxy->state = PR_STSTOPPED;
+ curproxy->state = PR_STPAUSED;
}
else if (!strcmp(args[0], "enabled")) { /* enables this proxy (used to
revert a disabled default) */
if (alertif_too_many_args(0, file, linenum, args, &err_code))
--
1.9.1