Milter-greylist

I agree fully,
If there was any SIMPLE (lets keep the milter daemon as simple as
possible) solution, I would vote for it. Current situation is not nice.
Either:
1. keep the old configuration in case error detection.
2. Bail out but SHOUT LOUDLY

Ondrej
Oliver Fromme wrote:
>
>
> Emmanuel Dreyfus wrote:
> > On Wed, Sep 24, 2008 at 07:24:52AM -0400, Greg Troxel wrote:
> > > I find milter-greylist's auto-rereading a bit aggressive, and think it
> > > might be better to just do that on SIGHUP like inetd and others.
> > > Then one could "/etc/rc.d/milter-greylist reload" or ".. check".
> >
> > We cannot: the milter API says libmilter takes care of signals.
>
> Just a small hint: Besides signals, there are other
> ways for inter-process communication. For example
> UNIX domain sockets, FIFOs, POSIX named semaphores
> or SysV semaphores. Another, very simple way would
> be to use an empty "flag file", which milter-greylist
> uses to check the mtime instead of the actual conf
> file.
>
> However, all of that doesn't solve the real problem:
> If the configuration file contains an error, milter-
> greylist will terminate.
>
> Best regards
> Oliver
>
> -- 
> Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
> Handelsregister: Registergericht Muenchen, HRA 74606, Gesch�ftsfuehrung:
> secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M�n-
> chen, HRB 125758, Gesch�ftsf�hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart
>
> FreeBSD-Dienstleistungen, -Produkte und mehr:
> http://www.secnetix.de/bsd <http://www.secnetix.de/bsd>
>
> "C++ is the only current language making COBOL look good."
> -- Bertrand Meyer
>
>