Yes, Deluge is Free Software, as defined by the Free Software Foundation, and is released under the GPL, giving our users complete freedom. The source code is available in the [download section](/download.md). Our GPL nature allows you to be 100% sure that our program will never “spy” on your activities. Closed-source BitTorrent clients cannot make that same claim.
On Windows, the installer should do this automatically. On Linux/Unix (GNOME), right-click on a torrent file, click on properties, click on the "open with" tab. Is Deluge listed there? If so, select it to be your default, if not, click on "add", then click on "use custom command". Insert `/usr/bin/deluge` and click add.
* **OSX** GTK does not support Magnet URIs (see [#2420](https://dev.deluge-torrent.org/ticket/2420)) but there is a plugin available: http://forum.deluge-torrent.org/viewtopic.php?f=9&t=52619
The default location for the Deluge config directory is in the `home` directory of the current user. The config location can be manually changed by using the `--config` option at startup.
Linux, BSD and Mac OSX::
`~/.config/deluge`
Windows OS::
`%APPDATA%\deluge`
*When running Deluge as a service the config directory is relative to the user specified in the service configuration.*
If you don't care about losing your current torrents then delete everything in Deluge's [config](/faq.md#where-does-deluge-store-its-settingsconfig) directory.
2. Edit `web.conf` in [config](/faq.md#where-does-deluge-store-its-settingsconfig) and delete the entire `pwd_sha1` line or use quick method via command-line e.g.:
The easiest way to configure plugins is using the GTK UI. If unable to use GTK UI on the machine with your daemon, it is possible to connect to that daemon from another computer with the GTK UI. See [ThinClient](/userguide/thinclient.md) for more information on remote GTK UI setup.
2. Edit `web.conf` in [config](/faq.md#where-does-deluge-store-its-settingsconfig), find `"default_daemon"` and set its value to the daemon `id` in `hostlist.conf`
This is likely due to mismatching config locations, ensure you are running deluge-console with same user as deluged: [More Details](/userguide/thinclient.md#accessing-deluged-service-with-local-ui-client)
Seeds use something called "seed rank" to determine which should be active and which should be queued. The seed rank is determined by the number of seed cycles a torrent has completed. Torrents with fewer completed seed cycles are prioritized for seeding. A seed cycle is completed when a torrent meets either the share ratio limit (uploaded bytes / downloaded bytes), the share time ratio (time seeding / time downloading) or seed time limit (time seeded).
Note: if you do not know your upload speed, go to http://speedtest.net and run a test. You can view the results in KB/s by choosing "kilobytes" for "Speed Measurement" which can be accessed under "Settings" in the top left corner of the page.
* If you have Deluge setup as a [ThinClient](/userguide/thinclient.md) then this setting is determined by the OS the daemon is running on, not the thin client.
Deluge handles files as pieces, not as individual files. This gets tricky, as sometimes the same piece is shared between consecutive files. So if you tell Deluge to download a file, it'll download all of the pieces within that file, and if one of those pieces is shared with another file, that file will also be created, although not necessarily entirely downloaded.
Note: Deluge can be run with experimental libtorrent from libtorrent_aio branch. In this case all pieces of not wanted files will be stored in one temporary file per torrent.
Compact allocation only allocates as much storage as it needs to keep the pieces downloaded so far. This means that pieces will be moved around to be placed at their final position in the files while downloading (to make sure the completed download has all its pieces in the correct place). In full allocation, the entire space that a file needs is allocated as soon as one piece of that file is downloaded, thus decreasing fragmentation.
We suggest that our users use full allocation.
Deluge uses [sparse files](http://en.wikipedia.org/wiki/Sparse_file) for full allocation, the compact allocation option is only useful on file systems that don't support sparse files (such as FAT or HFS+).
The official ports for Bittorrent are `6881-6889`, but most ISPs block or at least throttle those ports, so users are encouraged to use a port range of something between `49152` and `65535`.
An "auto managed" torrent, is a torrent managed by Deluge.
This means that it obeys Deluge's queue settings.
By disabling "auto managed", a torrent will become active (i.e. start downloading/uploading).
It will still be be bound by the stop ratio though (see 'Stop seed at ratio' under the Queue section of the torrent's Options tab).
Note: All active torrents (including those not "auto managed") are counted in the total active queue settings. This means that if the total number of active torrents ("auto managed" and not) exceed the limit for total active torrents in the queue settings, Deluge will automatically queue any "auto managed" torrents until the limit is no longer exceeded.
IPv4 Header Type Of Service Byte [http://shorewall.net/manpages/shorewall-tcclasses.html (More Info)](http://shorewall.net/manpages/shorewall-tcclasses.html (More Info))
Masks: Normal Service `0x00`, Minimize Cost `0x02`, Maximize Reliability `0x04`, Maximize Throughput `0x08`, Minimize-delay `0x10`