Author: arma Date: 2013-08-16 06:03:34 +0000 (Fri, 16 Aug 2013) New Revision: 26310 Modified: website/trunk/docs/en/faq.wml Log: change from nickm, modified by arma Modified: website/trunk/docs/en/faq.wml =================================================================== --- website/trunk/docs/en/faq.wml 2013-08-15 16:17:06 UTC (rev 26309) +++ website/trunk/docs/en/faq.wml 2013-08-16 06:03:34 UTC (rev 26310) @@ -1771,11 +1771,13 @@ use this feature.</li> - <li>If you're running on Solaris, OpenBSD, NetBSD, or - old FreeBSD, Tor is probably forking separate processes - rather than using threads. Consider switching to a <a - href="<wikifaq>#WhydoesntmyWindowsorotherOSTorrelayrunwell">better - operating system</a>.</li> + <li>If you're running on Solaris, Tor is probably + forking separate processes for each CPUWorker rather + than using threads. Try explicitly configuring Tor with + <tt>--enable-threads</tt>, but be ready for the lockups some + people reported back in 2005. Also consider running your relay on <a + href="https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#WhydoesntmyWindowsorotherOSTorrelayrunwell">an + operating system where Tor works better</a>.</li> <li>If you still can't handle the memory load, consider reducing the amount of bandwidth your relay advertises. Advertising less