nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-12-01 08:03:31 +01:00
Code Issues Packages Projects Releases Wiki Activity

Raise the timeout for complaining about wedged cpuworkers.

Browse Source 
This value is high because some servers with low memory/cpu
sometimes spend an hour or more swapping, and Tor starves.


svn:r6406
This commit is contained in:
Roger Dingledine 2006-04-18 19:48:06 +00:00
parent 5721747de2
commit 2d78d74c80
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/or/cpuworker.c
View File

@ -396,8 +396,11 @@ process_pending_task(connection_t *cpuworker)
log_warn(LD_OR,"assign_to_cpuworker failed. Ignoring."); log_warn(LD_OR,"assign_to_cpuworker failed. Ignoring.");
} }
/** How long do we let a cpuworker work before deciding that it's wedged? */ /** How long should we let a cpuworker stay busy before we give
#define CPUWORKER_BUSY_TIMEOUT (60*60) * 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 /** 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 * stuck in the 'busy' state, even though the cpuworker process thinks of