On 2010-06-05 18:11, James Corteciano wrote:
Thanks for your response. What is your configuration for ErrorLog on all
vhost?
For one single error log to wich all vhosts log, just place the ErrorLog
directive in the server config scope (outside of any VirtualHost container).
For multiple
Hi Jonas,
Thanks for your response. What is your configuration for ErrorLog on all
vhost?
Regards,
James
On Fri, May 28, 2010 at 10:57 PM, Jonas Eckerman jonas_li...@frukt.orgwrote:
On 2010-05-24 11:16, James Corteciano wrote:
I'm thinking to use logger tool for every httpd services
On 2010-05-24 11:16, James Corteciano wrote:
I'm thinking to use logger tool for every httpd services running but
it's not an ideal because it takes more resources in server. Let say
there are 50 vhost in a server, then 100 logger apps will be running
because 2 logger per vhost (ErrorLog
Have you looked at syslog-ng?
Also might want to take a look at loganalysis.org. They have some
resources which may (or may not) be of some help.
Sheryl
We wanted to use syslog too, but it's very rigid (only 8 localX facility
for custom logs) so we discarded this solution.
We heard of
On 24.05.10 11:45, Sandro Tosi wrote:
We wanted to use syslog too, but it's very rigid (only 8 localX facility
for custom logs) so we discarded this solution.
you can use one local facility and zillions of program names to distinguish
between different logs.
--
Matus UHLAR - fantomas,
Hi All,
I have running various web farms and I'm looking for better solution to
forward all vhost logs to the centralized syslog server. How do you guys
keep vhost logs? I have done googling this kind of setup but there is no
result.
I'm thinking to use logger tool for every httpd services
Don't get complicated through the various loggers available, simply use
logrotate the default linux application used to rotate the log files in
apache.
On 24 May 2010 14:46, James Corteciano ja...@linux-source.org wrote:
Hi All,
I have running various web farms and I'm looking for better
We wanted to use syslog too, but it's very rigid (only 8 localX facility
for custom logs) so we discarded this solution.
We heard of scribe, the logs aggregator Facebook uses; it seems very
flexible, and since FB is using it for his web servers, it's probably
doing its job quite well. Sitll,
