Difference between revisions of "AMule files"

Revision as of 19:16, 11 January 2011

Most of aMule's config files and data are the same as or are compatible with eMule's.

Have in mind that you might not have all of them on your hard disk, since they are generated when needed.

Program Files

Here is a list and the usage of each of them (On Mac OS X the "~/.aMule" folder corresponds to "~/Library/Application Support/aMule"):

• ~/.eMule: aMule's old personal configuration file (version prior to aMule 2.0.0). It was renamed to ~/.aMule/amule.conf.
• ~/.aMule/addresses.dat: Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup.
• ~/.aMule/amule.conf: aMule's personal configuration file (where most preferences are stored).
• ~/.aMule/amulesig.dat: This is aMule's OnLineSignature file, which is the same as eMule's signature (see onlinesig.dat below) but with extended information.
• ~/.aMule/aMule.tmpl: This was the template file which aMule WebServer used in version prior to aMule 2.0.0.
• ~/.aMule/aMule-online-sign.png: This file will only exist if CAS has been run sometime with the -o switch and ~/.aMule/casrc was successfully configured. It is an image containing details on aMule's status.*~/.aMule/aMule-online-sign.html: This file will only exist if CAS has been asked sometime to generate an HTML stats page. This HTML page contains details on aMule's status.
• ~/.aMule/casrc: This file will only exist if CAS has been run sometime with the -o switch. It contains the settings for the CAS image creation.
• ~/.aMule/clients.met: Contains the public hashes of other known clients along with the credits it owes each of them.
• ~/.aMule/clients.met.BAK: Backup of clients.met file.
• ~/.aMule/cryptkey.dat: It contains the unique 384 bit private RSA key of your client.
• ~/.aMule/emfriends.met: Contains your friends list configuration.
• ~/.aMule/ED2KLinks: This file acts as an external interface to add downloads to aMule.
• ~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to IPFilter.
• ~/.aMule/ipfilter.download: This is where ipfilter.dat files are temporary downloaded, before being renamed to ipfilter.dat (if the download succeeds).
• ~/.aMule/ipfilter_static.dat: This file contains the IP ranges and access levels restrictions which will be passed to IPFilter. The difference between this file and ipfilter.dat file is that this one contains static IP ranges which will override those in ipfilter.dat in case of collision, and that this file will never be modified by aMule, while ipfilter.dat may be auto-updated.
• ~/.aMule/key_index.dat: This file stores information your client provides to the Kademlia network.
• ~/.aMule/known.met: This file stores the hashes and some details of your shared files like size, path, statics, etc.
• ~/.aMule/known2.met: This file stored in older aMule versions the verified AICH hashes of your shared files.
• ~/.aMule/known2_64.met: This file stores the verified AICH hashes of your shared files (supporting large files).
• ~/.aMule/last_version_check: Temporary file containing the version of the latest official aMule release available.
• ~/.aMule/lastversion: This is only for aMule to know if you changed your version or if it's the first time you run it.
• ~/.aMule/load_index.dat: Contains keyIDs of other Kademlia clients and the date when they where last seen.
• ~/.aMule/logfile: This file contains the log of the current aMule execution.
• ~/.aMule/logfile.bak: This file contains the log of the aMule execution before the current.
• ~/.aMule/muleconn: This file is a socket for aMule communications. It is no longer used since 2.1.0
• ~/.aMule/muleLock: This file contains currently running's user's aMule PID. It prevents uers from running two aMules simoultaneously. It replaces the old muleconn socket file.
• ~/.aMule/nodes.dat: Contains a list of Kademlia contacts and details on how to contact each of them.
• ~/.aMule/onlinesig.dat: This is an eMule compatible OnLineSignature file. It's used by other applications to know basic information on aMule's stat. See also amulesig.dat above.
• ~/.aMule/preferences.dat: Contains the public key of your client on the ed2k network, also known as user hash.
• ~/.aMule/preferencesKad.dat: Contains the IP and client ID of your client on the Kademlia network, that is, your identification keys.
• ~/.aMule/remote.conf: Configuration file for External Connections.
• ~/.aMule/server.met: This is a list of all known servers and your preferences about them (priority, name, IP, port and such).
• ~/.aMule/server.met.download: This is where server.met files are temporary downloaded, before being renamed to server.met (if the download succeeds).
• ~/.aMule/server.met.new: Temporal file while it is being written into disk. As soon as aMule is finished writting it, it is renamed to server.met.
• ~/.aMule/server_auto.met: Here is where server.met files are downloaded before merging them with aMule's server.met file.
• ~/.aMule/server_met.old: Backup of server.met file.
• ~/.aMule/shareddir.dat: Stores the paths to all shared directories.
• ~/.aMule/src_index.dat: This file stores information your client provides to the Kademlia network.
• ~/.aMule/staticservers.dat: Stores a list of static servers.
• ~/aMule-online-sign.{png|jpg|bmp}: Default location where wxCAS stores the stat image.
• ~/my_ed2k_link.txt: Default location where aLinkCreator stores computed ed2k links.
• /usr/share/fonts/corefonts/times.ttf: Default location where CAS will look for a font to generate the stats image.
• /usr/share/pixmaps/stat.png: Default location where CAS will look for a template image to generate the stats image.
• /usr/share/pixmaps/tmp.html: Default location where CAS will look for a template HTML page to generate the stats HTML page.

Other files in ~/.aMule/ are most surely backups of some of the above files.

See also: Category:Program Files

Temporary Files

In the Temp directory (which is ~/.aMule/Temp by default but can be set to any other in Preferences), aMule will create, for each download in queue, the following files:

• *.part: This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As aMule is able to download from more than one user at the same time, this file has the size of the complete file. The missing parts are filled with zeros.
• *.part.met: This file contains information on the downloaded parts of the download, the verified chunks, the hash values of the remaining chunks, etc.
• *.part.met.bak: This are backups of the *.part.met files. Every now and then aMule creates this backups since without the *.part.met file, a download has no meaning for aMule. If any *.part.met file "disappeared, you should rename the *.part.met.bak to *.part.met.
• *.part.met.backup: This are temporal *.part.met while the data is being stored. As soon as aMule finishes writting the file, it is renamed to *.part.met.
• *.part.met.seeds: This file only exists if you have enabled to store the IPs of sources of rare files in the preferences, so that aMule can try to connect to these sources again after a restart.

Directories

The directories in ~/.aMule/ have the following use:

• ~/.aMule/Incoming/: By default, the directory where aMule stores the completed downloads (except on MacOS X).
• ~/.aMule/Temp/: By default, the directory where aMule stores the non-completed downloads (temporary files).
• ~/.aMule/webserver/: This directory contains the skins for aMuleWeb.
• ~/aMule Downloads: The directory where aMule stored the completed downloads on Windows in old versions (previous to aMule 2.1.0).
• ~/Documents/aMule Downloads: By default, the directory where aMule stores the completed downloads on MacOS X and Windows (since aMule 2.0.0).
• <app_dir>/Incoming: In MacOS X and Windows, if aMule cannot determine the user's Documents folder, it will store the downloaded files here.