From: Denis Perchine <dyp@perchine.com>
To: linux-kernel@vger.kernel.org
Subject: Problems with kernel-2.2.19-6.2.7 from RH update for 6.2
Date: Mon, 20 Aug 2001 01:01:18 +0700 [thread overview]
Message-ID: <20010819150344.AFC87204DB@mx.webmailstation.com> (raw)
Hello,
I see quite strange behavior of subj.
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 40
fcntl(40, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(40, F_SETFL, O_RDWR|O_NONBLOCK) = 0
setsockopt(40, SOL_SOCKET, SO_LINGER, [1], 8) = 0
connect(40, {sin_family=AF_INET, sin_port=htons(2030),
sin_addr=inet_addr("127.0.0.1")}}, 16) = -1 EINPROGRESS (Operation now in
progress)
select(41, NULL, [40], NULL, {180, 0}) = 1 (out [40], left {180, 0})
getsockopt(40, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
select(41, [40], NULL, NULL, {180, 0}) = 1 (in [40], left {175, 550000})
ioctl(4, FIONREAD, [0]) = 0
select(41, [40], NULL, NULL, {180, 0}) = 1 (in [40], left {180, 0})
recv(4, 0x806aa28, 1, 0x4000) = -1 EAGAIN (Resource temporarily
unavailable)
As far as you can see select say that socket is writable after connect. This
mean that connection is completed... But later before read we do select on
read, and get OK. But recv fails with EAGAIN. This situation is repeated
constantly. The program stucks in the loop trying to connect, but fails.
Any ideas what can this be?
Maybe comment from Alan, as RH employee?
As a side comment. Server is highly loaded. The program usually works well,
but if it happend once, it will repeat forever...
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
next reply other threads:[~2001-08-19 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 18:01 Denis Perchine [this message]
2001-08-20 2:11 ` Problems with kernel-2.2.19-6.2.7 from RH update for 6.2 Alexey Kuznetsov
2001-08-20 18:52 ` Denis Perchine
2001-08-22 0:53 ` Alexey Kuznetsov
2001-08-23 4:32 ` Denis Perchine
2001-08-23 16:29 ` kuznet
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=20010819150344.AFC87204DB@mx.webmailstation.com \
--to=dyp@perchine.com \
--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