You can run the torrent in background to enter other commands. And BTW lftp doesn't use threads.
On пн, 18 сент. 2017, 6:20 Stu Midgley <sdm...@gmail.com> wrote: > Morning > > Thanks for taking time with this. > > How do I type the jobs -vv in? All the terminals are waiting in the > torrent command (to receive the files) > > I also notice a LOT of DHT timeouts on almost every node I'm testing > with... some are to the dht-bootstrap, but most are to the other lftp > torrent clients. > > > ---- DHT node [172.16.250.22]:6881 has lost 2 packets > > > > > > initrd2 > > > **** DHT request get_peers to [172.16.250.22]:6881 timed out > > ---- DHT node [172.16.250.22]:6881 has lost 3 packets > > > > > > > initrd2: dn:0 up:0 > > **** DHT request find_node to [172.16.250.33]:6882 timed out > > ---- DHT node [172.16.250.33]:6882 has lost 1 packets > > **** DHT request find_node to [172.16.250.182]:6886 timed out > > ---- DHT node [172.16.250.182]:6886 has lost 1 packets > > > Something is not right. After quite some time (10+ minutes) clients > suddenly start downloading the files and also seeding. BUT it takes over > 10 minutes to get into that state. I feel their is a critical thread > somewhere stuck and it eventually timeouts. > > Thanks > Stuart. > > > > > On Sun, Sep 17, 2017 at 7:25 PM, Alexander Lukyanov <lavv...@gmail.com> > wrote: > >> Try "jobs -vv" to see the peer status. >> >> On пт, 15 сент. 2017, 8:15 Stu Midgley <sdm...@gmail.com> wrote: >> >>> OK... getting further along. It turns out that I had to delete the lftp >>> cache so that the nodes didn't all have the same node_id (from ip address >>> 127.0.0.1). >>> >>> I now >>> * remove the tests for 172.16 ip addresses in both lftp and >>> dht-bootstrap >>> * specify the torret:ip as the host ip >>> * delete the lftp cache (~/.cache/lftp) >>> >>> However, no data is transfered. >>> >>> On the client I get >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (1 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (1 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (1 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (1 seeds) >>> >>> On the server I get >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (0 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (0 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (0 seeds) >>> >>> ---- torrent B40B0E478CB94A69CE6A3E811744D09AA7F60D31 has 1 known peers >>> (0 seeds) >>> >>> >>> I can see the communication with the dht-bootstrap server and that >>> looks good. >>> >>> I can also see the client and server sending each other dht get_peers >>> and getting a response. >>> >>> Stu. >>> >>> >>> -- >>> Dr Stuart Midgley >>> sdm...@gmail.com >>> _______________________________________________ >>> lftp mailing list >>> lftp@uniyar.ac.ru >>> http://univ.uniyar.ac.ru/mailman/listinfo/lftp >>> >> > > > -- > Dr Stuart Midgley > sdm...@gmail.com >
_______________________________________________ lftp mailing list lftp@uniyar.ac.ru http://univ.uniyar.ac.ru/mailman/listinfo/lftp
