Comment by lapcat
4 hours ago
> 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.
4 hours ago
> 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...
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.
> 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.
> It's basic sockets.
Yup. I've done a bit of that stuff, in my time.
> If any apps are misbehaving, they're simply badly coded.
Plenty of that stuff, going around.
Might want to ease back on the "instant insult" thing. Not a good look.
2 replies →
I don't think you can get ENETUNREACH from recv though. If the request was sent, it'll time out.
1 reply →