From: Markus Wenke <M.Wenke@web.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: to many sockets ?
Date: Fri, 06 Oct 2006 07:32:36 +0200 [thread overview]
Message-ID: <4525EA74.7030701@web.de> (raw)
In-Reply-To: <1160083851.1607.22.camel@localhost.localdomain>
Alan Cox schrieb:
> Ar Iau, 2006-10-05 am 09:14 +0200, ysgrifennodd Markus Wenke:
>
>> and the oom-killer kills my application at the same time (at 140000
>> connections).
>>
>> I can not see in the messages that the system is out of memory,
>> there is also no swap space used
>>
>> You can download my /var/log/messages at
>> http://hemaho.mine.nu/~biber/messages
>>
>> May you can give me a hint which line/value in the log shows me,
>> that the system is out of memory?
>>
>
> That sounds like a bug. What kernel are you using ?
>
I use 2.6.18 with this config:: http://hemaho.mine.nu/~biber/.config
Markus
prev parent reply other threads:[~2006-10-06 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 15:03 to many sockets ? Markus Wenke
2006-10-04 16:33 ` Alan Cox
2006-10-05 7:14 ` Markus Wenke
2006-10-05 7:58 ` Eric Dumazet
2006-10-05 8:20 ` Markus Wenke
2006-10-05 8:45 ` Eric Dumazet
2006-10-05 9:16 ` Markus Wenke
2006-10-05 21:30 ` Alan Cox
2006-10-06 5:32 ` Markus Wenke [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=4525EA74.7030701@web.de \
--to=m.wenke@web.de \
--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