Steve skrev, on 23-12-2007 12:02:
[...]
I lied, it's still sigseving; back to 3.8.0 that doesn't. As I just
wrote in a post mainly to Steve, "I can't honestly see what
non-descriptive Gentoo patches can possibly do for FC6/RHELL5 where
dspam 3.8.0 is running well and stably, without memory leaks or
anything, for weeks at a time."
Sorry to say: Shit!
No need to be sorry, shit happens.
I have over here the possibility to run DSPAM on CentOS 5.1. Should I do that?
Up to you, ain' it? Works for me on RHEL5. I only work with Red Hat
systems, someoe once forced me to use Debian Sarge (wasn't allowed to
use Etch) and that was horrible.
What switches have you active in DSPAM?
Well, he offered cautiously, I have my own srpm for RHEL5, which was
written at the behest of Jonz.
How did you compile it?
See the above. It's available at my ftp site, which I've already given.
It should build on CentOS5, maybe not recognize the Release. It will
install to LFH directories, which you might not like.
Any thing other you can tell me in order to reproduce that issue on my end?
Just don't patch with any Gentoo patches ;)
Any message triggering that segmentation fault?
This was the line in my cron script that caused it:
/usr/bin/dspam --class=spam --source=error --deliver=spam --user $mail <
$misclass > /dev/null 2>&1
$mail is the shared group "leerlingen".
$misclass is the message.
This is what happened:
/etc/cron.hourly/dspam.cron:
/etc/cron.hourly/dspam.cron: line 14: 3620 Segmentation fault
/usr/bin/dspam --class=spam --source=error --deliver=spam --user $mail
<$misclass >/dev/null 2>&1
It don't happen with 3.8.0 on RHEL5 nor FC6.
Best,
--Tonni
--
Tony Earnshaw
Email: tonni at hetnet dot nl
