http://bugzilla.spamassassin.org/show_bug.cgi?id=3442
Summary: flock locking creates and doesn't clean up lock files
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: Libraries
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I was noticing that I have this perpetual bayes.lock file now that I've begun
dogfooding. The PID listed in the file no longer exists. If I remove it, and
do an "sa-learn -D --rebuild" I get:
debug: lock: 31408 created /home/felicity/.spamassassin/bayes.lock
debug: lock: 31408 trying to get lock on /home/felicity/.spamassassin/bayes
with
300 timeout
debug: lock: 31408 link to /home/felicity/.spamassassin/bayes.lock: link ok
[...]
debug: refresh: 31408 refresh /home/felicity/.spamassassin/bayes.lock
[...]
debug: bayes: files locked, now unlocking lock
but the bayes.lock file remains, and it has "31408" as the contents, so I know
it's the sa-learn process that did it.
I'm not familiar with the flock code, but I assume it flocks the DB file, not
the .lock file, which doesn't seem to be needed at all (it doesn't block new
write attempts to the DB, for instance...)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
