Difference between revisions of "AMule files"
From AMule Project FAQ
| Line 14: | Line 14: | ||
*'''[[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]]. |
| − | *'''[[cryptkey.dat_file|~/.aMule/cryptkey.dat]]:''' It contains the unique 384 bit private [http://www.rsasecurity.com/rsalabs/node.asp?id=2125 RSA] key of your client. | + | *'''[[cryptkey.dat_file|~/.aMule/cryptkey.dat]]:''' It contains the unique 384 bit private [http://www.rsasecurity.com/rsalabs/node.asp?id=2125 RSA] key of your [[client]]. |
*'''[[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]]:''' | *'''[[ED2KLinks_file|~/.aMule/ED2KLinks]]:''' | ||
*'''[[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]] ranges and access levels restrictions which will be passed to ipfilter. | ||
| − | *'''[[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. |
*'''[[known2.met file|~/.aMule/known2.met]]:''' This file stores the verified [[AICH]] hashes of your shared files. | *'''[[known2.met file|~/.aMule/known2.met]]:''' This file stores the verified [[AICH]] hashes of your shared files. | ||
*'''[[lastversion_file|~/.aMule/lastversion]]:''' This is only for [[aMule_Project_FAQ:About|aMule]] to know if it's the first time you're starting [[aMule_Project_FAQ:About|aMule]], if you had [[aMule_Project_FAQ:About|aMule]] installed before and which version you had installed previously. | *'''[[lastversion_file|~/.aMule/lastversion]]:''' This is only for [[aMule_Project_FAQ:About|aMule]] to know if it's the first time you're starting [[aMule_Project_FAQ:About|aMule]], if you had [[aMule_Project_FAQ:About|aMule]] installed before and which version you had installed previously. | ||
| Line 36: | Line 36: | ||
*'''*.part:''' This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As [[aMule_Project_FAQ:About|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:''' This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As [[aMule_Project_FAQ:About|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:''' 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.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.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 [[IP]]s of sources of rare files in the preferences, so that [[aMule_Project_FAQ:About|aMule]] can try to connect to these sources again after a restart. | *'''*.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_Project_FAQ:About|aMule]] can try to connect to these sources again after a restart. | ||
Revision as of 20:09, 9 March 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 old personal configuration file (version prior to aMule 2.0.0).
- ~/.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/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:
- ~/.aMule/ipfilter.dat: This file contains the IP ranges and access levels restrictions which will be passed to ipfilter.
- ~/.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/server_met.old: Backup of server.met file.
- ~/.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/shareddir.dat: Stores the paths to all shared directories.
- ~/.aMule/staticservers.dat: Stores a list of static servers.
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:
