Linux -Blue forest free software | Return to home page | Site Map | Search WWW | Contact Us |
Your current position : Homepage > Free Software > Technological exchanges >Application Programming


    

Blue Forest http://www.lslnet.com at 10:18 on June 6, 2006


Socket send in automatic withdrawal procedures at issue is how ah, ME

AIX system client

Serv send information, client information packets received after business disposed of sending back information (in the news serv sent immediately stopped serv end), found the client端 withdrew from the process, I track a bit, as follows : only the OK, OK1 not see, I do not know if you have encountered. how to run ah

Client端 :

Printf ( "ok\n");
Send (_gSockId, &ans_cz, sizeof (Ans_CZ_Pack), 0);
Printf ( "ok1\n");

Socket send in automatic withdrawal procedures at issue is how ah, ME

The signal could be received, to capture how I know

Socket send in automatic withdrawal procedures at issue is how ah, ME

Upstairs, it can be said that the detailed points, how to catch ah

Socket send in automatic withdrawal procedures at issue is how ah, ME

SIGPIPE signal capture what you
Signal (SIGPIPE, func);
Func is your signal capture function

Socket send in automatic withdrawal procedures at issue is how ah, ME

Sockid may be ineffective at this time, you can
Read some data to see if there is any readable and, if so, sockid have been to no avail.

Socket send in automatic withdrawal procedures at issue is how ah, ME

Is sigpipe. Do something for signal processing.

Socket send in automatic withdrawal procedures at issue is how ah, ME

Sigpipe allow withdraw from the process?
End Signal Processing not continue printf ( "ok1\n"); -

Socket send in automatic withdrawal procedures at issue is how ah, ME

Bars should be core document generation, starting to go from here



 Privacy Policy  Copyright © 1999-2000 LSLNET.COM. All rights reserved. Blue Forest website owners. E-mail : Webmaster@lslnet.com