[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Corrupted messages...
From: |
Dan Nelson |
Subject: |
Re: Corrupted messages... |
Date: |
Mon, 9 Jun 2003 16:53:18 -0500 |
User-agent: |
Mutt/1.5.4i |
In the last episode (Jun 09), Chuck Yerkes said:
> Quoting Dan Nelson (address@hidden):
> > Most likely the problem is either spamass-milter or libmilter.
> > both spamd and sendmail should fork new copies of themselves for
> > each message, so they shouldn't cause parts of one message to end
> > up in another one.
> ...
> > If you can stand it, try running spamass-milter with watchmalloc,
> > using either MALLOC_DEBUG=WATCH (slow) or MALLOC_DEBUG=RW (very
> > slow), which should cause a coredump on bad memory accesses. I've
> > run spamass-milter under dmalloc and valgrind on my systems with no
> > problems, so if there is a problem it may be OS-dependant.
>
> Speed isn't the problem as much as watching logs of maybe 500 msgs/hr.
>
> This is a build option for gcc?
It's a shared library that comes with Solaris, so all you have to do is
set LD_PRELOAD=watchmalloc.so.1 and MALLOC_DEBUG to one of the above
values before starting spamass-milter. See the watchmalloc manpage for
more info.
--
Dan Nelson
address@hidden
- Corrupted messages..., Chuck Yerkes, 2003/06/09
- Corrupted messages..., Ken Gribble, 2003/06/09
- Re: Corrupted messages..., Chuck Yerkes, 2003/06/09
- Re: Corrupted messages..., Dan Nelson, 2003/06/09
- watchmalloc (Re: Corrupted messages...), Chuck Yerkes, 2003/06/10
- Re: watchmalloc (Re: Corrupted messages...), Dan Nelson, 2003/06/10
- Re: watchmalloc (Re: Corrupted messages...), Chuck Yerkes, 2003/06/12
- None, Valentin Chopov, 2003/06/12
- Re: None, Dan Nelson, 2003/06/12
- New options, Valentin Chopov, 2003/06/13
- Re: New options, Dan Nelson, 2003/06/13