diff options
| author | Roger Dingledine <arma@torproject.org> | 2005-04-07 20:07:34 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2005-04-07 20:07:34 +0000 |
| commit | 6bdfd9727249b980e23b49d6338f18a0728e7caa (patch) | |
| tree | 122c26ff43e55c4dde83c879384569a97d554202 /src/or/cpuworker.c | |
| parent | ab8a0bb52c97aefa1c12b2d4add6a561758ebd0e (diff) | |
| download | tor-6bdfd9727249b980e23b49d6338f18a0728e7caa.tar.gz tor-6bdfd9727249b980e23b49d6338f18a0728e7caa.zip | |
add function comment
svn:r4043
Diffstat (limited to 'src/or/cpuworker.c')
| -rw-r--r-- | src/or/cpuworker.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/or/cpuworker.c b/src/or/cpuworker.c index 119398aa06..7a5a046b27 100644 --- a/src/or/cpuworker.c +++ b/src/or/cpuworker.c @@ -358,6 +358,10 @@ static void process_pending_task(connection_t *cpuworker) { #define CPUWORKER_BUSY_TIMEOUT 100 /* 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. */ static void cull_wedged_cpuworkers(void) { connection_t **carray; |