mailscanner (Solaris 2.6) Could not open file

[Chang Kai Cheong]

Hi Kevin,

My Solaris got:

set rlim_fd_max = 4096

in /etc/system and I think 2048 (out of 4096) should be fairly good but
still it failed.  The strange thing is that the same error message keeps
going even after the restart of MailScanner.  I have to move the mqueue.in
away and create a new one in order to successfully start MailScanner and
make it work properly again (should it be a file descriptor problem??).  I
can re-start the MailScanner only if the mqueue.in is re-created and then
gradually moved back the queued messages.

Actually, my MailScanner has been running smoothly for over a year and got
this intermittent error since January 2004 (and I got the same version
running on Alpha Tru64 without problem).  I cannot find any clues in
truss output as well (only find a number of fstat/open/fcntl call to mail
messages and then rmdir of the incoming dir. before dying of child
mailscanner processes).  Any ideas?

Thanks for your input.
KC Chang

On Mon, 9 Feb 2004, Kevin Spicer wrote:

> On Mon, 2004-02-09 at 06:42, Chang Kai Cheong wrote:
> >
> >
> > Does anyone has similar experience to solve the problem?
> >
> I recommended once to someone that they should add ulimit -n unlimited
> to the init script, based on the fact I had a similar problem with a
> different program which that cured (I don't use Solaris for my mail
> servers).  I think that solved the problem for them.
> You can also tweak system wide limits in /etc/system, but that requires
> care (you can knacker the entire system) and a reboot.
>
>
>
>
> BMRB International
> http://www.bmrb.co.uk
> +44 (0)20 8566 5000
> _________________________________________________________________
> This message (and any attachment) is intended only for the
> recipient and may contain confidential and/or privileged
> material.  If you have received this in error, please contact the
> sender and delete this message immediately.  Disclosure, copying
> or other action taken in respect of this email or in
> reliance on it is prohibited.  BMRB International Limited
> accepts no liability in relation to any personal emails, or
> content of any email which does not directly relate to our
> business.
>