On Thu, Aug 09, 2012 at 03:16:07PM +0200, Aleksandar Lazic wrote:
> Hi,
>

Hello,

> [...]
> 
> As you can see I have not 'option logasap' but get the '+'-sign?!
>  
> Please can anybody help me to find the error, thanks.
> 
> Best regards
> Aleks
> 

It looks like a bug with the option unique-id-format.

Can you try this patch ?


-- 
William Lallemand
>From 7d40e9f6d3f8f1c5ce09e264226a1e5e369d70a0 Mon Sep 17 00:00:00 2001
From: William Lallemand <wlallem...@exceliance.fr>
Date: Thu, 9 Aug 2012 16:41:35 +0200
Subject: [PATCH] BUG/MINOR: to_log erased with unique-id-format

curproxy->to_log was reset to LW_INIT when using unique-id-format,
so logs looked like option logasap
---
 src/log.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/log.c b/src/log.c
index 2a3cd16..b1f532a 100644
--- a/src/log.c
+++ b/src/log.c
@@ -309,7 +309,7 @@ void parse_logformat_string(char *str, struct proxy *curproxy, struct list *list
 	struct logformat_node *tmplf, *back;
 	int options = 0;
 
-	curproxy->to_log = LW_INIT;
+	curproxy->to_log |= LW_INIT;
 
 	/* flush the list first. */
 	list_for_each_entry_safe(tmplf, back, list_format, list) {
-- 
1.7.9.5

Reply via email to