diff options
| author | Roger Dingledine <arma@torproject.org> | 2005-04-23 20:58:44 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2005-04-23 20:58:44 +0000 |
| commit | 92b970d2a6a4e75e093ba4718413f58e67458717 (patch) | |
| tree | 6fc648fb24f83d829fecd66a75f7d72fedb9270b /src | |
| parent | 4fb95f166edfe06b39700ce7a9f06ea4abad0fea (diff) | |
| download | tor-92b970d2a6a4e75e093ba4718413f58e67458717.tar.gz tor-92b970d2a6a4e75e093ba4718413f58e67458717.zip | |
only complain about wedged cpuworkers after an hour, not 100 secs
svn:r4100
Diffstat (limited to 'src')
| -rw-r--r-- | src/or/cpuworker.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/or/cpuworker.c b/src/or/cpuworker.c index afe3b7a103..6a9005b25b 100644 --- a/src/or/cpuworker.c +++ b/src/or/cpuworker.c @@ -356,12 +356,12 @@ static void process_pending_task(connection_t *cpuworker) { log_fn(LOG_WARN,"assign_to_cpuworker failed. Ignoring."); } -#define CPUWORKER_BUSY_TIMEOUT 100 /* seconds */ +#define CPUWORKER_BUSY_TIMEOUT 3600 /* seconds */ /** 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 itself as idle. I don't know why. But here's a workaround - * to kill any cpuworker that's been busy for more than 100 seconds. */ + * to kill any cpuworker that's been busy for more than 3600 seconds. */ static void cull_wedged_cpuworkers(void) { connection_t **carray; |