Timeline for In bash, what are potential negative consequences of pausing a process with control-z?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2012 at 20:01 | comment | added | Magellan | Not speaking to keepalives, those are obviously Application level. I'm talking about ACKs for the TCP sliding window at the Transport level. | |
| May 25, 2012 at 17:08 | comment | added | jippie | Keep alive packets is not part of the TCP nor the IP protocol, at best it is part of the application. So a firewall or a remote client or server may timeout waiting for a packet and drop the socket/connection. | |
| May 25, 2012 at 15:55 | comment | added | Magellan | The TCP stack would continue sending ACKs that the window is full though, right? | |
| May 25, 2012 at 6:55 | comment | added | jippie | network / firewall sessions may time out and not be restarted because TCP-SYN not being resent. | |
| May 25, 2012 at 5:15 | history | answered | Magellan | CC BY-SA 3.0 |