Milter-greylist

manu@... wrote:
 > A usual problem with Solaris boxen is the stream limit at 256 for 32 bit
 > applications. Is milter-greylist built as a 32 bit binary?

You don't need to make a 64bit binary in order to
get around that limit.  On recent Solaris versions
you can increase the current limit using ulimit on
the command line, or setrlimit() from within a
program (which is recommended if a program needs
that many).  In Solaris 10 you can use resource
limits, see the resource_controls(5) manual page.

In old Solaris releases you can increase the limits
globally via /etc/system.  For example, add these
lines:

set rlim_fd_max=8192
set rlim_fd_cur=1024

It sets the maximum ("hard") limit to 8192 and the
current ("soft") limit to 1024.  You need to reboot
for the change to take effect, because the kernel
reads /etc/system only upon reboot.  (Well, you
can also change the values with adb on a running
system, but that's somewhat dangerous.)

Furthermore, the application (milter-greylist) must
be compiled with a larger FD_SETSIZE if you need more
than 1024 file descriptors (the default is 1024 for
32bit apps).  It might be useful to add a configure
option for that to milter-greylist.

Maybe that hint should be added to milter-greylist's
README, because many Solaris users seem to stumble
across that problem.

Best regards
   Oliver


-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Gesch\ufffdftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M\ufffdn-
chen, HRB 125758,  Gesch\ufffdftsf\ufffdhrer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

"Python is an experiment in how much freedom programmers need.
Too much freedom and nobody can read another's code; too little
and expressiveness is endangered."
        -- Guido van Rossum