Package: spamprobe
Severity: normal

I don't know if the original submitter ever solved their problem but I only
started testing SpamProbe today and managed to encounter deadlock behaviour
using the BDB back-end. It appears that the database managed to get itself
into a state where any spamprobe processing accessing it just blocks. Killing
the spamprobe processes and removing the lock file had no affect. Only deleting
the database was enough to fix it.

It's not clear whether this is a bug in SpamProbe or the database back end. If
it's the latter, maybe it's worth upgrading, just to see if it fixes the
problem. db4.6 is due to be removed from unstable anyway.

Francis


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-164.6.1.el5xen (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages spamprobe depends on:
ii  debconf [debconf-2.0]         1.5.28     Debian configuration management sy
ii  libc6                         2.10.2-2   GNU C Library: Shared libraries
ii  libdb4.6                      4.6.21-15  Berkeley v4.6 Database Libraries [
ii  libgcc1                       1:4.4.2-8  GCC support library
ii  libgif4                       4.1.6-8    library for GIF images (library)
ii  libjpeg62                     6b-15      The Independent JPEG Group's JPEG 
ii  libpng12-0                    1.2.41-1   PNG library - runtime
ii  libstdc++6                    4.4.2-8    The GNU Standard C++ Library v3

Versions of packages spamprobe recommends:
ii  procmail                      3.22-18    Versatile e-mail processor

spamprobe suggests no packages.

-- debconf information:
  spamprobe/db46_upgrade:



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to