Jeff, Thanks for the additional information, this helps clear things up a lot. Can you also tell me what signals you use to kill?
thanks, micah Jeff Bonham schrieb am Thursday, den 13. January 2005: > The data loss on the client side is the torrent metainfo that is stored > in ~/.BitTornado/datacache. If a bittornado process is ended using the > curses or GUI interface, a file is written out here containing progress > information. However, if the user does not have access to the UI of the > bittornado process in question and kills the process with a signal, the > data is never written and is lost. This causes the bittornado process > to lose track of (a) its total bytes up/down, destroying any ratio > recording on the user side and (b) the file progress, causing the > entire file to be rescanned on the next startup. > > The data loss on the tracker side are the bandwidth statistics reported > by bittornado when it announces to the tracker. If the process is ended > from the curses or GUI interface, bittornado makes a final announce to > the tracker before exiting. However, if the user does not have access > to the bittornado UI and kills the process with a signal, the data is > never sent and is lost. This causes the tracker to improperly record > (a) ratio statistics (the numbers from the last announce before the exit > are used instead) and (b) whether the client is still connected to the > tracker, causing double, triple or more "ghost" connections on the > tracker side until they time out. > > -- > Jeff Bonham > [EMAIL PROTECTED] > PGP Public Key ID: BA289747 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
