Excellent, I'll give this a try. Thanks,
Alberto On Mon, 2006-02-13 at 10:51 +0530, Gayathri Sundar wrote: > Probably you can call the following > > iRet = SSL_get_shutdown(pSSL); > if(iRet >= 0) SSL_shutdown(pSSL); > > This is because, SSL_shutdown writes data on the wire, > i.e the closure alerts..and if a FIN was received meanwhile, > you will catch a SIGPIPE..this piece of code, actually > saves me from this.. > > Thanks > --G3 > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Alberto Alonso > Sent: Sunday, February 12, 2006 2:08 PM > To: openssl-users@openssl.org > Subject: SSL_shutdown and SIGPIPE > > > I am getting SIGPIPE signals under Linux when calling > on SSL_shutdown and the remote is gone. > > Basically, the remote end terminates the connection abruptly, > then the server finishes doing whatever is doing and issues > a SSL_shutdown on the ssl structure that used to handle the > connection. This generates a SIGPIPE on the server. > > Is there anything I should be checking for before calling > SSL_shutdown to make sure the connection is still OK? > > > Thanks, > > Alberto -- Alberto Alonso Global Gate Systems LLC. (512) 351-7233 http://www.ggsys.net Hardware, consulting, sysadmin, monitoring and remote backups ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
