anyone? cheers..
On Thu, Sep 8, 2011 at 6:14 PM, Steve Foster stephenfoster1...@gmail.comwrote:
All,
did anyone have any thoughts or opinions on this?
cheers
Steve
On Wed, Aug 31, 2011 at 5:31 PM, Steve Foster
stephenfoster1...@gmail.com wrote:
i've also had a thought, I also
All,
did anyone have any thoughts or opinions on this?
cheers
Steve
On Wed, Aug 31, 2011 at 5:31 PM, Steve Foster
stephenfoster1...@gmail.comwrote:
i've also had a thought, I also implemented the following:
LimitRequestLine 4000
Which is about half of the default size i beleive, could
Steve
On Tue, Aug 30, 2011 at 4:44 PM, Steve Foster
stephenfoster1...@gmail.comwrote:
Correction , the static file gives a 206 status code...
hi there,
I have multiple versions of Apache, all built with minimal inclusions of
modules in the core binary , they don't exhibit the memory consumption issue
when attacked with the killapache script, they all run happily for hours
with no resource issues.
Does anyone know which particular
On Tue, Aug 30, 2011 at 3:18 PM, Eric Covener cove...@gmail.com wrote:
It's tuff baked into the core binary, httpd. Note that many dynamic
responses can't be satisfied as range requests, so maybe your / is
such a response.
Hi eric,
sorry i was referring to the compiled-in modules, e.g:
Hi eric,
yes i have tried it on a static file as well and no issues., obviously the
static file gives a 200 status code back in the logs, but i am still sending
the Range header as per the kill script.
Steve
On Tue, Aug 30, 2011 at 3:42 PM, Eric Covener cove...@gmail.com wrote:
When you
Correction , the static file gives a 206 status code...
On Tue, Aug 30, 2011 at 4:14 PM, Steve Foster
stephenfoster1...@gmail.comwrote:
Hi eric,
yes i have tried it on a static file as well and no issues., obviously the
static file gives a 200 status code back in the logs, but i am still
Hi there,
I am looking at ways i can more reliably centralise apache access logs into
a single logging area, i have discounted syslog on the basis of reliabilty
and the sheer volume of log entries i need to handle.
I am canvassing opinion on what others who maintain large configurations
might
Hi there,
I have a slight issue with rotatelogs and british summer and wintertime.
When in BST my logfile entries are being written with the correct timestamp
(localised) but the logfile rotation filename does not match the current
time,
e.g i set my logfile name as
...@twistfare.bewrote:
hey Steve,
didn't know you guys have summers in Britain ?! ;-)
I would guess your Apache is started either from CRON or in any case from a
startup script that didn't have the right TZ environment variable set.
Rob
Citeren Steve Foster stephenfoster1...@gmail.com:
Hi there,
I have
You would assume so, but the guidance in the documentation says the
following:
Causes the use of local time rather than GMT as the base for the interval
or for strftime(3) formatting with size-based rotation. Note that
using -lin an environment which changes the GMT offset (such as for
BST or
11 matches
Mail list logo
