- djm@cvs.openbsd.org 2010/12/08 04:02:47

[ssh_config.5 sshd_config.5]
     explain that IPQoS arguments are separated by whitespace; iirc requested
     by jmc@ a while back
This commit is contained in:
Damien Miller 2010-12-26 14:26:45 +11:00
parent bf5fec1bc6
commit 928362dc03
3 changed files with 13 additions and 6 deletions

View File

@ -1,3 +1,10 @@
20101226
- (dtucker) OpenBSD CVS Sync
- djm@cvs.openbsd.org 2010/12/08 04:02:47
[ssh_config.5 sshd_config.5]
explain that IPQoS arguments are separated by whitespace; iirc requested
by jmc@ a while back
20101205
- (dtucker) openbsd-compat/openssl-compat.c] remove sleep leftover from
debugging. Spotted by djm.

View File

@ -33,8 +33,8 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $OpenBSD: ssh_config.5,v 1.145 2010/11/29 23:45:51 djm Exp $
.Dd $Mdocdate: November 29 2010 $
.\" $OpenBSD: ssh_config.5,v 1.146 2010/12/08 04:02:47 djm Exp $
.Dd $Mdocdate: December 8 2010 $
.Dt SSH_CONFIG 5
.Os
.Sh NAME
@ -657,7 +657,7 @@ Accepted values are
.Dq throughput ,
.Dq reliability ,
or a numeric value.
This option may take one or two arguments.
This option may take one or two arguments, separated by whitespace.
If one argument is specified, it is used as the packet class unconditionally.
If two values are specified, the first is automatically selected for
interactive sessions and the second for non-interactive sessions.

View File

@ -33,8 +33,8 @@
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.\" $OpenBSD: sshd_config.5,v 1.130 2010/11/18 15:01:00 jmc Exp $
.Dd $Mdocdate: November 18 2010 $
.\" $OpenBSD: sshd_config.5,v 1.131 2010/12/08 04:02:47 djm Exp $
.Dd $Mdocdate: December 8 2010 $
.Dt SSHD_CONFIG 5
.Os
.Sh NAME
@ -540,7 +540,7 @@ Accepted values are
.Dq throughput ,
.Dq reliability ,
or a numeric value.
This option may take one or two arguments.
This option may take one or two arguments, separated by whitespace.
If one argument is specified, it is used as the packet class unconditionally.
If two values are specified, the first is automatically selected for
interactive sessions and the second for non-interactive sessions.