Configuration directory
From VuzeWiki
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.
Contents |
[edit] Location
Default location of the configuration files is OS-dependant:
- Under Unix, this usually is ~/.azureus/
- Under Mac OS X, this usually is "/Users/<username>/Library/Application Support/Azureus/"
- Under Windows, this usually is %appdata%\Azureus\
- With Vista, Windows 7 and later, %appdata% corresponds usually to C:\Users\USERNAME\AppData\Roaming** With XP, %appdata% corresponds usually to C:\Documents and Settings\USERNAME\Application Data
- In very old Windows 95, 98 and Me system the files may also be located in %programfiles%\Azureus i.e. C:\Program Files\Azureus
- Please note that the user's Windows profile directory %appdata% is hidden by default, and you have to enable seeing hidden files in Windows Explorer in order to see the directory.
[edit] Contents
Note: not complete
| Name | Type | Description |
|---|---|---|
| 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. |
| 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). |
| 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. |
| 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. |
[edit] Clear settings
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. There is no built-in command in Vuze to clear the settings, so you have to do it manually.
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.
- Main settings are stored in the file 'azureus.config'. Delete the file (and its backup 'azureus.config.bak'), 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: 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.
[edit] Notes
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.
