I've had mod_gzip working fine for about a month now then all of a suddent its just stopped removing .wrk files from the specified directory. I had it set to place the wrk files in /tmp and after about a month it just started filling it up and not removing the work files for some reason. I then moved it to /home/tmpdir to see if it might have been a problem with the settings on my /tmp that caused the problem and it filled that baby right up as well. Anyone ever experience this? I can't seem to find any possible reason why this is happeneing.

In your apache configuration, in the mod_gzip section, check for this:

mod_gzip_keep_workfiles
Set it to yes/no depending what you need.

mod_gzip_keep_workfiles No

Its been set to no ever since i set it up. It only just started doing this, and i can't figure out why.

mod_gzip is pretty flaky about the tmp files. If this is the first time you've seen it, you've been lucky. I wish I had a good workaround for you. The Apache 2 filter doesn't use tmp files, so that's a good option if Apache 2 has the modules you need.

maybe a cron to deleted them periodically?

Originally posted by thelinuxguy
maybe a cron to deleted them periodically?

That would probably do more harm than good. I would probably end up deleting files currently in use, etc. I'm also concerned the work files are not being removed from memory. I'd rather get to the source of the problem and fix it from there rather than use the bandaid approach.

I have a cron job to clean them out, and it does help. Every few weeks, though, it feels like freaking out and drops 25mb files until tmp fills. Cron can't save it then.