> TCP keepalives are nasty for machines that suspend. Imagine you have a
> X server running on a machine, and at night you want to suspend the
> machine. If your X clients (running on another machine, say your group
> server) aare well-behaved, they will not generate any traffic, since
> you won't be sending events.
I think there are plenty of clients that will generate traffic regardless
of what the X server is up to. (Glances at window manager's menues) The
following seem like likely candidates:
xbiff, xclock, netscape viewing any sort of dynamic page,
xterms which have active programs running in them, xlock,
xearth, xload
> Now, with keepalives, the OS on the server will send packets to your X
> server (and expect a response), which of course won't respond. Boom!
> You've lost your remote X clients.
The same would happen if any client tries to talk to the X server in that
time.
> No, I think we want to avoid keepalives. Better to fix Netscape so
> that it exits when the connection to the X server is lost.
You don't have to turn it on, it's switchable. I have 60 Xterms here,
none of which suspend - your situation may be different.
David.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/