[or-cvs] Raise the timeout for complaining about wedged cpuworkers.

arma at seul.org arma at seul.org
Tue Apr 18 19:48:08 UTC 2006


Update of /home2/or/cvsroot/tor/src/or
In directory moria:/home/arma/work/onion/cvs/tor/src/or

Modified Files:
	cpuworker.c 
Log Message:
Raise the timeout for complaining about wedged cpuworkers.
This value is high because some servers with low memory/cpu
sometimes spend an hour or more swapping, and Tor starves.


Index: cpuworker.c
===================================================================
RCS file: /home2/or/cvsroot/tor/src/or/cpuworker.c,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -p -d -r1.101 -r1.102
--- cpuworker.c	12 Mar 2006 23:31:16 -0000	1.101
+++ cpuworker.c	18 Apr 2006 19:48:06 -0000	1.102
@@ -396,8 +396,11 @@ process_pending_task(connection_t *cpuwo
     log_warn(LD_OR,"assign_to_cpuworker failed. Ignoring.");
 }
 
-/** How long do we let a cpuworker work before deciding that it's wedged? */
-#define CPUWORKER_BUSY_TIMEOUT (60*60)
+/** How long should we let a cpuworker stay busy before we give
+ * up on it and decide that we have a bug or infinite loop?
+ * This value is high because some servers with low memory/cpu
+ * sometimes spend an hour or more swapping, and Tor starves. */
+#define CPUWORKER_BUSY_TIMEOUT (60*60*12)
 
 /** We have a bug that I can't find. Sometimes, very rarely, cpuworkers get
  * stuck in the 'busy' state, even though the cpuworker process thinks of



More information about the tor-commits mailing list