Milter-greylist

On Tue, Sep 05, 2006 at 03:25:38PM +0200, Oliver Fromme wrote:
> It usually only happens when there's a bug in a program,
> such as when the programmer started a timer (e.g. using
> setitimer()) but forgot to install a handler for SIGALRM.
> Or the handler got lost or reset to the default, which
> might happen when using signal() on systems that implement
> the SystemV semantics (as opposed to BSD semantics), such
> as Solaris.  You should better always use sigaction()
> instead of signal() to avoid that problem.
> 
> Disclaimer:  I haven't looked at the milter-greylist code,
> so I don't know if any of the above applies.  It was just
> a generic explanation.

milter-greylist does not use timers, neither it uses signals.
Perhaps a problem in libmilter? 

-- 
Emmanuel Dreyfus
manu@...