You should be able to use normal ulimit style settings,   Limiting open files count (a socket is an open file).


On Wed, Apr 10, 2013 at 8:38 AM, Roger Dingledine <arma@mit.edu> wrote:
On Tue, Apr 09, 2013 at 10:19:38PM -0400, Steve Snyder wrote:
> I am running Tor v0.2.3.25 in a VPS that limits me to a max of 4096
> sockets in use.  How can I instruct Tor not to attempt to use more
> than this number?
>
> Yes, I know about ConstrainedSockets/ConstrainedSockSize, but the
> way I read these it limits the amount of memory used, not the socket
> count.
>
> Advice, please?  Thanks.

I believe there is no such feature currently.

How should it work? That is, which connections should it refuse?

Currently we assume that all relays are able to reach all other relays.
Otherwise we get into the situation where the network isn't a clique,
and anonymity analysis from path selection gets complex really quickly
("I saw the connection from that relay, so the hop before that couldn't
have been this other relay because there's no link, therefore ...")

--Roger

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays