Base idle timeout on player->curup again, not current time
Idle timeout used to expire max_idle minutes after the last
player->curup update. When we got rid of the idle thread in commit
08b94556
(v4.3.20), this got changed to "wait no more than max_idle
minutes for input". Time spent computing and time spent blocked on
output no longer counts. In particular, a connection can block
indefinitely on output since then. Let's fix that.
Start with basing the input timeout on player->curup again. The
missing output timeout will be added shortly.
Aside: since status() updates player->curup, the idle timer gets reset
when the update aborts a command. Left for another day.
This commit is contained in:
parent
a96b400da3
commit
ed1cbc97e6
5 changed files with 22 additions and 6 deletions
|
@ -92,8 +92,7 @@ recvclient(char *cmd, int size)
|
|||
if (player->aborted)
|
||||
break;
|
||||
|
||||
timeout.tv_sec = minutes(max_idle);
|
||||
timeout.tv_usec = 0;
|
||||
io_timeout(&timeout, player->curup + minutes(max_idle));
|
||||
res = io_input(player->iop, &timeout);
|
||||
if (res > 0)
|
||||
;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue