Tor running on mipsel

[Chris Palmer]

Ferdinand O. Tempel writes:

> I do see the following error in syslog though:
> Dec 23 22:34:50 10.164.10.1  Tor: connection_dir_client_reached_eof():
> Received http status code 503 from dirserver. Failing.
> Is that important?

Yes, the directory listing had gotten too large for the memory allocated 
to store it! Nick has comitted a patch.

> If memory usage goes through the roof, I can always try to run tor in
> client mode to see how that goes. Is there a way to limit tor's memory
> usage, of would that require redesign of said buffer handling? By the
> sound of it not a bad idea anyway.

Tor on my Mac chews up a fair amount of RAM:

~ $ ps auxww | grep tor
chris   2275   0.0  0.9    28712   3616 std- S    Wed06PM   2:49.45 tor

Tor as a server needs more, but less than it used to (several memory
leaks were found and fixed a couple weeks ago). This is from a Tor 
server:

$ ps auxww | grep tor
chris     2482  8.4  2.5 14848 12968 p2  S     13Dec04  868:00.84 tor 
chris     6187  3.4  1.6 16592  8592 p2  S     Mon03PM  131:18.76 tor 
chris    16992  0.0  0.0  5056     0 p1  R+     7:23PM    0:00.00 grep 
tor (ksh)
chris    16751  0.0  0.3  5248  1384 p2  I     13Dec04    0:00.01 tor 
chris     1552  0.0  0.2  5248  1112 p2  I     13Dec04    0:00.01 tor 
chris    21902  0.0  0.2  5248  1112 p2  I     13Dec04    0:00.01 tor 


-- 
Chris Palmer
Technology Manager, Electronic Frontier Foundation
415 436 9333 x124 (desk), 415 305 5842 (cell)

81C0 E11D CE73 4390 B6C7  3415 B286 CD8F 68E4 09CD

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20041223/f50970da/attachment.pgp>