• If it's with a BitTorrent client working on versions prior to 3.3, you can safely resume your download with Azureus.
• From 3.3 on, you need to make your client, either pre-allocate the space used by the files or try and finish the allocation. If it can't, it's not safe to resume the download with Azureus.
• To continue downloads begun with BitComet, you need to check "Truncate existing files that are too large" in Options > Files as BitComet adds bytes at the end of the files...

• Memory usage is known to climb up and drop back repeatedly when using java jre 1.4.2 with some configurations. The cpu load is higher too.
  Please use latest Java 1.5.
• A high cpu load has been experienced with some configurations using Zonealarm.

• Netlimiter for windows users (Note: can cause 100% cpu usage on some configurations).
• The Wonder Shaper (or Trickle) for linux (openbsd, solaris...) users.

• you don't have to use it, of course,
• it's meant to be a gathering of experiences on the program, an exchange of thoughts, preferences, wishes even,

• it took no time to implement it, so the main concern among Azureus' team is still and always taking care of the development of the program itself.

• Max active torrents: maximum number of torrents that are either "downloading", "seeding" or "ready".
• Max simultaneous downloads: maximum number of torrents "downloading".
  (always inferior to (Highest port number - Lowest port number) and to (Max active torrents))

• You will then have 2 "downloading" torrents, and 1 torrent "ready" and 1 torrent "stopped".
  When one download finishes, the torrent then switches to "seeding" mode and the "ready" torrent begins to download.
  Once over, you will have 3 "seeding" torrents and a "stopped" one.

• Are you behind a router? Enable port forwarding to your computer on port 6881 (or whatever you specified in the configuration).

• how many peers are you connected to? Set "number of max connections per torrent" sufficiently high (to 100 for instance) in "configuration" menu > transfer, unless you have some disconnection issues.
• what's the "total speed" of your torrent (directly under "max uploads" in the general view) ?
  this gives you an estimate of the speed of your swarm, so an estimate of your speed (speed of the swarm/numbers of peers you're connected to)
• When allocating bandwith, please allow at the very least 2kB/s per uploads (4kB/s is recommended), that means that using the default value of 4 uploads per torrent, you need AT LEAST 8kB/s of upload per downloading torrents. Not uploading will result in poor performances, trying to increase the number of uploads while the bandwidth is limited WILL result in a serious slow down.

My line is 512/128.
The settings for a BitTorrent application is directly linked to my max upload speed, here 128kbps (16kB/s).
So my max upload speed in azureus will be 13kB/s (letting room for download and browsing).
With 13kB/s upload, I can have 6 uploads at a time, because one upload needs to be at the very least least 2kB/s (uploading less might be damaging both for you and for the peer you're uploading to - seeing that you're not sending fast enough, the peer will ask someone else for the same piece and discard yours when it finally arrives, having downloaded it (and you uploaded it) for nothing... ).
I will have 2 active torrents (1 at most downloading, the other seeding) with 3 uploads each. (3 uploads means I will be uploading to 3 peers at a time on one torrent).
That way, if I'm only downloading, each peer will get 13/3 = 4kB/s approx, which is good and will make them sending me data more likely. The more you upload to a peer, the more likely he is to send you data fast.
And if I'm seeding one torrent and downloading another, each peer will get 13/6 = 2kB/s approx, which is ok.

All those settings should have been taken care of when you first ran the config wizard. Of course, it's essential that you know your max upload speed for the wizard to be effective, both for the peers and for you.

• Discarded: is the data you somehow received although you didn't need it, so you got rid of it.
  Measured in chunks of 16KB (that Azureus uses).
• Hash fails: are pieces that failed the test of "validation", some wrong data was received, thus unusable.
  Measured in pieces (whose size depends on the torrent). There is no normal amount of "hash fails" as it depends on peers sending wrong data.

• A torrent file contains information encoded using a space-efficient technique, however this renders the file hard to understand and modify. The "export torrent" facility allows this torrent information to be saved in an XML format which is more amenable to modification.
• The "import torrent" function takes an XML encoded torrent file and converts this back into the original format, making it usable as the basis for downloading/seeding.
• To uniquely identify a torrent a "hash" is computed from the "INFO" part of the XML document. For example, this hash is used when communicating with a tracker. Changes made to the "INFO" data will alter the hash value and make the torrent incompatible with other downloaders/seeders for the torrent content.
• The XML schema for XML torrent documents can be found here.
• Due to character set issues the torrent name and file name components are currently exported as hex encoded bytes.

Azureus has a built in tracker to allow users to share torrents directly, rather than uploading them to an "external" tracker. This is called "hosting" and can be performed by selecting this option from the context menu on the "My Torrents" view.

Configure the details of the embedded tracker via the "Tracker" tab on the "Configuration" view. There is an "External tracker IP address" field that must refer to the external IP address of your machine. Note that if you are behind a firewall this may differ from your machine's local address. To help in this task there is a "Check Address" button here. If your machine's external address isn't fixed (e.g. your ISP regularly changes it) then this will interfere with your hosted torrents, as the "announce url" will need to keep changing. If this is the case then it is advisable to use a DNS redirection service, such as DynDNS.org, to assign yourself a fixed DNS name - refer to the site for details.

In order to host a torrent it must have the correct "announce url" defined in the torrent. It must refer to the url of the embedded tracker. Use the File Menu/ "create a torrent" facility to construct a torrent, selecting the "Use Azureus embedded tracker" option to ensure the correct announce url is used. Then open the torrent and select "host". You will probably want to seed the new torrent, at least initially, so start the torrent and navigate to the file/directory used to create the torrent when selecting the download location.

You will see on the tracker configuration dialog that there is a port associated with the tracker, default value 6969. If you have a router/firewall you will need to open this port up for incoming TCP connections, as you will have done for the peer transport ports (default 6881 to 6889).

The tracker also, if enabled, publishes the hosted torrents and statistics as a web page. This can be accessed by using the tracker's root url. For example, http://127.0.0.1:6969/. Other users can then download the torrents directly from here ( http://yourexternalIP:6969/ ).

The "My Torrent" context menu item "Publish" enables you to publish a torrent to the tracker's web page (above) without hosting it. This provides a quick way of sharing a torrent with other users. The torrent's existing tracker will be used by any other users, not yours.

• keytool -genkey -keystore %home%\.keystore -keypass changeit -storepass changeit -keyalg rsa -alias azureus

• keytool -export -keystore %home%\.keystore -keypass changeit -storepass changeit -alias azureus -file azureus.cer

• keytool -import -keystore %home%\.certs -alias azureus -file azureus.cer

Requirements :

• a web server of some kind installed on the Azureus PC (e.g. : Apache)
• an access to a Cocoon server (e.g. : http://www.mycgiserver.com), or
• a Cocoon server installed on the Azureus PC (http://xml.apache.org/cocoon/)
• Azureus ;o)

1. Configure Azureus to make it output the Azureus_Stats.xml somewhere on your harddisk
2. (optional) Register for a Dyndns account (http://www.dyndns.org) and install a dyndns client updater (same URL)
3. Configure the http server so the Azureus_Stats.xml is published on the web (let's say the URL will be http://my.server.org/azureus/Azureus_stats.xml)
4. Edit the azureus.cocoon.xml file, and replace the string http://xxx.homedns.org/azureus/Azureus_Stats.xml" with the URL you configured at step 3 (e.g. http://my.server.org/azureus/Azureus_stats.xml)
5. Either :
   • Configure Cocoon so it publishes azureus.cocoon.xml and azureus.xsl, or
   • Upload the azureus.cocoon.xml and azureus.xsl files to your MyCgiServer account