The standard practice is that of ignoring SIGPIPE in all TCP servers. signal(SIGPIPE,SIG_IGN);
OpenSSL cannot help you here because the problem occurs at a lower level(TCP). I remember seeing this line in the ssh server source code as well. regards, Girish --- Alberto Alonso <[EMAIL PROTECTED]> wrote: > 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] > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
