From: "Jose González" <jose.gonzalez@psa.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: socketpair - too many open files
Date: Thu, 05 Jan 2006 14:39:07 +0100 [thread overview]
Message-ID: <43BD217B.8030607@psa.es> (raw)
In-Reply-To: <1136467519.16358.19.camel@localhost.localdomain>
Alan Cox wrote:
>On Iau, 2006-01-05 at 13:21 +0100, Jose González wrote:
>
>
>>Hello.
>>I am programming an application that need to create over 300 threads.
>>Each thread calls socketpair function, but it returns EMFILE when it is
>>called 150 times. Which kernel parameter can I change to do it?
>>
>>
>
>Its a user space matter. See "ulimit -a" and find out how your
>distribution sets the default limits
>
>
>
>
I modified this limit (open files, ulimit -n), even I have modified it
in the kernel sources. I think that open file number isn't the problem.
Is there a limit in the open sockets?
prev parent reply other threads:[~2006-01-05 13:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 12:21 socketpair - too many open files Jose González
[not found] ` <1136467519.16358.19.camel@localhost.localdomain>
2006-01-05 13:39 ` Jose González [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BD217B.8030607@psa.es \
--to=jose.gonzalez@psa.es \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox