Displaying 2 results from an estimated 2 matches for "max_time_second".
Did you mean:
max_time_seconds
2001 Aug 16
4
Idletimeout patch
...s SIGCHLD kludge is used to detect when the child exits. The server
* will exit after that, as soon as forwarded connections have terminated.
@@ -193,7 +194,9 @@
struct timeval tv, *tvp;
int ret;
int client_alive_scheduled = 0;
-
+ /* Secs until idletimeout, zero if no idletimeout */
+ int max_time_seconds=0;
+
/*
* if using client_alive, set the max timeout accordingly,
* and indicate that this particular timeout was for client
@@ -208,6 +211,24 @@
} else
client_alive_scheduled = 0;
+
+ if (options.idletimeout>0) {
+ if (idletime_last==0) {
+ /* Initialize idletime_l...
2001 Aug 20
1
Idletimeout patch, third attempt
...lect() ssh-client side idletimeout could be easily
implemented, if anybody would need a feature like that.
- Counting of idle timeouts starts now immediately after authorization
has been successfull, not when sshd first enters
wait_until_can_do_something()
- IMHO, the patch is much cleaner. max_time_seconds variable has been
removed.
- It fixes two places, where select() might have been called after
EAGAIN or EINTR, but the fd_sets would not have been reinitialized.
- If select returns error other than EAGAIN or EINTR, it exits with
fatal(). Before the error would either be ignored or just lo...