Bug #10222

t_bind(3NSL) could mention data types for transports

Added by Jason King about 1 month ago. Updated 19 days ago.

Status:ClosedStart date:2019-01-11
Priority:NormalDue date:
Assignee:Jason King% Done:


Category:manpage - manual pages
Target version:-
Difficulty:Bite-size Tags:needs-triage


Upstream of Joyent OS-6101:

The t_bind(3NSL) manpage currently states:

The addr field of the t_bind structure specifies a protocol address

but is never defined anywhere. It turns out, that for tcp(7P) and udp(7P) transports, sockaddr_in or sockaddr_in6 should be used. It would be good to mention this for anyone that has to deal with XTI sockets.


#1 Updated by Electric Monk 19 days ago

  • % Done changed from 0 to 100
  • Status changed from New to Closed

git commit c787c4e4eefec8e93a6441f70c306064870d781d

commit  c787c4e4eefec8e93a6441f70c306064870d781d
Author: Jason King <jason.king@joyent.com>
Date:   2019-01-31T22:04:30.000Z

    10222 t_bind(3NSL) could mention data types for transports
    Reviewed by: Robert Mustacchi <rm@joyent.com>
    Reviewed by: Dan McDonald <danmcd@joyent.com>
    Approved by: Hans Rosenfeld <hans.rosenfeld@joyent.com>

Also available in: Atom