I also run in the same problem, but the bug does not show itself in the CVS 
vesion of bittornado. So it is either a debian-specific issue or, more likely, 
it has already been fixed upstream. 

Ivan



      

Reply via email to