On Fri, 2003-01-10 at 17:11, Triebwasser, Mark wrote:
> Has anyone had issues where newsx gets a "Too many open files" error?  I'm
> running newsx on a i386 FreeBSD machine.
> 
> >inserting newsx path
> >newsx: can't open incoming spool
> "/usr/local/news/spool/incoming/.tmp.gig2.33553": Too many open files
> >transfer interrupted
> >latest article was 5080555
> >no spool to flush
> >state: pull: cleanup
> >no news is good news!
> >state: aborting server
> >->QUIT
> ><- 205 GoodBye
> >unlocked: /usr/local/news/run/L.33553
> >unlocked: /usr/local/news/run/LOCK.newsx.gig2
> >unlocked: /usr/local/news/run/LOCK.gig2
> 
> Should I be changing the shell's limit or should I be doing a kernel
> rebuild?

Good question.

Does this happen every time, or only in heavy load situations?

Although I do not know FreeBSD very well, basically there is usually two
errors for too many open files. EMFILE is open count per process, and
ENFILE is system wide.

I think Posix uses "Too many open files in system" for ENFILE, which
would indicate that you have an EMFILE situation.

I don't *think* that newsx itself should have very many files open at
any one time. It *should* close its files after use - and I've never
heard of such problems. 

So it is a bit of a puzzle.

I think the best procedure is to run
newsx under 'strace' to see what really happens. Just do:

        $ strace 2>out newsx ...

You may then grep for 'open' and 'close', or you can email me the 'out'
file and I can have a look for anything suspicious.

What is your per-process limit set to, anyway?

Egil
-- 
Email: [EMAIL PROTECTED]  
Voice/videophone: +47 22523641 Voice: +47 92022780 Fax: +47 22525899
Mail:  Egil Kvaleberg, Husebybakken 14A, 0379 Oslo, Norway
Home:  http://www.kvaleberg.com/
-----------------------------------------------------------------------
This message has been sent to you because you are subcribed to the mailing
list [EMAIL PROTECTED] To remove yourself from this lists, send an email to
[EMAIL PROTECTED] containing "unsubscribe newsx <your_email_address>"
in the message body.

Reply via email to