On Thu, 16 Jun 2011 09:35:03 -0700
Mark Dadgar <[email protected]> wrote:

Hello Mark,


> On Jun 16, 2011, at 9:26 AM, Stevan Bajić wrote:
> >> /etc/cron.daily/dspam
> >> /usr/bin/dspam_maintenance: line 530: 23521 Floating point exception
> >> ${DSPAM_BIN_DIR}/cssclean "${name}" > /dev/null 2>&1
> >> 
> > aggrr... the Hash driver has serious issues and needs a major 
> > rework/recoding.
> > 
> > 
> >> i'm use storage hash_drv.
> >> .css and .sig files stored in /var/spool/dspam/
> >> 
> >> How to fix this issue ?
> >> Same error i got on few other servers, also Debian Squeeze.
> >> 
> > Has nothing to do with Debian. The problem is that the Hash driver is not 
> > 32/64 Bit safe nor is it little/big endian safe.
> > 
> > If no one is going to invest major coding time behind the Hash driver then 
> > I will probably go after 3.9.1 to look closer into the whole problem with 
> > the Hash driver.
> 
> Maybe it's time to deprecate the hash driver?
>
NO! The Hash driver has good reasons to be there.


> It's pretty hard to run a server these days without needing MySQL or Postgres 
> for something anyway.
> 
True but not every one is running DSPAM in a server environment and beside that 
the Hash driver is one of the fastest storage driver in DSPAM. Why removing it 
when we can fix it?


> Just a thought to reducing the dspam support workload ... 
> 
Well... one strong point of DSPAM is that flexible and removing stuff will 
remove one of the strong selling points of DSPAM.


> - Mark
> -----
> [email protected]
> 
-- 
Kind Regards from Switzerland,

Stevan Bajić

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user

Reply via email to