Bug#401006: [Libtorrent-devel] [Fwd: Bug#401006: libtorrent9: safe_sync errors]

2006-12-10 Thread jaris
On Sat, December 9, 2006 17:05, Jose Luis Rivas Contreras wrote:
 Hi, this is a problem on a Debian system, I can't confirmed and I have a
 2.6.18-3-686 kernel. Could anyone confirmed it?

As indicated earlier, this is likely a filesystem/vm layer bug. Several
people have encountered this problem on the latest kernel versions, so
check with the kernel maintainers.

Rakshasa



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#384949: Doesn't handle forgetfull (buggy) clients well

2006-10-03 Thread jaris
On Tue, October 3, 2006 04:40, Jose Luis Rivas Contreras wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 package rtorrent
 tags 384949 confirmed
 severity 384949 wishlist
 thanks
 I now think it is a combination of things:

 1. clients sometimes forget requests, they skip ahead.
 2. rtorrent tries to reget those holes after a while (which seems to
 work much better now)
 3. super-seeder hide chunks they have served

 If you combine those 3 it seem that rtorrent looses a source for the
 chunk with the hole and if there aren't any other sources the block
 will remain incomplete and stall the download till the superseeder
 resets itself. At least that is what it looks like now.


 I'm not sure what to do about this. It isn't really a bug in rtorrent
 but we can't fix every other client out there.

 Rtorrent could better remember that some client did have that chunk
 and re-request it even if that client now says it isn't available
 anymore. I.e. ignore the super-seeder hack. Unless the super-seeder
 will NAK such requests.

 MfG
 Goswin

 Ok, so since this isn't a problem of rtorrent, but you add a request for
 feature to rtorrent I'm changing this to severity wishlist.

 Plus, I'm sending this to upstreams.

That's too much data to keep around, so it won't be implemented. It might
be an idea to add a limit on request pipe-line size on a per-client type
basis, so I added a ticket (#484) for that.

The super-seeder can't really hide chunks, so it must be a problem of the
super-seeder restarting/being reconnected. Anyway, it would have to be a
bad super-seeder implementation, not to mention super-seeding has been
superseded by Fast Extension so the incentive isn't really there to use
resources to fix this.

Rakshasa



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#384949: Doesn't handle forgetfull (buggy) clients well

2006-09-27 Thread jaris
This should be fixed in the latest release, but I didn`t test it very much.

Rakshasa

On Mon, September 25, 2006 04:18, Jose Luis Rivas Contreras wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 package rtorrent
 tags 384949 upstream
 thanks

 Hi,

 I'm letting know the upstream about this issue.

 Jaris please see [1] for further information about the problem.

 Thanks and Cheers!
 [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384949
 - --

 ~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
 http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
 San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
 CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
 Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.5 (GNU/Linux)

 iD8DBQFFFzx+OKCtW8rKsRgRAmzwAKCZI5SwUU3NbpY1eesVpV5l3wfyiwCgtw8V
 2lOFCkvEMLPdu4dtLGlbOe0=
 =71mR
 -END PGP SIGNATURE-



Furu-Furu-Furu Moon!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#383460: rtorrent: segfault after hashing

2006-09-27 Thread jaris
This is probably fixed in the latest release.

Rakshasa

On Mon, September 25, 2006 03:48, Jose Luis Rivas Contreras wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,

 3 persons have reported segfault after hashing in files biggers than 50MB.

 Please check the full bug at:

 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383460

 Thanks guys for the report.
 Cheers!
 - --

 ~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
 http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
 San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
 CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
 Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.5 (GNU/Linux)

 iD8DBQFFFzV6OKCtW8rKsRgRAl0bAKCCRlixqhx1b7pRqcne1jfAwX5BdgCfQmPJ
 ruk3MPmFPM2PYWnnb6zScaw=
 =5An3
 -END PGP SIGNATURE-



Furu-Furu-Furu Moon!



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]