Difference between revisions of "AMule files"

From AMule Project FAQ
Jump to: navigation, search
m (Adjusted Link)
m (Adjusted Links)
Line 18: Line 18:
 
*'''[[emfriends.met file|~/.aMule/emfriends.met]]:''' Contains your friends list configuration.
 
*'''[[emfriends.met file|~/.aMule/emfriends.met]]:''' Contains your friends list configuration.
 
*'''[[ED2KLinks_file|~/.aMule/ED2KLinks]]:''' This file acts as an external interface to add downloads to [[aMule]].
 
*'''[[ED2KLinks_file|~/.aMule/ED2KLinks]]:''' This file acts as an external interface to add downloads to [[aMule]].
*'''[[ipfilter.dat file|~/.aMule/ipfilter.dat]]:''' This file contains the [[IP]] ranges and access levels restrictions which will be passed to [[IPFilter]].
+
*'''[[ipfilter.dat file|~/.aMule/ipfilter.dat]]:''' This file contains the [[IP address|IP]] ranges and access levels restrictions which will be passed to [[IPFilter]].
 
*'''~/.aMule/ipfilter.download:''' This is where [[ipfilter.dat file]]s are temporary downloaded, before being renamed to ''ipfilter.dat'' (if the download succeeds).
 
*'''~/.aMule/ipfilter.download:''' This is where [[ipfilter.dat file]]s 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/ipfilter_static.dat:''' This file contains the [[IP address|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 address|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.
 
*'''[[key_index.dat file|~/.aMule/key_index.dat]]:'''  
 
*'''[[key_index.dat file|~/.aMule/key_index.dat]]:'''  
 
*'''[[known.met file|~/.aMule/known.met]]:''' This file stores the hashes and some details of your shared files like size, path, statics, etc.
 
*'''[[known.met file|~/.aMule/known.met]]:''' This file stores the hashes and some details of your shared files like size, path, statics, etc.
Line 33: Line 33:
 
*'''[[onlinesig.dat_file|~/.aMule/onlinesig.dat]]:''' This is an [[eMule|eMule]] compatible [[signature|OnLineSignature]] file. It's used by other applications to know basic information on [[aMule]]'s stat. See also [[amulesig.dat_file|''amulesig.dat'']] above.
 
*'''[[onlinesig.dat_file|~/.aMule/onlinesig.dat]]:''' This is an [[eMule|eMule]] compatible [[signature|OnLineSignature]] file. It's used by other applications to know basic information on [[aMule]]'s stat. See also [[amulesig.dat_file|''amulesig.dat'']] above.
 
*'''[[preferences.dat_file|~/.aMule/preferences.dat]]:''' Contains the public key of your client on the [[FAQ_eD2k-Kademlia|ed2k]] network, also known as user hash.
 
*'''[[preferences.dat_file|~/.aMule/preferences.dat]]:''' Contains the public key of your client on the [[FAQ_eD2k-Kademlia|ed2k]] network, also known as user hash.
*'''[[preferencesKad.dat_file|~/.aMule/preferencesKad.dat]]:''' Contains the [[IP]] and client ID of your client on the [[Kademlia]] network, that is, your identification keys.
+
*'''[[preferencesKad.dat_file|~/.aMule/preferencesKad.dat]]:''' Contains the [[IP address|IP]] and client ID of your client on the [[Kademlia]] network, that is, your identification keys.
 
*'''[[remote.conf_file|~/.aMule/remote.conf]]:''' Configuration file for [[External Connections]].
 
*'''[[remote.conf_file|~/.aMule/remote.conf]]:''' Configuration file for [[External Connections]].
*'''[[server.met file|~/.aMule/server.met]]:''' This is a list of all known servers and your preferences about them (priority, name, [[IP]], port and such).
+
*'''[[server.met file|~/.aMule/server.met]]:''' This is a list of all known servers and your preferences about them (priority, name, [[IP address|IP]], port and such).
 
*'''~/.aMule/server.met.download:''' This is where [[server.met file]]s are temporary downloaded, before being renamed to ''server.met'' (if the download succeeds).
 
*'''~/.aMule/server.met.download:''' This is where [[server.met file]]s 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 file|server.met]].
 
*'''~/.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 file|server.met]].
Line 56: Line 56:
 
*'''*.part.met.bak:''' This are backups of the ''[[part.met file|*.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.bak:''' This are backups of the ''[[part.met file|*.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 file|*.part.met]]'' while the data is being stored. As soon as [[aMule]] finishes writting the file, it is renamed to ''*.part.met''.
 
*'''*.part.met.backup:''' This are temporal ''[[part.met file|*.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 file|*.part.met.seeds]]:''' This file only exists if you have enabled to store the [[IP]]s of sources of rare files in the preferences, so that [[aMule]] can try to connect to these sources again after a restart.
+
*'''[[part.met.seeds file|*.part.met.seeds]]:''' This file only exists if you have enabled to store the [[IP address|IP]]s 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:
 
The directories in ''~/.aMule/'' have the following use:
Line 69: Line 69:
 
== Version ==
 
== Version ==
 
Created by Jacobo221 on 09.12.04 at 16:36<br>
 
Created by Jacobo221 on 09.12.04 at 16:36<br>
Updated by Vollstrecker on 23.01.08 at 13:05
+
Updated by Vollstrecker on 23.01.08 at 14:36

Revision as of 14:36, 23 January 2008

English | Nederlands | Deutsch | Magyar

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 (On Mac OS X the "~/.aMule" folder corresponds to "~/Library/Application Support/aMule"):

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

Version

Created by Jacobo221 on 09.12.04 at 16:36
Updated by Vollstrecker on 23.01.08 at 14:36