On Tue, Jan 08, 2008 at 01:31:49PM -0500, Kevin Stam wrote: > Jeez, perhaps btpd should finally support protocol encryption? Last time I > checked it didn't. A surprising number of ISPs limit BitTorrent traffic, and > more and more seeders, including me, can only be connected to via a client > that supports encryption. Until btpd gets around to supporting this, it's > unusable for me. > > Perhaps Transmission would work better for you? If rtorrent keeps crashing > things, try a different client. If it's not a matter of too few open files, > then hopefully we can get around to fixing the bugs, if we can narrow down > the problem. > > I just noticed unworkable in ports. It uses mmap(). Does anybody encounter > problems with it? If not, then it must be rtorrent's problem, not mmap().
I haven't been able to tickle any VM bugs with Unworkable on OpenBSD for some time. However its still in early stages of development and doesn't support MSE yet either. Works fine for me but YMMV. Of course, I accept patches ;-) > > On 8 Jan 2008 08:46:18 -0800, Unix Fan <[EMAIL PROTECTED]> wrote: > > > Jeez, Perhaps you people should start using btpd instead? rtorrent sounds > > like a nightmare ;) > > > > > > > > http://www.murmeldjur.se/btpd/ > > > > > > > > -Nix Fan.
