Difference between revisions of "AMule files"

From AMule Project FAQ
Jump to: navigation, search
Line 12: Line 12:
 
*'''~/.aMule/aMule.tmpl:''' This was the template file which [[amuleweb|aMule WebServer]] used in version prior to [[aMule]] 2.0.0.
 
*'''~/.aMule/aMule.tmpl:''' This was the template file which [[amuleweb|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_Project_FAQ:About|aMule]]'s status.
 
*'''~/.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_Project_FAQ:About|aMule]]'s status.
*'''[[casrc_file|~/.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.
+
*'''[[casrc_file|~/.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.
 
*'''[[clients.met_file|~/.aMule/clients.met]]:''' Contains the public hashes of other known clients along with the credits it owes each of them.
 
*'''[[clients.met_file|~/.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/clients.met.BAK:''' Backup of [[clients.met file]]

Revision as of 20:07, 9 March 2005

English | Nederlands

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:

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.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.

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

  • ~/.aMule/Incoming: By default, the directory where aMule stores the completed downloads.
  • ~/.aMule/Temp: By default, the directory where aMule stores the non-completed downloads (temporary files).
  • ~/.aMule/webserver/: This directory contains the skins for aMuleWeb.