Comment by ChrisMarshallNY
10 days ago
The problem with doing that, is that the standard TCP timeout is 60 seconds.
All of a sudden, you are beset with 60-second hangs.
10 days ago
The problem with doing that, is that the standard TCP timeout is 60 seconds.
All of a sudden, you are beset with 60-second hangs.
If the computer doesn't have any online network connection, shouldn't it outright error? I understand that the timeout sucks when your network is not connected to the internet but still alive, then that's an issue, but if there is no connection at all, why would the timeouts matter?
It wouldn't be able to open a TCP connection without knowing what IP address / interface to use.
You're right--it should outright error. You should only see timeouts like that if you were dropping the packets from some middleware or middlebox, but your client still had a valid IP address.
Just a wrap-up.
It was a badly-written comment. I meant some apps (and background tasks) on my computer hang. Most deal with it, but a surprising number don’t. I gave up on sniffing with Terminal and other tools, trying to figure out which ones. I have a number of dev tools installed on my computer, and a lot of those have a … casual … approach to quality.
I have no issue admitting fault (I do it way too often), but I don’t really dig rewarding boorish behavior, so I just figured I’d leave it alone.
You just gave me flashbacks of mistyping a folder share name on windows and having the whole PC lock up for a minute or two.
> All of a sudden, you are beset with 60-second hangs.
No, that's not how it works. Frankly, I'm astonished to see this claim here.
The problem with this is some apps do incredibly stupid things. Now I'm not saying the operating system itself, but I had some ide screw off and go into long pause mode when my laptop was in airplane mode.
I'm sure there are stupid apps out there, but "the standard TCP timeout" was a misdiagnosis of the problem.
Depends.
I have a couple of apps on my computer that do exactly that.
I am looking forward to learning how it does work...
> I am looking forward to learning how it does work...
It's basic sockets. If you call connect() when the internet is disabled, the errno is ENETUNREACH.
The higher-level API are built on sockets. If any apps are misbehaving, they're simply badly coded.
5 replies →
You're not thinking like a systemd developer. The right thing to do is to ignore all anecdotes and direct evidence that a problem exists. I am talking about systemd renaming your network interfaces because you added or removed hardware.
4 replies →