Am Dienstag, 12. November 2013, 13:33:23 schrieb Jan Kaluža:
I think LDAPLibraryDebug is one user of stderr going to the error
log. As the logging is done by the ldap library, there is really
no way to change it. But I guess it would be acceptable if that
works only if logging to a file
On 10/15/2013 05:27 PM, Jeff Trawick wrote:
Does this patch/commit look okay? It works for me with a simple
provider in different scenarios (vhost that inherits provider setup from
s_main, vhost that has its own setup).
I suppose mod_syslog needs to disallow any attempts to configure it in a
On 11/11/2013 10:50 AM, Stefan Fritsch wrote:
On Thu, 7 Nov 2013, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group wrote:
Hmm. This points out another issue when using an error log provider for the
main server log:
We lose everything that the server or
On Tue, Nov 12, 2013 at 7:33 AM, Jan Kaluža jkal...@redhat.com wrote:
On 11/11/2013 10:50 AM, Stefan Fritsch wrote:
On Thu, 7 Nov 2013, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group
wrote:
Hmm. This points out another issue when using an error
On Thu, 7 Nov 2013, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group wrote:
Hmm. This points out another issue when using an error log provider for the
main server log:
We lose everything that the server or other programs like CGI-scripts write
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group wrote:
Hmm. This points out another issue when using an error log provider for the
main server log:
We lose everything that the server or other programs like CGI-scripts write
to the stderr FD as it
is simply written to
On 11/07/2013 11:11 AM, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group wrote:
Hmm. This points out another issue when using an error log provider for the
main server log:
We lose everything that the server or other programs like CGI-scripts write to
Seems fine.
Regards
Rüdiger
-Original Message-
From: Jan Kaluža
Sent: Donnerstag, 7. November 2013 13:09
To: dev@httpd.apache.org
Subject: Re: error log providers, multiple vhosts, mod_syslog
On 11/07/2013 11:11 AM, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +
On Thu, Nov 7, 2013 at 7:09 AM, Jan Kaluža jkal...@redhat.com wrote:
On 11/07/2013 11:11 AM, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger, Vodafone Group
wrote:
Hmm. This points out another issue when using an error log provider for
the main server log:
We lose
On 11/07/2013 07:07 PM, Jeff Trawick wrote:
On Thu, Nov 7, 2013 at 7:09 AM, Jan Kaluža jkal...@redhat.com
mailto:jkal...@redhat.com wrote:
On 11/07/2013 11:11 AM, Joe Orton wrote:
On Thu, Oct 17, 2013 at 12:33:50PM +, Plüm, Rüdiger,
Vodafone Group wrote:
, Vodafone Group
ruediger.pl...@vodafone.com mailto:ruediger.pl...@vodafone.com
wrote:
-Original Message-
From: Jan Kaluža
Sent: Donnerstag, 17. Oktober 2013 13:21
To: dev@httpd.apache.org mailto:dev@httpd.apache.org
Subject: Re: error log providers, multiple
On Wed, 6 Nov 2013 10:05:25 -0500
Jeff Trawick traw...@gmail.com wrote:
What are the thoughts around handling stderr?
In some cases it is just junk if not wrapped in a proper message
(i.e., there can be a requirement that error log be completely
parseable and/or a requirement that stderr
mailto:ruediger.pl...@vodafone.com wrote:
-Original Message-
From: Jan Kaluža
Sent: Donnerstag, 17. Oktober 2013 13:21
To: dev@httpd.apache.org mailto:dev@httpd.apache.org
Subject: Re: error log providers, multiple vhosts, mod_syslog
There's another
: Donnerstag, 17. Oktober 2013 13:21
To: dev@httpd.apache.org mailto:dev@httpd.apache.org
Subject: Re: error log providers, multiple vhosts, mod_syslog
There's another problem with log providers and vhosts and I think
I have
no idea how to fix it without doing dirty
:
-Original Message-
From: Jan Kaluža
Sent: Donnerstag, 17. Oktober 2013 13:21
To: dev@httpd.apache.org
Subject: Re: error log providers, multiple vhosts, mod_syslog
There's another problem with log providers and vhosts and I think I have
no idea how to fix it without doing
There's another problem with log providers and vhosts and I think I have
no idea how to fix it without doing dirty hacks...
The problem is with ap_open_logs function, which does following:
1. Main server log is opened (open_error_log()). If this log uses error
log provider, s_main-error_log
-Original Message-
From: Jan Kaluža
Sent: Donnerstag, 17. Oktober 2013 13:21
To: dev@httpd.apache.org
Subject: Re: error log providers, multiple vhosts, mod_syslog
There's another problem with log providers and vhosts and I think I have
no idea how to fix it without doing dirty
On 10/15/2013 05:27 PM, Jeff Trawick wrote:
Does this patch/commit look okay? It works for me with a simple
provider in different scenarios (vhost that inherits provider setup from
s_main, vhost that has its own setup).
The patch looks OK to me. Thanks for it.
I suppose mod_syslog needs to
18 matches
Mail list logo
