foundry27 : Post

Forum Topic - QNX 4.25 / TCP 5.10 Bad Pipe?: (2 Items)

View: as

Steve Higgs

02/21/2011 7:27 AM

post83347

It seems as if when opening a TCP connection non=blocking and the client responds with Connection Reset meaning that the
 service is not ready yet, the TCP 5.10 runtime raises the Bad Pipe signal. What is the correct recovery from this 
signal?

Sean Boudreau(deleted)

02/22/2011 9:01 AM

post83369

Re: QNX 4.25 / TCP 5.10 Bad Pipe?

Handle or ignore the signal.  The latter will cause the write to fail with EPIPE.

-seanb

----- Original Message -----
From: Steve Higgs [mailto:community-noreply@qnx.com]
Sent: Monday, February 21, 2011 07:27 AM
To: qnx4-community <post83347@community.qnx.com>
Subject: QNX 4.25 / TCP 5.10 Bad Pipe?

It seems as if when opening a TCP connection non=blocking and the client responds with Connection Reset meaning that the
 service is not ready yet, the TCP 5.10 runtime raises the Bad Pipe signal. What is the correct recovery from this 
signal?

_______________________________________________

QNX4 Community Support
http://community.qnx.com/sf/go/post83347

Return

The text you entered is not a valid object ID
More Information
Object IDs begin with an object prefix and end with a number. For example, if you enter
artf2345
the application will jump directly to an artifact with the ID artf2345. Some valid object prefixes are:
artf	for an artifact
doc	for a document
page	for a project page
topc	for a discussion topic
wiki	for a wiki page