Bug#400301: [Pkg-dspam-misc] Bug#400301: dspam should not be run with hash drivers in daemon mode

[Daniel Kahn Gillmor]

On November 24, dkg-debian.org at fifthhorseman.net said:

> Yikes!  i wish i'd noticed that earlier.  Is it documented anywhere
> else that anyone knows?

in /usr/share/doc/dspam/README.gz, i just noticed that in one part it
claims the hash driver is threadsafe:

   Driver       Requirements
   -------------------------------------------------------------------------
 T mysql_drv:   MySQL client libraries      (and a server to connect to) 
   ora_drv:     Oracle Call Interface       (and a server to connect to)
 T pgsql_drv:   PostgreSQL client libraries (and a server to connect to)
   sqlite_drv:  SQLite v2.7.7 or above 
   sqlite3_drv: SQLite v3.x
*T hash_drv:    None (Self-Contained Hash-Based Driver)

   Legend:
    * Default storage driver
    T Thread-safe (Required for running DSPAM in server daemon mode)

but then later it goes on to claim the opposite:

 The DSPAM agent can be compiled with client/server support by configuring
  with --enable-daemon. You will need to use a multithread-safe storage driver
  (presently mysql_drv and pgsql_drv are supported). Once you have compiled

hrm...

Does anyone with more experience with fcntl() locking want to weigh in
on the thread-safety of the hash_drv?  I've asked on the dspam lists,
and if Jonathan responds, i'll forward his response to this bug.

	--dkg