My first question would be why would you want to maintain (on an
ongoing basis) access logs for what appears to be a pretty busy server?
An important piece of information that's missing is the version of
resin that you're running. I know from personal experience that older
versions, in the 2.x world, did not properly rotate log files.
Also, what settings for the logs do you have configured in your resin
configuration? If you're running resin with apache, then (usually)
apache is in control of the access logs, not resin. It's hard to tell
from what you've said how you have resin configured, standalone or
On Oct 15, 2008, at 04:33, Richard Grantham wrote:
I've got a major issue with our live servers. The logs don't appear to
be rotating correctly. This is filling the disk and causing
Resin is running as the resin user - therefore will have reduced
permissions but, even so, this shouldn't be happening as that user is
the owner of the folder that is being written to.
Any ideas on how to sort this or is it a bug?
[EMAIL PROTECTED] logs]# ls -l
-rw-r--r-- 1 resin apache 1073979392 Oct 15 11:30 access.log
-rw-r--r-- 1 resin apache 1073745275 Oct 15 00:50 access.log.20081015
-rw-r--r-- 1 resin apache 1073892465 Oct 15 00:52 access.log.
-rw-r--r-- 1 resin apache 49848320 Oct 15 00:54 access.log.
-rw-r--r-- 1 resin apache 0 Oct 15 00:56 access.log.
-rw-r--r-- 1 resin apache 0 Oct 15 00:58 access.log.
-rw-r--r-- 1 resin apache 0 Oct 15 01:00 access.log.
-rw-r--r-- 1 resin apache 0 Oct 15 01:02 access.log.
-rw-r--r-- 1 resin apache 0 Oct 15 01:04 access.log.
[rest deleted for brevity]
resin-interest mailing list