From: Steve Whitehouse <steve@gw.chygwyn.com>
To: chris@scary.beasts.org (Chris Evans)
Cc: linux-kernel@vger.kernel.org
Subject: Re: SO_RCVTIMEO, SO_SNDTIMEO
Date: Tue, 13 Feb 2001 10:19:38 +0000 (GMT) [thread overview]
Message-ID: <200102131019.KAA21847@gw.chygwyn.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0102130035550.9858-100000@ferret.lmh.ox.ac.uk> from "Chris Evans" at Feb 13, 2001 12:38:16 AM
Hi,
They are the maximum amount of time that a send or receive call will
block for. The standard socket error returns apply, so if data has
been sent or received, then the return value will be the amount of
data transferred; if no data has been transferred and the timeout
has been reached then -1 is returned with errno=EAGAIN just as if the socket
was specified to be nonblocking. If the timeout is set to zero (the default)
then the operation will never timeout.
Steve.
>
>
> Hi,
>
> I notice the entities in the subject line have appeared in Linux 2.4.
>
> What is their functional specification? I guess they trigger if no bytes
> are received/send within a consecutive period. How does the app get the
> error? -EPIPE for a blocking read/write? If so, does SIGPIPE
> get raised? Or is -ETIMEDOUT used? ...
>
> TIA,
> Chris
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://vger.kernel.org/lkml/
>
prev parent reply other threads:[~2001-02-13 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 0:38 Chris Evans
2001-02-13 10:19 ` Steve Whitehouse [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=200102131019.KAA21847@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=chris@scary.beasts.org \
--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®