http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4693
------- Additional Comments From [EMAIL PROTECTED] 2006-03-15 17:47 ------- well, i suppose it does, bug i'm just guessing because i dont hear anyone complain until their disk is full and their mail stops coming in. i've seen cases where daily logrotate will save it for a while.... in this case, it was happending daily for the last 8 days. -rw-rw-r-- 1 doublech doublech 1098107980 Mar 13 04:02 spamd.log.3.gz -rw-rw-r-- 1 doublech doublech 1142570815 Mar 12 04:01 spamd.log.4.gz -rw-rw-r-- 1 doublech doublech 1188325192 Mar 11 04:02 spamd.log.5.gz -rw-rw-r-- 1 doublech doublech 1231933772 Mar 10 04:03 spamd.log.6.gz -rw-rw-r-- 1 doublech doublech 1287468111 Mar 9 04:02 spamd.log.7.gz -rw-rw-r-- 1 doublech doublech 1327049798 Mar 8 04:02 spamd.log.8.gz -rw-rw-r-- 1 doublech doublech 1904957 Mar 7 03:11 spamd.log.9.gz -rw-r--r-- 1 doublech doublech 1294305 Mar 6 01:07 spamd.log.10.gz -rwxr-xr-x 1 doublech doublech 1151532 Mar 3 19:19 spamd.log.11.gz -rwxr-xr-x 1 doublech doublech 864265 Mar 1 22:15 spamd.log.12.gz -rwxr-xr-x 1 doublech doublech 863982 Feb 28 22:03 spamd.log.13.gz -rwxr-xr-x 1 doublech doublech 985953 Feb 27 21:00 spamd.log.14.gz shouldnt be hard to identify when this this an issue if i monitor disk usage. When its in this high speed logging loop, the CPU is also hitting pretty hard... so i'm not sure how much of that CPU is due to the actual log write, and how much is due to it being stuck in a loop. i can try adding that line to Logging.pm and see what happens. i'll post more if i can catch it in progress. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
