Custom Query (2449 matches)
Results (577 - 579 of 2449)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #960 | WontFix | Choosing paths for (not) localhost torrents | ||
| Description |
I have deluged running at a box at home, and for the sake of being difficult, I run an ssh tunnel to my house (from work) for port 58846. Deluge GTK connects to this if I specify localhost on port 58846 with creds just fine. However, deluge GTK notices that I'm connecting to "localhost", even though I'm not, and changes path entry fields to browse. When I add a torrent, I'll choose /home/afunk, which happens to exist on both my workstation and my deluged box back home. I'd love for it to go to /media/videos, but for the sake of being a hurry, I symlinked on the remote box. I could create a dummy directory structure on my workstation to mock that of my NAS, but that would be tedious and ugly. I love the ability to browse localhost, don't get me wrong. I ask that there be a place that I can type the path, even for localhost, for idiots like me who have convoluted ssh tunneling schemes. I'm even fine with starting the torrent in /home/afunk, then "moving storage" after the fact, although it'd be slick if I could type a path before I start the torrent. The alternative solution to this is to have browse available on remote deluged's, but I can only imagine that this is a considerable amount of work - work which the awesome devs may not have time for. Both the client and server are running 1.1.8 on Gentoo Linux. Please let me know if any more information is required. |
|||
| #964 | WontFix | free torrent flag | ||
| Description |
It would be good if there is a 'free torrent' flag, wich can be checked/unchecked when torrent is added (for each torrent). |
|||
| #969 | WontFix | Full allocation allocates for files not selected to download | ||
| Description |
When using full allocation with torrents that have multiple files. If I only select to download one file (all others set to "do not download"), it still allocates for the close by torrents in the file segments. I understand it is because segments can overlapp the files, but should deluge really allocate for the entire close by file?
Example:
If only downloading "File 2" which is 1 GB, deluge allocates for both the files but only downloads maybe 0,58% of "File 1". This means that for each torrent where I download 1 GB of 2 GB the usage on disk requires it to have 2 GB. |
|||
