All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khalid Aziz <khalid@fc.hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Alessandro Baretta <alex@baretta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Inadequate documentation: sockets
Date: Tue, 06 Mar 2001 12:05:04 -0500	[thread overview]
Message-ID: <3AA518C0.A0194586@fc.hp.com> (raw)
In-Reply-To: <E14aMHj-0001E1-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > =46inally I'm left with my original problem: how am I supposed to
> > detect a close or a shutdown from the peer? Once again, I thank in
> > advance anyone who will lend me a hand by explaining this to me or
> > by addressing me to more adequate documentation.
> 
> By an EOF on read or getting SIGPIPE/EPIPE on a write. You might want to pick
> up a book on the subject of network programming. There are some very nice ones
> around

As Alan already pointed out, a book on network programming can answer
these questions. I would recommend "UNIX Network Programming, Volume 1:
Networking APIs - Sockets and XTI" by W. Richard Stevens.

-- 
Khalid

====================================================================
Khalid Aziz                             Linux Development Laboratory
(970)898-9214                                        Hewlett-Packard
khalid@fc.hp.com                                    Fort Collins, CO

  reply	other threads:[~2001-03-06 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 18:14 Inadequate documentation: sockets Alessandro Baretta
2001-03-06 18:34 ` Alan Cox
2001-03-06 17:05   ` Khalid Aziz [this message]
2001-03-06 19:26 ` kuznet
2001-03-06 19:30   ` Alessandro Baretta

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=3AA518C0.A0194586@fc.hp.com \
    --to=khalid@fc.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alex@baretta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.