diff options
author | espie <> | 2014-03-18 17:46:04 +0000 |
---|---|---|
committer | espie <> | 2014-03-18 17:46:04 +0000 |
commit | 26550da6583df81675b762ecb111b695c4faa098 (patch) | |
tree | f20442b45f29c41e8fbe121686e5ec91b50f5440 /src/lib/libssl/src/doc/ssl/SSL_shutdown.pod | |
parent | c74788490dc35ac7f27276f94af13e1e707b039c (diff) | |
download | openbsd-26550da6583df81675b762ecb111b695c4faa098.tar.gz openbsd-26550da6583df81675b762ecb111b695c4faa098.tar.bz2 openbsd-26550da6583df81675b762ecb111b695c4faa098.zip |
prepare manpages for new perl.
Note that I missed two of these in the diff shown initially, thx
to the atrocious Makefile rule...
okay millert@, sthen@, basically
Diffstat (limited to 'src/lib/libssl/src/doc/ssl/SSL_shutdown.pod')
-rw-r--r-- | src/lib/libssl/src/doc/ssl/SSL_shutdown.pod | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/lib/libssl/src/doc/ssl/SSL_shutdown.pod b/src/lib/libssl/src/doc/ssl/SSL_shutdown.pod index 89911acbca..69ad31e80b 100644 --- a/src/lib/libssl/src/doc/ssl/SSL_shutdown.pod +++ b/src/lib/libssl/src/doc/ssl/SSL_shutdown.pod | |||
@@ -92,19 +92,19 @@ The following return values can occur: | |||
92 | 92 | ||
93 | =over 4 | 93 | =over 4 |
94 | 94 | ||
95 | =item 1 | 95 | =item C<1> |
96 | 96 | ||
97 | The shutdown was successfully completed. The "close notify" alert was sent | 97 | The shutdown was successfully completed. The "close notify" alert was sent |
98 | and the peer's "close notify" alert was received. | 98 | and the peer's "close notify" alert was received. |
99 | 99 | ||
100 | =item 0 | 100 | =item C<0> |
101 | 101 | ||
102 | The shutdown is not yet finished. Call SSL_shutdown() for a second time, | 102 | The shutdown is not yet finished. Call SSL_shutdown() for a second time, |
103 | if a bidirectional shutdown shall be performed. | 103 | if a bidirectional shutdown shall be performed. |
104 | The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an | 104 | The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an |
105 | erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred. | 105 | erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred. |
106 | 106 | ||
107 | =item -1 | 107 | =item C<-1> |
108 | 108 | ||
109 | The shutdown was not successful because a fatal error occurred either | 109 | The shutdown was not successful because a fatal error occurred either |
110 | at the protocol level or a connection failure occurred. It can also occur if | 110 | at the protocol level or a connection failure occurred. It can also occur if |