Milter-greylist

On 11/24/06, Oliver Fromme <olli@...> wrote:
>  shuttlebox wrote:
>   > Nov 24 11:20:04 viola milter-greylist: [ID 653641 mail.error]
>   > mkstemp("/var/milter-greylist/greylist.db-XX.caqCI") failed: Too many
>   > open files
>
>  There's your problen:  "Too many open files".
>  You need to increase the limit on file descriptors.
>  (The exact way to do that depends on your OS and shell.)
>
>  Most shells have a "ulimit" or "limit" built-in command,
>  some systems also have /usr/bin/limits (see the manual
>  pages).  They can be used to lift the soft limit on
>  file descriptors, among other things.
>
>  If you need to increase the hard limit of your OS, well,
>  that's OS-dependant.  For example, FreeBSD has a sysctl
>  variable (kern.maxfiles and kern.maxfilesperproc), and
>  the limits can be tuned per login-class in /etc/login.conf
>  (for system daemons like milter-greylist the login class
>  would be "daemon", unless a different one is created.)

But the limit for open files is 256 for both root and the milter user,
I can't see how the milter user needs more than that when I can't find
more than three files and none of them are actively open. Does the
process use a lot of temporary files outside the milter directory?

I raised the ulimit to 1024 files before I wrote the first mail and it
kept crashing. How can I know how many files I need? How many do you
use?

Another thing, the init.d script starts milter-greylist as root and
then drops privileges to the milter user I assume, where do I put the
ulimit change then to make it count? I made /var/milter-greylist/ the
home directory of the milter user and created a .profile containing
"ulimit -n 1024" there. Is that the correct way to make
milter-greylist pick it up? Can I check that it uses the new limit?

Sorry for all the questions but I have a lot of load problems when
greylisting doesn't work. Thanks for the help. :-)

-- 
/peter