Yat Ho
Yat Ho
Do you have any publicly available files where this can be reproduced?
@komali2 `Error: Couldn't get '....': Too many open files (24)` stood out to me, `'....'` should contain the file path of one of the files in the torrent. This implies...
I had a look at the code from libtransmission. AFAICT, Transmission is supposed to have at most 32 files descriptors open for torrent files at any time, with the following...
@mihirukiss Hmm, nice find! This is a big hint. Does your Synology NAS by chance use OpenSSL 1.x? If you do, then your case looks a lot like https://github.com/haproxy/haproxy/commit/56996dabe67b484b7c0e90192539c57e60483751.
Hmmm, looks like the commit I linked isn't related here: According to the commit message, the bug it fixed is triggered by calling `execvp()`, but we don't do anything like...
> wanted to know if there was any specific information beyond what I have requested that would be useful to help resolve this issue. @mreid-tt I'm also poking around in...
Bummer, so that's a miss. 😊
I can't reproduce this. I've worked on port forwarding code recently, and they did not cause any problems for me when testing.
> I am not sure if the direct communication through this command is implemented or not. Can you clarify? You are right, there is no option to specify sequential download...
> can't we keep those files as `tmp` so they will be deleted if the user removes the torrent completely from the list. So, with this way, seeding won't be...