freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: Brian Bruns <camber AT umcc.ais.org>
- To: TDS Development Group <freetds AT franklin.oit.unc.edu>
- Subject: Re: patch for SIGPIPE in tds_write_packet
- Date: Wed, 26 Jan 2000 19:16:19 -0500 (EST)
On Thu, 27 Jan 2000, James Cameron wrote:
> Geoff Winkless wrote:
> > [...] whether disconnecting the client from the server at the server
> > end would cause a SIGPIPE (as it does in write()) or if it merely
> > causes read() to fail with an error returned.
>
> It causes read() to return zero. I've not heard of the possibility of
> SIGPIPE. None of my (other) code has seen that.
>
> It is difficult to discriminate between an empty input queue with
> non-blocking I/O enabled and a terminated connection.
>
fortunately we use blocking I/O, however the code does need to check for
EINTR in the read routines...I guess I just never got around to it :-)
> > I suppose I could write some test code, I was just wondering if anyone
> > knew the answer already.
>
> Fun, eh?
>
Always!
Brian
-
patch for SIGPIPE in tds_write_packet,
Geoff Winkless, 01/25/2000
- <Possible follow-up(s)>
- Re: patch for SIGPIPE in tds_write_packet, Mark Schaal, 01/25/2000
- Re: patch for SIGPIPE in tds_write_packet, Dave Blob, 01/25/2000
- Re: patch for SIGPIPE in tds_write_packet, Geoff Winkless, 01/26/2000
- Re: patch for SIGPIPE in tds_write_packet, Mark Schaal, 01/26/2000
- Re: patch for SIGPIPE in tds_write_packet, James Cameron, 01/26/2000
- Re: patch for SIGPIPE in tds_write_packet, Brian Bruns, 01/26/2000
- Re: patch for SIGPIPE in tds_write_packet, Brian Bruns, 01/26/2000
Archive powered by MHonArc 2.6.24.