Answer / chaitanya

The SO_KEEPALIVE option causes a packet (called a 'keepalive probe') to be sent to the remote system if a long time (by default, more than 2 hours) passes with no other data being sent or received. This packet is designed to provoke an ACK response from the peer. This enables detection of a peer which has become unreachable (e.g. powered off or disconnected from the net).

Note that the figure of 2 hours comes from RFC1122, "Requirements for Internet Hosts". The precise value should be configurable, but I've often found this to be difficult. The only implementation I know of that allows the keepalive interval to be set per-connection is SVR4.2.

After the chroot(), calls to socket() are failing. Why?

1 Answers  

---

What exactly does SO_KEEPALIVE do?

1 Answers  

---

What exactly is a socket?

0 Answers  

---

How can my client work through a firewall/proxy server?

1 Answers  

---

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?

0 Answers  

---

When should I use UDP instead of TCP?

1 Answers  

---

What is a deep well socket?

0 Answers  

---

Can a socket have multiple ports?

0 Answers  

---

What are the types of sockets?

0 Answers  

---

How does a socket work?

0 Answers  

---

How can I put a timeout on connect()?

1 Answers  

---

How come only the first part of my datagram is getting through?

1 Answers  

---