Print this page
4344 Minor typos in the 3nsl man pages
   1 '\" te
   2 .\"  Copyright 1994, The X/Open Company Ltd., All Rights Reserved. Portions Copyright 1989 AT&T. Portions Copyright (c) 1998, Sun Microsystems, Inc. , All Rights Reserved
   3 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
   4 .\" http://www.opengroup.org/bookstore/.
   5 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
   6 .\"  This notice shall appear on any product containing this material.
   7 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   9 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
  10 .TH T_BIND 3NSL "May 7, 1998"
  11 .SH NAME
  12 t_bind \- bind an address to a transport endpoint
  13 .SH SYNOPSIS
  14 .LP
  15 .nf
  16 #include <xti.h>
  17 
  18 
  19 
  20 
  21 \fBint\fR \fBt_bind\fR(\fBint\fR \fIfd\fR, \fBconst struct t_bind *\fR\fIreq\fR, \fBstruct t_bind *\fR\fIret\fR);
  22 .fi
  23 
  24 .SH DESCRIPTION
  25 .sp
  26 .LP
  27 This routine is part of the \fBXTI\fR interfaces that evolved from the
  28 \fBTLI\fR interfaces. \fBXTI\fR represents the future evolution of these
  29 interfaces. However, \fBTLI\fR interfaces are supported for compatibility. When
  30 using a \fBTLI\fR routine that has the same name as an \fBXTI\fR routine, the
  31 \fBtiuser.h\fRheader file must be used.  Refer to the  \fBTLI\fR
  32 \fBCOMPATIBILITY\fR section for a description of differences between the two
  33 interfaces.
  34 .sp
  35 .LP
  36 This function associates a protocol address with the transport endpoint
  37 specified by \fIfd\fR and activates that transport endpoint. In connection
  38 mode, the transport provider may begin enqueuing incoming connect indications,
  39 or servicing a connection request on the transport endpoint. In
  40 connectionless-mode, the transport user may send or receive data units through
  41 the transport endpoint.
  42 .sp
  43 .LP
  44 The \fIreq\fR and \fIret\fR arguments point to a \fBt_bind\fR structure
  45 containing the following members:
  46 .sp
  47 .in +2
  48 .nf
  49 struct netbuf   addr;
  50 unsigned        qlen;
  51 .fi


  93 bind to the transport endpoint and does not return that information to the
  94 user.
  95 .sp
  96 .LP
  97 The \fIqlen\fR field has meaning only when initializing a connection-mode
  98 service. It specifies the number of outstanding connection indications that the
  99 transport provider should support for the given transport endpoint. An
 100 outstanding connection indication is one that has been passed to the transport
 101 user by the transport provider but which has not been accepted or rejected. A
 102 value of \fIqlen\fR greater than zero is only meaningful when issued by a
 103 passive transport user that expects other users to call it. The value of
 104 \fIqlen\fR will be negotiated by the transport provider and may be changed if
 105 the transport provider cannot support the specified number of outstanding
 106 connection indications. However, this value of \fIqlen\fR will never be
 107 negotiated from a requested value greater than zero to zero. This is a
 108 requirement on transport providers; see \fBWARNINGS\fR below. On return, the
 109 \fIqlen\fR field in \fIret\fR will contain the negotiated value.
 110 .sp
 111 .LP
 112 If \fIfd\fR refers to a connection-mode service, this function allows more than
 113 one transport endpoint to be bound to the same protocol address.  but it is not
 114 possible to bind more than one protocol address to the same transport endpoint.
 115 However, the transport provider must also support this capability. If a user
 116 binds more than one transport endpoint to the same protocol address, only one
 117 endpoint can be used to listen for connection indications associated with that
 118 protocol address. In other words, only one \fBt_bind()\fR for a given protocol
 119 address may specify a value of \fIqlen\fR greater than zero. In this way, the
 120 transport provider can identify which transport endpoint should be notified of
 121 an incoming connection indication. If a user attempts to bind a protocol
 122 address to a second transport endpoint with a value of \fIqlen\fR greater than
 123 zero, \fBt_bind()\fR will return  -1 and set \fBt_errno\fR to \fBTADDRBUSY\fR.
 124 When a user accepts a connection on the transport endpoint that is being used
 125 as the listening endpoint, the bound protocol address will be found to be busy
 126 for the duration of the connection, until a \fBt_unbind\fR(3NSL) or
 127 \fBt_close\fR(3NSL) call has been issued. No other transport endpoints may be
 128 bound for listening on that same protocol address while that initial listening
 129 endpoint is active (in the data transfer phase or in the  \fBT_IDLE\fR state).
 130 This will prevent more than one transport endpoint bound to the same protocol
 131 address from accepting connection indications.
 132 .sp
 133 .LP


   1 '\" te
   2 .\"  Copyright 1994, The X/Open Company Ltd., All Rights Reserved. Portions Copyright 1989 AT&T. Portions Copyright (c) 1998, Sun Microsystems, Inc. , All Rights Reserved
   3 .\" Sun Microsystems, Inc. gratefully acknowledges The Open Group for permission to reproduce portions of its copyrighted documentation. Original documentation from The Open Group can be obtained online at
   4 .\" http://www.opengroup.org/bookstore/.
   5 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
   6 .\"  This notice shall appear on any product containing this material.
   7 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License").  You may not use this file except in compliance with the License.
   8 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.  See the License for the specific language governing permissions and limitations under the License.
   9 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE.  If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
  10 .TH T_BIND 3NSL "Dec 27, 2013"
  11 .SH NAME
  12 t_bind \- bind an address to a transport endpoint
  13 .SH SYNOPSIS
  14 .LP
  15 .nf
  16 #include <xti.h>
  17 
  18 
  19 
  20 
  21 \fBint\fR \fBt_bind\fR(\fBint\fR \fIfd\fR, \fBconst struct t_bind *\fR\fIreq\fR, \fBstruct t_bind *\fR\fIret\fR);
  22 .fi
  23 
  24 .SH DESCRIPTION
  25 .sp
  26 .LP
  27 This routine is part of the \fBXTI\fR interfaces that evolved from the
  28 \fBTLI\fR interfaces. \fBXTI\fR represents the future evolution of these
  29 interfaces. However, \fBTLI\fR interfaces are supported for compatibility. When
  30 using a \fBTLI\fR routine that has the same name as an \fBXTI\fR routine, the
  31 \fBtiuser.h\fR header file must be used.  Refer to the  \fBTLI\fR
  32 \fBCOMPATIBILITY\fR section for a description of differences between the two
  33 interfaces.
  34 .sp
  35 .LP
  36 This function associates a protocol address with the transport endpoint
  37 specified by \fIfd\fR and activates that transport endpoint. In connection
  38 mode, the transport provider may begin enqueuing incoming connect indications,
  39 or servicing a connection request on the transport endpoint. In
  40 connectionless-mode, the transport user may send or receive data units through
  41 the transport endpoint.
  42 .sp
  43 .LP
  44 The \fIreq\fR and \fIret\fR arguments point to a \fBt_bind\fR structure
  45 containing the following members:
  46 .sp
  47 .in +2
  48 .nf
  49 struct netbuf   addr;
  50 unsigned        qlen;
  51 .fi


  93 bind to the transport endpoint and does not return that information to the
  94 user.
  95 .sp
  96 .LP
  97 The \fIqlen\fR field has meaning only when initializing a connection-mode
  98 service. It specifies the number of outstanding connection indications that the
  99 transport provider should support for the given transport endpoint. An
 100 outstanding connection indication is one that has been passed to the transport
 101 user by the transport provider but which has not been accepted or rejected. A
 102 value of \fIqlen\fR greater than zero is only meaningful when issued by a
 103 passive transport user that expects other users to call it. The value of
 104 \fIqlen\fR will be negotiated by the transport provider and may be changed if
 105 the transport provider cannot support the specified number of outstanding
 106 connection indications. However, this value of \fIqlen\fR will never be
 107 negotiated from a requested value greater than zero to zero. This is a
 108 requirement on transport providers; see \fBWARNINGS\fR below. On return, the
 109 \fIqlen\fR field in \fIret\fR will contain the negotiated value.
 110 .sp
 111 .LP
 112 If \fIfd\fR refers to a connection-mode service, this function allows more than
 113 one transport endpoint to be bound to the same protocol address.  But it is not
 114 possible to bind more than one protocol address to the same transport endpoint.
 115 However, the transport provider must also support this capability. If a user
 116 binds more than one transport endpoint to the same protocol address, only one
 117 endpoint can be used to listen for connection indications associated with that
 118 protocol address. In other words, only one \fBt_bind()\fR for a given protocol
 119 address may specify a value of \fIqlen\fR greater than zero. In this way, the
 120 transport provider can identify which transport endpoint should be notified of
 121 an incoming connection indication. If a user attempts to bind a protocol
 122 address to a second transport endpoint with a value of \fIqlen\fR greater than
 123 zero, \fBt_bind()\fR will return  -1 and set \fBt_errno\fR to \fBTADDRBUSY\fR.
 124 When a user accepts a connection on the transport endpoint that is being used
 125 as the listening endpoint, the bound protocol address will be found to be busy
 126 for the duration of the connection, until a \fBt_unbind\fR(3NSL) or
 127 \fBt_close\fR(3NSL) call has been issued. No other transport endpoints may be
 128 bound for listening on that same protocol address while that initial listening
 129 endpoint is active (in the data transfer phase or in the  \fBT_IDLE\fR state).
 130 This will prevent more than one transport endpoint bound to the same protocol
 131 address from accepting connection indications.
 132 .sp
 133 .LP