[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] only complain about wedged cpuworkers after an hour, not 10...
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] only complain about wedged cpuworkers after an hour, not 10...
- From: arma@xxxxxxxx (Roger Dingledine)
- Date: Sat, 23 Apr 2005 16:58:41 -0400 (EDT)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Sat, 23 Apr 2005 16:59:04 -0400
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Update of /home2/or/cvsroot/tor/src/or
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/src/or
Modified Files:
cpuworker.c
Log Message:
only complain about wedged cpuworkers after an hour, not 100 secs
Index: cpuworker.c
===================================================================
RCS file: /home2/or/cvsroot/tor/src/or/cpuworker.c,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -d -r1.75 -r1.76
--- cpuworker.c 8 Apr 2005 04:59:34 -0000 1.75
+++ cpuworker.c 23 Apr 2005 20:58:39 -0000 1.76
@@ -356,12 +356,12 @@
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;