diff options
author | Rebecca Cran <brucec@FreeBSD.org> | 2010-09-11 10:49:56 +0000 |
---|---|---|
committer | Rebecca Cran <brucec@FreeBSD.org> | 2010-09-11 10:49:56 +0000 |
commit | 5512804bb8fe7606fcc50062327c11622c79b6ca (patch) | |
tree | 9b0dbb739b35e3d9e69dd5c1d72fd4a2c349c473 /secure | |
parent | dba0ac63fbdc2da1410a659b6dd2d917a7ad1d23 (diff) | |
download | src-test2-5512804bb8fe7606fcc50062327c11622c79b6ca.tar.gz src-test2-5512804bb8fe7606fcc50062327c11622c79b6ca.zip |
Notes
Diffstat (limited to 'secure')
-rw-r--r-- | secure/lib/libcrypto/man/BIO_s_bio.3 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/secure/lib/libcrypto/man/BIO_s_bio.3 b/secure/lib/libcrypto/man/BIO_s_bio.3 index 956f3f6d13e3..34345d112a8f 100644 --- a/secure/lib/libcrypto/man/BIO_s_bio.3 +++ b/secure/lib/libcrypto/man/BIO_s_bio.3 @@ -317,7 +317,7 @@ find out, how many bytes must be written into the buffer before the .IX Header "WARNING" As the data is buffered, \fISSL_operation()\fR may return with a \s-1ERROR_SSL_WANT_READ\s0 condition, but there is still data in the write buffer. An application must -not rely on the error value of \fISSL_operation()\fR but must ensure that the +not rely on the error value of \fISSL_operation()\fR but must assure that the write buffer is always flushed first. Otherwise a deadlock may occur as the peer might be waiting for the data before being able to continue. .SH "SEE ALSO" |