Milter-greylist

Im with the rest here re use of sockets and the like eating up your limit. 
Frankly, I think 256 is a bit low for this user, and would probably set it to 
512 or 1024. It isnt a generic user after all, and has to support up to ~260 
descriptors open at once. 

On Saturday 25 November 2006 11:03 am, shuttlebox wrote:
> On 11/24/06, Oliver Fromme <olli@...> wrote:
> >  File descriptors are not only used for plain files, but
> >  also for network connections and other things.  You can
> >  view the current descriptors with the "lsof" tool.
> >
> >  On my personal machine (which has very low traffic), the
> >  milter-greylist process currently uses 21 descriptors.
>
> Ok, thanks. I will install lsof.
>
> >  I think 1024 should be plenty.  As I said above, use the
> >  "lsof" tool to check how many descriptors are in use by
> >  the process.
> >
> >  Actually, looking at the error message again, it might be
> >  the case that the mkstemp() function opens a large number
> >  of files while trying to find a unique filename.  If that's
> >  the case, then the implementation of mkstemp() of your OS
> >  (which you still didn't mention) is broken.
>
> Sorry, it's Solaris 9. But it shouldn't be hard to find a unique
> filename in a directory containing only three files..?
>
> >  No, .profile is read only by login shells.  You should put
> >  the ulimit command inside the init.d script right before
> >  milter-greylist is started.  The limits are inherited by
> >  child processes.
>
> I tried both :-) and it still crashes all the time.
>
> >  Depends on your OS.  When you use the "lsof" utility (see
> >  above) and it reports more than 256 descriptors in use for
> >  your milter-greylist process, then it obviously uses the
> >  new limit.  ;-)
>
> I'll install lsof first thing Monday morning and see what it tells me.
> Thanks again.