Re: Logging to file when HAProxy failed to start

2015-02-17 Thread Baptiste
will appreciate your answer for the question below. Thanks, Galit _ From: Yosef Amir Sent: Tuesday, February 10, 2015 5:08 PM To: HAProxy Cc: Cohen Galit; Yosef Amir Subject: Logging to file when HAProxy failed to start Hi , Currently, When

RE: Logging to file when HAProxy failed to start

2015-02-17 Thread Cohen Galit
Hello HAProxy team, We will appreciate your answer for the question below. Thanks, Galit _ From: Yosef Amir Sent: Tuesday, February 10, 2015 5:08 PM To: HAProxy Cc: Cohen Galit; Yosef Amir Subject: Logging to file when HAProxy failed to start Hi

Recall: Logging to file when HAProxy failed to start

2015-02-10 Thread Yosef Amir
Yosef Amir would like to recall the message, Logging to file when HAProxy failed to start. “This e-mail message may contain confidential, commercial or privileged information that constitutes proprietary information of Comverse Inc. or its subsidiaries. If you

Logging to file when HAProxy failed to start

2015-02-10 Thread Yosef Amir
Hi , Currently, When HAproxy failed to initial (E.G invalid haproxy.cfg options) it write the error to the screen. Is there option that HAproxy will write to log file when it failed to initial? Thanks Amir Yosef This e-mail message may contain confidential,

Logging to file when HAProxy failed to start

2015-02-10 Thread Yosef Amir
Hi , Currently, When HAproxy failed to initial (E.G invalid haproxy.cfg options) it write the error to the screen. Is there option that HAproxy will write to log file when it failed to initial? Example: [root@proxy-au2 ~]# haproxy -f /usr/cti/conf/haproxy/haproxy.cfg [ALERT] 040/172141 (12460) :