https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7138
Jeremy Chadwick <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Jeremy Chadwick <[email protected]> --- I've been seeing this problem for several years, and still see it to this day. Details: This problem also happens on BSD (i.e. non-Linux) systems. I run sa-update on a nightly basis via a periodic job on FreeBSD (read: cron job). If sa-update downloaded something successfully (exit code 0), sa-compile is then run. Then if sa-compile is successful (exit code 0), spamd is restarted. As described in this bug, after the sa-compile run, there are residual cruft files left over in /tmp. The filenames seem to be an mkstemp(3) template of /tmp/.spamassassin{PID}XXXXXX with "tmp" then appended to the resulting name. This is done several times, thus several files with different names reside. These cruft files contain what looks like perl code of complex regex matches (basically the contents are "use bytes; m{very complex regex}". However, sa-compile also does a mkdir /tmp/.spamassassin{PID}XXXXXX (and then "tmp" appended) as well, and actively uses that directory during its compile. It cleans up that directory (rm -fr) at the very end. sa-compile output shows this. Attached is my most recent sa-compile cron job run -- from today, 2017/11/19 -- which includes output of sa-compile, as well as a ls -ldT /tmp/.spamassassin* to show the residual cruft this program is leaving behind. There were no errors during this sa-compile, thus no indications die() conditions were triggered. I can't speak for others methodologies, but in my case, I've added detection of the problem, doing rm -f /tmp/.spamassassin*tmp after a successful sa-compile and only if there is are such cruft files left over. Possibly these wiles were intended to reside within the /tmp/.spamassassin{PID}XXXXXXtmp directory itself, thus when the rm -fr kicks in at the end, everything gets cleaned up? I don't know. The maintainers of SA should look into this. Two and a half years with no attention is disappointing. -- You are receiving this mail because: You are the assignee for the bug.
