[Mimedefang] MIMEDefang and SpamAssassin forking threads

Jon Rowlan jon.rowlan at sads.com
Sat May 3 04:56:16 EDT 2008


Hi All,

I am using MD and trying to use SA for spam management.

There appears to be a problem, under Debian at least, where a file
opened during SA is being closed by another thread of the MD
multiplexor.

My log shows :

May  2 20:45:17 britney mimedefang-multiplexor[19378]: Slave 0 stderr:
print() on closed filehandle LTMP at
/usr/share/perl5/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 146.

May  2 20:45:17 britney mimedefang-multiplexor[19378]: Slave 0 stderr:
stat() on closed filehandle LTMP at
/usr/share/perl5/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line 148.

May  2 20:45:17 britney mimedefang-multiplexor[19378]: Slave 0 stderr:
locker: safe_unlock: failed to create lock tmpfile
/var/spool/MIMEDefang/.spamassassin/auto-whitelist.lock.britney.sads.com
.19378 at /usr/share/perl5/Mail/SpamAssassin/Locker/UnixNFSSafe.pm line
149.

This was reported over a year ago by a Debian developer to the authors
of SA (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398831) and
it seems that they do not consider this a bug as they do not support
multi threaded use of their software.
(see https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5333)

Does anyone have any idea what I can do from MD perspective ... should I
perhaps not use a multi threaded install? Is this possible? Should I
tune the number of threads to one?

jON


 



More information about the MIMEDefang mailing list