I'm running LSWS 3.3.3 on CentOS Enterprise 4.6 i686. It is a dynamic site. I posted about a problem I had with the LSWS bytelogger a few months back, and just now checked to see if it had been resolved. I checked today to see if LSWS had started properly logging bytes again, but as of yet the answer is still no. The file permissions are as follows: -rw-rw-rw- 1 nobody nobody 0 Nov 30 23:16 domain.net-bytes_log The vhost in LSWS has /usr/local/apache/domlogs/domain.net-bytes_log configured as byte log path, runs as nobody:nobody, all have read/write access to it, but it still doesn't write the log. It appeared to work correctly until 02/13/07 or so, the date of the last log rollover. Any ideas? Is this a problem with LSWS, or my configuration? It is strange though that it would suddenly decide all those months ago to quit working. Also, if you all have time, it'd be nice if we could configure the bytelog rollover/compression/etc. separate from the access log. I'd actually prefer it didn't rollover at all, though it did (while it was still working) on multiple occasions.