On Tue, Dec 09, 2008 at 10:24:02AM +0100, Peter Palfrader wrote: > On Tue, 09 Dec 2008, Marc Olzheim wrote: > > > Package: tor > > Version: 0.2.0.31-1 > > Severity: important > > > > Tor slowly leaks memory, resulting in the usual out-of-memory problems, > > usualy getting tor killed by the kernel, but before that, slowing the > > machine down because it eats all memory resources. > > > > top output, just before i just restarted it again: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > 28780 debian-t 20 0 1453m 345m 4048 S 0.3 70.7 468:43.85 tor > > > > Just after restart: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > > > 8308 debian-t 20 0 114m 96m 24m S 1.0 19.7 0:16.09 tor > > > > This is the result of keeping it running about 2 weeks. > > That doesn't mean it's leaking. What's the amount of bandwidth you're > pushing? Are you an exit node? What's your exit policy?
Pretty much all defaults, with exit disabled, here is my /etc/tor/torrc: mzh:/>grep '^[^#]' /etc/tor/torrc SocksPort 9050 # what port to open for local application connections SocksListenAddress 127.0.0.1 # accept connections only from localhost SocksListenAddress 85.17.141.90:9100 # listen on this IP:port also Nickname coredev RelayBandwidthRate 50 KB # Throttle traffic to 100KB/s (800Kbps) RelayBandwidthBurst 100 KB # But allow bursts up to 200KB/s (1600Kbps) ContactInfo 1024D/B14E82B1 Marc Olzheim <zlo AT zlo dot nu> ORPort 9001 DirPort 9030 # what port to advertise for directory connections ExitPolicy reject *:* mzh:/> Access to port 9100 is firewalled to allow only my own hosts. Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
