On 1 May 2007, at 20:19, Dragon wrote:
Having said that, it would be nice if that module cleaned up after
itself when it is done with a file.
I believe it does. The OP has a problem that would be worth the
effort to fix
if it wasn't an obsolete version.
--
Nick Kew
Actually, I will be moving to Apache 2.2.3 (using deflate)soon, but want to cap
the bandwidth on the server in question until then.
-Grant
- Original Message -
From: Nick Kew
To: users@httpd.apache.org
Sent: Tuesday, May 01, 2007 3:07 PM
Subject: Re: [EMAIL PROTECTED
Grant Peel wrote:
Hi all,
I have added mod_gzip to my apache config a few weeks back.
Yesterday, the server pretty much locked up due to no disk space
left on the root filesystem.
It appears that with mod_gzip turned on, hundreds of *.wrk files are
left in the /tmp dir, eventually filling i
I also think Apache 1.3 is capable of doing in memory compression only upto
certain KB of data after which it creates temp files.
So, if moving to Apache 2.0 doesn't look likely immediately, you might want
to look into that approach.
Thanks,
Mandy.
http://mandysingh.blogspot.com
On 5/2/07, Nic
On 1 May 2007, at 19:28, Grant Peel wrote:
Does anyone know of a fix for this?
Yes. Upgrade to Apache 2.
You're using a 1998 server. Things have moved on since then.
Like, a clean compression architecture that eliminates the need
for crap like tempfiles.
--
Nick Kew
Hi all,
I have added mod_gzip to my apache config a few weeks back.
Yesterday, the server pretty much locked up due to no disk space left on the
root filesystem.
It appears that with mod_gzip turned on, hundreds of *.wrk files are left in
the /tmp dir, eventually filling it up.
Does anyone k
