Print this page
10067 Miscellaneous man page typos
Reviewed by: Robert Mustacchi <rm@joyent.com>
Reviewed by: Andy Fiddaman <andy@omniosce.org>
Reviewed by: Volker A. Brandt <vab@bb-c.de>

Split Close
Expand all
Collapse all
          --- old/usr/src/man/man3nsl/t_sndvudata.3nsl
          +++ new/usr/src/man/man3nsl/t_sndvudata.3nsl
↓ open down ↓ 52 lines elided ↑ open up ↑
  53   53  #include <xti.h>
  54   54  
  55   55  
  56   56  
  57   57  
  58   58  \fBint\fR \fBt_sndvudata\fR(\fBint\fR \fIfd\fR, \fBstruct t_unitdata *\fR\fIunitdata\fR, \fBstruct t_iovec  *\fR\fIiov\fR,
  59   59       \fBunsigned int\fR \fIiovcount\fR);
  60   60  .fi
  61   61  
  62   62  .SH DESCRIPTION
  63      -.sp
  64   63  .LP
  65   64  This function is used in connectionless mode to send a data unit to another
  66   65  transport user.  The argument  \fIfd\fR identifies the local transport endpoint
  67   66  through which data will be sent,  \fIiovcount\fR contains the number of
  68   67  non-contiguous  \fIudata\fR buffers and is limited to an implementation-defined
  69   68  value given by  \fBT_IOV_MAX\fR which is at least 16, and  \fIunitdata\fR
  70   69  points to a  \fBt_unitdata\fR structure containing the following members:
  71   70  .sp
  72   71  .in +2
  73   72  .nf
↓ open down ↓ 50 lines elided ↑ open up ↑
 124  123  If the amount of data specified in  \fIiov\fR\fB0\fR\fI\fR through \fIiov
 125  124  [iovcount-1]\fR exceeds the TSDU size as returned in the  \fItsdu\fR field of
 126  125  the  \fIinfo\fR argument of \fBt_open\fR(3NSL) or  \fBt_getinfo\fR(3NSL), or is
 127  126  zero and sending of zero octets is not supported by the underlying transport
 128  127  service, a \fBTBADDATA\fR error is generated.  If  \fBt_sndvudata()\fR is
 129  128  called before the destination user has activated its transport endpoint (see
 130  129  \fBt_bind\fR(3NSL)\|), the data unit may be discarded.
 131  130  .sp
 132  131  .LP
 133  132  If it is not possible for the transport provider to immediately detect the
 134      -conditions that cause the errors \fBTBADDADDR\fR and \fBTBADOPT\fR, these
      133 +conditions that cause the errors \fBTBADADDR\fR and \fBTBADOPT\fR, these
 135  134  errors will alternatively be returned by  \fBt_rcvuderr\fR(3NSL). An
 136  135  application must therefore be prepared to receive these errors in both of these
 137  136  ways.
 138  137  .SH RETURN VALUES
 139      -.sp
 140  138  .LP
 141  139  Upon successful completion, a value of  \fB0\fR is returned. Otherwise, a value
 142  140  of  -1 is returned and  \fBt_errno\fR is set to indicate an error.
 143  141  .SH VALID STATES
 144      -.sp
 145  142  .LP
 146  143  \fBT_IDLE\fR.
 147  144  .SH ERRORS
 148      -.sp
 149  145  .LP
 150  146  On failure,  \fBt_errno\fR is set to one of the following:
 151  147  .sp
 152  148  .ne 2
 153  149  .na
 154  150  \fB\fBTBADADDR\fR\fR
 155  151  .ad
 156  152  .RS 15n
 157  153  The specified protocol address was in an incorrect format or contained illegal
 158  154  information.
↓ open down ↓ 93 lines elided ↑ open up ↑
 252  248  .sp
 253  249  .ne 2
 254  250  .na
 255  251  \fB\fBTSYSERR\fR\fR
 256  252  .ad
 257  253  .RS 15n
 258  254  A system error has occurred during execution of this function.
 259  255  .RE
 260  256  
 261  257  .SH TLI COMPATIBILITY
 262      -.sp
 263  258  .LP
 264  259  In the \fBTLI\fR interface definition, no counterpart of this routine was
 265  260  defined.
 266  261  .SH ATTRIBUTES
 267      -.sp
 268  262  .LP
 269  263  See \fBattributes\fR(5)  for descriptions of the following attributes:
 270  264  .sp
 271  265  
 272  266  .sp
 273  267  .TS
 274  268  box;
 275  269  c | c
 276  270  l | l .
 277  271  ATTRIBUTE TYPE  ATTRIBUTE VALUE
 278  272  _
 279  273  MT Level        Safe
 280  274  .TE
 281  275  
 282  276  .SH SEE ALSO
 283      -.sp
 284  277  .LP
 285  278  \fBfcntl\fR(2), \fBt_alloc\fR(3NSL), \fBt_open\fR(3NSL),
 286  279  \fBt_rcvudata\fR(3NSL), \fBt_rcvvudata\fR(3NSL) \fBt_rcvuderr\fR(3NSL),
 287  280  \fBt_sndudata\fR(3NSL), \fBattributes\fR(5)
    
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX