[Mimedefang] SA doesn't remove bayes lockfile when recieving TERM signal?

David F. Skoll dfs at roaringpenguin.com
Sun Oct 26 12:23:20 EST 2003


On Sat, 25 Oct 2003, Dave Ellenberger wrote:

> Now the memory limit was reached when running SA. The child is beeing
> killed and forked again, the filter is temp failing - no biggie (since
> it doesn't happen that often). A new mail is incoming - it's a ham mail,
> SA want's to learn it, but the bayes database is still locked.

> Shoudn't spamassassin (when recieving a TERM signel) remove the bayes
> lockfile before dying? Is this a SA version 2.60 bug?

When a slave dies from lack of memory, it doesn't get a TERM signal.
Perl just calls exit(1), so signal handlers will not run.

> BTW: I don't have much idea about file locking. But why is SA using lock
> file locking instead of flock or fcntl?

Because of faulty design, IMO.  On the other hand, lock files work even
on marginal systems and over NFS, whereas flock/fcntl might not be
as portable or reliable.

Regards,

David.



More information about the MIMEDefang mailing list