From: "James Stevenson" <mistral@stev.org>
To: "Kevin Curtis" <kevin.curtis@farsite.co.uk>,
<linux-kernel@vger.kernel.org>
Subject: Re: Closing a socket
Date: Thu, 18 Jul 2002 19:01:28 +0100 [thread overview]
Message-ID: <001701c22e85$240635b0$0501a8c0@Stev.org> (raw)
In-Reply-To: <7C078C66B7752B438B88E11E5E20E72E0EF451@GENERAL.farsite.co.uk>
Hi
either use non-blocking sockets
or send a signal to the other process
to make it exit from the read.
> I have implemented a new socket address family and have noted that
> from a multi-threaded application, if a thread calls close(fd) while a
> second thread has a blocking read outstanding, the sockets release() is
not
> called. Is this correct? How can one unblock the read in order to do the
> close.
>
next prev parent reply other threads:[~2002-07-18 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 16:36 Kevin Curtis
2002-07-18 18:01 ` James Stevenson [this message]
2002-07-18 19:50 ` Maksim (Max) Krasnyanskiy
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='001701c22e85$240635b0$0501a8c0@Stev.org' \
--to=mistral@stev.org \
--cc=kevin.curtis@farsite.co.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
all inboxes | Powered by JetHome®