Changes between Version 96 and Version 97 of Faq
- Timestamp:
- 02/15/2009 02:13:08 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Faq
v96 v97 2 2 3 3 = General = 4 4 5 == Is Deluge Free? Can I get the source? == 5 6 … … 7 8 8 9 == How to start the various user-interfaces == 10 9 11 Gtk: 12 10 13 {{{ 11 14 deluge 12 15 }}} 13 16 Console: 17 14 18 {{{ 15 19 deluge --ui null 16 20 }}} 21 17 22 or 23 18 24 {{{ 19 25 deluge --ui console 20 26 }}} 27 21 28 Web: 29 22 30 {{{ 23 31 deluge --ui web 24 32 }}} 33 25 34 Go to http://localhost:8112/ 26 35 default-password = "deluge" … … 63 72 64 73 == Seeding torrents have no queue position! Why? == 74 65 75 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). 66 76 67 68 77 == What bandwidth settings should I use? == 78 69 79 Start with the following: 70 80 ||Maximum Connections||200|| … … 95 105 Force recheck discards all incomplete pieces. 96 106 97 98 107 == Does Deluge support Initial/Super Seed? == 99 108 … … 111 120 == What is the difference between full allocation and compact allocation? == 112 121 113 114 122 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. 115 123 … … 117 125 118 126 Deluge uses sparse-files(http://en.wikipedia.org/wiki/Sparse_file) for full allocation, the compact allocation option is only useful on windows-file systems. 119 120 127 121 128 == Which ports should I use? == … … 152 159 153 160 == I upgraded from 0.5 and plugin x is missing == 161 154 162 1.0 was a rewrite, all old 0.5 plugins have to be rewritten. 155 163 … … 158 166 Torrent-Notification is builtin in the future 1.1 (will be moved to a plugin) 159 167 160 == Can Deluge use blocklists such as SafePeer orPeerGuardian? ==161 162 Yes. Enable the “Blocklist” plugin. Currently this plugin can handle PeerGuardian (binary and text), SafePeer and Emule lists. PeerGuardian *7zip format files are not supported*. GenerallyPeerGuardian files come in 7zip format, so you'll need to extract them first and then feed Deluge the plain text file. Files may be specified as URLs or locations on the local filesystem. Here are some suggested blocklists:163 164 1. http://www.deluge-torrent.org/blocklist/pipfilter.dat.gz (Emule) 168 == Can Deluge use blocklists such as !SafePeer or !PeerGuardian? == 169 170 Yes. Enable the “Blocklist” plugin. Currently this plugin can handle !PeerGuardian (binary and text), !SafePeer and Emule lists. !PeerGuardian *7zip format files are not supported*. Generally !PeerGuardian files come in 7zip format, so you'll need to extract them first and then feed Deluge the plain text file. Files may be specified as URLs or locations on the local filesystem. Here are some suggested blocklists: 171 172 1. http://www.deluge-torrent.org/blocklist/pipfilter.dat.gz (Emule)[[BR]] 165 173 2. http://www.deluge-torrent.org/blocklist/nipfilter.dat.gz (Emule) 166 174 167 175 == Where is the scheduler plugin? What are the alternatives for the missing scheduler plugin? == 176 168 177 There is no scheduler plugin for 1.0 yet. 169 178 170 1.0 : use cron + this script: http://dev.deluge-torrent.org/ticket/382#comment:4 171 172 1.1 : [wiki:Scheduling] 173 179 1.0 : use cron + this script: http://dev.deluge-torrent.org/ticket/382#comment:4[[BR]] 180 1.1 : ['UserGuide/Scheduling'] 174 181 175 182 = Console = 183 176 184 == How do I connect the console UI to a daemon on a non-default port ? == 185 177 186 {{{ 178 187 $ deluge -u console … … 183 192 184 193 == Why is deluge still listed in my task manager even after I close it ? == 194 185 195 You closed the UI, but you did not close the daemon. 186 196 Choose "Quit & Shutdown Daemon" to close both Daemon and GtkUI. 187 197 188 198 == How do I start the daemon ? == 199 189 200 {{{ 190 201 deluged … … 192 203 193 204 == How do I start the daemon with logging enabled ? == 205 194 206 === Logging to console === 207 195 208 {{{ 196 209 deluged -d … … 198 211 199 212 ==== With debug info ==== 213 200 214 {{{ 201 215 deluged -d -L debug … … 203 217 204 218 === Logging to file === 219 205 220 {{{ 206 221 deluged -l <logfile> … … 208 223 209 224 ==== With debug info ==== 225 210 226 {{{ 211 227 deluged -L debug -l <logfile> … … 214 230 == How do I stop the daemon ? == 215 231 232 {{{ 216 233 killall deluged 234 }}} 217 235 218 236 Deluge accepts the SIGTERM signal and cleanly shuts down. 219 237 220 221 238 == I can't connect to the daemon from another machine == 239 222 240 * Configure the daemon to allow remote connections 223 241 * Configure [wiki:UserGuide/Authentication Authentication] … … 227 245 228 246 == How do I make deluge connect to a different daemon? == 247 229 248 By default, deluge is in classic mode: the daemon and gtk ui are linked together. 230 249 To disable classic mode: … … 236 255 237 256 == How do I stop deluge from killing the daemon when I quit the GTK UI? == 257 238 258 See above. 239 259 240 260 = Web UI = 261 241 262 == How do I use https? == 242 1.1 and newer : 263 264 1.1 and newer: 243 265 * 1 Create (self-signed) ssl certificates: http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html#selfcert 244 266 245 -Windows:267 === Windows === 246 268 * 2 Put deluge.cert.pem and deluge.key.pem in %APPDATA%\deluge\ssl\ 247 269 248 -Linux:270 === Linux === 249 271 * 2 Put deluge.cert.pem and deluge.key.pem in ~/.config/deluge/ssl/ 250 272 251 -ALL:273 === ALL === 252 274 * 3 Enable https in the webui config. 253 275 * 4 Restart the webui 254 255 276 256 277 = Installing =