What is with the second parameter in bind()?
Answer / chaitanya
The man page shows it as "struct sockaddr *my_addr". The sockaddr struct though is just a place holder for the structure it really wants. You have to pass different structures depending on what kind of socket you have. For an AF_INET socket, you need the sockaddr_in structure. It has three fields of interest:
sin_family
Set this to AF_INET.
sin_port
The network byte-ordered 16 bit port number
sin_addr
The host's ip number.
This is a struct in_addr,
which contains only one field,
s_addr which is a u_long.
| Is This Answer Correct ? | 0 Yes | 0 No |
What is socket address with example?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
Why does connect() succeed even before my server did an accept()?
Can multiple sockets use the same port?
How are unix domain sockets implemented?
What is a socket set used for?
How do unix sockets work?
How do Sockets Work?
Where can a get a library for programming sockets?
How many sockets can a port have?
What exactly does SO_REUSEADDR do?
How come I get address already in use from bind()?