 | | Notice that the actual address bound by t_bind may be different than the requested address; this occurs if an address is already in use. In the case of servers, which usually have to live at specific addresses, the benefit of this behavior is not clear. It would probably make more sense to just refuse to bind the address, and return an “address in use” error, like the socket interface does. At any rate, after performing the t_bind, a process that cares about the address to which it is bound should check to see that the address in retp is the same as that in reqp. | |
|