diff options
| author | Roger Dingledine <arma@torproject.org> | 2006-04-18 19:48:06 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2006-04-18 19:48:06 +0000 |
| commit | 2d78d74c80983da02eeb2418d9a3ac866359becd (patch) | |
| tree | 1ed9ddf4c5e7b58023491c4a31b1ce874aa1ba5f /src/or/cpuworker.c | |
| parent | 5721747de2733bfcfc1eb94d7d9460cfd976a089 (diff) | |
| download | tor-2d78d74c80983da02eeb2418d9a3ac866359becd.tar.gz tor-2d78d74c80983da02eeb2418d9a3ac866359becd.zip | |
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.
svn:r6406
Diffstat (limited to 'src/or/cpuworker.c')
| -rw-r--r-- | src/or/cpuworker.c | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/src/or/cpuworker.c b/src/or/cpuworker.c index 1e57c93316..badca3563e 100644 --- a/src/or/cpuworker.c +++ b/src/or/cpuworker.c @@ -396,8 +396,11 @@ process_pending_task(connection_t *cpuworker) 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 |