Milter-greylist

On Wed, 5 Sep 2007, manu@... wrote:

> Date: Wed, 5 Sep 2007 14:42:02 +0200
> From: manu@...
> Reply-To: milter-greylist@yahoogroups.com
> To: milter-greylist@yahoogroups.com
> Subject: Re: [milter-greylist] Solaris crash on db dump (FIXED!)
> 
> Jeff A. Earickson <jaearick@...> wrote:
>
>> I am happy to report that my changes to the 4.0b1 code that I submitted
>> yesterday via makepatch have solved my issues with milter-greylist
>> crashing at db dump time.  Before the code change, it would crash at
>> least a dozen times a day; it has not crashed once since yesterday's
>> code change (15+ hours).  Many thanks to Mr. Herrb for finding that
>> Sun article.
>
> The change looks really minor, I wonder if this is safe for inclusion in
> 4.0b2. Could the F flag be harmful to some Solaris setups? Or is the
> Solaris situation so bad that nobody can get milter-greylist working
> without that change?

IMHO, yes the situation is that bad.  Your code really is unstable without 
this change.  But....   The caveats here are:

    * You must be running Solaris 10.  There may be patches for Solaris 9
    and earlier, but I didn't see any reference to earlier releases in the
    Sun doc.

    * You must have the following patches installed if your version of S10
    is less than the release of July 2007 (which I haven't seen yet):

    SPARC platform:

        * 125100-04 Kernel Update Patch
        * 120473-05 libc nss ldap PAM zfs Patch
        * 125800-01 Fault Manager Patch

    x86/x64 platform:

        * 125101-04 Kernel Update Patch
        * 120037-15 libc nss ldap PAM zfs Patch
        * 125801-01 Fault Manager Patch

    * You must raise the file descriptor limit in the parent process/shell
    before launching milter-greylist via "ulimit -n".  I have attached my
    /etc/init.d script as an example.

I did take a look at the runtime option in the doc instead of the 
programming option.  I does work, but it seemed kludgy to me.  Since
your code "follows the rules" regarding the use of FILE, the use of "F"
was a quick fix for me.  You may not be happy cluttering up your code
with OS-specific ifdefs.

Probably the real solution is to get the Makefile to just automatically
build a 64-bit application for Solaris.  I couldn't quickly figure this
out; school is just starting and I don't have a lot of spare time right
now.

>
> In the first case, we should probably make this available as a configure
> option, disabled by default.

Words of warning about this problem in the README are always a good thing.

Jeff Earickson
Colby College