In Vuze's configuration directory, there are several files stored. Here's a brief description of what they are (which is useful if you want to know what to keep and what to delete). If you are using a recent version of Vuze, you can go to Options-->Files and there will be a link to the configuration directory at the bottom of the screen.
Default location of the configuration files is OS-dependant:
- In Linux the location is "~/.azureus/"
- In Mac OS X the location is "/Users/<username>/Library/Application Support/Vuze/"
- Under OSX 10.7 Lion the User Library folder is inivisible by default. Quick way to it is in the Finder, go to the "Go" menu, hold down the Option key and you should see a Library option appear. Select it and you're in your User/Library folder.
- In Vista and Windows 7 the location is "C:\Users\<username>\AppData\Roaming\Azureus\"
- In Windows XP the location is "C:\Documents and Settings\<username>\Application Data\Azureus\"
- In very old Windows 95, 98 and Me system the files may also be located in "C:\Program Files\Azureus"
Please note that the user's Windows profile directory is hidden by default, and you have to enable show hidden files in Windows Explorer in order to see the directory. Depending on your version of windows there may be more than one way to do this but for a typical copy of XP and above you can do the following. Enter the Control Panel from the Start Menu and select Appearance and Themes (XP) or Appearance and Personalization (Windows 7). Now select Folder Options and change to the view tab. Once there you can select the radio button titles Show hidden files and folders.
Note: not complete
|active||Directory||Contains details information for every download that Vuze is currently managing. Each download will have a file of hashid.dat, which is essentially a copy of the torrent file used to create it, plus other values stored alongside for that particular download (created by Vuze and plugins). Torrents' status information is stored in 'downloads.config' file. 1|
|debug||Directory||This directory is used to store screenshots, logs and other information when you choose to generate a debug report.|
|dht||Directory||DHT stuff, I guess.|
|net||Directory||Some .dat files.|
|logs||Directory||Contains text files containing logs relating to different parts of Vuze. If you select "Generate debug info" from Help menu, the generated debug.zip file will include the log files here and will be created here.|
|plugins||Directory||Stores the plugin files which have been installed for your user only (rather than for all users).|
|shares||Directory||DHT stuff, I guess.|
|subs||Directory||.vuze and .results files.|
|tmp||Directory||Temporary (.tmp) objects.|
|torrents||Directory||A few .tmp files.|
|azureus.config||Bencoded file2||Stores all the main settings used by Vuze. Some plugins will also store data here too.|
|azureus.statistics||Bencoded file||Stores a count of how many bytes you have downloaded and uploaded.|
|azureus.properties||Plain text file||Optional: List of system properties to set - each line is of the form <property_name>=<property_value> and results in a call to System.setProperty( <property_name>, <property_value> )|
|banips.config||Bencoded file||Stores information about banned IPs (related to IP filters).|
|categories.config||Bencoded file||Stores information about each category you currently have configured.|
|devices.config||Bencoded file||Stores information about devices.|
|downloads.config||Bencoded file||Stores information about every download you currently have in Vuze. Some minimal status information will be stored in here about each download, but the majority of information for each download will be in the corresponding *.dat file (renamed copy of original .torrent file) in the active directory.|
|filters.config||Bencoded file||Stores information about the IP filters you have set up. Related files include: ipfilter.dl, ipfilter.ext and ipfilter.cache|
|friends.config||Bencoded file||Stores information about friends (if you use the azbuddy/friends functionality)|
|tables.config||Bencoded file||Stores information about layout and column setup of tables.|
|update.log||Plain text file||Stores information regarding actions performed by Vuze that require Vuze to be closed (and optionally restarted) before they can be applied.|
You can change the location of the configuration folder by performing the following steps:
- Backup your existing installation!
- Note the old location of the Vuze configuration directory, call this <config_old> (the main settings would therefore be in <config_old>/azureus.config)
- Prepare the new location (call it <config_new>) and ensure that your user (and the Vuze runtime process) has full write permission to this folder
- Note the existing location of the Vuze installation directory (call it <install>). On Windows this the folder that contains Azureus.exe, on OSX it is the Vuze.app package.
- Close Vuze
- Copy the entire contents of <config_old> to <config_new>. If you are making <config_new> and <install> the same location then this will require you to merge the contents of the 'plugin' sub-directories.
- Do one of the following in order to pass the location of <config_new> to Vuze on startup (expand <config_new> to be the full absolute path when inserting)
Create/edit a file named Azureus.exe.vmoptions in <install> and add the single line
If there is an existing line
then replace this with
(unless <install> is the same as <config_new>)
Locate the info.plist file in <install>/Contents (show the package contents of the .app if needed)
Edit this in textedit and locate the section starting with
Insert after the<dict>, on a new line
(obviously replacing the <config_new> ...)
Edit the startup script to add an extra parameter to java, -Dazureus.config.path=<config_new>
- Restart Vuze
If you manage to somehow break Vuze's configuration and you can't get things to work again, you might try to reset settings and start again with the default settings.
A new Reset option was added to Mode options in version 22.214.171.124.3 In the older Vuze clients (before version 126.96.36.199), there was no built-in command to clear the settings, so you would have to do it manually.
- Note: uninstall/reinstall of Vuze does not change the settings.
You can easily clear settings by deleting the respective files from this configuration directory. Please note that the configuration files usually have a backup copy (*.bak), so remember to delete it, too.
- Exit Vuze properly (and check that the process really died). Vuze always saves the configuration files at exit, so deleting the files while Vuze is still active does not produce good results.
- Delete the file 'azureus.config' (and its backup 'azureus.config.bak'), where the main settings are stored, and almost all options in Vuze return to default settings.
- Table layout settings (result of column setup actions etc.) are stored in 'tables.config'. Delete it, and you get the default columns back to most tables (Library, Peers, etc.)
There are also other configuration files, like explained in table above, but those files should not concern most users.
Note about active torrents: Like explained in the table above, all status information about the currently active torrents is stored in the file 'downloads.config' and in the directory 'active'. Deleting them will remove all status information about your current torrents. So, be careful with those files.
Note about plugins: Although deleting the settings file azureus.config does clear settings related to most plugins, it does not remove or uninstall plugins. You have to uninstall plugins through the uninstall wizard in Vuze menus or manually remove plugin files (the subdirectory and the files) either from the configuration directory or the Vuze program directory.
You can create a file containing configuration presets (i.e. initial values) that you want Vuze to use by creating a folder named 'custom' in the configuration directory and then placing a text file in that folder that has a name ending in ".config" - for example <config_dir>/custom/mypresets.config
This file should contain lines in the following format:
- parameter_name - the internal parameter name used by Vuze for the configuration setting
- type - one of 'long', 'bool' (value 'true' or 'false'), 'string', 'float', 'byte' (value must be encoded as base16 string), 'list' or 'map' (last two use a bencoded string to represent the value)
The following sets the default save location to 'C:\My Downloads\ and TCP listen port to 48787:
Default\ save\ path=string:c:\\My Downloads TCP.Listen.Port=long:48787
Note that spaces in the config key name (the part before the = sign) need to be escaped by prefixing with a \, likewise any \ characters in the value itself.
Once the settings have been applied the file will be renamed to have a suffix of ".applied" - this means the settings will only be applied once, not every time Vuze is started.
Note 1: If you want to add all active torrents back into Vuze, you should copy across the active directory to your new configuration directory. If you aren't able to add your torrents back in from the location that you saved your torrents to, then you can always copy the .dat files from active directory across to a temporary directory, rename them from *.dat to *.torrent and drag them into Vuze. If all goes well, Azureus will match the hash ID stored in the renamed *.dat file, and then load up all the previous settings related to that download from the *.dat file in the active directory.
Note 2: Bencoded files are specially encoded files used by torrent programs. Usually they can be read also with text/hex editors, although their contents will look like gibberish. There are special Bencode editors, which enable proper handling of the information. One of the best editors is Ultima's Bencode Editor, which was originally distributed at the uTorrent forums, http://forum.utorrent.com/viewtopic.php?id=31306 , but has now also a site at Google: http://sites.google.com/site/ultimasites/bencode-editor
Note 3: A built-in command to reset configuration to default values was introduced in version 188.8.131.52. The command resides in the Mode options, where a Reset button will clean options stored in azureus.config to the default values.