Difference between revisions of "AMule files"

Revision as of 10:22, 12 January 2005

Most aMule's config files and data are the same as or is 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.

Here is a list and the usage of each of them:

• ~/.eMule: aMule's personal configuration file (that is, things such as you nickname, your Temp and Incoming directories, your upload and download limits, and such...).
• ~/.aMule/addresses.dat: Contains a list of serverlist URLs to check (if enabled in Preferences) for new servers on startup.
• ~/.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 is the template file which aMule WebServer uses to create the web page.
• ~/.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/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/cryptkey.dat: It contains the unique 384 bit private RSA key of your client.
• ~/.aMule/emfriends.met: Contains your friends list configuration.
• ~/.aMule/ED2KLinks:
• ~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to ipfilter.
• ~/.aMule/Incoming: By default, the directory where aMule stores the completed downloads.
• ~/.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 stores the verified AICH hashes of your shared files.
• ~/.aMule/lastversion: This is only for aMule to know if it's the first time you're starting aMule, if you had aMule installed before and which version you had installed previously.
• ~/.aMule/logfile: This file contains the log of the last aMule execution.
• ~/.aMule/muleconn: This file is a socket for aMule communications.
• ~/.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, also known as user hash.
• ~/.aMule/server.met: This is a list of all known servers and your preferences about them (priority, name, IP, port and such).
• ~/.aMule/shareddir.dat: Stores the paths to all shared directories.
• ~/.aMule/Temp: By default, the directory where aMule stores the not completed downloads (temporary files).
• ~/.aMule/webserver: This directory contains the necessary files for aMule WebServer to display a nice Web page.

Other files in ~/.aMule/ are most surely backups of some of the above files. Also, on the Temp directory (which is ~/.aMule/Temp by default but can be set to any other on 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.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.