BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

socket closing question

Subject: socket closing question
From: warlord at MIT.EDU (Derek Atkins)
Date: 03 May 2003 12:09:32 -0400
In-reply-to: <20030502174921.40bbcdaa.gaf@blu.org>
References: <20030502135337.GB7465@javalinux.net> <OF776E7832.BE4BD5D3-ON85256D1A.004E0A93-85256D1A.004E69C4@cashqe2.hq.castel.com> <20030502174921.40bbcdaa.gaf@blu.org>

Jerry Feldman <gaf at blu.org> writes:

> The write(2) function returns -1 with errno==EPIPE when the socket has
> been closed. 

Actually, some times you'll get a SIGPIPE in this case...
So you probably should be careful to block/handle that signal.

-derek
-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available

Follow-Ups:
- socket closing question
  - From: gaf at blu.org (Jerry Feldman)

References:
- socket closing question
  - From: nmeyers at javalinux.net (Nathan Meyers)
- socket closing question
  - From: FRamsay at castelhq.com (FRamsay at castelhq.com)
- socket closing question
  - From: gaf at blu.org (Jerry Feldman)

Prev by Date: Job: US-MA-Boston North-Linux Expert.htm
Next by Date: SCO Unix Intellectual Property Pedigree Chart
Previous by thread: socket closing question
Next by thread: socket closing question
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org