Hi DSPAM folks--
running dspam_clean with hash drivers on an account with 147 files in
its .sig directory (many of which are 14 days old or older), doesn't
actually remove any signature files.
This appears to also be true for the directories with 59236 files in
their .sig directory, which is pushing way beyond the limits of most
normal filesystems.
here's an excerpt of an ltrace right around when it tries to do this:
17945 _ds_match_attribute(0x804e348, 0x804ba9f, 0x804bab1, 6, 0x804f4e0)
= 0
17945 _ds_match_attribute(0x804e348, 0x804ba78, 0x804baa6, 6, 0x804f4e0)
= 0
17945 dspam_attach(0x804f7e8, 0, 0x804e6d8, 1, 0)
= 0
17945 nt_create(0, 0, -1, 0x804b668, 0x804f7e8)
= 0x8051040
17945 printf("Processing sigs; age: %d\n", 14)
= 25
17945 _ds_get_nextsignature(0x804f7e8, 14, -1, 0x804b668, 0x804f7e8)
= 0
17945 nt_destroy(0x8051040, 14, -1, 0x804b668, 0x804f7e8)
= 72
17945 printf("Processing probabilities; age: %"..., 90)
= 34
17945 ds_diction_create(196613, 90, 0x8051040, 0xb7fd4250, 0)
= 0x8050e30
it seems that ds_get_nextsignature isn't returning any signatures at
all.
and that's no surprise:
[0 [EMAIL PROTECTED] dspam-3.6.8]$ grep -A3 -B1 ds_get_nextsignature
src/hash_drv.c
struct _ds_storage_signature *
_ds_get_nextsignature (DSPAM_CTX * CTX)
{
return NULL;
}
[0 [EMAIL PROTECTED] dspam-3.6.8]$
It seems i'm not the only person with this problem, either:
http://unixcluster.dk/index.php?url=archives/7-Dspam-hash-trouble...-again..html
Is this just a stub function that was never implemented in the hash
driver? Should i be clearing these .sig directories by hand? Or am i
completely off-base, and this is actually out of dspam_clean's
purview? Or have i missed some documentation somewhere?
If you're running with hash drivers, what do your account signature
directories look like? Are they cleaned as recently as
PurgeSignatures in dspam.conf would suggest?
Thanks for any advice, corroboration, or suggestions,
--dkg
