On Tuesday 31 March 2015, Tim van der Molen wrote:
> - Correct title.
> - tls_accept_socket() also may return TLS_{READ,WRITE}_AGAIN.
I've committed a slightly different version of this and fixed the title -
thanks for the diff.
> Index: tls_init.3
> ===================================================================
> RCS file: /cvs/src/lib/libtls/tls_init.3,v
> retrieving revision 1.18
> diff -u -r1.18 tls_init.3
> --- tls_init.3 22 Feb 2015 15:09:54 -0000 1.18
> +++ tls_init.3 30 Mar 2015 16:36:47 -0000
> @@ -15,7 +15,7 @@
> .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
> .\"
> .Dd $Mdocdate: February 22 2015 $
> -.Dt TLS 3
> +.Dt TLS_INIT 3
> .Os
> .Sh NAME
> .Nm tls_init ,
> @@ -391,9 +391,10 @@
> Functions that return a pointer will return NULL on error.
> .Pp
> The
> -.Fn tls_read
> -and
> +.Fn tls_read ,
> .Fn tls_write
> +and
> +.Fn tls_accept_socket
> functions and the
> .Fn tls_connect
> family of functions have two special return values.
--
"Action without study is fatal. Study without action is futile."
-- Mary Ritter Beard
