public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <jesse@cats-chateau.net>
To: Krzysztof Halasa <khc@pm.waw.pl>, <linux-kernel@vger.kernel.org>
Subject: Re: select for UNIX sockets?
Date: Wed, 4 Jun 2003 06:55:47 -0500	[thread overview]
Message-ID: <03060406554700.28116@tabby> (raw)
In-Reply-To: <m3llwkauq5.fsf@defiant.pm.waw.pl>

On Monday 02 June 2003 19:08, Krzysztof Halasa wrote:
> Hi,
>
> Should something like this work correctly?
>
> while(1) {
>         FD_ZERO(&set);
>         FD_SET(fd, &set);
>         select(FD_SETSIZE, NULL, &set, NULL, NULL); <<<<<<< for writing
>
>         if (FD_ISSET(fd, &set))
>                 sendto(fd, &datagram, 1, 0, ...);
> }
>
> fd is a normal local datagram socket. It looks select() returns with
> "fd ready for write" and sendto() then blocks as the queue is full.
>
> I don't know if it's expected behaviour or just a not yet known bug.
> Of course, I have a more complete test program if needed.
>
> 2.4.21rc6, haven't tried any other version.
>
> strace shows:
>
> select(1024, NULL, [3], NULL, NULL)     = 1 (out [3])
> sendto(3, "\0", 1, 0, {sa_family=AF_UNIX, path="/tmp/tempUn"}, 13 <<<
> blocks

Could. There may be room for the buffer, but unless it is set to nonblock, 
you may have a stream open to another host that may not accept the data (busy,
network congestion...) With the required acks, the return may (should?) be
delayed until the ack arrives.

  parent reply	other threads:[~2003-06-04 11:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03  0:08 select for UNIX sockets? Krzysztof Halasa
2003-06-03 14:51 ` Alan Cox
2003-06-04 23:27   ` Krzysztof Halasa
2003-06-05 13:17     ` Krzysztof Halasa
2003-06-04 11:55 ` Jesse Pollard [this message]
2003-06-04 12:42   ` Krzysztof Halasa
  -- strict thread matches above, loose matches on Subject: below --
2003-06-04 12:19 Petr Vandrovec
2003-06-06  0:28 ` Valdis.Kletnieks
2003-06-06  0:38   ` Petr Vandrovec
2003-06-06 12:20 MarKol
2003-06-07  0:14 ` David Schwartz
2003-06-08  0:04   ` Krzysztof Halasa
2003-06-09  3:11     ` David Schwartz
2003-06-09 17:18       ` Krzysztof Halasa
2003-06-09 17:55         ` David Schwartz
2003-06-09 22:24           ` Krzysztof Halasa
2003-06-10 13:34             ` Timothy Miller
2003-06-10 13:52               ` Richard B. Johnson
2003-06-10 14:21               ` Krzysztof Halasa
2003-06-10 19:04                 ` Jesse Pollard
2003-06-11 21:55                   ` Krzysztof Halasa
2003-06-11 22:50                     ` David Schwartz
2003-06-11 12:51                 ` Edgar Toernig
2003-06-10 21:40             ` David Schwartz
2003-06-11 22:04               ` Krzysztof Halasa
2003-06-09 23:45         ` James Stevenson
2003-06-08  4:15   ` Chris Friesen
2003-06-09  3:05     ` David Schwartz
2003-06-09 16:46   ` MarKol
2003-06-09 17:05     ` David Schwartz

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=03060406554700.28116@tabby \
    --to=jesse@cats-chateau.net \
    --cc=khc@pm.waw.pl \
    --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