AMule Project FAQ - User contributions [en]

Universal Plug and Play

2007-01-04T23:17:48Z

Phoenix: =The right libupnp for aMule=

'''Universal Plug and Play (uPnP)''' is a new feature of [[aMule]] (CVS) which allows you to automatically configure the ports on your router, provided your router supports uPnP. This functionality is still being tested and should appear soon in an official release.

== External link ==
* [http://en.wikipedia.org/wiki/Universal_Plug_and_Play "Universal Plug and Play"]

== The right libupnp for aMule ==

It is highly recommended to use libupnp version 1.4.1.

You can download the source tarball at the [http://pupnp.sourceforge.net/ sourceforge project page].

There are some user made packages available:

'''OpenSuse 10.2''' by [http://forum.amule.org/profile.php?userid=5567 Gerd78]
* [http://gw78.ja-nee.de/suse/10.2/i586/libupnp-1.4.1-0.i586.rpm libupnp-1.4.1-0.i586.rpm]
* [http://gw78.ja-nee.de/suse/10.2/i586/libupnp-devel-1.4.1-0.i586.rpm libupnp-devel-1.4.1-0.i586.rpm]

'''Ubuntu 6.10''' by [http://forum.amule.org/profile.php?userid=3842 Wuischke]
* [http://wuischke.hateworx.org/download/libupnp/libupnp_1.4.1-1_i386.deb libupnp_1.4.1-1_i386.deb]

'''Fedora Core 4, 5 and 6'''
* Fedora Core libupnp packager (Eric Tangui) has updated the package to the last library version, so please, use the official distribution package.

Firewall SuSE

2007-01-04T01:49:13Z

Phoenix: =The clean way: Restart the daemon=

<h2>By [[User:Tuxlover|Tuxlover]]</h2>

== Preamble ==

This document has been tested on [http://www.suse.com SuSE Linux 8.2] and [http://en.opensuse.org/ OpenSUSE 10.1]

For non-[http://www.suse.com SuSE] distributions help, take a look at [[Firewall|this HowTo]].

== Using [http://www.suse.com SuSE Linux] as a [[client]] machine ==

If you run [http://www.suse.com SuSE Linux] on your client machine which runs a firewall itself, you need to do the following to allow the correct ports to come through:

You basically need to allow [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] and [http://www.faqs.org/rfcs/rfc768.html UDP] ports 4662 and 4672 to be open.

Open ''/etc/sysconfig/SuSEfirewall2'', and locate ''FW_SERVICES_EXT_TCP'' and ''FW_SERVICES_EXT_UDP''. Now add to both of these the above ports:

''FW_SERVICES_EXT_TCP="4662"'' 
''FW_SERVICES_EXT_UDP="4665 4672"''

Note that you should keep ports that are already in there.

After making these changes save the file.

== Using [http://www.suse.com SuSE Linux] as a router/firewall ==

If you use [http://www.suse.com SuSE Linux] on your router/firewall to connect to the internet you can do the following to forward the ports used by [[aMule]]/[[eMule]]/etc to your [[client]]:

Set your firewall to forward all connections coming to it thorugh ports 4662 and 4672 in [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] and [http://www.faqs.org/rfcs/rfc768.html UDP] to your internal client machine.

Open ''/etc/sysconfig/SuSEfirewall2'' and locate ''FW_FORWARD_MASQ'' (it's in ''14.''). Now, assuming your client's [http://www.faqs.org/rfcs/rfc791.html IP] is 192.168.0.3, set this to this value:

''FW_FORWARD_MASQ="0/0,192.168.0.3,tcp,4662 0/0,192.168.0.3,udp,4662 0/0,192.168.0.3,tcp,4672 0/0,192.168.0.3,udp,4672"''

Note that a rule like ''"0/0,192.168.0.3,tcp,4662"'' simply means that incoming [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] connections through port 4662 from any address (0/0) will be forwarded to your the machine 192.168.0.3 on the same port.)

For this to work, you have to have ''FW_ROUTE'' (in ''5.'') set to ''"yes"'' in the same file.

After making these changes, save the file.

== For both: Restarting the firewall ==

Once you finish configurating the firewall, you must restart the firewall daemon for the changes to take effect.

You can restart [http://susefaq.sourceforge.net/articles/firewall/fw_manual.html SuSEfirewall2] through two different ways:

#Restarting the daemon
#Through [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST]

Use the first one whenever possible. If you can't then restart the firewall through [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST].

=== The clean way: Restart the daemon ===

Run:

''/etc/init.d/network force-reload && /etc/init.d/SuSEfirewall2_setup force-reload''

Be aware that if you are connected to the router remotely, if something failed during this process, this could terminate your connection and so, leave the router in an accessible way.

=== The dirty way: [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST] gives us a hand ===

Start [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST]. Go to "Security and users" (or similar), and once there choose "Firewall". Now simply go through all dialogs and end up with them. At the end it will restart your firewall with these new rules.

Firewall SuSE

2007-01-04T01:44:45Z

Phoenix: =Using [http://www.suse.com SuSE Linux] as a client machine=

<h2>By [[User:Tuxlover|Tuxlover]]</h2>

== Preamble ==

This document has been tested on [http://www.suse.com SuSE Linux 8.2] and [http://en.opensuse.org/ OpenSUSE 10.1]

For non-[http://www.suse.com SuSE] distributions help, take a look at [[Firewall|this HowTo]].

== Using [http://www.suse.com SuSE Linux] as a [[client]] machine ==

If you run [http://www.suse.com SuSE Linux] on your client machine which runs a firewall itself, you need to do the following to allow the correct ports to come through:

You basically need to allow [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] and [http://www.faqs.org/rfcs/rfc768.html UDP] ports 4662 and 4672 to be open.

Open ''/etc/sysconfig/SuSEfirewall2'', and locate ''FW_SERVICES_EXT_TCP'' and ''FW_SERVICES_EXT_UDP''. Now add to both of these the above ports:

''FW_SERVICES_EXT_TCP="4662"'' 
''FW_SERVICES_EXT_UDP="4665 4672"''

Note that you should keep ports that are already in there.

After making these changes save the file.

== Using [http://www.suse.com SuSE Linux] as a router/firewall ==

If you use [http://www.suse.com SuSE Linux] on your router/firewall to connect to the internet you can do the following to forward the ports used by [[aMule]]/[[eMule]]/etc to your [[client]]:

Set your firewall to forward all connections coming to it thorugh ports 4662 and 4672 in [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] and [http://www.faqs.org/rfcs/rfc768.html UDP] to your internal client machine.

Open ''/etc/sysconfig/SuSEfirewall2'' and locate ''FW_FORWARD_MASQ'' (it's in ''14.''). Now, assuming your client's [http://www.faqs.org/rfcs/rfc791.html IP] is 192.168.0.3, set this to this value:

''FW_FORWARD_MASQ="0/0,192.168.0.3,tcp,4662 0/0,192.168.0.3,udp,4662 0/0,192.168.0.3,tcp,4672 0/0,192.168.0.3,udp,4672"''

Note that a rule like ''"0/0,192.168.0.3,tcp,4662"'' simply means that incoming [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] connections through port 4662 from any address (0/0) will be forwarded to your the machine 192.168.0.3 on the same port.)

For this to work, you have to have ''FW_ROUTE'' (in ''5.'') set to ''"yes"'' in the same file.

After making these changes, save the file.

== For both: Restarting the firewall ==

Once you finish configurating the firewall, you must restart the firewall daemon for the changes to take effect.

You can restart [http://susefaq.sourceforge.net/articles/firewall/fw_manual.html SuSEfirewall2] through two different ways:

#Restarting the daemon
#Through [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST]

Use the first one whenever possible. If you can't then restart the firewall through [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST].

=== The clean way: Restart the daemon ===

'''Thanks to g-maverick for this tip.'''

Just run:

''/sbin/SuSEfirewall2 stop && /sbin/SuSEfirewall2 start''

Be aware that if you are connected to the router remotely, if something failed during this process, this could terminate your connection and so, leave the router in an accessible way.

=== The dirty way: [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST] gives us a hand ===

Start [http://www.suse.de/en/private/products/suse_linux/prof/yast.html YaST]. Go to "Security and users" (or similar), and once there choose "Firewall". Now simply go through all dialogs and end up with them. At the end it will restart your firewall with these new rules.

Skins

2006-12-25T20:02:20Z

Phoenix: =Procedure=

== Definition ==

A skin (in software context) is a file or group of files which allow an application's interface to change, so that it is more comfortable for each user.

== Using real skins ==

=== Explanation ===

[[aMule]] supports bitmaps skinning, allowing for anyone to change the icons and images displayed in it.

=== Procedure ===

'''CVS tarballs only!'''

Skins are implemented through a text file, just like an .ini file, which will have lines that point to bitmaps. This text file must be specified in Preferences->Gui Tweaks->Skin Support->Skin File.

Of course, to enable skins, the checkbox "Use skin file to set aMule bitmaps" must be checked.

Currently, there are two kinds of skins:
* Client bitmaps
* Toolbar bitmaps

Both must be specified in the same text file. An example file is below. If you omit any option, aMule will use the default image. There are no restrictions on the image sizes, but gui may look weird if they are too big.

'''IMPORTANT:''' eMule toolbar skins (one .png with all images in a row) '''are not supported'''.

<pre>
[Toolbar Bitmaps]
Connect_icon=/home/user/icons/32x32/actions/connect_established.png
Disconnect_icon=/home/user/icons/32x32/actions/connect_no.png
Connecting_icon=/home/user/icons/32x32/actions/connect_creating.png
Network_icon=/home/user/icons/32x32/actions/homepage.png
Transfer_icon=/home/user/icons/32x32/actions/reload.png
Search_icon=/home/user/icons/32x32/actions/find.png
Share_icon=/home/user/icons/32x32/actions/fileopen.png
Messages_icon=/home/user/icons/32x32/apps/kopete.png
Stat_icon=/home/user/icons/32x32/apps/clock.png
Pref_icon=/home/user/icons/32x32/actions/configure.png
Import_icon=/home/user/icons/32x32/actions/kaboodleloop.png
Help_icon=/home/user/icons/32x32/actions/help.png

[Client Bitmaps]
Client_Transfer=/home/user/icons/small/Client_Green_Smiley.png
Client_Connecting=/home/user/icons/small/Client_Red_Smiley.png
Client_OnQueue=/home/user/icons/small/Client_Yellow_Smiley.png
Client_A4AFNoNeededPartsQueueFull=/home/user/icons/small/Client_Grey_Smiley.png
Client_Unknown=/home/user/icons/small/Client_White_Smiley.png
Client_ExtendedProtocol=/home/user/icons/small/Client_ExtendedProtocol_Smiley.png
Client_SecIdent=/home/user/icons/small/Client_SecIdent_Smiley.png
Client_BadGuy=/home/user/icons/small/Client_BadGuy_Smiley.png
Client_CreditsGrey=/home/user/icons/small/Client_CreditsGrey_Smiley.png
Client_CreditsYellow=/home/user/icons/small/Client_CreditsYellow_Smiley.png
Client_Upload=/home/user/icons/small/Client_Upload_Smiley.png
Client_Friend=/home/user/icons/small/Client_Friend_Smiley.png
Client_eMule=/home/user/icons/small/Client_eMule_Smiley.png
Client_mlDonkey=/home/user/icons/small/Client_mlDonkey_Smiley.png
Client_eDonkeyHybrid=/home/user/icons/small/Client_eDonkeyHybrid_Smiley.png
Client_aMule=/home/user/icons/small/Client_aMule_Smiley.png
Client_lphant=/home/user/icons/small/Client_lphant_Smiley.png
Client_Shareaza=/home/user/icons/small/Client_Shareaza_Smiley.png
Client_xMule=/home/user/icons/small/Client_xMule_Smiley.png
Client_Unknown=/home/user/icons/small/Client_Unknown.png
Client_InvalidRatingOnFile=/home/user/icons/small/Client_InvalidRating_Smiley.png
Client_PoorRatingOnFile=/home/user/icons/small/Client_PoorRating_Smiley.png
Client_GoodRatingOnFile=/home/user/icons/small/Client_GoodRating_Smiley.png
Client_FairRatingOnFile=/home/user/icons/small/Client_FairRating_Smiley.png
Client_ExcellentRatingOnFile=/home/user/icons/small/Client_ExcellentRating_Smiley.png
</pre>

== Using generic GTK skins ==

'''NOTE:''' Most [http://windows.microsoft.com Windows] and [[MacOS X]] users will not need to read this chapter, since they won't be using GTK (allthough it is possible to compile aMule linked to GTK on both platforms).

=== Explanation ===

aMule uses [[GTK]], and the GTK library allows all widgets to be skinned. So we can use that to skin aMule.

This is a widget skinning. This means that you can change fonts, colours, shapes, sizes and behaviours of scrollbars, buttons, etc. But you won't be able to change aMule specific images and icons.

Have in mind that this will not only change the widgets aspect and behaviour for aMule, but for all other GTK applications.

=== Procedure ===

First, you must know if you are running aMule linked to GTK1 or to GTK2. Just run:

''amule --version''

You will get something like this:

aMule 2.0.3 using wxGTK2 v2.6.1 (Unicoded) (OS: Linux)

The important part is ''wxGTK2''. This means you are using GTK2. If you see ''wxGTK'' instead (notice there's no ''2''), then you're using GTK1.

Ok, now make sure you have ''switch'' (got GTK1 users) or ''switch2'' (for GTK2 users). If you don't have it, install it.

By running ''switch''/''switch2'' you'll be able to switch the GTK theme. Of course, you'll have to have some GTK theme(s) installed on your system.

You'll also be able to change the font and it's size if you click on the icon at the right of the ''switch''/''switch2'' application.

==== Switch/Switch2 in Debian ====

[[Debian]] users can install ''gtk-theme-switch'' to get both ''switch'' and ''switch2''.

Available themes for GTK1 users are all those whose names begin with ''gtk-engines-*'', such as ''gtk-engines-pixmap''(run ''aptitude search gtk1-engines'' to get all themes available for GTK1)

Available themes for GTK2 users are all those whose names begin with ''gtk2-engines-*'', such as ''gtk2-engines-*'', such as ''gtk2-engines-xfce'' (run ''aptitude search gtk2-engines'' to get all themes available for GTK2)

Skins

2006-12-25T19:59:43Z

Phoenix: =Procedure=

== Definition ==

A skin (in software context) is a file or group of files which allow an application's interface to change, so that it is more comfortable for each user.

== Using real skins ==

=== Explanation ===

[[aMule]] supports bitmaps skinning, allowing for anyone to change the icons and images displayed in it.

=== Procedure ===

'''CVS tarballs only!'''

Skins are implemented through a text file, just like an .ini file, which will have lines that point to bitmaps. This text file must be specified in Preferences->Gui Tweaks->Skin Support->Skin File.

Of course, to enable skins, the checkbox "Use skin file to set aMule bitmaps" must be checked.

Currently, there are two kinds of skins:
* Client bitmaps
* Toolbar bitmaps

Both must be specified in the same text file. An example file is below. If you omit any option, aMule will use the default image.

<pre>
[Toolbar Bitmaps]
Connect_icon=/home/user/icons/32x32/actions/connect_established.png
Disconnect_icon=/home/user/icons/32x32/actions/connect_no.png
Connecting_icon=/home/user/icons/32x32/actions/connect_creating.png
Network_icon=/home/user/icons/32x32/actions/homepage.png
Transfer_icon=/home/user/icons/32x32/actions/reload.png
Search_icon=/home/user/icons/32x32/actions/find.png
Share_icon=/home/user/icons/32x32/actions/fileopen.png
Messages_icon=/home/user/icons/32x32/apps/kopete.png
Stat_icon=/home/user/icons/32x32/apps/clock.png
Pref_icon=/home/user/icons/32x32/actions/configure.png
Import_icon=/home/user/icons/32x32/actions/kaboodleloop.png
Help_icon=/home/user/icons/32x32/actions/help.png

[Client Bitmaps]
Client_Transfer=/home/user/icons/small/Client_Green_Smiley.png
Client_Connecting=/home/user/icons/small/Client_Red_Smiley.png
Client_OnQueue=/home/user/icons/small/Client_Yellow_Smiley.png
Client_A4AFNoNeededPartsQueueFull=/home/user/icons/small/Client_Grey_Smiley.png
Client_Unknown=/home/user/icons/small/Client_White_Smiley.png
Client_ExtendedProtocol=/home/user/icons/small/Client_ExtendedProtocol_Smiley.png
Client_SecIdent=/home/user/icons/small/Client_SecIdent_Smiley.png
Client_BadGuy=/home/user/icons/small/Client_BadGuy_Smiley.png
Client_CreditsGrey=/home/user/icons/small/Client_CreditsGrey_Smiley.png
Client_CreditsYellow=/home/user/icons/small/Client_CreditsYellow_Smiley.png
Client_Upload=/home/user/icons/small/Client_Upload_Smiley.png
Client_Friend=/home/user/icons/small/Client_Friend_Smiley.png
Client_eMule=/home/user/icons/small/Client_eMule_Smiley.png
Client_mlDonkey=/home/user/icons/small/Client_mlDonkey_Smiley.png
Client_eDonkeyHybrid=/home/user/icons/small/Client_eDonkeyHybrid_Smiley.png
Client_aMule=/home/user/icons/small/Client_aMule_Smiley.png
Client_lphant=/home/user/icons/small/Client_lphant_Smiley.png
Client_Shareaza=/home/user/icons/small/Client_Shareaza_Smiley.png
Client_xMule=/home/user/icons/small/Client_xMule_Smiley.png
Client_Unknown=/home/user/icons/small/Client_Unknown.png
Client_InvalidRatingOnFile=/home/user/icons/small/Client_InvalidRating_Smiley.png
Client_PoorRatingOnFile=/home/user/icons/small/Client_PoorRating_Smiley.png
Client_GoodRatingOnFile=/home/user/icons/small/Client_GoodRating_Smiley.png
Client_FairRatingOnFile=/home/user/icons/small/Client_FairRating_Smiley.png
Client_ExcellentRatingOnFile=/home/user/icons/small/Client_ExcellentRating_Smiley.png
</pre>

== Using generic GTK skins ==

'''NOTE:''' Most [http://windows.microsoft.com Windows] and [[MacOS X]] users will not need to read this chapter, since they won't be using GTK (allthough it is possible to compile aMule linked to GTK on both platforms).

=== Explanation ===

aMule uses [[GTK]], and the GTK library allows all widgets to be skinned. So we can use that to skin aMule.

This is a widget skinning. This means that you can change fonts, colours, shapes, sizes and behaviours of scrollbars, buttons, etc. But you won't be able to change aMule specific images and icons.

Have in mind that this will not only change the widgets aspect and behaviour for aMule, but for all other GTK applications.

=== Procedure ===

First, you must know if you are running aMule linked to GTK1 or to GTK2. Just run:

''amule --version''

You will get something like this:

aMule 2.0.3 using wxGTK2 v2.6.1 (Unicoded) (OS: Linux)

The important part is ''wxGTK2''. This means you are using GTK2. If you see ''wxGTK'' instead (notice there's no ''2''), then you're using GTK1.

Ok, now make sure you have ''switch'' (got GTK1 users) or ''switch2'' (for GTK2 users). If you don't have it, install it.

By running ''switch''/''switch2'' you'll be able to switch the GTK theme. Of course, you'll have to have some GTK theme(s) installed on your system.

You'll also be able to change the font and it's size if you click on the icon at the right of the ''switch''/''switch2'' application.

==== Switch/Switch2 in Debian ====

[[Debian]] users can install ''gtk-theme-switch'' to get both ''switch'' and ''switch2''.

Available themes for GTK1 users are all those whose names begin with ''gtk-engines-*'', such as ''gtk-engines-pixmap''(run ''aptitude search gtk1-engines'' to get all themes available for GTK1)

Available themes for GTK2 users are all those whose names begin with ''gtk2-engines-*'', such as ''gtk2-engines-*'', such as ''gtk2-engines-xfce'' (run ''aptitude search gtk2-engines'' to get all themes available for GTK2)

Skins

2006-12-25T19:27:35Z

Phoenix: =Explanation=

Skins

2006-12-25T17:45:35Z

Phoenix: =Explanation=

FAQ aMule-de

2006-12-09T20:14:27Z

Phoenix: =Unterstützt aMule Universal Plug and Play (UPnP)?=

<center>
<h4>F.A.Q auf [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]'' (Übersetzt durch ''nachbarnebenan'')</h2>

[[FAQ_aMule|English]] | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | '''Deutsch''' | [[FAQ_aMule-nl|Nederlands]] | [[FAQ_aMule-ru|Russian]]
</center>

== Was ist denn dieses ominöse [[aMule_Project_FAQ:About|aMule]] eigentlich? ==

'''''[[aMule]] ist ein plattformunabhängiger Client für das [[FAQ_eD2k-Kademlia-de|eDonkey/eMule Filesharing Netzwerk]], entstanden im August 2003 aus einer Abspaltung von [[xMule]], das wiederum eine Abspaltung von [[lMule]], das wiederum eine Portierung des nur-Windows Clients [[EMule-de|eMule]] ist.'''''

Im Moment ist es unter GNU/Linux, FreeBSD und OpenBSD, MacOSX, Windows und der X-Box sowohl auf 32- als auch 64bit Systemen lauffähig. Die Windows-Version ist allerdings noch nicht wirklich für den produktiven Einsatz geeignet.

Es ist beabsichtigt, dass [[aMule-de|aMule]] genauso funktionell und einfach zu benutzen ist, wie [[EMule-de|eMule]] und auch genauso aussieht, so dass Nutzer, die mit einem der beiden vertraut sind, ohne Schwierigkeiten zwischen beiden wechseln können.

Da [[aMule_Project_FAQ:About|aMule]] auf den Quellen von [[EMule-de|eMule]] basiert, finden neue Funktionen sehr schnell ihren Platz in [[aMule]], nachdem sie in [[EMule-de|eMule]] eingebaut wurden, so dass auch die Nutzer von [[aMule_Project_FAQ:About|aMule]] sicher sein können, sich immer an der Spitze der Entwicklung der [[FAQ_eD2k-Kademlia-de|ED2k]] Clients zu befinden.

Nicht unwichtig ist, dass es von einem großartigen Team entwickelt wird, dass (sofern das überhaupt möglich ist), vielleicht noch nutzerfreundlicher und -bezogener ist, als [[aMule_Project_FAQ:About|aMule]] selbst. Daher schauen Sie auch mal bei #amule auf irc.freenode.net vorbei oder besuchen Sie [http://www.amule.org/amule unsere Foren], wenn Sie Fragen oder Probleme haben, oder einfach nur einen guten Vorschlag, was man besser machen könnte.

Möchten Sie vielleicht sogar dem Entwicklerteam beitreten, melden Sie sich bitte in den Foren oder im IRC.

== Wie kann man sich die Credits eines Clients ansehen? ==

Man kann sich die Credits eines Clients (was man ihm schuldet) ansehen, wenn man auf seinen Namen rechts klickt und Details anzeigen auswählt. Die Credits haben keinen bestimmten Wert, man kann sich entweder die gesamtübertragene Datenmenge, die man von diesem Clients bekommen hat, ansehen oder den Credit Modifikator (DL/UL Modifikator). Das Fenster zeigt auch, wenn der Client in der Uploadwarteschlange steht, seine Position und seine Bewertung.

== Was bedeuten diese ganzen Farben in der Fortschrittsanzeige? ==

In der Liste der Downloads:
'''Rot:''' Für Blöcke in rot wurden in der aktuellen Sitzung noch keine Quellen gefunden.
'''Blau:''' Blöcke in blau haben mindestens eine nutzbare Quelle, je dunkler das Blau ist, desto mehr Quellen gibt es.
'''Gelb:''' Gerade in diesem Moment heruntergeladenen Blöcke werden gelb dargestellt.
'''Schwarz:''' Schwarze Blöcke wurden bereits fertig heruntergeladen und überprüft.
'''Grün:''' Sobald eine Datei komplett fertiggestellt ist, wird sie grün dargestellt (und ist dann im Eingangsverzeichnis zu finden).

Auf der ausführlichen Downloadliste (aufzurufen durch Doppelklick auf einen einzelnen Transfer):
'''Schwarz:''' Der Client hat diesen Chunk, wir aber noch nicht.
'''Weiß:''' Diesen Chunk hat der Client nicht.
'''Grün:''' Wir haben diesen Chunk beide.
'''Gelb:''' Dieser Chunk wird gerade von diesem Client zu uns heraufgeladen.

Auf der Uploadliste:
'''Schwarz:''' Diesen Chunk hat der Client fertiggestellt und überprüft.
'''Grau:''' Der Client hat diesen Chunk nicht.

Beachten Sie, dass nicht alle Clients die Fähigkeite haben, anderen beim Upload zu sagen, welche Teile sie bereits haben, daher haben manche Clients keine Anzeige der einzelnen Blöcke.

Bei den freigegebenen Dateien:
'''Rot:''' Außer uns gibt es keine andere Quelle dieses Chunks.
'''Blau:''' Umso dunkler das Blau ist, umso mehr Clients haben diesen Teil.

Auf der Suchseite:
'''Schwarz:''' Für schwarze Dateien wurde nur ein Clients gefunden, der sie hat.
'''Blau:''' Dateien in blau haben mindestens zwei Quellen, je dunkler das Blau, desto mehr.
'''Rot:''' Rote Dateien befinden sich bereits in der Downloadliste.
'''Grün:''' Bereits vollständig heruntergeladene Dateien werden auch hier in grün dargestellt.

== Was bedeuten diese ganzen Icons? ==

Siehe [[Getting_Started-de#Icons_und_was_sie_bedeuten|hier]].

== Was bedeuten die Zahlen in Klammern im Suchfenster? ==

Sie zeigen die Zahl der Clients an, die bekanntermaßen die Datei vollständig haben. Aber auch wenn die Anzahl 0 ist, heißt das noch lange nicht, dass keiner sie komplett hat, nur, dass sie keiner als "komplett" markiert hat (viele Clients tun dies). Trotzdem kann man so einen Eindruck davon gewinnen, wieviele Leute die Datei vollständig haben, auch wenn es keine Gewissheit ist.

== Was bedeuten die ganzen Zahlen in der Quellen-Spalte in der Transferliste? ==

Das Format der Quellenangabe ist XX/YY + ZZ (WW), wobei
*'''XX''' für die Anzahl der verfügbaren Quellen steht (von denen man downloaden kann),
*'''YY''' für die Gesamtanzahl an gefundenen Quellen steht,
*'''ZZ''' für die Anzahl der Quellen, die "nach einer anderen Datei gefragt" worden sind (A4AF), und
*'''WW''' für die Anzahl der Quellen steht, von denen wir gerade einen Chunk herunterladen.

== Wofür stehen die Zahlen in der Spalte Priorität in der aufgeklappten Downloadliste? ==

Das ist die Warteschlangenposition, die man beim jeweiligen Client einnimmt. Nicht alle Clients geben diese an, daher steht in manchen Fällen dort einfach nichts.

Die Zahl in Klammern gibt die Positionen an, die man sich schon in der Warteschlange des Clients *bewegt* hat. '''Negative''' Zahlen stehen für '''vorangeschrittene'' Positionen, '''positive''' für verlorene. Wenn negativ, wird die Zahl blau dargestellt, bei positiv rot.

== Warum werden in der Uploadliste zwei Geschwindigkeiten angegeben? ==

Wenn man zu einem Client hochlädt, zeigt die Uploadliste die Geschwindigkeit (in Kilobyte pro Sekunde) zu diesem Client an, wenn nun, zur gleichen Zeit, dieser Client auch zu uns hochlädt, verändert sich die Anzeige zu XX/YY, wobei XX für unsere und YY für seine Uploadgeschwindigkeit steht. Wenn man in der Downloadliste sucht, wird man diesen Client finden.

Dies ist besonders nützlich, wenn man versucht, eine seltene Datei zu bekommen, da man sehen kann, was der Client zu einem hochlädt und, wenn es die gesuchte Datei ist, ihm einen Uploadplatz für Freunde vergeben kann, so dass man schneller zu ihm hochlädt, man damit mehr Credits bekommt und folglich auch schneller von ihm herunterladen kann.

== Was ist A4AF? ==

A4AF (Asked for/4 another File) bedeutet ''nach anderer Datei gefragt''. Damit werden die Ressourcen eines bestimmten Downloads optimiert.

Wenn man eine Datei downloaded, holt sich aMule eine Liste aller Clients, die diese Datei haben. Einige davon haben möglicherweise auch andere Dateien, die man herunterladen möchte, daher kann man einen Client bei mehreren separaten Downloads haben.

A4AF versucht, dies zu vermeiden. Warum? Man kann nicht zwei Blöcke zur gleichen Zeit vom gleichen Client herunterladen. Durch das Aktivieren von A4AF sagt man aMule, nach Clients zu suchen, die sowohl bei dieser als auch bei anderen Dateien in der Downloadliste stehen, und sie bei den anderen zu entfernen. Dadurch bekommt man für diese Datei mehr Quellen.

Man kann auch einen Download auf das Gegenteil setzen, um A4AF andersherum anzuwenden, also Quellen an andere Downloads abzugeben. Das sollte für Dateien getan werden, die nicht so dringend sind, oder erst nach einer anderen ähnlichen Datei heruntergeladen werden sollen (z.B. bei einer Serie von Dateien).

Man kann das als eine Möglichkeit, persönliche Vorlieben in den Downloads einzustellen, ansehen.

Wenn eine Quelle gewechselt wird, bleibt der Platz in der Warteschlange dabei erhalten.

'''HINWEIS:''' Quellen mit einem Warteschlangenplatz kleiner als 50 beim Download mit der höheren Priorität werden niemals ausgewechselt. Damit wird sichergestellt, dass der Download auch beginnt.

== Was bedeuten die Zahlen bei "QR: xxxx", die ich sehe, wenn ich mir meine Quellen anschaue? ==

QR bedeutet "Queue Rank", also sinngemäß etwa "Warteschlangenplatz", und bezeichnet die momentane Position in der Warteschlange dieser Quelle.

Offensichtlich ist ein niedrigerer Wert besser. Falls die Quelle ein eMule-Client ist, und hinter "QR" keine Zahl steht, ist dessen Warteschlange vermutlich voll, und er kann keine weiteren Clients mehr annehmen.

== Wo ist der Unterschied zwischen "übertragen" und "fertiggestellt" in der Downloadliste? ==

Übertragen ist die Gesamtmenge an Daten, die man für die ausgewählte Datei erhalten hat. Die Daten sind komprimiert, sobald sie ankommen, werden sie von aMule verarbeitet und entpackt. Die Gesamtmenge an Nutzdaten (also die Teile, die wirklich zur Datei gehören, alles andere sind Header, Prüfsummen usw.) kann in der Spalte Fertiggestellt abgelesen werden.

== Was ist der Unterschied zwischen Pausieren und Stoppen eines Downloads? ==

Wen ein Download pausiert, werden alle Verbindungen die zu diesem Download gehören getrennt so dass keine Daten mehr übertragen werden, die Quellen werden aber beibehalten, bei der Wiederaufnahme wird aMule also versuchen, die Quellen wieder zu kontaktieren.

Wird ein Download gestoppt, werden auch die Quellen verworfen, bei der Wiederaufnahme wird aMule als von neuem beginnen, Clients zu finden, die diese Datei haben.

== Wofür sind die ganzen Dateien, die [[aMule_Project_FAQ:About|aMule]] beim ersten Start anlegt? ==

Die meisten gleichen denen von [[EMule-de|eMule]].

Genauere Informationen und eine detailierte Liste aller [[aMule]] Dateien findest du [[AMule_files-de|hier]].

== Kann man die Dateien und Einstellungen von [[eMule|eMule]] benutzen und umgekehrt? ==

Das meiste ja. Lediglich die Programmkonfiguration (preferences.ini bei [[eMule]] und ~/.aMule bei [[aMule_Project_FAQ:About|aMule]]) sind nicht zwischen [[aMule_Project_FAQ:About|aMule]] und [[eMule]] austauschbar. Alle das [[FAQ_eD2k-Kademlia|ED2K-Netzwerk]] betreffenden Dateien sind problemlos verwendbar, sie müssen nur aus dem [[eMule]]-Verzeichnis nach ~/.aMule kopiert werden - oder umgekehrt. Allerdings sind einige Dateien in ~/.aMule [[aMule_Project_FAQ:About|aMule]]-spezifisch, z.B. amulesig.dat und aMule.tmpl, daher ist es besser, nur die Dateien zu kopieren, die sowohl im [[aMule_Project_FAQ:About|aMule]]-, als auch im [[eMule]]-Verzeichnis vorhanden sind.

Die noch nicht abgeschlossenen Downloads zu übernehmen ist leicht: Einfach die Dateien aus dem [[eMule]]-Temp-Verzeichnis (standardmäßig ''C:\Programm Dateien/eMule\Temp'') nach ''~/.aMule/Temp'' kopieren, bzw. in das eingestellte Temp-Verzeichnis von aMule.

== Was hat es mit amulesig.dat und onlinesig.dat auf sich? ==

[[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|Weiter oben]] wurde bereits beschrieben, wofür die Dateien amulesig.dat und onlinesig.dat Verwendung finden. Hier wird der Inhalt beschrieben (Berücksichtigen Sie bitte, dass bei einem Absturz von [[aMule_Project_FAQ:About|aMule]] der Inhalt dem zuletzt geschriebenen entspricht):

onlinesig.dat

*Besteht aus zwei Zeilen, getrennt durch LF (kein CR dazwischen). Die erste enthält, wenn [[aMule_Project_FAQ:About|aMule]] offline ist, nur eine 0 und nichts weiter. Ist [[aMule_Project_FAQ:About|aMule]] online, dann eine 1, gefolgt vom Pipe-Symbol |, dem Namen des Server mit dem aMule verbunden ist, einem weiteren Pipe-Symbol, der IP des Servers, weil's so schön war noch einem Pipe und zuletzt dem Port des Servers.
*Die zweite Zeile enthält, in dieser Reihenfolge: Die Downloadrate, die Uploadrate und den Füllgrad der Warteschlange, alles ebenfalls mit jeweils einem Pipe-Symbol voneinander getrennt.
*Die zweite Zeile endet übrigens '''nicht''' mit einem Newline ('\n').
*Wird [[aMule_Project_FAQ:About|aMule]] ordnungsgemäß beendet, behält die zweite Zeile ihre Form, aber alle Einträge sind mit Null gefüllt, die erste Zeile enthält dann nur eine einzele Null.

amulesig.dat

Die [[signature|Signatur]]-Datei von aMule ist sehr viel leistungsfähiger als die von [[eMule]]. Jede Zeile ist ein Datenfeld mit folgendem Inhalt:
*Die erste Zeile enthält eine Null wenn [[aMule_Project_FAQ:About|aMule]] nicht verbunden oder regulär beendet ist, eine 1 wenn online und eine 2 wenn gerade eine Verbindung aufgebaut wird (erst seit 2.0.0-rc4).
*Die zweite, dritte und vierte Zeile enthalten den Namen, IP und Port des Servers, mit dem aMule verbunden ist (in dieser Reihenfolge), oder Null wenn aMule offline ist. Ab 2.0.0-rc4 enthalten sie auch dann Null, wenn aMule beim Verbinden oder ordentlich beendet ist.
*In der fünften Zeile steht ein großer L oder H, je nachdem ob [[aMule_Project_FAQ:About|aMule]] mit einer hohen (H) oder niedrigen (L) ID verbunden ist. Beginnend mit 2.0.0-rc4 enthält auch diese Zeile eine Null, wenn aMule noch verbindet oder korrekt beendet ist.
*Die sechste und siebte Zeile enthalten die aktuelle Download- und Uploadgeschwindigkeit, seit 2.0.0-rc4 enthalten sie "0." wenn aMule normal beendet wurde.
Achte und neunte Zeile zeigen die Anzahl der Clients in der Uploadwarteschlange *und die Menge der freigegebenen Dateien. Auch hier stehen seit 2.0.0-rc4 jeweils Null, wenn aMule beendet wurde.
*Der Spitzname des Benutzers steht in der zehnten Zeile.
*In der elften und zwölften Zeile sind die Gesamtsummen von Download- und Uploadmengen aufgeführt.
*Die verwendete Version von [[aMule_Project_FAQ:About|aMule]] ist in der dreizehnten Zeile zu finden.
*Die Anzahl der in der aktuellen Sitzung von aMule herunter- und hochgeladenen Bytes sind in der vierzehnten und fünfzehnten Zeile zu finden, ab 2.0.0-rc4 sind beide Null, wenn aMule beim Verbinden oder ordentlich beendet ist.
*In der sechzehnten (und letzten) Zeile steht die Zeit, die [[aMule_Project_FAQ:About|aMule]] nun schon läuft. Nach einem Leerzeichen kommt "secs" "mins" oder "hours", oder die Entsprechung in der jeweils eingestellten Landessprache. Ab 2.0.0-rc4 steht hier 00 gefolgt von "secs" bzw. der jeweiligen *Abkürzung, falls aMule beendet oder noch beim Verbinden ist.
*Die letzte Zeile wird mit einem Newline ('\n') beendet.

== Ich habe [[aMule_Project_FAQ:About|aMule]] gerade zum ersten Mal installiert, was muss ich einstellen? ==

aMule zu konfigurieren ist größtenteils eine Frage des Geschmacks und hängt von vielen Faktoren ab. Für einen Konfigurations-Crashkurs einfach weiterlesen.

Starten Sie [[aMule_Project_FAQ:About|aMule]] und klicken Sie auf Einstellungen. Denken Sie sich einen Spitznamen aus und wählen Sie die gewünschte Sprache, in der [[aMule_Project_FAQ:About|aMule]] erscheinen soll. Wechseln Sie dann auf den Punkt Verbindungen und geben Sie die maximalen Kapazitäten Ihres Anschlusses sowie die von [[aMule_Project_FAQ:About|aMule]] davon zu verwendende Bandbreite ein. Gehen Sie auf den Punkt Verzeichnisse und legen Sie das temporäre (wo unvollständige Downloads abgelegt werden) und das Eingangsverzeichnis fest. Dann wählen Sie die Verzeichnisse, deren Dateien für andere freigegeben werden sollen. Geben Sie nicht zu viele Dateien frei (siehe unter "Welches sind die besten Einstellungen, um eine optimale Downloadrate zu erzielen?") und wählen Sie keine Dateien mit kritischen Inhalten (e.g. ~/.ssh usw.). Um ein Verzeichnis rekursiv samt seiner Unterverzeichnisse auszuwählen, lesen Sie bitte unter [[aMule_problems#Is there any way to recursively select a whole directory and its contents?]] nach.

== Kann [[aMule_Project_FAQ:About|aMule]] meine [[xMule]]- und [[lMule]]-Dateien verarbeiten? Und wie? ==

[[aMule_Project_FAQ:About|aMule]] handhabt sowohl [[lMule]]- als auch [[xMule]]-Konfigurationsdateien automatisch, aber auf verschiedene Weise: [[lMule]] wird seit mehreren Jahren nicht mehr weiterentwickelt, daher geht aMule davon aus, dass Sie es ersetzen wollen. Daher wird das Verzeichnis ~/.lMule in ~/.aMule umbenannt. Wenn Sie ~/.lMule/Temp und ~/.lMule/Incoming als temporäres und Eingangsverzeichnis verwendet haben, müssen Sie dies nachfolgend in den Einstellungen auf ~/.aMule/Temp und ~/.aMule/Incoming ändern.

[[xMule]] ist seit Mai 2004 offiziell eingestellt (öffentliche Bekanntgabe durch den Hauptentwickler im [[xMule]]-Forum der mittlerweile nicht mehr existenten Seite [http://www.xmule.org http://www.xmule.org]), aus historischen Gründen lässt [[aMule_Project_FAQ:About|aMule]] das ~/.xMule Verzeichnis aber unangetastet und kopiert nur die Konfigurationsdateien nach ~/.aMule. Das bedeutet, dass alle Downloads im ~/.xMule Verzeichnis verbleiben, wenn sie dort abgelegt wurden, aber da [[aMule_Project_FAQ:About|aMule]] die Konfiguration von [[xMule]] übernommen hat, wird es sie weiterhin benutzen. Entweder man lässt es so oder man man verschiebt ~/.xMule/Temp und ~/.xMule/Incoming nach ~/.aMule und ändert die Einstellungen entsprechend.

== Wie fange ich denn nun mit [[aMule_Project_FAQ:About|aMule]] an? ==

Klicken Sie einfach den Verbinden-Knopf. Dafür benötigen Sie allerdings gültige Einträge in der Serverliste, sollte das nicht der Fall sein, klicken Sie vorher im Server-Fenster auf den kleinen Knopf unter dem Verbinden-Knopf und die Liste wird neu geholt. Nach einer Weile wird sich [[aMule_Project_FAQ:About|aMule]] mit einem Server verbinden (das merken Sie daran, dass die Meldung "nicht verbunden" in der unteren rechten Ecke verschwinden). Sobald Sie verbunden sind, wechseln sie ins Suchen-Fenster und suchen Sie nach den gewünschten Dateien. Haben Sie sie gefunden, können Sie mit einem Doppelklick darauf den Download anstoßen.

Für allgemeine Hinweise zu Benutzung von [[aMule_Project_FAQ:About|aMule]] kommen Sie nach #amule auf irc.freenode.net oder fragen Sie in den Foren auf [http://www.amule.org/amule http://www.amule.org/amule] um Rat.

== Welches sind die besten Einstellungen, um eine optimale Downloadrate zu erzielen? ==

Wenn Sie "Welche Grenzen hat das [[FAQ_eD2k-Kademlia|ED2K]]-Netzwerk?" verstanden haben, wissen Sie, dass es das Beste ist, sofern ihre Anbindung dies erlaubt, die Uploadbandbreite auf ein Minimum von 10KB/s zu stellen. Außerdem, wenn sie "Was hat es mit all den Credits, Wertungen und Punkten auf sich?" gelesen haben, sollten Sie wissen, dass mit der uploadrate auch Ihre downloadrate steigt. Setzen Sie also den Upload so hoch wie möglich, geben sie bekannte und beliebte Dateien frei (stellen Sie nicht zuviele Dateien zur Verfügung (nicht mehr als etwa 200), da Sie sonst womöglich von einigen Server aufgrund zu hohen Traffics abgelehnt werden) und versuchen Sie, auch kleinere, populäre Dateien vorzuhalten, da einige Clients zusätzliche Credits vergeben, wenn Sie ihnen eine komplette kleinere Datei liefern können. Ein guter Rat (vielen Dank an kaouete) ist es, bei einer seltenen oder "niemals fertig werden wollenden" Datei einem Client, der Ihnen ein Stück davon hochlädt, einen Freundes-Uploadplatz zuzuweisen, so dass er, wenn er etwas von Ihnen herunterladen will, sofort zum Zug kommt und Sie im Gegenzug bessere Credits erhalten.

== Gibt es einen Weg, alle ED2K-Links aus einer Textdatei auf einmal zu laden? ==

Ja, gibt es. Speichern Sie einfach alle Links, die Sie downloaden wollen, in einer Textdatei, jeweils einen pro Zeile, nennen Sie diese Datei ''EDED2KLinks'', plazieren Sie sie in ''~/.aMule'' und aMule wird sie automatisch finden, die enthaltenen Links der Downloadliste hinzufügen und die Datei löschen.

[[ED2KLinks_file|Hier]] können Sie mehr über die Funktion dieser Datei nachlesen.

== Kann man [[aMule_Project_FAQ:About|aMule]] genauso mittels telnet fernsteuern, wie das bei [[eDonkey2000|eDonkey]] der Fall ist? ==

Ja, das geht, aber nicht auf genau die gleiche Weise, wie bei [[eDonkey2000|eDonkey]]. Starten Sie einfach eine normale ssh-Verbindung zum Computer, auf dem [[aMule_Project_FAQ:About|aMule]] läuft und verbinden Sie sich mittels <code>amulecmd</code> zu [[aMule_Project_FAQ:About|aMule]]. Um neue Downloads anzustoßen, benutzen Sie den Befehl [[ed2k_command|ed2k]]. Damit das funktioniert, muss [[aMuleCMD]] allerdings vorher konfiguriert werden.

Für Sie vielleicht auch interessant ist ein anderes Tool, [[CAS]] (Aufruf mit <code>cas</code>), das grundlegende Statistiken über [[aMule_Project_FAQ:About|aMule]] anzeigt.

Ansonsten bliebe da noch der [[amuleweb|aMule WebServer]], wenn es Sie nicht stört, dass Sie zu seiner Nutzung einen Webbrowser auf dem CLient laufen lassen müssen. Auch der aMule WebServer muss vorher konfiguriert werden.

== Bekommt man [[aMule_Project_FAQ:About|aMule]] auch ohne grafische Oberfläche zum Laufen? ==

Ja. Beginnend mit aMule 2.0.0-rc6 kann man dafür den aMule Daemon benutzen (zu starten mit <code>amuled</code>). Zu kontrollieren ist er genauso wie der "normale" aMule, also via Browser oder aMuleCMD.

Bis Version 2.0.0-rc6 war [[aMule_Project_FAQ:About|aMule]] ein monolithisches Programm, Netzwerkteil und Oberfläche waren zu einem einzigen, riesigen Klotz verschmolzen. Seitdem haben die Entwickler begonnen, stückweise beide Teile voneinander zu trennen.

Für diejenigen, die noch eine ältere Version benutzen oder die aMuleD (aMule Daemon) nicht verwenden möchten, gibt es noch zwei andere Möglichkeiten, aMule ohne GUI laufen zu lassen, diese sind aber indirekt:
*Einmal mittels ''[http://x.org/4.4.0/Xvfb.1.html Xvfb]''
*Oder via ''[http://www.realvnc.com VNC]''

'''Mittels ''[http://x.org/4.4.0/Xvfb.1.html Xvfb]:'''

Dazu starten Sie <code>[http://x.org/4.4.0/Xvfb.1.html Xvfb]</code> und darin dann aMule. Danach können Sie aMule auf die übliche Weise mit [[aMuleCMD]] und [[ed2k_command|ed2k]] kontrollieren, als würden Sie es über ssh benutzen (siehe oben).

Einfaches Beispiel:
*Start von [http://x.org/4.4.0/Xvfb.1.html Xvfb]: <code>Xvfb :1 -screen 0 640x480x16 &</code>
*Das zu verwendende X-Display für aMule setzen: <code>export DISPLAY=:1</code>
*Als letztes [[aMule_Project_FAQ:About|aMule]] aufrufen: <code>amule &</code> />

'''Hinweis:''' Nachdem mit <code>export DISPLAY=:1</code> die X-Ausgabe auf den Xvfb gesetzt wurde, gilt das für '''alle''' X-Anwendungen, die von dieser Shell aufgerufenw erden. Möchten Sie das vermeiden, starten Sie [[aMule_Project_FAQ:About|aMule]] wie folgt, um die Änderung auf es zu begrenzen: <code>DISPLAY=:1 amule &</code>

'''Via ''[http://www.realvnc.com VNC]:'''

Statt [http://x.org/4.4.0/Xvfb.1.html Xvfb] kann man auch ''vncserver'' benutzen, um etwas Ähnliches zu erreichen. Installieren Sie einfach RealVNC und starten Sie ''vncserver :1 -geometry 1024x768'' gefolgt von ''export DISPLAY=:1''. Das erzeugt einen im Hintergrund laufenden [http://x.org X]-Server, auf den mit einem [http://www.realvnc.com VNC]-Client zugegriffen werden kann. Sobald der [http://x.org X]-Server läuft, benötigen Sie noch einen Windowmanager. (Genaugenommen brauchen Sie ihn nicht, aber es ist nützliche, aMule einfach schließen zu können, anstatt es "abschießen" zu müssen) [http://fluxbox.sourceforge.net FluxBox] ist aufgrund seines geringen Speicher- und CPU-Verbrauchs empfehlenswert (aber auch andere, kleine Windowmanager wie twm erfüllen diesen Zweck). Einfach mit ''fluxbox &'' starten und danach aMule via ''amule &''. Jetzt können Sie sich zum [http://www.realvnc.com VNC]-Server verbinden und das [[aMule]]-Fenster ganz normal verwenden.

Berücksichtigen Sie bitte, dass, wenn [[aMule]] ein Dialogfenster anzeigt, dass auf eine Nutzereingabe wartet (wie es beim ersten Start geschieht), es stehenbliebt, bis sich jemand mit dem VNV verbindet und den Dialog schließt. Normalerweise ist das nur einmal nötig (später kann die Verbindung benutzt werden, um Einstellungen zu verändern oder die Serverliste neu zu laden), und [[aMule]] sollte ab dann ohne Hilfe des Nutzers starten und lediglich Statusinformationen anzeigen.

Wenn Sie Hilfe zu diesem Thema benötigen, suchen Sie in [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule Foren] oder kommen Sie in den [[IRC]]-Kanal #amule auf irc.freenode.net und fragen Sie einfach.

== Kann ich zwei Instanzen von [[aMule_Project_FAQ:About|aMule]] zur gleichen Zeit laufen lassen? ==

Ja, obwohl das nicht empfehlenswert ist. aMule prüft nur, ob der aktuelle Benutzer bereits eine Instanz laufen hat, es können also soviele gleichzeitig laufen, wie es Benutzer auf dem System gibt.
Dafür startet man aMule einfach mit <code>sux user -c amule &</code> unter einer anderen Benutzerkennung.

Aber Vorsicht, aMule kann nur feststellen, ob der aktuelle Benutzer bereits auf dem gleichen X Display eine Instanz laufen hat. Wenn also unter dem aktuellen Account bereits ein aMule auf einem anderen Display läuft, darf man keinen zweiten starten, da es sonst fehlerhafte Konfigurationseinstellungen und beschädigte temporäre Dateien geben kann.

== Woher bekommt man diese hübschen [[aMule_Project_FAQ:About|aMule]]-Statistiken, die die Leute im IRC posten? ==

Sie können entweder die Ausgabe von [[CAS]] (C [[aMule_Project_FAQ:About|aMule]] Statistik, [[CAS]] ist mit <code>cas</code> zu starten) oder, wenn Sie xChat als IRC-Client benutzen und das Perl-Modul installiert haben, [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistik) verwenden.

== Was ist Slot-Zuweisung? ==

Jeder Upload ist ein Slot, wenn Sie also zu fünf Clients zur gleichen Zeit hochladen, haben Sie fünf bestehende Slots. Slot-Zuweisung ist die Uploadbandbreite, die jedem Slot zugewiesen ist.

Zum Beispiel: Wenn Sie ein Upload-Limit von 20KB/s haben, können Sie die Slot-Zuweisung auf 2KB/s setzen, dann werden maximal 10 Clients in der Lage sein, gleichzeitig von Ihnen herunterzuladen, jeder mit einer maximalen Übertragungsrate von 2KB/s.

Siehe aber auch "Warum ignoriert aMule die Bandbreiteneinstellung per Slot?" in [[AMule_problems|Häufig auftretende Probleme mit aMule]].

== Was ist ein Freundes-Slot? ==

Ein Freundes-Slot wird speziell einem Client aus der Freundesliste zugewiesen, nur einer kann einen solchen zu jedem Zeitpunkt haben. Wenn der Freund (für den der Slot aktiviert wurde) versucht, einen Chunk herunterzuladen, bekommt er sofort die höchste Priorität in der Uploadwarteschlange, da ihm der Slot fest zugeteilt ist. Solange der Freund nichts herunterlädt, wird der Slot dem Client mit der höchsten Warteschlangenwertung zugeteilt, genau wie erwartet.

== Warum sollte man die maximalen Leitungskapazitäten in den Einstellungen angeben? Sollten [[aMule_Project_FAQ:About|aMule]] denn nicht nur die Bandbreiten-Beschränkungen interessieren? ==

Tatsächlich kümmern aMule nur die Bandbreitenlimits, die Leitungskapazitäten werden nur für die Statistik benötigt. Beispiel: Man hat eine 100KB/s-Anbindung, das Limit wird auf 40KB/s gesetzt, da ein auf dem gleichen Host laufender Webserver mindestens 60KB/s für die Befriedigung der Anfragen benötigt. Nun lädt man einige seltene freie indonesische Stücke herunter, man bekommt nie mehr als 3KB/s im Download. Damit die Grafik im Statistikfenster sinnvolle Aussagekraft hat, setzt man die Downloadkapazität auf 5KB/s, denn bei 100KB/s wäre lediglich ein horizontaler Strich ohne jeden Informationsgehalt zu sehen.

== aMule stürzt recht oft ab, kann man es automatisch neustarten lassen? ==

Nein. Man kann dies aber einem Script auftragen, einige davon funktionieren vielleicht sogar, wenn aMule '''einfriert''' und nicht '''abstürzt'''.

Diese Scripte können eventuell von Nutzen sein:
*http://www.amule.org/amule/thread.php?threadid=1232
*http://www.amule.org/amule/thread.php?threadid=542
*http://deepthought.ena.si/mulerunner

== Kann aMule Daten von der Standardeingabe lesen und an GDB oder Valgrind weiterreichen? ==

Ja, bis 2.0.0-rc3 war das nicht möglich, ab 2.0.0-rc4 kann man das mit dem Parameter ''-i'' bzw. ''--enable-stdin'' erreichen. 
Wer noch ein aMule vor 2.0.0-rc4 verwendet, kann [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin Patch] verwenden.

== Wie kann ich von eMule zu aMule wechseln, ohne meine Credits zu verlieren? ==

Wer [[FAQ_aMule#Wofür_sind_die_ganzen_Dateien,_die_aMule_beim_ersten_Start_anlegt?|"Wofür sind die ganzen Dateien, die aMule beim ersten Start anlegt?"]] gelesen hat, weiß bereits, was zu tun ist:

Die Dateien ''cryptkey.dat'', ''clients.met'' und ''preferences.dat'' aus dem eMule-Konfigurationsverzeichnis (bei Windows irgendwo unter ''C:\Programm Dateien\eMule\config'') nach ''~/.aMule'' kopieren. Jetzt verwendet aMule die gleichen Einstellungen. Das war's!.

== Unterstützt aMule Universal Plug and Play (UPnP)? ==

YES!

Since Dec, 9th, 2006 the code in our daily tarballs supports UPnP port mappings. The current version of aMule is 2.1.3, so, our next oficial version will have UPnP support.

== Was hat es mit der Geschichte um das [[rabbit|Kaninchen]] auf sich? ==

Hmm, es fing an... mit... nun ja... es war... folge einfach dem weißen [[rabbit|Kaninchen]] ;-)

== Welche Distribution wird empfohlen / Betriebssysteme zum Ausführen von [[aMule-de|aMule]]? ==

Die unbedingt empfohlene Distribution ist [[YSWPS]]. Das ist zwar noch keine ausgereifte Distribution, aber den Aufwand wert, sich damit zu befassen.

== Wann kommt der nächste aMule raus? ==

Egal, welche nächste Ausgabe, die Antwort ist immer die gleiche, sie lautet für gewöhnlich: [[Soon|Bald]] (Vorschlag: folge dem Link).

FAQ aMule-ko KR

2006-12-09T20:13:57Z

Phoenix: =Does aMule support Universal Plug and Play (UPnP)?=

<center>
<h4>[[aMule_Project_FAQ:About|어뮬]]에대해 자주하는 질문</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | [[FAQ_aMule-de|Deutsch]] | [[FAQ_aMule-nl|Nederlands]] | [[FAQ_aMule-ru|Russian]]
</center>

== [[aMule_Project_FAQ:About|어뮬]]?이란 ==

'''''[[어뮬]] 어뮬은 [[FAQ_eD2k-Kademlia|ED2K 파일공유 네트워크]]를 위한 다중플랫폼 클라이언트이며 윈도우 클라이언트인 [[eMule]]을 기반으로한다. 어뮬은 [[lMule]]의 다른 갈래인 [[xMule]]의 또다른 갈래로써 2003년 8월에 시작되었다.

어뮬은 현재 [http://en.wikipedia.org/wiki/64-bit#32_vs_64_bit 32bit와 64bit]에서 작동되는 [http://www.kernel.org 리눅스], [http://www.freebsd.org FreeBSD], [http://www.openbsd.org OpenBSD], [http://www.microsoft.com MS윈도우], [http://www.apple.com/macosx MacOS X] 그리고 [http://www.microsoft.com/xbox X-Box]를 지원한다.

[[어뮬]]은 [[eMule]]의 모양과 느낌을 그대로 적용하고 [[eMule]]의 기능과 사용자에 대한 친밀성을 적용했기 때문에 [[어뮬]]이나 [[eMule]]에 능숙한 사용자는 둘 사이를 쉽게 바꿀 수 있다.

[[aMule_Project_FAQ:About|어뮬]]은 [[eMule]]의 코드를 기반으로 하기 때문에, 새로운 기능이 [[eMule]]에 포함되면 [[어뮬]]에서도 나름대로의 방식으로 포함된다. 따라서 [[aMule_Project_FAQ:About|어뮬]] 사용자들은 [[FAQ_eD2k-Kademlia|ED2k]] 클라이언트의 최첨단 기능을 사용할 수 있다.

[[aMule_Project_FAQ:About|어뮬]] 그 자체보다 더 사용자에게 친근한 팀에 의해서 만들어진다는 것이 가장 좋은 점이다. 만약 당신 생각한 제안이나 질문, 문제, 버그, 패치 등등이 있다면 [http://www.amule.org/amule 어뮬 포럼]을 방문하던지 irc.freenode.net의 #amule에 참여하라.

만약 개발팀에 참여하고 싶으면 [http://www.amule.org/amule 어뮬 포럼]이나 IRC채널을 통해서 우리에게 연락하라.

== 어떻게 클라인어트이 신용을 볼수있나? ==

클라이언트의 닉네임 위에서 오른쪽 마우스 클릭후 세부사항을 선택함으로써 임의의 클라이언트의 신용(당신이 해당 클라이언트에 빚지고 있는 신용)을 볼수 있다. 특정값이 보여지지 않는 것은, 클라이언트가 당신에게 보내주는 데이터의 총량을 볼수 있거나 신용변경자(업/다운 변경자)를 볼수있기 때문이다. 똑 같은 창에서, 해당 클라이언트가 당신의 올려주기 대기열에 있다면, 당신은 클라이언트의 비율과 점수를 볼수 있다.

== 진행바의 색은 무엇을 의미하는가? ==

내려받기 전송목록에서:
*'''빨강:''' 현재 세션에서 자료가 없는 부분이다.
*'''파랑:''' 적어도 하나의 가능한 자료가 부분이다. 더 진한 파랑색은 더 많은 자료가 있는것이다.
*'''노랑:''' 지금순간에 내려받기가 진행중인 부분이다.
*'''검정:''' 이미 내려받기가 되고 검증된 부분이다.
*'''녹색:''' 파일이 녹색이 되면, 내려받기가 완료되고 성공적으로 검증된것이다(파일이 incoming폴더에 존재할것이다.)

확장된 전송목록에서(전송자를 더블클릭하면 볼수있다) :
*'''검정:''' 클라이언트에게는 있고 당신에게는 없는 부분.
*'''흰색:''' 클라이언트에게 없는 부분.
*'''녹색:''' 클라이언트와 당신에게 있는 부분.
*'''노랑:''' 클라이언트가 당신에게 현재 올려주기 하는 부분.

올려주기 전송목록에서:
*검정: 클라이언트에 있고 검증된 부분.
*회색: 클라이언트에게 없는 부분.

올려주기시 모든 클라이언트가 이미 완료된 부분을 다른 클라이언트에게 알려주지는 않는다. 따라서 몇몇 클라이언트는 바를 가지지 않는다.

공유파일 창에서:
*'''빨강:''' 같은 부분에 대해 자료가 없을 때.
*'''파랑:''' 푸른색이 진할수록 더 많이 유포된 부분이다.

검색창에서:
*'''검정:''' 오직 하나의 클라이언트가 가지고 있는 파일.
*'''파랑:''' 둘이상의 클라이언트가 가지고 있는 파일. 진할수록 더 많은 클라이언트가 가지고있다.
*'''빨강:''' 이미 내려받기 대기열에 존재하는 파일.
*'''녹색:''' 당신이 이미 공유하고 있는 파일(내려받기가 완료되었다).

== 아이콘들은 무엇인가? ==

[[Getting_Started#Icons_and_What_They_Signify|시작하기]] 부분의 “아이콘과 그들이 의미하는 것”을 보라.

== 검색창의 자료항목에서 괄호안의 수가 의미하는 것은? ==

완전한 파일을 가지고 있는 클라이언트이다. 괄호안의 수가 0이라도, 완전한 파일을 가진사람이 아무도 없다는 것을 의미하는 것은 아니다. 단지 공유파일에 “완료됨”이라고 표시된 클라이언트가 없다는 의미이다. 얼마나 많은 사람들이 완료된 파일을 가지고 있는가를 표현하는 방식이다.

== 전송창의 자료항목에서 괄호안의 수가 의미하는 것은? ==

XX/YY + ZZ (WW) 형식에서
*'''XX'''는 가능한 자료(내려받기 가능한)의 수를 표시한다.
*'''YY'''는 발견된 자료(검색된 자료의 총갯수)의 수를 표시한다.
*'''ZZ'''는 다른 파일을 요청하는 자료의 수를 표시한다.
*'''WW'''는 당신이 현재 파일의 어떤 부분을 내려받기중인 자료의 수를 표시한다.

== 확장된 전송창에서 우선권항목에 있는 숫자들의 의미는? ==

해당 클라이언트에서 특정파일에 대한 대기열 순위이다. 모든 클라이언트가 그런 정보를 제공하는 것이 아니며, 어떤 경우에는 아무것도 표시되지 않는다.

괄호안의 숫자는 해당 클라이언트의 올려주기 대기열을 통해서 옮겨진 위치의 크기이다. ‘’’음수’’’값은 대기열에 추가된 이후에 ‘’’획득’’’한 위치를 표시하고, ‘’’양수’’’값은 대기열에 추가된 이후에 ‘’’잃은’’’ 위치를 표시한다. 숫자가 음수일 때는 파란색으로 표시되고, 양수일때는 빨간색으로 표시된다.

== 올려주기 전송 리스트에 왜 두개의 전송율이 있는가? ==

당신이 파일을 클라이언트에 올려줄 때, 올려주기 전송 리스트는 해당 클라이언트에 올려주는 전송률(KBps단위)을 보여줄 것이다. 만약, 동시에 해당 클라이언트가 당신에게 올려준다면, 전송률의 형태는 당신이 클라이언트에 올려주는 전송률 XX와 클라이언트가 당신에게 올려주는 전송률 YY를 의미하는 XX/YY로 바뀔것이다. 당신은 해당 클라이언트를 내려받기 전송리스트에서 찾을수 있다.

이것은 희귀한 파일을 얻는데 유용하다. 당신은 해당 클라이언트가 올려주는 파일을 볼수있으므로, 만약 그 파일이 희귀하다면, 당신은 그를 친구로 설정할수 있고 그렇게 함으로써 당신은 더 빨리 올려줄수 있고 해당 클라이언트에 대해 더많은 신용을 얻을수 있다(그 결과로, 더 빨리 내려받을 수 있다).

== A4AF는 무엇인가? ==

A4AF는 ''다른 파일을 요청한다''를 의미한다. 이것은 특정한 내려받기에 대해 자원들을 최적화하는 방법이다.

당신이 파일을 내려받으려고 할 때, 어뮬은 해당 파일을 공유하고 있는 클라이언트의 목록을 얻는다. 이 클라이언트중 몇몇은 당신이 내려받으려는 다른 파일을 공유할수도 있다. 따라서, 당신은 해당 클라이언트의 두개의 구분된 내려받기 대기열에 존재할 수 있다.

A4AF는 이 상황을 피하도록 한다. 왜? 왜냐하면 당신은 같은시간에 같은 클라이언트로부터 두개의 부분을 내려받을수 없다. 따라서, 특정한 내려받기에 A4AF를 설정함으로써, 당신은 해당파일의 내려받기 대기열에서 다른 클라이언트를 찾도록 어뮬에게 요구하고, 또 다른 파일도 다른 클라이언트를 찾도록하며, 내려받기 대기열에서 삭제된다. 이렇게 해서, 당신은 해당 파일에 대해 더 많은 자료를 가지게 된다.

반대로 당신은 다른 내려받기에 자료들을 주기위해서 A4AF를 내려받기에 적용시킬수 있다. 이것은 매우 급한 내려받기나 몇몇 비슷한 파일(예를 들면 연속된 파일)을 받은후 내려받아야 되는 파일의 내려받기에 사용된다. 이것 또한 선호하는 내려받기를 수립하는 방식으로 사용될수 있다.

교환 요구가 수행되었을 때, 대기열순위는 유지될것이다.

'''주의:''' 내려받기에서 대기열 순위가 높은것보다 50 이상 낮은 자료는 교환되지 않는다. 이것은 해당 자료로부터 내려받기가 시작된다고 판단하는 방식으로 사용된다.

만약 파일이 XX+ZZ 자료를 가지고 있다면, ZZ 자료들은 필요하지 않은 부분들을 포함하고 있다. 만약 당신이 파일에 교환을 요구하면 어뮬은 이것들을 제외 시킬것이다.

== QR:xxxx가 의미하는 것은 무엇인가? ==

QR은 “대기열 순위”를 의미하며, 공급자의 대기열 안에서 당신의 현재위치를 나타낸다.

명백하게, 낮은값이 더 좋다. 만약 공급자가 eMule 클라이언트이고 QR값이 없다면, 공급자의 대기열이 가득차고 더 이상 클라이언트를 받을수 없다는 것이다.

== 전송창에서 전송됨과 완료됨의 차이점은 무엇인가? ==

전송됨은 해당파일에 대하여 당신이 받은 데이터의 양을 보여준다. 이 데이터는 압축된형태로 내려받아진다. 데이터가 당신의 컴퓨터에 도착하면, 어뮬은 그것을 복원하고 처리한다. 받은 데이터로부터 획득될수 있는 유용한 데이터(즉, 헤더나 그런것들이 아닌, 당신이 내려받으려는 파일의 실제적인 부분)는 완료됨 항목에 보여지는 양이다.

== 전송의 잠시멈춤과 중단의 차이점은 무엇인가? ==

전송이 잠시멈춤이 되었을 때, 잠시멈춤과 관련된 모든 다른 클라이언트와의 연결은 끊어지고 데이터는 전송되지 않지만, 공급자는 버려지지 않고, 전송이 재계되면, [[aMule_Project_FAQ:About|어뮬]]은 그 공급자들을 다시 연결하려고 시도할것이다.

대신에, 전송이 중단되면, 모든 공급자들은 버려지고, 전송이 재개되면 [[aMule_Project_FAQ:About|어뮬]]은 그파일을 공유하고 있는 클라이언트들을 찾기 시작할것이다.

== [[aMule_Project_FAQ:About|어뮬]]이 최초로 실행될 때 생성되는 파일들은 무엇인가? ==

파일들의 대부분은 [[eMule|eMule]]의 파일들과 같다.

[[어뮬]] 파일들의 목록과 각각에 대한 상세한 정보는 [[aMule files|여기]]에서 볼수 있다.

== [[eMule|eMule]]의 파일과 설정등을 사용 할 수 있는가? ==

대부분 사용할수 있다. [[aMule_Project_FAQ:About|어뮬]]과 [[eMule]]사이에 공유할수 없는 한가지는 환경설정(즉, [[eMule]]에서의 preferences.ini와 [[aMule_Project_FAQ:About|어뮬]]에서의 ''~/.aMule/amule.conf'') 파일이다.

완료되지 않은 파일을 옮기는 것은 쉽다: 단지 당신의 [[eMule]] 임시 디렉토리(기본적으로 ''C:\Program files\eMule\Temp'' 이다.)에서 ''~/.aMule/Temp'' 또는 [[aMule]] 환경설정안의 임시 디렉토리로 옮기면 된다.

== amulesig.dat와 onlinesig.dat안의 항목들은 무엇인가? ==

[[amulesig.dat_file|''amulesig.dat'']]와 [[onlinesig.dat_file|''onlinesig.dat'']]가 무엇인지 [FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|위]].에서 이미 읽었을 것이다.

이 파일들은 현재의 [[signature]]([[aMule]]의 현재 상태, 가능하다면)을 가지고 있다.

이 파일들의 상세한 정보는 [[amulesig.dat_file|''amulesig.dat'' 항목]]과 [[onlinesig.dat_file|''onlinesig.dat'' 항목]]에서 볼수 있다.

== [[aMule_Project_FAQ:About|어뮬]]을 처음으로 설치했다. 어떻게 구성하는가? ==

어뮬의 적합한 구성은 취미의 문제이며 많은 요인에 의존적이다. 만약 당신이 빠른 환경설정을 원한다면 계속해서 읽어라.

[[aMule_Project_FAQ:About|어뮬]]을 열고 환경설정 버튼을 클릭한다. [[aMule_Project_FAQ:About|어뮬]]이 사용할 언어와 별명을 설정한다. 그리고 연결탭으로 전환한후 당신의 라인양을 입력한다. 그다음 [[aMule_Project_FAQ:About|어뮬]]이 사용하기를 원하는 대역폭의 최대값에 따른 대역폭의 한계치를 입력한다. 그후 디렉토리탭으로 전환하여 임시파일(완전히 내려받을 때까지 저장되어지는 파일)과 완료된파일의 디렉토리를 설정한다. 마지막으로, 당신이 공유할 디렉토리를 선택한다. 너무많은 파일의 공유는 권장되지 않는다. 아래의 “최선의 내려받기 비율을 가지기위한 최고의 설정법은 무엇인가?”를 읽어라. 어떤 디렉토리안의 모든 디렉토리를 반복적으로 선택하는 것은 [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|모든 디렉토리와 그 내용을 반복적으로 선택하는 방법은?]]을 읽어라.

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==

[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways:

[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporary and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively.

If a ~/.xMule directory is found, it will be kept unchanged and [[aMule]] will just copy the configuration files found in it. That means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==

Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it.

For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==

If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==

Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file.

You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==

Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured.

Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics.

Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example:
#Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: <code>Xvfb :1 -screen 0 640x480x16 &</code>
#Set display to use for amule: <code>export DISPLAY=:1</code>
#Then run [[aMule_Project_FAQ:About|aMule]]: <code>amule &</code>

'''Note:''' After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: <code>DISPLAY=:1 amule &</code>

'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:'''

It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==

Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell.

Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statistics some people post on the IRC channels? ==

You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statistics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistics).

== What is slot allocation? ==

Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given.

As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps.

See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==

A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==

aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==

No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''.

The following scripts might suit your needs:
*http://www.amule.org/amule/thread.php?threadid=1232
*http://www.amule.org/amule/thread.php?threadid=542
*http://deepthought.ena.si/mulerunner

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==

Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''.

Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without losing my credits? ==

If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'', ''preferences.dat'', ''preferencesKad.dat'', ''key_index.dat'', ''load_index.dat'' and ''src_index.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

You might still want to take a look at the [[migrate from eMule to aMule]] article, though.

== Does aMule support Universal Plug and Play (UPnP)? ==

YES!

Since Dec, 9th, 2006 the code in our daily tarballs supports UPnP port mappings. The current version of aMule is 2.1.3, so, our next oficial version will have UPnP support.

== What's the story behind the [[rabbit]]? ==

Ah, yeah, this all began... ehm... well... I mean... follow the white [[rabbit]] ;-)

== Which one is the recomended distro / Operating System for running [[aMule]]? ==

The absolutely recomended distro is [[YSWPS]]. It's still not a mature distro, but it's worth the effort to look for it.

== When will next aMule release happen? ==

Whatever next release, the answer is always the same, it is standard: [[Soon]] (suggestion: follow the link).

FAQ aMule-de

2006-12-09T20:12:57Z

Phoenix: =Unterstützt aMule Universal Plug and Play (UPnP)?=

<center>
<h4>F.A.Q auf [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]'' (Übersetzt durch ''nachbarnebenan'')</h2>

[[FAQ_aMule|English]] | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | '''Deutsch''' | [[FAQ_aMule-nl|Nederlands]] | [[FAQ_aMule-ru|Russian]]
</center>

== Was ist denn dieses ominöse [[aMule_Project_FAQ:About|aMule]] eigentlich? ==

'''''[[aMule]] ist ein plattformunabhängiger Client für das [[FAQ_eD2k-Kademlia-de|eDonkey/eMule Filesharing Netzwerk]], entstanden im August 2003 aus einer Abspaltung von [[xMule]], das wiederum eine Abspaltung von [[lMule]], das wiederum eine Portierung des nur-Windows Clients [[EMule-de|eMule]] ist.'''''

Im Moment ist es unter GNU/Linux, FreeBSD und OpenBSD, MacOSX, Windows und der X-Box sowohl auf 32- als auch 64bit Systemen lauffähig. Die Windows-Version ist allerdings noch nicht wirklich für den produktiven Einsatz geeignet.

Es ist beabsichtigt, dass [[aMule-de|aMule]] genauso funktionell und einfach zu benutzen ist, wie [[EMule-de|eMule]] und auch genauso aussieht, so dass Nutzer, die mit einem der beiden vertraut sind, ohne Schwierigkeiten zwischen beiden wechseln können.

Da [[aMule_Project_FAQ:About|aMule]] auf den Quellen von [[EMule-de|eMule]] basiert, finden neue Funktionen sehr schnell ihren Platz in [[aMule]], nachdem sie in [[EMule-de|eMule]] eingebaut wurden, so dass auch die Nutzer von [[aMule_Project_FAQ:About|aMule]] sicher sein können, sich immer an der Spitze der Entwicklung der [[FAQ_eD2k-Kademlia-de|ED2k]] Clients zu befinden.

Nicht unwichtig ist, dass es von einem großartigen Team entwickelt wird, dass (sofern das überhaupt möglich ist), vielleicht noch nutzerfreundlicher und -bezogener ist, als [[aMule_Project_FAQ:About|aMule]] selbst. Daher schauen Sie auch mal bei #amule auf irc.freenode.net vorbei oder besuchen Sie [http://www.amule.org/amule unsere Foren], wenn Sie Fragen oder Probleme haben, oder einfach nur einen guten Vorschlag, was man besser machen könnte.

Möchten Sie vielleicht sogar dem Entwicklerteam beitreten, melden Sie sich bitte in den Foren oder im IRC.

== Wie kann man sich die Credits eines Clients ansehen? ==

Man kann sich die Credits eines Clients (was man ihm schuldet) ansehen, wenn man auf seinen Namen rechts klickt und Details anzeigen auswählt. Die Credits haben keinen bestimmten Wert, man kann sich entweder die gesamtübertragene Datenmenge, die man von diesem Clients bekommen hat, ansehen oder den Credit Modifikator (DL/UL Modifikator). Das Fenster zeigt auch, wenn der Client in der Uploadwarteschlange steht, seine Position und seine Bewertung.

== Was bedeuten diese ganzen Farben in der Fortschrittsanzeige? ==

In der Liste der Downloads:
'''Rot:''' Für Blöcke in rot wurden in der aktuellen Sitzung noch keine Quellen gefunden.
'''Blau:''' Blöcke in blau haben mindestens eine nutzbare Quelle, je dunkler das Blau ist, desto mehr Quellen gibt es.
'''Gelb:''' Gerade in diesem Moment heruntergeladenen Blöcke werden gelb dargestellt.
'''Schwarz:''' Schwarze Blöcke wurden bereits fertig heruntergeladen und überprüft.
'''Grün:''' Sobald eine Datei komplett fertiggestellt ist, wird sie grün dargestellt (und ist dann im Eingangsverzeichnis zu finden).

Auf der ausführlichen Downloadliste (aufzurufen durch Doppelklick auf einen einzelnen Transfer):
'''Schwarz:''' Der Client hat diesen Chunk, wir aber noch nicht.
'''Weiß:''' Diesen Chunk hat der Client nicht.
'''Grün:''' Wir haben diesen Chunk beide.
'''Gelb:''' Dieser Chunk wird gerade von diesem Client zu uns heraufgeladen.

Auf der Uploadliste:
'''Schwarz:''' Diesen Chunk hat der Client fertiggestellt und überprüft.
'''Grau:''' Der Client hat diesen Chunk nicht.

Beachten Sie, dass nicht alle Clients die Fähigkeite haben, anderen beim Upload zu sagen, welche Teile sie bereits haben, daher haben manche Clients keine Anzeige der einzelnen Blöcke.

Bei den freigegebenen Dateien:
'''Rot:''' Außer uns gibt es keine andere Quelle dieses Chunks.
'''Blau:''' Umso dunkler das Blau ist, umso mehr Clients haben diesen Teil.

Auf der Suchseite:
'''Schwarz:''' Für schwarze Dateien wurde nur ein Clients gefunden, der sie hat.
'''Blau:''' Dateien in blau haben mindestens zwei Quellen, je dunkler das Blau, desto mehr.
'''Rot:''' Rote Dateien befinden sich bereits in der Downloadliste.
'''Grün:''' Bereits vollständig heruntergeladene Dateien werden auch hier in grün dargestellt.

== Was bedeuten diese ganzen Icons? ==

Siehe [[Getting_Started-de#Icons_und_was_sie_bedeuten|hier]].

== Was bedeuten die Zahlen in Klammern im Suchfenster? ==

Sie zeigen die Zahl der Clients an, die bekanntermaßen die Datei vollständig haben. Aber auch wenn die Anzahl 0 ist, heißt das noch lange nicht, dass keiner sie komplett hat, nur, dass sie keiner als "komplett" markiert hat (viele Clients tun dies). Trotzdem kann man so einen Eindruck davon gewinnen, wieviele Leute die Datei vollständig haben, auch wenn es keine Gewissheit ist.

== Was bedeuten die ganzen Zahlen in der Quellen-Spalte in der Transferliste? ==

Das Format der Quellenangabe ist XX/YY + ZZ (WW), wobei
*'''XX''' für die Anzahl der verfügbaren Quellen steht (von denen man downloaden kann),
*'''YY''' für die Gesamtanzahl an gefundenen Quellen steht,
*'''ZZ''' für die Anzahl der Quellen, die "nach einer anderen Datei gefragt" worden sind (A4AF), und
*'''WW''' für die Anzahl der Quellen steht, von denen wir gerade einen Chunk herunterladen.

== Wofür stehen die Zahlen in der Spalte Priorität in der aufgeklappten Downloadliste? ==

Das ist die Warteschlangenposition, die man beim jeweiligen Client einnimmt. Nicht alle Clients geben diese an, daher steht in manchen Fällen dort einfach nichts.

Die Zahl in Klammern gibt die Positionen an, die man sich schon in der Warteschlange des Clients *bewegt* hat. '''Negative''' Zahlen stehen für '''vorangeschrittene'' Positionen, '''positive''' für verlorene. Wenn negativ, wird die Zahl blau dargestellt, bei positiv rot.

== Warum werden in der Uploadliste zwei Geschwindigkeiten angegeben? ==

Wenn man zu einem Client hochlädt, zeigt die Uploadliste die Geschwindigkeit (in Kilobyte pro Sekunde) zu diesem Client an, wenn nun, zur gleichen Zeit, dieser Client auch zu uns hochlädt, verändert sich die Anzeige zu XX/YY, wobei XX für unsere und YY für seine Uploadgeschwindigkeit steht. Wenn man in der Downloadliste sucht, wird man diesen Client finden.

Dies ist besonders nützlich, wenn man versucht, eine seltene Datei zu bekommen, da man sehen kann, was der Client zu einem hochlädt und, wenn es die gesuchte Datei ist, ihm einen Uploadplatz für Freunde vergeben kann, so dass man schneller zu ihm hochlädt, man damit mehr Credits bekommt und folglich auch schneller von ihm herunterladen kann.

== Was ist A4AF? ==

A4AF (Asked for/4 another File) bedeutet ''nach anderer Datei gefragt''. Damit werden die Ressourcen eines bestimmten Downloads optimiert.

Wenn man eine Datei downloaded, holt sich aMule eine Liste aller Clients, die diese Datei haben. Einige davon haben möglicherweise auch andere Dateien, die man herunterladen möchte, daher kann man einen Client bei mehreren separaten Downloads haben.

A4AF versucht, dies zu vermeiden. Warum? Man kann nicht zwei Blöcke zur gleichen Zeit vom gleichen Client herunterladen. Durch das Aktivieren von A4AF sagt man aMule, nach Clients zu suchen, die sowohl bei dieser als auch bei anderen Dateien in der Downloadliste stehen, und sie bei den anderen zu entfernen. Dadurch bekommt man für diese Datei mehr Quellen.

Man kann auch einen Download auf das Gegenteil setzen, um A4AF andersherum anzuwenden, also Quellen an andere Downloads abzugeben. Das sollte für Dateien getan werden, die nicht so dringend sind, oder erst nach einer anderen ähnlichen Datei heruntergeladen werden sollen (z.B. bei einer Serie von Dateien).

Man kann das als eine Möglichkeit, persönliche Vorlieben in den Downloads einzustellen, ansehen.

Wenn eine Quelle gewechselt wird, bleibt der Platz in der Warteschlange dabei erhalten.

'''HINWEIS:''' Quellen mit einem Warteschlangenplatz kleiner als 50 beim Download mit der höheren Priorität werden niemals ausgewechselt. Damit wird sichergestellt, dass der Download auch beginnt.

== Was bedeuten die Zahlen bei "QR: xxxx", die ich sehe, wenn ich mir meine Quellen anschaue? ==

QR bedeutet "Queue Rank", also sinngemäß etwa "Warteschlangenplatz", und bezeichnet die momentane Position in der Warteschlange dieser Quelle.

Offensichtlich ist ein niedrigerer Wert besser. Falls die Quelle ein eMule-Client ist, und hinter "QR" keine Zahl steht, ist dessen Warteschlange vermutlich voll, und er kann keine weiteren Clients mehr annehmen.

== Wo ist der Unterschied zwischen "übertragen" und "fertiggestellt" in der Downloadliste? ==

Übertragen ist die Gesamtmenge an Daten, die man für die ausgewählte Datei erhalten hat. Die Daten sind komprimiert, sobald sie ankommen, werden sie von aMule verarbeitet und entpackt. Die Gesamtmenge an Nutzdaten (also die Teile, die wirklich zur Datei gehören, alles andere sind Header, Prüfsummen usw.) kann in der Spalte Fertiggestellt abgelesen werden.

== Was ist der Unterschied zwischen Pausieren und Stoppen eines Downloads? ==

Wen ein Download pausiert, werden alle Verbindungen die zu diesem Download gehören getrennt so dass keine Daten mehr übertragen werden, die Quellen werden aber beibehalten, bei der Wiederaufnahme wird aMule also versuchen, die Quellen wieder zu kontaktieren.

Wird ein Download gestoppt, werden auch die Quellen verworfen, bei der Wiederaufnahme wird aMule als von neuem beginnen, Clients zu finden, die diese Datei haben.

== Wofür sind die ganzen Dateien, die [[aMule_Project_FAQ:About|aMule]] beim ersten Start anlegt? ==

Die meisten gleichen denen von [[EMule-de|eMule]].

Genauere Informationen und eine detailierte Liste aller [[aMule]] Dateien findest du [[AMule_files-de|hier]].

== Kann man die Dateien und Einstellungen von [[eMule|eMule]] benutzen und umgekehrt? ==

Das meiste ja. Lediglich die Programmkonfiguration (preferences.ini bei [[eMule]] und ~/.aMule bei [[aMule_Project_FAQ:About|aMule]]) sind nicht zwischen [[aMule_Project_FAQ:About|aMule]] und [[eMule]] austauschbar. Alle das [[FAQ_eD2k-Kademlia|ED2K-Netzwerk]] betreffenden Dateien sind problemlos verwendbar, sie müssen nur aus dem [[eMule]]-Verzeichnis nach ~/.aMule kopiert werden - oder umgekehrt. Allerdings sind einige Dateien in ~/.aMule [[aMule_Project_FAQ:About|aMule]]-spezifisch, z.B. amulesig.dat und aMule.tmpl, daher ist es besser, nur die Dateien zu kopieren, die sowohl im [[aMule_Project_FAQ:About|aMule]]-, als auch im [[eMule]]-Verzeichnis vorhanden sind.

Die noch nicht abgeschlossenen Downloads zu übernehmen ist leicht: Einfach die Dateien aus dem [[eMule]]-Temp-Verzeichnis (standardmäßig ''C:\Programm Dateien/eMule\Temp'') nach ''~/.aMule/Temp'' kopieren, bzw. in das eingestellte Temp-Verzeichnis von aMule.

== Was hat es mit amulesig.dat und onlinesig.dat auf sich? ==

[[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|Weiter oben]] wurde bereits beschrieben, wofür die Dateien amulesig.dat und onlinesig.dat Verwendung finden. Hier wird der Inhalt beschrieben (Berücksichtigen Sie bitte, dass bei einem Absturz von [[aMule_Project_FAQ:About|aMule]] der Inhalt dem zuletzt geschriebenen entspricht):

onlinesig.dat

*Besteht aus zwei Zeilen, getrennt durch LF (kein CR dazwischen). Die erste enthält, wenn [[aMule_Project_FAQ:About|aMule]] offline ist, nur eine 0 und nichts weiter. Ist [[aMule_Project_FAQ:About|aMule]] online, dann eine 1, gefolgt vom Pipe-Symbol |, dem Namen des Server mit dem aMule verbunden ist, einem weiteren Pipe-Symbol, der IP des Servers, weil's so schön war noch einem Pipe und zuletzt dem Port des Servers.
*Die zweite Zeile enthält, in dieser Reihenfolge: Die Downloadrate, die Uploadrate und den Füllgrad der Warteschlange, alles ebenfalls mit jeweils einem Pipe-Symbol voneinander getrennt.
*Die zweite Zeile endet übrigens '''nicht''' mit einem Newline ('\n').
*Wird [[aMule_Project_FAQ:About|aMule]] ordnungsgemäß beendet, behält die zweite Zeile ihre Form, aber alle Einträge sind mit Null gefüllt, die erste Zeile enthält dann nur eine einzele Null.

amulesig.dat

Die [[signature|Signatur]]-Datei von aMule ist sehr viel leistungsfähiger als die von [[eMule]]. Jede Zeile ist ein Datenfeld mit folgendem Inhalt:
*Die erste Zeile enthält eine Null wenn [[aMule_Project_FAQ:About|aMule]] nicht verbunden oder regulär beendet ist, eine 1 wenn online und eine 2 wenn gerade eine Verbindung aufgebaut wird (erst seit 2.0.0-rc4).
*Die zweite, dritte und vierte Zeile enthalten den Namen, IP und Port des Servers, mit dem aMule verbunden ist (in dieser Reihenfolge), oder Null wenn aMule offline ist. Ab 2.0.0-rc4 enthalten sie auch dann Null, wenn aMule beim Verbinden oder ordentlich beendet ist.
*In der fünften Zeile steht ein großer L oder H, je nachdem ob [[aMule_Project_FAQ:About|aMule]] mit einer hohen (H) oder niedrigen (L) ID verbunden ist. Beginnend mit 2.0.0-rc4 enthält auch diese Zeile eine Null, wenn aMule noch verbindet oder korrekt beendet ist.
*Die sechste und siebte Zeile enthalten die aktuelle Download- und Uploadgeschwindigkeit, seit 2.0.0-rc4 enthalten sie "0." wenn aMule normal beendet wurde.
Achte und neunte Zeile zeigen die Anzahl der Clients in der Uploadwarteschlange *und die Menge der freigegebenen Dateien. Auch hier stehen seit 2.0.0-rc4 jeweils Null, wenn aMule beendet wurde.
*Der Spitzname des Benutzers steht in der zehnten Zeile.
*In der elften und zwölften Zeile sind die Gesamtsummen von Download- und Uploadmengen aufgeführt.
*Die verwendete Version von [[aMule_Project_FAQ:About|aMule]] ist in der dreizehnten Zeile zu finden.
*Die Anzahl der in der aktuellen Sitzung von aMule herunter- und hochgeladenen Bytes sind in der vierzehnten und fünfzehnten Zeile zu finden, ab 2.0.0-rc4 sind beide Null, wenn aMule beim Verbinden oder ordentlich beendet ist.
*In der sechzehnten (und letzten) Zeile steht die Zeit, die [[aMule_Project_FAQ:About|aMule]] nun schon läuft. Nach einem Leerzeichen kommt "secs" "mins" oder "hours", oder die Entsprechung in der jeweils eingestellten Landessprache. Ab 2.0.0-rc4 steht hier 00 gefolgt von "secs" bzw. der jeweiligen *Abkürzung, falls aMule beendet oder noch beim Verbinden ist.
*Die letzte Zeile wird mit einem Newline ('\n') beendet.

== Ich habe [[aMule_Project_FAQ:About|aMule]] gerade zum ersten Mal installiert, was muss ich einstellen? ==

aMule zu konfigurieren ist größtenteils eine Frage des Geschmacks und hängt von vielen Faktoren ab. Für einen Konfigurations-Crashkurs einfach weiterlesen.

Starten Sie [[aMule_Project_FAQ:About|aMule]] und klicken Sie auf Einstellungen. Denken Sie sich einen Spitznamen aus und wählen Sie die gewünschte Sprache, in der [[aMule_Project_FAQ:About|aMule]] erscheinen soll. Wechseln Sie dann auf den Punkt Verbindungen und geben Sie die maximalen Kapazitäten Ihres Anschlusses sowie die von [[aMule_Project_FAQ:About|aMule]] davon zu verwendende Bandbreite ein. Gehen Sie auf den Punkt Verzeichnisse und legen Sie das temporäre (wo unvollständige Downloads abgelegt werden) und das Eingangsverzeichnis fest. Dann wählen Sie die Verzeichnisse, deren Dateien für andere freigegeben werden sollen. Geben Sie nicht zu viele Dateien frei (siehe unter "Welches sind die besten Einstellungen, um eine optimale Downloadrate zu erzielen?") und wählen Sie keine Dateien mit kritischen Inhalten (e.g. ~/.ssh usw.). Um ein Verzeichnis rekursiv samt seiner Unterverzeichnisse auszuwählen, lesen Sie bitte unter [[aMule_problems#Is there any way to recursively select a whole directory and its contents?]] nach.

== Kann [[aMule_Project_FAQ:About|aMule]] meine [[xMule]]- und [[lMule]]-Dateien verarbeiten? Und wie? ==

[[aMule_Project_FAQ:About|aMule]] handhabt sowohl [[lMule]]- als auch [[xMule]]-Konfigurationsdateien automatisch, aber auf verschiedene Weise: [[lMule]] wird seit mehreren Jahren nicht mehr weiterentwickelt, daher geht aMule davon aus, dass Sie es ersetzen wollen. Daher wird das Verzeichnis ~/.lMule in ~/.aMule umbenannt. Wenn Sie ~/.lMule/Temp und ~/.lMule/Incoming als temporäres und Eingangsverzeichnis verwendet haben, müssen Sie dies nachfolgend in den Einstellungen auf ~/.aMule/Temp und ~/.aMule/Incoming ändern.

[[xMule]] ist seit Mai 2004 offiziell eingestellt (öffentliche Bekanntgabe durch den Hauptentwickler im [[xMule]]-Forum der mittlerweile nicht mehr existenten Seite [http://www.xmule.org http://www.xmule.org]), aus historischen Gründen lässt [[aMule_Project_FAQ:About|aMule]] das ~/.xMule Verzeichnis aber unangetastet und kopiert nur die Konfigurationsdateien nach ~/.aMule. Das bedeutet, dass alle Downloads im ~/.xMule Verzeichnis verbleiben, wenn sie dort abgelegt wurden, aber da [[aMule_Project_FAQ:About|aMule]] die Konfiguration von [[xMule]] übernommen hat, wird es sie weiterhin benutzen. Entweder man lässt es so oder man man verschiebt ~/.xMule/Temp und ~/.xMule/Incoming nach ~/.aMule und ändert die Einstellungen entsprechend.

== Wie fange ich denn nun mit [[aMule_Project_FAQ:About|aMule]] an? ==

Klicken Sie einfach den Verbinden-Knopf. Dafür benötigen Sie allerdings gültige Einträge in der Serverliste, sollte das nicht der Fall sein, klicken Sie vorher im Server-Fenster auf den kleinen Knopf unter dem Verbinden-Knopf und die Liste wird neu geholt. Nach einer Weile wird sich [[aMule_Project_FAQ:About|aMule]] mit einem Server verbinden (das merken Sie daran, dass die Meldung "nicht verbunden" in der unteren rechten Ecke verschwinden). Sobald Sie verbunden sind, wechseln sie ins Suchen-Fenster und suchen Sie nach den gewünschten Dateien. Haben Sie sie gefunden, können Sie mit einem Doppelklick darauf den Download anstoßen.

Für allgemeine Hinweise zu Benutzung von [[aMule_Project_FAQ:About|aMule]] kommen Sie nach #amule auf irc.freenode.net oder fragen Sie in den Foren auf [http://www.amule.org/amule http://www.amule.org/amule] um Rat.

== Welches sind die besten Einstellungen, um eine optimale Downloadrate zu erzielen? ==

Wenn Sie "Welche Grenzen hat das [[FAQ_eD2k-Kademlia|ED2K]]-Netzwerk?" verstanden haben, wissen Sie, dass es das Beste ist, sofern ihre Anbindung dies erlaubt, die Uploadbandbreite auf ein Minimum von 10KB/s zu stellen. Außerdem, wenn sie "Was hat es mit all den Credits, Wertungen und Punkten auf sich?" gelesen haben, sollten Sie wissen, dass mit der uploadrate auch Ihre downloadrate steigt. Setzen Sie also den Upload so hoch wie möglich, geben sie bekannte und beliebte Dateien frei (stellen Sie nicht zuviele Dateien zur Verfügung (nicht mehr als etwa 200), da Sie sonst womöglich von einigen Server aufgrund zu hohen Traffics abgelehnt werden) und versuchen Sie, auch kleinere, populäre Dateien vorzuhalten, da einige Clients zusätzliche Credits vergeben, wenn Sie ihnen eine komplette kleinere Datei liefern können. Ein guter Rat (vielen Dank an kaouete) ist es, bei einer seltenen oder "niemals fertig werden wollenden" Datei einem Client, der Ihnen ein Stück davon hochlädt, einen Freundes-Uploadplatz zuzuweisen, so dass er, wenn er etwas von Ihnen herunterladen will, sofort zum Zug kommt und Sie im Gegenzug bessere Credits erhalten.

== Gibt es einen Weg, alle ED2K-Links aus einer Textdatei auf einmal zu laden? ==

Ja, gibt es. Speichern Sie einfach alle Links, die Sie downloaden wollen, in einer Textdatei, jeweils einen pro Zeile, nennen Sie diese Datei ''EDED2KLinks'', plazieren Sie sie in ''~/.aMule'' und aMule wird sie automatisch finden, die enthaltenen Links der Downloadliste hinzufügen und die Datei löschen.

[[ED2KLinks_file|Hier]] können Sie mehr über die Funktion dieser Datei nachlesen.

== Kann man [[aMule_Project_FAQ:About|aMule]] genauso mittels telnet fernsteuern, wie das bei [[eDonkey2000|eDonkey]] der Fall ist? ==

Ja, das geht, aber nicht auf genau die gleiche Weise, wie bei [[eDonkey2000|eDonkey]]. Starten Sie einfach eine normale ssh-Verbindung zum Computer, auf dem [[aMule_Project_FAQ:About|aMule]] läuft und verbinden Sie sich mittels <code>amulecmd</code> zu [[aMule_Project_FAQ:About|aMule]]. Um neue Downloads anzustoßen, benutzen Sie den Befehl [[ed2k_command|ed2k]]. Damit das funktioniert, muss [[aMuleCMD]] allerdings vorher konfiguriert werden.

Für Sie vielleicht auch interessant ist ein anderes Tool, [[CAS]] (Aufruf mit <code>cas</code>), das grundlegende Statistiken über [[aMule_Project_FAQ:About|aMule]] anzeigt.

Ansonsten bliebe da noch der [[amuleweb|aMule WebServer]], wenn es Sie nicht stört, dass Sie zu seiner Nutzung einen Webbrowser auf dem CLient laufen lassen müssen. Auch der aMule WebServer muss vorher konfiguriert werden.

== Bekommt man [[aMule_Project_FAQ:About|aMule]] auch ohne grafische Oberfläche zum Laufen? ==

Ja. Beginnend mit aMule 2.0.0-rc6 kann man dafür den aMule Daemon benutzen (zu starten mit <code>amuled</code>). Zu kontrollieren ist er genauso wie der "normale" aMule, also via Browser oder aMuleCMD.

Bis Version 2.0.0-rc6 war [[aMule_Project_FAQ:About|aMule]] ein monolithisches Programm, Netzwerkteil und Oberfläche waren zu einem einzigen, riesigen Klotz verschmolzen. Seitdem haben die Entwickler begonnen, stückweise beide Teile voneinander zu trennen.

Für diejenigen, die noch eine ältere Version benutzen oder die aMuleD (aMule Daemon) nicht verwenden möchten, gibt es noch zwei andere Möglichkeiten, aMule ohne GUI laufen zu lassen, diese sind aber indirekt:
*Einmal mittels ''[http://x.org/4.4.0/Xvfb.1.html Xvfb]''
*Oder via ''[http://www.realvnc.com VNC]''

'''Mittels ''[http://x.org/4.4.0/Xvfb.1.html Xvfb]:'''

Dazu starten Sie <code>[http://x.org/4.4.0/Xvfb.1.html Xvfb]</code> und darin dann aMule. Danach können Sie aMule auf die übliche Weise mit [[aMuleCMD]] und [[ed2k_command|ed2k]] kontrollieren, als würden Sie es über ssh benutzen (siehe oben).

Einfaches Beispiel:
*Start von [http://x.org/4.4.0/Xvfb.1.html Xvfb]: <code>Xvfb :1 -screen 0 640x480x16 &</code>
*Das zu verwendende X-Display für aMule setzen: <code>export DISPLAY=:1</code>
*Als letztes [[aMule_Project_FAQ:About|aMule]] aufrufen: <code>amule &</code> />

'''Hinweis:''' Nachdem mit <code>export DISPLAY=:1</code> die X-Ausgabe auf den Xvfb gesetzt wurde, gilt das für '''alle''' X-Anwendungen, die von dieser Shell aufgerufenw erden. Möchten Sie das vermeiden, starten Sie [[aMule_Project_FAQ:About|aMule]] wie folgt, um die Änderung auf es zu begrenzen: <code>DISPLAY=:1 amule &</code>

'''Via ''[http://www.realvnc.com VNC]:'''

Statt [http://x.org/4.4.0/Xvfb.1.html Xvfb] kann man auch ''vncserver'' benutzen, um etwas Ähnliches zu erreichen. Installieren Sie einfach RealVNC und starten Sie ''vncserver :1 -geometry 1024x768'' gefolgt von ''export DISPLAY=:1''. Das erzeugt einen im Hintergrund laufenden [http://x.org X]-Server, auf den mit einem [http://www.realvnc.com VNC]-Client zugegriffen werden kann. Sobald der [http://x.org X]-Server läuft, benötigen Sie noch einen Windowmanager. (Genaugenommen brauchen Sie ihn nicht, aber es ist nützliche, aMule einfach schließen zu können, anstatt es "abschießen" zu müssen) [http://fluxbox.sourceforge.net FluxBox] ist aufgrund seines geringen Speicher- und CPU-Verbrauchs empfehlenswert (aber auch andere, kleine Windowmanager wie twm erfüllen diesen Zweck). Einfach mit ''fluxbox &'' starten und danach aMule via ''amule &''. Jetzt können Sie sich zum [http://www.realvnc.com VNC]-Server verbinden und das [[aMule]]-Fenster ganz normal verwenden.

Berücksichtigen Sie bitte, dass, wenn [[aMule]] ein Dialogfenster anzeigt, dass auf eine Nutzereingabe wartet (wie es beim ersten Start geschieht), es stehenbliebt, bis sich jemand mit dem VNV verbindet und den Dialog schließt. Normalerweise ist das nur einmal nötig (später kann die Verbindung benutzt werden, um Einstellungen zu verändern oder die Serverliste neu zu laden), und [[aMule]] sollte ab dann ohne Hilfe des Nutzers starten und lediglich Statusinformationen anzeigen.

Wenn Sie Hilfe zu diesem Thema benötigen, suchen Sie in [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule Foren] oder kommen Sie in den [[IRC]]-Kanal #amule auf irc.freenode.net und fragen Sie einfach.

== Kann ich zwei Instanzen von [[aMule_Project_FAQ:About|aMule]] zur gleichen Zeit laufen lassen? ==

Ja, obwohl das nicht empfehlenswert ist. aMule prüft nur, ob der aktuelle Benutzer bereits eine Instanz laufen hat, es können also soviele gleichzeitig laufen, wie es Benutzer auf dem System gibt.
Dafür startet man aMule einfach mit <code>sux user -c amule &</code> unter einer anderen Benutzerkennung.

Aber Vorsicht, aMule kann nur feststellen, ob der aktuelle Benutzer bereits auf dem gleichen X Display eine Instanz laufen hat. Wenn also unter dem aktuellen Account bereits ein aMule auf einem anderen Display läuft, darf man keinen zweiten starten, da es sonst fehlerhafte Konfigurationseinstellungen und beschädigte temporäre Dateien geben kann.

== Woher bekommt man diese hübschen [[aMule_Project_FAQ:About|aMule]]-Statistiken, die die Leute im IRC posten? ==

Sie können entweder die Ausgabe von [[CAS]] (C [[aMule_Project_FAQ:About|aMule]] Statistik, [[CAS]] ist mit <code>cas</code> zu starten) oder, wenn Sie xChat als IRC-Client benutzen und das Perl-Modul installiert haben, [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistik) verwenden.

== Was ist Slot-Zuweisung? ==

Jeder Upload ist ein Slot, wenn Sie also zu fünf Clients zur gleichen Zeit hochladen, haben Sie fünf bestehende Slots. Slot-Zuweisung ist die Uploadbandbreite, die jedem Slot zugewiesen ist.

Zum Beispiel: Wenn Sie ein Upload-Limit von 20KB/s haben, können Sie die Slot-Zuweisung auf 2KB/s setzen, dann werden maximal 10 Clients in der Lage sein, gleichzeitig von Ihnen herunterzuladen, jeder mit einer maximalen Übertragungsrate von 2KB/s.

Siehe aber auch "Warum ignoriert aMule die Bandbreiteneinstellung per Slot?" in [[AMule_problems|Häufig auftretende Probleme mit aMule]].

== Was ist ein Freundes-Slot? ==

Ein Freundes-Slot wird speziell einem Client aus der Freundesliste zugewiesen, nur einer kann einen solchen zu jedem Zeitpunkt haben. Wenn der Freund (für den der Slot aktiviert wurde) versucht, einen Chunk herunterzuladen, bekommt er sofort die höchste Priorität in der Uploadwarteschlange, da ihm der Slot fest zugeteilt ist. Solange der Freund nichts herunterlädt, wird der Slot dem Client mit der höchsten Warteschlangenwertung zugeteilt, genau wie erwartet.

== Warum sollte man die maximalen Leitungskapazitäten in den Einstellungen angeben? Sollten [[aMule_Project_FAQ:About|aMule]] denn nicht nur die Bandbreiten-Beschränkungen interessieren? ==

Tatsächlich kümmern aMule nur die Bandbreitenlimits, die Leitungskapazitäten werden nur für die Statistik benötigt. Beispiel: Man hat eine 100KB/s-Anbindung, das Limit wird auf 40KB/s gesetzt, da ein auf dem gleichen Host laufender Webserver mindestens 60KB/s für die Befriedigung der Anfragen benötigt. Nun lädt man einige seltene freie indonesische Stücke herunter, man bekommt nie mehr als 3KB/s im Download. Damit die Grafik im Statistikfenster sinnvolle Aussagekraft hat, setzt man die Downloadkapazität auf 5KB/s, denn bei 100KB/s wäre lediglich ein horizontaler Strich ohne jeden Informationsgehalt zu sehen.

== aMule stürzt recht oft ab, kann man es automatisch neustarten lassen? ==

Nein. Man kann dies aber einem Script auftragen, einige davon funktionieren vielleicht sogar, wenn aMule '''einfriert''' und nicht '''abstürzt'''.

Diese Scripte können eventuell von Nutzen sein:
*http://www.amule.org/amule/thread.php?threadid=1232
*http://www.amule.org/amule/thread.php?threadid=542
*http://deepthought.ena.si/mulerunner

== Kann aMule Daten von der Standardeingabe lesen und an GDB oder Valgrind weiterreichen? ==

Ja, bis 2.0.0-rc3 war das nicht möglich, ab 2.0.0-rc4 kann man das mit dem Parameter ''-i'' bzw. ''--enable-stdin'' erreichen. 
Wer noch ein aMule vor 2.0.0-rc4 verwendet, kann [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin Patch] verwenden.

== Wie kann ich von eMule zu aMule wechseln, ohne meine Credits zu verlieren? ==

Wer [[FAQ_aMule#Wofür_sind_die_ganzen_Dateien,_die_aMule_beim_ersten_Start_anlegt?|"Wofür sind die ganzen Dateien, die aMule beim ersten Start anlegt?"]] gelesen hat, weiß bereits, was zu tun ist:

Die Dateien ''cryptkey.dat'', ''clients.met'' und ''preferences.dat'' aus dem eMule-Konfigurationsverzeichnis (bei Windows irgendwo unter ''C:\Programm Dateien\eMule\config'') nach ''~/.aMule'' kopieren. Jetzt verwendet aMule die gleichen Einstellungen. Das war's!.

== Unterstützt aMule Universal Plug and Play (UPnP)? ==

Ja.

== Was hat es mit der Geschichte um das [[rabbit|Kaninchen]] auf sich? ==

Hmm, es fing an... mit... nun ja... es war... folge einfach dem weißen [[rabbit|Kaninchen]] ;-)

== Welche Distribution wird empfohlen / Betriebssysteme zum Ausführen von [[aMule-de|aMule]]? ==

Die unbedingt empfohlene Distribution ist [[YSWPS]]. Das ist zwar noch keine ausgereifte Distribution, aber den Aufwand wert, sich damit zu befassen.

== Wann kommt der nächste aMule raus? ==

Egal, welche nächste Ausgabe, die Antwort ist immer die gleiche, sie lautet für gewöhnlich: [[Soon|Bald]] (Vorschlag: folge dem Link).

FAQ aMule

2006-12-09T20:09:25Z

Phoenix: =Does aMule support Universal Plug and Play (UPnP)?=

<center>
<h4>F.A.Q on [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | [[FAQ_aMule-de|Deutsch]] | [[FAQ_aMule-nl|Nederlands]] | [[FAQ_aMule-ru|Russian]]
</center>

== What is [[aMule_Project_FAQ:About|aMule]]? ==

'''''[[aMule]] is a multi-platform client for the [[FAQ_eD2k-Kademlia|ED2K file sharing network]] and based on the windows client [[eMule]].''''' aMule started in August 2003, as a fork of [[xMule]], which is a fork of [[lMule]].

aMule currently supports [http://www.kernel.org Linux], [http://www.freebsd.org FreeBSD], [http://www.openbsd.org OpenBSD], [http://www.microsoft.com Windows], [http://www.apple.com/macosx MacOS X] and [http://www.microsoft.com/xbox X-Box] on both [http://en.wikipedia.org/wiki/64-bit#32_vs_64_bit 32 and 64 bit] computers.

[[aMule]] is intended to be as user friendly and feature rich as [[eMule]] and to remain faithful to the look and feel of [[eMule]] so users familiar with either [[aMule_Project_FAQ:About|aMule]] or [[eMule]] will be able switch between the two easily.

Since [[aMule_Project_FAQ:About|aMule]] is based upon the [[eMule]] codebase, new features in [[eMule]] tend to find their way into [[aMule]] soon after their inclusion into [[eMule]] so users of [[aMule_Project_FAQ:About|aMule]] can expect to ride the cutting-edge of [[FAQ_eD2k-Kademlia|ED2k]] clients.

The best part is that it's developed by a great team whom are probably even more user friendly than [[aMule_Project_FAQ:About|aMule]] itself. Join us in #amule on irc.freenode.net or visit the [http://www.amule.org/amule aMule forums] if you have any suggestions, questions, problems, bugs, patches or anything else that you might think of.

If you are interested in joining the development team, please contact us via the [http://www.amule.org/amule aMule forums] or in the IRC channel.

== How do I view a client's credits? ==

You can see any client's credits (the credits you owe the client) by right clicking on the client's nickname and selecting ''Show Details''. There is no specific value shown so you can either view the total amount of data that client has sent you or the ''Credits Modifier'' (which is called DL/UL Modifier). In the same dialog window, if that client is in your upload queue, you'll be able to view the client's rate and score on you.

== What do those colors in the progress bar mean? ==

On the downloading transfers list:
*'''Red:''' Chunks in red are chunks with no sources found on current session.
*'''Blue:''' Chunks in blue are chunks with at least one source availble. The more solid blue it is, the more sources available have been found.
*'''Yellow:''' Chunks in yellow are chunks which are being downloaded at this very moment.
*'''Black:''' Chunks in black are chunks which have already been downloaded and verified.
*'''Green:''' When a file is in green it means that it's been completely downloaded and successfully verified (so, it'll be in the Incoming folder).

On the expanded transfers list (can be viewed by double-clicking a transfer):
*'''Black:''' Chunks which that client has and you don't have.
*'''White:''' Chunks which that client doesn't have.
*'''Green:''' Chunks which that client has and you have, too.
*'''Yellow:''' Chunks which that client is currently uploading to you.

On the uploading transfers list:
*Black: That client has completed and verified that chunk.
*Grey: That client doesn't have that chunk.

Keep in mind that not all clients support telling other clients what parts they have already completed when uploading, so some clients might have no bar at all.

On the shared files window:
*'''Red:''' When there's no source found to have that same chunk (apart from you, of course).
*'''Blue:''' The more solid the blue is, the more spread that chunk is. 

On the search windows:
*'''Black:''' Files in black are those which only a client has been found to have.
*'''Blue:''' Files in blue are those which two or more clients have been found to have. The more solid the blue is, the more clients have been found to have it.
*'''Red:''' Files in red are those which are already in the downloading queue.
*'''Green:''' Files in green are those which you are already sharing (you completely downloaded it).

== What are all these icons? ==

See section "Icons and what they signify" in the [[Getting_Started#Icons_and_What_They_Signify|Getting Started]] guide.

== What do those numbers in brackets in the sources column of the searches window mean? ==

Those are the clients who are known to have the complete file. Even if the number in brackets is 0, it doesn't mean that no one has the complete file, it juts means that no client has marked the shared file as "completed" (lots of clients don't do so). It's a way to have an idea of how many people have the complete file but not the definitive way.

== What do all those numbers in the sources column in the transfers window mean? ==

The sources format is XX/YY + ZZ (WW) where
*'''XX''' stands for the number of sources available (the number of sources found that you can download from)
*'''YY''' stands for the number of sources found (the total number of sources found)
*'''ZZ''' stands for the number of "Asked for another file" sources
*'''WW''' stands for the number of sources from whom you are currently downloading some chunk of that file.

== What do all those numbers in the priority column in the extended transfers window mean? ==

That's the queue position you have on that client for that specific file. Not all clients provide such information, so in some cases, nothing is displayed.

The number in brackets is the amount of positions you have "moved" through that client's upload queue. '''Negative''' numbers stand for positions you have '''won''' in the queue since you were added while '''positive''' numbers mean positions you've '''lost''' since you were added. Notice that when that number is negative, it is displayed blue, while when it's positive, it's displayed red.

== Why are there two transfer rates in the uploading transfer list? ==

When you are uploading some file to some client, the uploading transfer list will show the transfer rate (speed in KBps) in which you are uploading to that client. If, at the same time, that client is uploading to you some file (or files), then the transfer rate's format will change to XX/YY where XX stands for the speed at which you are uploading to that client and YY will stand for the speed at which that client is uploading to you. If you search in the downloading transfers list you'll find that client.

This is useful if you are trying to get a rare file, since you can see which file that client is uploading to you and, if it's the rare file, you can set him a friend slot so that you upload to that client faster and gain more credits on that client (and consequently, download faster from the client).

== What is A4AF? ==

A4AF stands for ''Asked For Another File''. It is a way to optimize the resources on a specific download.

When you try to download a file, aMule gets a list of clients who are sharing that file. Some of these clients might also share some other file which you are also trying to download and, so, you might have that client in two separate download queues.

A4AF tries to avoid this situations. Why? Because you can't download two chunks at the same time from the same client. So, by setting A4AF in a specific download, you are telling aMule to search for any client in that file's download queue who is also in some other file's download queue and remove it from that other download queue. This way, you'll get more sources on that file.

You can also set a specific download to apply A4AF in the opposite way, that is, to give sources to the other downloads. This should be done on downloads which are not to be downloaded with too much hurry or which should be downloaded after some other similar file has been downloaded (in a series of files, for example). This also can be seen as a way of establishing preferences in downloads.

When the request swapping is done, the Queue Rank will be maintained.

'''NOTE:''' A source with a QR lower than 50 in the download with the higher priority will never be swapped. This is done this way to ensure it starts downloading from it.

If a file has XX+ZZ sources, the ZZ sources might include some which have no needed parts. aMule will exclude those if you tell it to swap to the file.

== What do the "QR: xxxx" numbers mean that I see when I look at my sources? ==

QR stands for "Queue Rank" and it is your current position in this source's queue.

Obviously, a lower value is better. If the source is an eMule client and there is no QR number, it's likely that it's queue is full and cannot accept more clients.

== What is the difference between Transfered and Completed in the Transfers window? ==

Transfered shows the amount of data you have received concerning that file. This data is downloaded in a compressed format. Once the data gets to your machine, aMule processes it and decompresses it. The total useful data that can be taken from that received data (that is, the parts of that data which are actually real parts of the file you are trying to download and not headers or such stuff) is the amount that can be viewed in the Completed column.

== What is the difference between pausing and stopping a transfer? ==

When a transfer is paused, all connections related to the paused transfer are broken with the other clients so that no data is transfered, but sources aren't dropped, so that when the transfer is resumed, [[aMule_Project_FAQ:About|aMule]] will try to connect to those sources.

Instead, when a transfer is stopped, all sources are dropped so, when it's resumed, [[aMule_Project_FAQ:About|aMule]] will start searching for clients who are sharing that file.

== What are all those files [[aMule_Project_FAQ:About|aMule]] creates the first time it is run? ==

Most them are the same as [[eMule|eMule]]'s.

Detailed information about each and a list of all of [[aMule]]'s files can be found [[aMule files|here]].

== Can I use [[eMule|eMule]]'s files and settings and vice-versa? ==

Most of them yes. The only ones you can't share between [[aMule_Project_FAQ:About|aMule]] and [[eMule]] are the program configuration (that is, preferences.ini in [[eMule]] and ''~/.aMule/amule.conf'' in [[aMule_Project_FAQ:About|aMule]]). All the [[FAQ_eD2k-Kademlia|ED2K network]] related files can be successfully shared between the two applications with no more effort than copying the files in ''~/.aMule'' to the [[eMule]]'s directory and vice-versa. But have in mind that some files in ''~/.aMule'' are [[aMule_Project_FAQ:About|aMule]] specific, such as ''amulesig.dat'' or ''aMule.tmpl'', so it's better to only move those files that are in both the [[aMule_Project_FAQ:About|aMule]] and the [[eMule]] directory.

Moving half downloaded files is easy: just move them from your [[eMule]] temp directory (by default ''C:\Program files\eMule\Temp'') into ''~/.aMule/Temp'' or whatever your temp directory is in your [[aMule]] configuration.

== What is all that stuff in amulesig.dat and onlinesig.dat? ==

I guess you already read what [[amulesig.dat_file|''amulesig.dat'']] and [[onlinesig.dat_file|''onlinesig.dat'']] are for [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|above]].

So, this files contain the current [[signature]] (the current [[aMule]] status, if enabled, of course).

Detailed information about each of these files can be found in the [[amulesig.dat_file|''amulesig.dat'' article]] and the [[onlinesig.dat_file|''onlinesig.dat'' article]].

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==

Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading.

Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read below "What are the best settings I can set to have a nice download rate". To select recursively all directories inside a certain directory read [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|Is there any way to recursively select a whole directory and its contents?]].

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==

[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways:

[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporary and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively.

If a ~/.xMule directory is found, it will be kept unchanged and [[aMule]] will just copy the configuration files found in it. That means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==

Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it.

For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==

If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==

Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file.

You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==

Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured.

Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics.

Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example:
#Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: <code>Xvfb :1 -screen 0 640x480x16 &</code>
#Set display to use for amule: <code>export DISPLAY=:1</code>
#Then run [[aMule_Project_FAQ:About|aMule]]: <code>amule &</code>

'''Note:''' After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: <code>DISPLAY=:1 amule &</code>

'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:'''

It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==

Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell.

Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statistics some people post on the IRC channels? ==

You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statistics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistics).

== What is slot allocation? ==

Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given.

As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps.

See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==

A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==

aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==

No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''.

The following scripts might suit your needs:
*http://www.amule.org/amule/thread.php?threadid=1232
*http://www.amule.org/amule/thread.php?threadid=542
*http://deepthought.ena.si/mulerunner

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==

Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''.

Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without losing my credits? ==

If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'', ''preferences.dat'', ''preferencesKad.dat'', ''key_index.dat'', ''load_index.dat'' and ''src_index.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

You might still want to take a look at the [[migrate from eMule to aMule]] article, though.

== Does aMule support Universal Plug and Play (UPnP)? ==

YES!

Since Dec, 9th, 2006 the code in our daily tarballs supports UPnP port mappings. The current version of aMule is 2.1.3, so, our next oficial version will have UPnP support.

== What's the story behind the [[rabbit]]? ==

Ah, yeah, this all began... ehm... well... I mean... follow the white [[rabbit]] ;-)

== Which one is the recomended distro / Operating System for running [[aMule]]? ==

The absolutely recomended distro is [[YSWPS]]. It's still not a mature distro, but it's worth the effort to look for it.

== When will next aMule release happen? ==

Whatever next release, the answer is always the same, it is standard: [[Soon]] (suggestion: follow the link).

FAQ aMule

2006-12-09T20:08:17Z

Phoenix: =Does aMule support Universal Plug and Play (UPnP)?=

<center>
<h4>F.A.Q on [[aMule_Project_FAQ:About|aMule]]</h4>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[FAQ_aMule-es|Español]] | [[FAQ_aMule-it|Italiano]] | [[FAQ_aMule-pt_BR|Português]] | [[FAQ_aMule-fr|Français]] | [[FAQ_aMule-de|Deutsch]] | [[FAQ_aMule-nl|Nederlands]] | [[FAQ_aMule-ru|Russian]]
</center>

== What is [[aMule_Project_FAQ:About|aMule]]? ==

'''''[[aMule]] is a multi-platform client for the [[FAQ_eD2k-Kademlia|ED2K file sharing network]] and based on the windows client [[eMule]].''''' aMule started in August 2003, as a fork of [[xMule]], which is a fork of [[lMule]].

aMule currently supports [http://www.kernel.org Linux], [http://www.freebsd.org FreeBSD], [http://www.openbsd.org OpenBSD], [http://www.microsoft.com Windows], [http://www.apple.com/macosx MacOS X] and [http://www.microsoft.com/xbox X-Box] on both [http://en.wikipedia.org/wiki/64-bit#32_vs_64_bit 32 and 64 bit] computers.

[[aMule]] is intended to be as user friendly and feature rich as [[eMule]] and to remain faithful to the look and feel of [[eMule]] so users familiar with either [[aMule_Project_FAQ:About|aMule]] or [[eMule]] will be able switch between the two easily.

Since [[aMule_Project_FAQ:About|aMule]] is based upon the [[eMule]] codebase, new features in [[eMule]] tend to find their way into [[aMule]] soon after their inclusion into [[eMule]] so users of [[aMule_Project_FAQ:About|aMule]] can expect to ride the cutting-edge of [[FAQ_eD2k-Kademlia|ED2k]] clients.

The best part is that it's developed by a great team whom are probably even more user friendly than [[aMule_Project_FAQ:About|aMule]] itself. Join us in #amule on irc.freenode.net or visit the [http://www.amule.org/amule aMule forums] if you have any suggestions, questions, problems, bugs, patches or anything else that you might think of.

If you are interested in joining the development team, please contact us via the [http://www.amule.org/amule aMule forums] or in the IRC channel.

== How do I view a client's credits? ==

You can see any client's credits (the credits you owe the client) by right clicking on the client's nickname and selecting ''Show Details''. There is no specific value shown so you can either view the total amount of data that client has sent you or the ''Credits Modifier'' (which is called DL/UL Modifier). In the same dialog window, if that client is in your upload queue, you'll be able to view the client's rate and score on you.

== What do those colors in the progress bar mean? ==

On the downloading transfers list:
*'''Red:''' Chunks in red are chunks with no sources found on current session.
*'''Blue:''' Chunks in blue are chunks with at least one source availble. The more solid blue it is, the more sources available have been found.
*'''Yellow:''' Chunks in yellow are chunks which are being downloaded at this very moment.
*'''Black:''' Chunks in black are chunks which have already been downloaded and verified.
*'''Green:''' When a file is in green it means that it's been completely downloaded and successfully verified (so, it'll be in the Incoming folder).

On the expanded transfers list (can be viewed by double-clicking a transfer):
*'''Black:''' Chunks which that client has and you don't have.
*'''White:''' Chunks which that client doesn't have.
*'''Green:''' Chunks which that client has and you have, too.
*'''Yellow:''' Chunks which that client is currently uploading to you.

On the uploading transfers list:
*Black: That client has completed and verified that chunk.
*Grey: That client doesn't have that chunk.

Keep in mind that not all clients support telling other clients what parts they have already completed when uploading, so some clients might have no bar at all.

On the shared files window:
*'''Red:''' When there's no source found to have that same chunk (apart from you, of course).
*'''Blue:''' The more solid the blue is, the more spread that chunk is. 

On the search windows:
*'''Black:''' Files in black are those which only a client has been found to have.
*'''Blue:''' Files in blue are those which two or more clients have been found to have. The more solid the blue is, the more clients have been found to have it.
*'''Red:''' Files in red are those which are already in the downloading queue.
*'''Green:''' Files in green are those which you are already sharing (you completely downloaded it).

== What are all these icons? ==

See section "Icons and what they signify" in the [[Getting_Started#Icons_and_What_They_Signify|Getting Started]] guide.

== What do those numbers in brackets in the sources column of the searches window mean? ==

Those are the clients who are known to have the complete file. Even if the number in brackets is 0, it doesn't mean that no one has the complete file, it juts means that no client has marked the shared file as "completed" (lots of clients don't do so). It's a way to have an idea of how many people have the complete file but not the definitive way.

== What do all those numbers in the sources column in the transfers window mean? ==

The sources format is XX/YY + ZZ (WW) where
*'''XX''' stands for the number of sources available (the number of sources found that you can download from)
*'''YY''' stands for the number of sources found (the total number of sources found)
*'''ZZ''' stands for the number of "Asked for another file" sources
*'''WW''' stands for the number of sources from whom you are currently downloading some chunk of that file.

== What do all those numbers in the priority column in the extended transfers window mean? ==

That's the queue position you have on that client for that specific file. Not all clients provide such information, so in some cases, nothing is displayed.

The number in brackets is the amount of positions you have "moved" through that client's upload queue. '''Negative''' numbers stand for positions you have '''won''' in the queue since you were added while '''positive''' numbers mean positions you've '''lost''' since you were added. Notice that when that number is negative, it is displayed blue, while when it's positive, it's displayed red.

== Why are there two transfer rates in the uploading transfer list? ==

When you are uploading some file to some client, the uploading transfer list will show the transfer rate (speed in KBps) in which you are uploading to that client. If, at the same time, that client is uploading to you some file (or files), then the transfer rate's format will change to XX/YY where XX stands for the speed at which you are uploading to that client and YY will stand for the speed at which that client is uploading to you. If you search in the downloading transfers list you'll find that client.

This is useful if you are trying to get a rare file, since you can see which file that client is uploading to you and, if it's the rare file, you can set him a friend slot so that you upload to that client faster and gain more credits on that client (and consequently, download faster from the client).

== What is A4AF? ==

A4AF stands for ''Asked For Another File''. It is a way to optimize the resources on a specific download.

When you try to download a file, aMule gets a list of clients who are sharing that file. Some of these clients might also share some other file which you are also trying to download and, so, you might have that client in two separate download queues.

A4AF tries to avoid this situations. Why? Because you can't download two chunks at the same time from the same client. So, by setting A4AF in a specific download, you are telling aMule to search for any client in that file's download queue who is also in some other file's download queue and remove it from that other download queue. This way, you'll get more sources on that file.

You can also set a specific download to apply A4AF in the opposite way, that is, to give sources to the other downloads. This should be done on downloads which are not to be downloaded with too much hurry or which should be downloaded after some other similar file has been downloaded (in a series of files, for example). This also can be seen as a way of establishing preferences in downloads.

When the request swapping is done, the Queue Rank will be maintained.

'''NOTE:''' A source with a QR lower than 50 in the download with the higher priority will never be swapped. This is done this way to ensure it starts downloading from it.

If a file has XX+ZZ sources, the ZZ sources might include some which have no needed parts. aMule will exclude those if you tell it to swap to the file.

== What do the "QR: xxxx" numbers mean that I see when I look at my sources? ==

QR stands for "Queue Rank" and it is your current position in this source's queue.

Obviously, a lower value is better. If the source is an eMule client and there is no QR number, it's likely that it's queue is full and cannot accept more clients.

== What is the difference between Transfered and Completed in the Transfers window? ==

Transfered shows the amount of data you have received concerning that file. This data is downloaded in a compressed format. Once the data gets to your machine, aMule processes it and decompresses it. The total useful data that can be taken from that received data (that is, the parts of that data which are actually real parts of the file you are trying to download and not headers or such stuff) is the amount that can be viewed in the Completed column.

== What is the difference between pausing and stopping a transfer? ==

When a transfer is paused, all connections related to the paused transfer are broken with the other clients so that no data is transfered, but sources aren't dropped, so that when the transfer is resumed, [[aMule_Project_FAQ:About|aMule]] will try to connect to those sources.

Instead, when a transfer is stopped, all sources are dropped so, when it's resumed, [[aMule_Project_FAQ:About|aMule]] will start searching for clients who are sharing that file.

== What are all those files [[aMule_Project_FAQ:About|aMule]] creates the first time it is run? ==

Most them are the same as [[eMule|eMule]]'s.

Detailed information about each and a list of all of [[aMule]]'s files can be found [[aMule files|here]].

== Can I use [[eMule|eMule]]'s files and settings and vice-versa? ==

Most of them yes. The only ones you can't share between [[aMule_Project_FAQ:About|aMule]] and [[eMule]] are the program configuration (that is, preferences.ini in [[eMule]] and ''~/.aMule/amule.conf'' in [[aMule_Project_FAQ:About|aMule]]). All the [[FAQ_eD2k-Kademlia|ED2K network]] related files can be successfully shared between the two applications with no more effort than copying the files in ''~/.aMule'' to the [[eMule]]'s directory and vice-versa. But have in mind that some files in ''~/.aMule'' are [[aMule_Project_FAQ:About|aMule]] specific, such as ''amulesig.dat'' or ''aMule.tmpl'', so it's better to only move those files that are in both the [[aMule_Project_FAQ:About|aMule]] and the [[eMule]] directory.

Moving half downloaded files is easy: just move them from your [[eMule]] temp directory (by default ''C:\Program files\eMule\Temp'') into ''~/.aMule/Temp'' or whatever your temp directory is in your [[aMule]] configuration.

== What is all that stuff in amulesig.dat and onlinesig.dat? ==

I guess you already read what [[amulesig.dat_file|''amulesig.dat'']] and [[onlinesig.dat_file|''onlinesig.dat'']] are for [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|above]].

So, this files contain the current [[signature]] (the current [[aMule]] status, if enabled, of course).

Detailed information about each of these files can be found in the [[amulesig.dat_file|''amulesig.dat'' article]] and the [[onlinesig.dat_file|''onlinesig.dat'' article]].

== I just installed [[aMule_Project_FAQ:About|aMule]] for the first time. How do I set it up? ==

Setting up aMule properly is just a matter of tastes and depends on many factors. If you just wish a quick startup configuration, then continue reading.

Open [[aMule_Project_FAQ:About|aMule]] and click on the Preferences button. Set a nickname and the language in which you wish to have [[aMule_Project_FAQ:About|aMule]]. Then switch to the Connection tab and input your Line Capacities. Then input the Bandwidth Limits according to the maximum amount of bandwidth you want [[aMule_Project_FAQ:About|aMule]] to use. Then switch to the Directories tab and set a directory for both the temporary files (where files will be stored until they are completely downloaded) and the completed files. Finally, select the directories which you want to share. It is not recommended to share too much files. Read below "What are the best settings I can set to have a nice download rate". To select recursively all directories inside a certain directory read [[aMule_problems#Is there any way to recursively select a whole directory and its contents?|Is there any way to recursively select a whole directory and its contents?]].

== Will [[aMule_Project_FAQ:About|aMule]] handle my [[xMule]] and [[lMule]] files? What should I do? ==

[[aMule_Project_FAQ:About|aMule]] automatically handles both [[lMule]] and [[xMule]]'s configuration files, but in different ways:

[[lMule]] has been discontinued for several years now, so [[aMule_Project_FAQ:About|aMule]] understands that you are replacing [[lMule]] with [[aMule_Project_FAQ:About|aMule]], so it renames ~/.lMule folder to ~/.aMule. If you used ~/.lMule/Temp and ~/.lMule/Incoming as your temporary and downloading directories respectively, you should change the paths in Preferences to ~/.aMule/Temp and ~/.aMule/Incoming respectively.

If a ~/.xMule directory is found, it will be kept unchanged and [[aMule]] will just copy the configuration files found in it. That means that the files you were downloading will remain in the ~/.xMule directory if they were downloading there, but since [[aMule_Project_FAQ:About|aMule]] has handled [[xMule]]'s configuration files, it will still use it. You can either live with that, or move directories ~/.xMule/Temp and ~/.xMule/Incoming into ~/.aMule and change directories in Preferences.

== How do I start my [[aMule_Project_FAQ:About|aMule]] experience? ==

Just click on the Connect button. You should have some servers listed on the Servers window, though. If you have no servers listed, then click on the little button below the Connect button in the Servers window before clicking the Connect button. After some time, [[aMule_Project_FAQ:About|aMule]] will be connected to some server (you'll know because in the lower right corner the "Not connected" message will disappear). When connected, switch to the Search window and search for the file you want and once you find the file you want, double-click on it.

For general [[aMule_Project_FAQ:About|aMule]] usage, join [[aMule_Project_FAQ:About|aMule]] #amule in irc.freenode.net or ask in forums at [http://www.amule.org/amule http://www.amule.org/amule]

== What are the best settings I can set to have a nice download rate? ==

If you understood "Is there any limit on the [[FAQ_eD2k-Kademlia|ED2K]] network?" then you might have seen that, if your provider allows you, the best is to have the upload limit set to a minimum of 10 KBps. Also, if you understood "What is all that credits, rate and score stuff about?", you might also understand that the more you upload, the more you download, so take the upload limit up as much as you can. A good tip (thanks to kaouete) when you are trying to download some rare or "never completing" file, is, whenever you see someone uploading to you some chunk of that file, give that client a friend slot so that, if it tries to download something from you, it gets preference and you gain credits on that client.

== Is there a way to open a text file and load all the ed2k links from the file? ==

Yes, there is. Just place all the ed2k links you want to download in a text file, each ed2k link in a separate line. Name that file ''ED2KLinks'' then place it in ''~/.aMule'' and aMule will automatically detect it, add all those ed2k links to download and remove the file.

You might want to read [[ED2KLinks_file|this]] to know more about this file.

== Can I manage [[aMule_Project_FAQ:About|aMule]] remotely through telnet in the same way I do with [[eDonkey2000|eDonkey]]? ==

Yes you can, but not exactly in the same way as you do with [[eDonkey2000|eDonkey]]. Just start a normal telnet (or ssh) session with the host computer (the one running [[aMule_Project_FAQ:About|aMule]]) and, once in, use amulecmd to take control over [[aMule_Project_FAQ:About|aMule]]. To start new downloads just use the [[ed2k_command|ed2k command]]. Remember [[aMuleCMD]] must be configured.

Another aMule utility that might be of your interest is [[CAS]] (which's command is <code>cas</code>) which will show basic [[aMule_Project_FAQ:About|aMule]] statistics.

Also, [[amuleweb|aMule WebServer]] might be what you are looking for if you can and don't mind using a web browser on the client computer. Have in mind that aMule WebBrowser must also be configured.

== Is there any way to start [[aMule_Project_FAQ:About|aMule]] with no graphical interface? ==

Yes. Since aMule 2.0.0-rc6, you can use aMule Daemon, which can be executed on the command line by typing ''amuled''. To control it, use either aMuleWeb, aMuleCMD or any other such application for remotely controlling aMule.

Anyway, up to aMule 2.0.0-rc6, [[aMule_Project_FAQ:About|aMule]] was a monolithic application. This means that core and GUI were whole inseparable block.

So, for those using an old aMule version or who refuse to use aMuled (aMule Daemon), there are still two walkarounds to run [[aMule_Project_FAQ:About|aMule]] on command line but they're not direct ways:
*Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]''
*Through ''[http://www.realvnc.com VNC]''

'''Through ''[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]:''' 
You should run <code>[http://xfree.org/4.4.0/Xvfb.1.html Xvfb]</code> and then run aMule in it. Afterwards you can take control over [[aMule_Project_FAQ:About|aMule]] using [[aMuleCMD]] and [[ed2k_command|ed2k]] in the same way as you would if you were accessing [[aMule_Project_FAQ:About|aMule]] remotely over telnet (see above).

Short example:
#Run [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]: <code>Xvfb :1 -screen 0 640x480x16 &</code>
#Set display to use for amule: <code>export DISPLAY=:1</code>
#Then run [[aMule_Project_FAQ:About|aMule]]: <code>amule &</code>

'''Note:''' After running <code>export DISPLAY=:1</code>, all graphical applications launched from that shell will be opened in [http://xfree.org/4.4.0/Xvfb.1.html Xvfb]'s display. To avoid this, you can run [[aMule_Project_FAQ:About|aMule]] with the following command, so that only [[aMule_Project_FAQ:About|aMule]] runs there: <code>DISPLAY=:1 amule &</code>

'''INFO:''' See the [[Screen]] page to know more about the [[Screen]] command

'''Through ''[http://www.realvnc.com VNC]:'''

It's also possible to use ''vncserver'' instead of [http://xfree.org/4.4.0/Xvfb.1.html Xvfb] to achieve something similar. Just install ''vncserver'' and execute ''vncserver :0 -geometry 1024x768'' followed by ''export DISPLAY=:0''. This will create a hidden [http://xfree.org X] server, accessible only remotely using a [http://www.realvnc.com VNC] client. Once the [http://xfree.org X] server is running, you will need a window manager to manage [[aMule]] window (well, it's not really needed, but it's useful if you want to be able to close [[aMule]] without simply killing it), I recommend [http://fluxbox.sourceforge.net FluxBox] due to its low CPU and memory requirements. Just start it with ''fluxbox &'' and then run [[aMule]] with ''amule &''. Now you can connect to the [http://www.realvnc.com VNC] server and see the [[aMule]] window.

Keep in mind that if [[aMule]] shows any dialog that requires user input (like the one showed the first time [[aMule]] is executed), it will get stuck there until someone connects to the [http://www.realvnc.com VNC] server and clicks ok in the dialog. Usually, this should only need to be done once (and this connection may be used to update the serverlist and set the preferences), from then on [[aMule]] will start without user interaction, showing only some informational messages at startup.

If you need help on this issue, search [[aMule_Project_FAQ:About|aMule]]'s [http://www.amule.org/amule forums] or join #amule [[IRC]] channel at irc.freenode.net and ask.

== Can I run two [[aMule_Project_FAQ:About|aMule]] instances at the same time? ==

Yes you can, although it is not recommended. [[aMule_Project_FAQ:About|aMule]] will only check if the concurrent user is running some [[aMule_Project_FAQ:About|aMule]] instance, so you can run as many [[aMule_Project_FAQ:About|aMule]] instances as user accounts you have access to. To do this, just run <code>xhost +</code> and then <code>su</code> as another user and run aMule from that shell.

Be aware, since [[aMule_Project_FAQ:About|aMule]] can't check if a user is running [[aMule_Project_FAQ:About|aMule]] on another X display. So, if your account is already running some [[aMule_Project_FAQ:About|aMule]] instance in some other X display, do not run another [[aMule_Project_FAQ:About|aMule]] instance on another X display or you might end up with lost configuration settings and corrupt chunks.

== How can I get those nice [[aMule_Project_FAQ:About|aMule]] statistics some people post on the IRC channels? ==

You can either copy and paste [[CAS]]'s (C [[aMule_Project_FAQ:About|aMule]] Statistics) output (to execute [[CAS]], run <code>cas</code>) or, if you use xChat as your IRC client and have the Perl module installed, you could use [[XAS]] (xChat [[aMule_Project_FAQ:About|aMule]] Statistics).

== What is slot allocation? ==

Each upload is a slot, so, if you are uploading to five clients at the same time, you have five upload slots established. So, the amount of slot allocation is the bandwidth which each slot will be given.

As an example, if your upload limit is 20KBps, you can set slot allocation to 2KBps which means 10 clients will be able to download from you at the same time, each of them at a maximum transfer rate of 2KBps.

See section "Why is aMule ignoring the bandwidth I set per slot?" in [[AMule_problems|aMule common problem's FAQ]].

== What is a friend slot? ==

A friend slot is just a slot which is assigned to a client in the friends list. Only one friend can have a slot at the same time. Whenever that friend (who has the friend slot enabled) tries to download a file from you, it will be given highest priority in the uploads queue, since it has that slot always assigned. While that friend isn't downloading, that assigned slot will be given to the client with the highest priority in the upload queue, as expected.

== What is the real point on setting up Line Capacities in Preferences? Shouldn't [[aMule_Project_FAQ:About|aMule]] only care for the Bandwidth Limits? ==

aMule really only cares for the Bandwidth Limits. Line Capacities are only set for the Statics display. Let's see: Imagine you have a 100KBps connection, imagine you want to set the Limit at 40KBps because you have a web server which needs a minimum of 60KBps to serve all the petitions. Now imagine you download rare indonesian free songs. You most surely never download at more than 3KBps ever. So, you could set Line Capacities at 5KBps so that the graph at Statics has some meaning, since if you set it up as a 100KBps connection, the graph will show an horizontal line with no meaning at all.

== aMule is crashing quite often here. Can I set it to restart every time it crashes? ==

No, you can't. But you can have scripts to do so. Some of these scripts even work if aMule '''hangs''' but doesn't '''crash'''.

The following scripts might suit your needs:
*http://www.amule.org/amule/thread.php?threadid=1232
*http://www.amule.org/amule/thread.php?threadid=542
*http://deepthought.ena.si/mulerunner

== Can I have aMule get data from the standard input to pass it to GDB or Valgrind? ==

Yes, you can. Up to aMule 2.0.0-rc3 this wasn't allowed, but as of version 2.0.0-rc4 you can with the parameter ''-i'' or ''--enable-stdin''.

Anyway, people with aMule versions previous to 2.0.0-rc4 can use [http://www.amule.org/amule/thread.php?threadid=2474 phoenix's aMule stdin patch].

== How can I switch to aMule from eMule without losing my credits? ==

If you already read [[FAQ_aMule#What_are_all_those_files_aMule_creates_the_first_time_it_is_run?|about the meaning of aMule's files]], you might already know what you have to do: 
Get ''cryptkey.dat'', ''clients.met'', ''preferences.dat'', ''preferencesKad.dat'', ''key_index.dat'', ''load_index.dat'' and ''src_index.dat'' files from eMule's config directory (usually, under Windows, something like ''C:\Program files\eMule\config'') and copy them into ''~/.aMule''. Now start aMule so it reads those files. You're done!

You might still want to take a look at the [[migrate from eMule to aMule]] article, though.

== Does aMule support Universal Plug and Play (UPnP)? ==

YES!

Since Dec, 9th, 2006 the code in our daily tarballs supports UPnP port mappings.

== What's the story behind the [[rabbit]]? ==

Ah, yeah, this all began... ehm... well... I mean... follow the white [[rabbit]] ;-)

== Which one is the recomended distro / Operating System for running [[aMule]]? ==

The absolutely recomended distro is [[YSWPS]]. It's still not a mature distro, but it's worth the effort to look for it.

== When will next aMule release happen? ==

Whatever next release, the answer is always the same, it is standard: [[Soon]] (suggestion: follow the link).

Events

2006-12-02T21:59:35Z

Phoenix:

<center>
'''English''' | [[events-de|German]] | [[events-nds|Low-Saxon]]
</center>

'''Events''' are actions aMule can take upon when certain things happen. This actions can be configured on the Events tab of the [[Usage_Preferences]] notebook.

There are two kinds of Events supported at the moment:
* Download completed
* New chat session

When one of these events is triggered, you can configure aMule to execute a
* core command
* GUI command

A core command is a command that will be executed by a flavor of aMule that has a core (aMule daemon or aMule monolithic). A GUI command is a command that will be executed by a flavor of aMule that has GUI (aMule GUI or aMule monolithic). Notice that if you specify both, aMule monolithic will execute both.

=== Download completed ===

When a Download completed event is triggered, the following variables can be accessed:
* %NAME - the name of the downloaded file with full path
* %FILE - the name of the downloaded file without path
* %HASH - the ed2k hash of the downloaded file
* %SIZE - the size in bytes of the downloaded file
* %DLACTIVETIME - the total time the download was active

=== New chat session ===

When a New chat session event is triggered, one variable can be accessed:
* %Sender - username of the person initiating the chat

=== Syntax ===

To call an external script, enter the script name in the core command field, followed by the optional variables. For example:

:MyScript.sh %NAME %FILE %HASH %SIZE "%DLACTIVETIME"

'''Note:''' If the filename contains spaces, the variable names should be enclosed in quotes like this:

:MyScript.sh "%NAME" "%FILE" %HASH %SIZE "%DLACTIVETIME"

You need to make sure your script in your PATH or that you supply the pathname.

== Examples ==
Here the bash script by '''Ezeltje''' from [http://forum.amule.org/thread.php?threadid=11695 aMule-Forum] which will send you an email every time a download is completed. To use it, enter your email address where indicated and save it to a location in your PATH. Then add this line:

:doneDL.sh "%NAME" "%FILE" %HASH %SIZE "%DLACTIVETIME"

to the Core command field of the Download completed section of the Events page. It will now be invoked everytime aMule finishes a download.

#!/bin/bash
#
# doneDL.sh - sends an email upon completion of an aMule download
# Used in conjuction with aMule's Event feature
#
# Call like this: doneDL.sh "%NAME" "%FILE" %HASH %SIZE "%DLACTIVETIME"
#
# Enter your email address here:
eMail=
#
NameShort=$1
NameLong=$2
Hash=$3
Size=$4
DlActiveTime=$5
{
echo aMule completed this download:
echo ------------------------------
echo
echo File: "$NameLong"
echo Hash: $Hash
echo -n "Time: "
date | awk '{print $4 " " $5}'
echo -n Size: $Size bytes
if [ $Size -gt 102400 ] ; then echo " ("$(($(($Size / 1024)) / 1024)) "Mb)" ; fi
echo Dowload Active Time: $DlActiveTime
echo
echo --------------------------------------------------------------------
cas
echo -n "Resident memory: "
echo $(ps u -C amule --no-headers | awk '{print $6}') kB
echo -n "Virtual memory: "
echo $(ps u -C amule --no-headers | awk '{print $5}') kB
echo --------------------------------------------------------------------
} | mail -s "$NameShort" $eMail

__NOTOC__

Events

2006-12-02T21:56:51Z

Phoenix:

<center>
'''English''' | [[events-de|German]] | [[events-nds|Low-Saxon]]
</center>

'''Events''' are actions aMule can take upon when certain things happen. This actions can be configured on the Events tab of the [[Usage_Preferences]] notebook.

There are two kinds of Events supported at the moment:
* Download completed
* New chat session

When one of these events is triggered, you can configure aMule to execute a
* core command
* GUI command

A core command is a command that will be executed by a flavor of aMule that has a core (aMule daemon or aMule monolithic). A GUI command is a command that will be executed by a flavor of aMule that has GUI (aMule GUI or aMule monolithic). Notice that if you specify both, aMule monolithic will execute both.

=== Download completed ===

When a Download completed event is triggered, the following variables can be accessed:
* %NAME - the name of the downloaded file with full path
* %FILE - the name of the downloaded file without path
* %HASH - the ed2k hash of the downloaded file
* %SIZE - the size in bytes of the downloaded file
* %DLACTIVETIME - the total time the download was active

=== New chat session ===

When a New chat session event is triggered, one variable can be accessed:
* %Sender - username of the person initiating the chat

=== Syntax ===

To call an external script, enter the script name in the core command field, followed by the optional variables. For example:

:MyScript.sh %NAME %FILE %HASH %SIZE

'''Note:''' If the filename contains spaces, the variable names should be enclosed in quotes like this:

:MyScript.sh "%NAME" "%FILE" %HASH %SIZE

You need to make sure your script in your PATH or that you supply the pathname.

== Examples ==
Here the bash script by '''Ezeltje''' from [http://forum.amule.org/thread.php?threadid=11695 aMule-Forum] which will send you an email every time a download is completed. To use it, enter your email address where indicated and save it to a location in your PATH. Then add this line:

:doneDL.sh "%NAME" "%FILE" %HASH %SIZE

to the Core command field of the Download completed section of the Events page. It will now be invoked everytime aMule finishes a download.

#!/bin/bash
#
# doneDL.sh - sends an email upon completion of an aMule download
# Used in conjuction with aMule's Event feature
#
# Call like this: doneDL.sh "%NAME" "%FILE" %HASH %SIZE "%DLACTIVETIME"
#
# Enter your email address here:
eMail=
#
NameShort=$1
NameLong=$2
Hash=$3
Size=$4
DlActiveTime=$5
{
echo aMule completed this download:
echo ------------------------------
echo
echo File: "$NameLong"
echo Hash: $Hash
echo -n "Time: "
date | awk '{print $4 " " $5}'
echo -n Size: $Size bytes
if [ $Size -gt 102400 ] ; then echo " ("$(($(($Size / 1024)) / 1024)) "Mb)" ; fi
echo Dowload Active Time: $DlActiveTime
echo
echo --------------------------------------------------------------------
cas
echo -n "Resident memory: "
echo $(ps u -C amule --no-headers | awk '{print $6}') kB
echo -n "Virtual memory: "
echo $(ps u -C amule --no-headers | awk '{print $5}') kB
echo --------------------------------------------------------------------
} | mail -s "$NameShort" $eMail

__NOTOC__

Events

2006-12-02T19:07:32Z

Phoenix:

<center>
'''English''' | [[events-de|German]] | [[events-nds|Low-Saxon]]
</center>

'''Events''' are actions aMule can take upon when certain things happen. This actions can be configured on the Events tab of the [[Usage_Preferences]] notebook.

There are two kinds of Events supported at the moment:
* Download completed
* New chat session

When one of these events is triggered, you can configure aMule to execute a
* core command
* GUI command

A core command is a command that will be executed by a flavor of aMule that has a core (aMule daemon or aMule monolithic). A GUI command is a command that will be executed by a flavor of aMule that has GUI (aMule GUI or aMule monolithic). Notice that if you specify both, aMule monolithic will execute both.

=== Download completed ===

When a Download completed event is triggered, the following variables can be accessed:
* %NAME - the name of the downloaded file with full path
* %FILE - the name of the downloaded file without path
* %HASH - the ed2k hash of the downloaded file
* %SIZE - the size in bytes of the downloaded file
* %DLACTIVETIME - the total time the download was active

=== New chat session ===

When a New chat session event is triggered, one variable can be accessed:
* %Sender - username of the person initiating the chat

=== Syntax ===

To call an external script, enter the script name in the core command field, followed by the optional variables. For example:

:MyScript.sh %NAME %FILE %HASH %SIZE

'''Note:''' If the filename contains spaces, the variable names should be enclosed in quotes like this:

:MyScript.sh "%NAME" "%FILE" %HASH %SIZE

You need to make sure your script in your PATH or that you supply the pathname.

== Examples ==
Here the bash script by '''Ezeltje''' from [http://forum.amule.org/thread.php?threadid=11695 aMule-Forum] which will send you an email every time a download is completed. To use it, enter your email address where indicated and save it to a location in your PATH. Then add this line:

:doneDL.sh "%NAME" "%FILE" %HASH %SIZE

to the Core command field of the Download completed section of the Events page. It will now be invoked everytime aMule finishes a download.

#!/bin/bash
#
# doneDL.sh - sends an email upon completion of an aMule download
# Used in conjuction with aMule's Event feature
#
# Call like this: doneDL.sh "%NAME" "%FILE" %HASH %SIZE %DLACTIVETIME
#
# Enter your email address here:
eMail=
#
NameShort=$1
NameLong=$2
Hash=$3
Size=$4
DlActiveTime=$5
{
echo aMule completed this download:
echo ------------------------------
echo
echo File: "$NameLong"
echo Hash: $Hash
echo -n "Time: "
date | awk '{print $4 " " $5}'
echo -n Size: $Size bytes
if [ $Size -gt 102400 ] ; then echo " ("$(($(($Size / 1024)) / 1024)) "Mb)" ; fi
echo Dowload Active Time: $DlActiveTime
echo
echo --------------------------------------------------------------------
cas
echo -n "Resident memory: "
echo $(ps u -C amule --no-headers | awk '{print $6}') kB
echo -n "Virtual memory: "
echo $(ps u -C amule --no-headers | awk '{print $5}') kB
echo --------------------------------------------------------------------
} | mail -s "$NameShort" $eMail

__NOTOC__

Events

2006-12-02T03:29:37Z

Phoenix:

<center>
'''English''' | [[events-de|Deutsch]]
</center>

'''Events''' are actions aMule can take upon when certain things happen. This actions can be configured on the Events tab of the [[Usage_Preferences]] notebook.

There are two kinds of Events supported at the moment:
* Download completed
* New chat session

When one of these events is triggered, you can configure aMule to execute a
* core command
* GUI command

A core command is a command that will be executed by a flavor of aMule that has a core (aMule daemon or aMule monolithic). A GUI command is a command that will be executed by a flavor of aMule that has GUI (aMule GUI or aMule monolithic). Notice that if you specify both, aMule monolithic will execute both.

=== Download completed ===

When a Download completed event is triggered, four variables can be accessed:
* %NAME - the name of the downloaded file with full path
* %FILE - the name of the downloaded file without path
* %HASH - the ed2k hash of the downloaded file
* %SIZE - the size in bytes of the downloaded file

=== New chat session ===

When a New chat session event is triggered, one variable can be accessed:
* %Sender - username of the person initiating the chat

=== Syntax ===

To call an external script, enter the script name in the core command field, followed by the optional variables. For example:

:MyScript.sh %NAME %FILE %HASH %SIZE

'''Note:''' If the filename contains spaces, the variable names should be enclosed in quotes like this:

:MyScript.sh "%NAME" "%FILE" %HASH %SIZE

You need to make sure your script in your PATH or that you supply the pathname.

== Examples ==
Here the bash script by '''Ezeltje''' from [http://forum.amule.org/thread.php?threadid=11695 aMule-Forum] which will send you an email every time a download is completed. To use it, enter your email address where indicated and save it to a location in your PATH. Then add this line:

:doneDL.sh "%NAME" "%FILE" %HASH %SIZE

to the Core command field of the Download completed section of the Events page. It will now be invoked everytime aMule finishes a download.

#!/bin/bash
#
# doneDL.sh - sends an email upon completion of an aMule download
# Used in conjuction with aMule's Event feature
#
# Call like this: doneDL.sh "%NAME" "%FILE" %HASH %SIZE
#
# Enter your email address here:
eMail=
#
NameShort=$1
NameLong=$2
Hash=$3
Size=$4
{
echo aMule completed this download:
echo ------------------------------
echo
echo File: "$NameLong"
echo Hash: $Hash
echo -n "Time: "
date | awk '{print $4 " " $5}'
echo -n Size: $Size bytes
if [ $Size -gt 102400 ] ; then echo " ("$(($(($Size / 1024)) / 1024)) "Mb)" ; fi
echo
echo --------------------------------------------------------------------
cas
echo -n "Resident memory: "
echo $(ps u -C amule --no-headers | awk '{print $6}') kB
echo -n "Virtual memory: "
echo $(ps u -C amule --no-headers | awk '{print $5}') kB
echo --------------------------------------------------------------------
} | mail -s "$NameShort" $eMail

__NOTOC__

Compilation Installation

2006-04-08T01:17:21Z

Phoenix:

<center>
'''English''' | [[Compilation_Installation-fr|Français]] | [[Compilation_Installation-nl|Nederlands]] | [[Compilation_Installation-br|Português]] | [[Compilation_Installation-de|Deutsch]] | [[Compilation_Installation-ru|Russian]]
</center>

== Manual Installation ==

To install [[aMule]] you can either install it from scratch, as described in [[Compilation_Installation#Compiling From Sources|Compiling From Sources]], or use [http://www.rpm.org RPM]s, as described in the [[Compilation_Installation#Installing using RPMs|Installing using RPMs]] section. Using [http://www.rpm.org RPM]s will speed things up a lot but is not available by default with all [http://www.kernel.org linux] distributions.

== Compiling From Sources ==

'''WARNING:''' Make sure you have '''no''' copies of [[wxWidgets]] installed. If you already have [[wxWidgets]] installed, check [[How to uninstall wxWidgets]] before starting a new installation. If you continue have problems, then [[Check_if_wx_is_installed_twice|check if wx is installed twice]], since that's a common compilation and runtime problem.

'''NOTE:''' In [[wxWidgets]] >= 2.5.1, [[wxBase]] is not distributed as a separate tarball.

==== Step 1: [[wxWidgets|wxGTK]] ====

*Download [[wxWidgets|wxGTK]] ->
**[http://prdownloads.sourceforge.net/wxwindows/wxGTK-2.6.3.tar.bz2 wxGTK-2.6.3.tar.bz2]
**[ftp://biolpc22.york.ac.uk/pub/2.6.3/wxWidgets-2.6.3-Patch-2.tar.gz wxWidgets-2.6.3-Patch-2.tar.gz]

*Compile [[wxWidgets|wxGTK]]
**''tar -jxvf wxGTK-2.6.3.tar.bz2''
**''tar -zxvf wxWidgets-2.6.3-Patch-2.tar.gz''
**''mv src wxGTK-2.6.3''
**''cd wxGTK-2.6.3''
**''Linked against [http://www.gtk.org GTK]2: ./configure --prefix=/usr --with-gtk --enable-unicode --disable-compat24 --enable-optimise && make
*As '''root''':
**''make install''
**''ldconfig''

==== Step 2: [[wxBase]] ====

*Since [[wxGTK]] 2.5.x, you don't need [[wxBase]] anymore unless you want to compile [[aMuled|aMule daemon]] without X.

==== Step 3: [[aMule]] ====

*Download the latest [[aMule]] version ->
**[http://developer.berlios.de/project/showfiles.php?group_id=1296 Latest aMule]

*Compile [[aMule]] (please check the [[configure|configure article]]) ->
**''tar -zxvf aMule-X.X.X.tar.gz'' (replace X with the right version number..)
**''cd aMule-X.X.X''
**''./configure --disable-debug --enable-optimize && make''

*As '''root''':
**''make install''

*Run [[aMule]] as a regular user from console by typing -> ''amule''

== Installing using RPMs ==

==== Step 1: [[wxWidgets|wxGTK]] ====

*Download [[wxWidgets|wxGTK]] for your [http://www.kernel.org Linux] distribution ->
**[http://www.amule.org/files/files.php?cat=12 wxGTK-2.6.3]

*Install [[wxWidgets|wxGTK]] ->
**As '''root''':
***''rpm -Uvh wxGTK-2.6.3-X.rpm'' (replace X with the right name..)
***''ldconfig''

==== Step 2: [[aMule]] ====

*Download latest [[aMule]] version ->
**[http://developer.berlios.de/project/showfiles.php?group_id=1296 Latest aMule]

*Install [[aMule]] ->
**As '''root''':
***''rpm -Uvh aMule-X.rpm'' (replace X with the right name and version number..)

* Run [[aMule]] as a regular user from your console by typing -> ''amule''

Backtraces

2005-10-06T03:50:49Z

Phoenix:

== Introduction ==

Well, not hard to guess, this is about backtraces.

Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running [http://www.gnu.org/software/cvs CVS] which can also be unstable sometimes.
This is where the backtraces come in: if [[aMule]] crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace [[aMule]] provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

== The GNU Debugger ==

First of all, you need the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] installed. It's called ''gdb'' and you could check for that by typing ''which gdb'' in a console window. You should see something like this:

''<pre>
$ which gdb
/usr/bin/gdb
</pre>''

If you don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

''<pre>
$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])
</pre>''

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type this:
''<pre>
# emerge -av gdb
</pre>''

== Compiling [[aMule]] ==

Then, compile [[aMule]] with debugging information:

''<pre>
$ ./configure --enable-debug --disable-optimize --prefix=/where/to/install/aMule
$ make
$ make install
</pre>''

If you do not want to overwrite you old copy of [[aMule]], simply do this instead:

''<pre>
$ ./configure --enable-debug --disable-optimize
$ make
</pre>''

[[aMule]] can then be run by going into the dir ''src'' and typing ''./amule''

If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.

== Create a backtrace ==

Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):
''<pre>
ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
ha SIG33 nostop noprint pass
ha SIG34 nostop noprint pass
</pre>''

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

''<pre>
$ gdb /where/to/install/aMule/bin/amule
(gdb) run
</pre>''

Now use [[aMule]] normally until it crashes. If it crashes do the following:

''<pre>
(gdb) bt
(gdb) bt full
(gdb) thread apply all bt
</pre>''

Post the output of the last three commands in the [http://www.amule.org/amule/board.php?boardid=33 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The core file ==

If your [[aMule]] executable has been compiled with debug information (''--enable-debug'' configure flag), but you were not running it from within [http://www.gnu.org/software/gdb/gdb.html GDB], there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ''~/.bashrc'':

''ulimit -c unlimited''

Now, when a program crashes, suppose it generate the file ''core.1234'' (this name can be different, but usually will start with 'core') you can enter [http://www.gnu.org/software/gdb/gdb.html GDB] like that:

''$ gdb /path/to/amule /path/to/core/file/core.1234''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

(Most of the above shamelessly stolen from pure_ascii's post in backtraces forum, thanks, pure!)

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

FAQ network

2005-02-27T21:06:59Z

Phoenix: =Prefixes=

=Network speed: what you should know before asking questions=
by Froenchenko Leonid, lfroen@gmail.com

==Preface==
The purpose of this document is to clarify different issues regarding network
speed that pops up from time to time in amule forum. Generally speaking, there're several reasons for questions about "amule & network":
<ul>
<li>Speed reported by amule doesn't match provider given rate</li>
<li>Poor performance of amule itself or another network application on the same computer</li>
<li>What are key factors influencing network performance while amule is running
</li>
</ul>
Intended audience for this document are users who want to get better understanding of network functionality in general and in practical implication to amule functionality. 
This page, however, is not to be seen as comprehensive general purpose "Network
FAQ". 

==Network speed - how much is it ?==
While talking about network speed, people are using "bps" units, which mean
"bit per second". The reason for bit rather that byte is pretty
match historical, but also have engineering motivation behind. This motivation
comes from the fact, that not all networks in the world are transferring bytes. 
There's also convention to use capital "B" in "Bps" when speed is marked
in "bytes per second". However, this convention is not widely accepted. Particularly, organizations like IETF and IEEE are stick to original "bps". 

==Prefixes==
Since their invention, networks made quite a progress, and now we have networks
that transfers thousands and millions bits and more bits per second. For marking
those speeds, prefixes "kilo", "mega", "giga", "tera"
etc. are used. It is a common mistake to think that values with those prefixes are the same as in computer science, i.e. powers of 2. The truth is that, for historical reasons, prefixes in networking have a decimal base, and not a binary one.

<table cellpadding="2" cellspacing="2" border="1" width="100%"
title="Table 1">
<tr>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">Prefix 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">meaning in computers 
</th>
<th valign="middle" title="Table 1" align="center"
bgcolor="#33ff33">meaning in networks 
</th>
<th valign="middle" align="center" bgcolor="#33ff33">difference, %% 
</th>
</tr>
<tr>
<td valign="top">K (kilo) 
</td>
<td valign="top">2^10 = 1024 
</td>
<td valign="top">10^3 = 1000 
</td>
<td valign="top">2% 
</td>
</tr>
<tr>
<td valign="top">M (mega) 
</td>
<td valign="top">2^20 = 1,048,576 
</td>
<td valign="top">10^6 = 1,000,000 
</td>
<td valign="top">5% 
</td>
</tr>
<tr>
<td valign="top">G (giga) 
</td>
<td valign="top">2^30 = 1,073,741,624 
</td>
<td valign="top">10^9 = 1,000,000,000 
</td>
<td valign="top">7% 
</td>
</tr>
<tr>
<td valign="top">T (tera) 
</td>
<td valign="top">2^40 = 1,099,511,627,776 
</td>
<td valign="top">10^12 = 1,000,000,000,000 
</td>
<td valign="top">9% 
</td>
</tr>
<tr>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
<td valign="top"> 
</td>
</tr>

</table>
 
As you can see from the table above the error in calculation is about 5% when the prefix
is incorrectly interpreted. Please note that the speed your provider tells
you is "speed in network", i.e. calculated on decimal base. 
For example when your provider tells you that your link is "ADSL 256/128" you
should understand that he means 256000/128000 bps. Which means, that you have
32000/16000 bytes per second speed in your link. 

==Protocol overhead - what is it about==
When amule is running, it constantly "talks" with other "mules" and servers.
This data exchange is needed to identify itself, request information about
available sources and files, perform searches and so on. Since this information
has no use for the user itself, it's called "overhead" i.e. inevitable addition
to the data you actually want to upload or download. Amule calls this "connection
overhead". However, the number amule presents, includes only the size of the actual
data that amule itself is sending to the network stack. Later, this data is
sent down to the net with more overhead - now of network protocols. How much
is it - lets see that in the next section. 

==Network overhead==
First of all - we're talking about IPv4 network. Once upon a time, there
was only one type of IP network. Now there's 2 - IP version  4, the old
we all know; and IP version 6 - the new one. ED2K protocol by design, is
unable to talk over IPv6 network, so users who have it (in Japan and China
for example) will not be able to connect "as is". Using IPv4 means, that each
packet (TCP, UDP, ICMP) will have IPv4 header. The minimum size of this header
is 20 bytes. Header can have optional parts (each 4 bytes) and it's up to
your provider  - for example my add 1 option dword. 
When talking to other thing on ed2k network, amule uses the widely known TCP protocol.
UDP is also used, but in much smaller scale. As the reader might know, TCP is a reliable protocol, i.e. it's guaranteed that data which sent from one side will arrive on the other or an error will be reported. In order to achieve this, TCP send its own data in addition to the actual transfer. This data includes TCP client initial negotiation, checksums, sequence numbers and acknowledgments. All this is in the TCP header which is added to each packet sent. The size of this header
is 20 bytes minimum. While being small overhead for large bulk transfer, it
can take significant part of bandwidth when small amounts of data are being
exchanged. This is exactly what happens on source discovery part of amule.
Our client is trying to establish a connection and negotiate with a large number
of other clients. Doing this, amule opens new TCP connections all the
time. The amount of those connections is controlled by the "Maximum
number of connections in 5 seconds" setting in the preferences. A typical number
is about 100. Each TCP connection results in at least 3 packets traveling
the net - one is a SYN packet, i.e. connection request, and one an ACK or a RST
when the connection is accepted or refused, and SYN+ACK to establish the session.
There's more overhead of DNS queries when an address is resolved, retries when a
host doesn't reply and so on. 

===On low level:===
After passing TCP and IP layers packets go down to the network interface
driver. The kind of this driver depends on the way your computer is connected to the internet. For simplicity sake we will assume that this computer is connected to the ISP directly, i.e. you have no LAN (or switch or router) between.
Common setups that I'm aware of: 

<ol>
<li>Analog modem, connected to telephone line (ISDN modem falls in this category too)</li>
<li>Cable modem, connected through ethernet, ISP gives you an IP address through DHCP</li>
<li>Cable modem, connected through ethernet, ISP requires you to configure PPPoE or PPTP tunnel</li>
<li>ADSL modem, connected through ethernet. You must have a PPPoE or PPTP tunnel</li>
<li>Variation of above - modem connected to PC by USB. </li>

</ol>
In each of above setups there are different protocols in use, and different headers added to transmitted packets. But there's one important thing to note: ethernet frames traveling between cable/ADSL modem and PC don't reach the ISP. And consequently they are not counted in rate calculations. PPPoE and
PPTP headers, on the contrary do reach the ISP. Whether or not
your particular provider includes them in rate calculations I obviously have
no idea about. For this reason I will exclude those headers from my calculations.
If you think that your ISP includes it, add 4 bytes to the size of each packet. 

===Example:===
Let's see how much network overhead we have on a typical network. Our connection
is a cable modem connected via an ethernet link to a PC directly (no router between them).
In this setup we have IPv4 packets sent over ethernet. 
Lets say we have 10 new connections opened each second, and all are being accepted
(successfully established TCP session). This alone sums up to (I'm counting data
going up - from my computer to the net): 
 
10 connection * 2 packets * (20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
This means that we are starting with  1.16*8 Kbps of "invisible"
overhead caused by the very way the network works. Now, let's assume that
after each connection is established our amule sends something to the other side
and waits to receive an answer. 
 
10 connections * (1 packet of data + 1 ACK)*(20 bytes of TCP + 20 bytes of IPv4) = 800 bytes of overhead. 
 
Total of 800 bytes + 800 bytes = 1600 bytes per second = 6400 bps = 6.4 Kbps 
 
What we have here is 6.4 Kbps of network overhead alone. Taking into account
that amule has other data to send (uploads) and it is not the only network
application running we will have the following picture: Most chances that your
link to provider is not that fast.  Amule will try to open
10 connections per second and will try to upload on the specified
speed. Your operating system will share all available bandwidth between those and between amule and other network applications (browser for example). Actual results will vary depending on specific OS settings. 

==ACK bottleneck==
In all calculations above there was one assumption - zero download. But downloading is what amule was built for. So let's examine how the overhead
above affects your downloading speed. The answer is in TCP protocol. When TCP is sending
data, it requires from the other side to acknowledge the reception. So if client
A is sending data to client B by TCP, B has to send a special ACK packets to A which tells B "ok, I got it". If, however, A doesn't receive the ACK packets
in time, he will assume that either packet is lost. So, without going deeply
into TCP specification: if B fails to send ACK to A, as a result A will
transmit slower. 
Now let's see the situation in amule. We saw in the previous chapter, that the uplink
stream is congested by connection requests and uploads. As a result, there's a
good chance that ACK packets for a file we are downloading will not be sent
on time. The remote party will notice this and slow down. This is one
more reason why the upstream should better not be too congested. 

==Is there something I can do ?==
OK, now that you understood why your network is so slow while amule is
running you will maybe look for a way to fix this. The answer in 2 words: "rate limit".
The first thing you should do is to assign realistic rate limits in amule
itself. If you have a uplink rate of 128 Kbps don't set amules upload limit to
16 (kilobytes per second) just because 128/8=16. 
A better, but far more complicated solution is to use the QoS and packet scheduling
services of your OS. For example, you can give a higher priority to ACK packets
to solve the above mentioned "ACK bottleneck" problem. The QoS topic, however, is beyond
scope of this article. 
 

==Router (switch, home network):  is there any difference ?==
When the cable coming from your ISP is connected to some switching or routing
device, which in turn is connected to several PC's, bandwidth is shared between
them. So, having N computers connected, an ideal device would simply provide
each one of them with 1/N of the total bandwidth. The situation may vary in real
life, and your particular device may have different idea about fairness. Since
you're not going to have the hardware specs of your router chipset the only
advice here is "try and see yourself".

Webserver

2005-01-27T16:36:44Z

Phoenix: how to calculate md5 password

== Setting up [[aMuleWeb|Webserver]] with [[aMule]] ==

=== [[Webserver-1.2.x|Webserver with aMule 1.2.8 or earlier]] ===

=== Webserver with [[aMule]] 2.0.0-rc1 or later ===

*[http://www.gnu.org/software/tar/tar.html Untar] the sources and copy '''''src/aMule.tmpl''''' and '''''src/webserver/''''' into your '''''~/.aMule/''''' directory. The following (run from the sources directory), should do so:
:''$ cp -r src/aMule.tmpl src/webserver/ ~/.aMule/''

* If you installed [[aMule]] from rpm, then you can do:
:''$ cp /usr/share/amuleweb/aMule.tmpl ~/.aMule/''
:''$ cp /usr/share/amuleweb/webserver/ ~/.aMule/''

*Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
**Enable "Accept External Connections".
**Enable "Use TCP ports instead of unix local sockets".
**Enter a password for external connections. If you don't do this, amuleweb will not communicate with amule.

:'''NOTE:''' On some early [[aMule]] 2.0.0-rcX versions the above options weren't available (or didn't work). If you are using such [[aMule]] version and you don't wish to upgrade, then do the following:

:Shutdown [[aMule]] if it is still running.
:Edit your ''~/.eMule'' file, locate the ''[ExternalConnect]'' section and change:
::''AcceptExternalConnections=1'' <-- To enable [[aMule]] listening for [[External Connections]].
::''ECUseTCPPort=1'' <-- To use the [http://www.faqs.org/faqs/internet/tcp-ip/resource-list TCP] port. Very important since [http://www.unix.org Unix] sockets are disabled.
::''ECPassword=0a98sd7f0a9s8d7f0a98sd7f'' <-- To find the MD5 string for your password, do:
:::''$ echo -n yourpasswordhere | md5sum | cut -d ' ' -f 1''
:::''ca3c365274907c6fd527068788e14639''

*Restart [[aMule]]

*Go to your "Preferences"->"Remote Controls" (in [[aMule]]) and setup your passwords here for [[External Connections]] and [[aMuleWeb|webserver]] login.
::'''NOTE:''' When you change your [[aMuleWeb|webserver]] and [[External Connections]] ports here, make sure to restart [[aMule]].
::'''NOTE:''' that ''"Enable [[aMuleWeb|Webserver]]"'' has no effect and will be renamed in 2.0.0rc8. [[aMuleWeb|Webserver]] is always enabled as long as you have [[External Connections]] enabled.
::'''NOTE:''' For users running [[aMuled|aMule Daemon]] you have to edit the ''.eMule'' file like shown above. For a way to setup a password check the [[Webserver-1.2.x|1.2.8 aMule HowTo]]. You can still do it in the same way.

*Now you're done! You are ready to run [[aMuleWeb|amuleweb]] and connect to it.

'''[[User:Stefanero|Stefanero]]'''

== Connecting to [[aMuleWeb|amuleweb]] ==

To run [[aMuleWeb]] run '''''amuleweb''''' on a terminal. For more information about running [[aMuleWeb]] check the [[aMuleWeb|aMuleWeb document]].

Once [[aMuleWeb]] is running, open a web browser and connect to:

''http://host:port''

where ''host'' stands for your host's name (try with ''localhost'') and port stands for the [[aMuleWeb]] port ('''NOT''' the [[External Connections]] port).

For example: ''http://localhost:4711''

== Standard ports ==

The ports can be set to anything, but this are the most used (the standard ones):

*[[External Connections]]: 4712
*[[aMuleWeb|amuleweb]]: 4711

Make sure you do not confuse with what each of them is.

== Where to report problems and questions? ==

For Problems or Questions just report on http://forum.amule.org forum or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

AMule is slow

2005-01-09T14:50:05Z

Phoenix:

<center>'''English''' | [[AMule_is_slow-it|Italiano]]</center>

== [[aMule]] is slow ==

So [[aMule]] is slow? This can be due to:

*[[#Your fault|Your fault]]
*[[#The network's fault|The network's fault]]

== Your fault ==

This is a list of issues which can be the reason for slow download speeds:

*A low value in "Preferences"->"Download limit".
*A low value in "Preferences"->"Upload limit". Upload limits under 4 kbps limit your download speed to 3 times your upload speed. Upload limits under 10 kbps limit your download speed to 4 times your upload speed. Upload limits above or equal to 10 kbps give you unlimited download speed, limited only by the "Download limit" preference value (read [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|this link]] to know more about it).
*Having [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]].
*Some [http://en.wikipedia.org/wiki/ISP ISP]s block or limit connections to the standard [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[FAQ_eD2k-Kademlia#Which_ports_do_I_have_to_configure_in_a_firewall_or_router_to_run_aMule?|ports]]. Try changing the port in "Preferences"->"Connections" to some other values.

== The network's fault ==

We're sorry to tell you that sometimes, the low speeds aren't due to a bad [[aMule]] code or a bad configuration, but due to other facts. This is a list:

*The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] is a slow network. In some other [[P2P]] networks you can easily download faster. The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network is one of the fastest [[P2P]] networks existing, but its main goal is availability. While on other popular networks you'll be able to download very fast, you'll quickly find out that in the [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network there are millions of files you'll be unable to find in any other network.
*[[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]]. If you are running [[aMule]] for the first time or if you deleted some files in the ''~/.aMule'' directory, you'll have no [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]]. [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]] grant fast downloads. If you don't know what they are, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|this]].
*The file's availability. Rare files, old files, extremly new files... this kind of files have very few [[FAQ_eD2k-Kademlia#What_is_a_source?|source]]s, so it takes quite some time for [[aMule]] to connect to some other [[client]] sharing it.

AMule is slow

2005-01-09T14:48:43Z

Phoenix: =Your fault=

<center>'''English''' | [[AMule_is_slow-it|Italiano]]</center>

== [[aMule]] is slow ==

So [[aMule]] is slow? This can be due to:

*[[#Your fault|Your fault]]
*[[#The network's fault|The network's fault]]

== Your fault ==

This is a list of issues which can be the reason for slow download speeds:

*A low value in "Preferences"->"Download limit".
*A low value in "Preferences"->"Upload limit". Upload limits under 4 kbps limit your download speed to 3 times your upload speed. Upload limits under 10 kbps limit your download speed to 4 times your upload speed. Upload limits above or equal to 10 kbps give you unlimited download speed, limited only by the "Download limit" preference value. (read [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|this link]] to know more about it)
*Having [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]].
*Some [http://en.wikipedia.org/wiki/ISP ISP]s block or limit connections to the standard [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[FAQ_eD2k-Kademlia#Which_ports_do_I_have_to_configure_in_a_firewall_or_router_to_run_aMule?|ports]]. Try changing the port in "Preferences"->"Connections" to some other values.

== The network's fault ==

We're sorry to tell you that sometimes, the low speeds aren't due to a bad [[aMule]] code or a bad configuration, but due to other facts. This is a list:

*The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] is a slow network. In some other [[P2P]] networks you can easily download faster. The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network is one of the fastest [[P2P]] networks existing, but its main goal is availability. While on other popular networks you'll be able to download very fast, you'll quickly find out that in the [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network there are millions of files you'll be unable to find in any other network.
*[[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]]. If you are running [[aMule]] for the first time or if you deleted some files in the ''~/.aMule'' directory, you'll have no [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]]. [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]] grant fast downloads. If you don't know what they are, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|this]].
*The file's availability. Rare files, old files, extremly new files... this kind of files have very few [[FAQ_eD2k-Kademlia#What_is_a_source?|source]]s, so it takes quite some time for [[aMule]] to connect to some other [[client]] sharing it.

AMule is slow

2005-01-09T14:42:42Z

Phoenix: =Your fault=

<center>'''English''' | [[AMule_is_slow-it|Italiano]]</center>

== [[aMule]] is slow ==

So [[aMule]] is slow? This can be due to:

*[[#Your fault|Your fault]]
*[[#The network's fault|The network's fault]]

== Your fault ==

This is a list of issues which can be the reason for slow download speeds:

*A low value in "Preferences"->"Download limit".
*A low value in "Preferences"->"Upload limit". Upload limits under 4 kbps limit your download speed to 3 times your upload speed. Upload limits under 10 kbps limit your download speed to 4 times your upload speed. Upload limits above or equal to 10 kbps give you unlimited download speed, limited only by the "Download limit" preference value.
*Having [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|Low ID]].
*Some [http://en.wikipedia.org/wiki/ISP ISP]s block or limit connections to the standard [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[FAQ_eD2k-Kademlia#Which_ports_do_I_have_to_configure_in_a_firewall_or_router_to_run_aMule?|ports]]. Try changing the port in "Preferences"->"Connections" to some other values.

== The network's fault ==

We're sorry to tell you that sometimes, the low speeds aren't due to a bad [[aMule]] code or a bad configuration, but due to other facts. This is a list:

*The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] is a slow network. In some other [[P2P]] networks you can easily download faster. The [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network is one of the fastest [[P2P]] networks existing, but its main goal is availability. While on other popular networks you'll be able to download very fast, you'll quickly find out that in the [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] network there are millions of files you'll be unable to find in any other network.
*[[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]]. If you are running [[aMule]] for the first time or if you deleted some files in the ''~/.aMule'' directory, you'll have no [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|credits]]. [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|Credits]] grant fast downloads. If you don't know what they are, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|this]].
*The file's availability. Rare files, old files, extremly new files... this kind of files have very few [[FAQ_eD2k-Kademlia#What_is_a_source?|source]]s, so it takes quite some time for [[aMule]] to connect to some other [[client]] sharing it.

Backtraces

2004-12-28T10:56:54Z

Phoenix:

== Introduction ==

Well, not hard to guess, this is about backtraces.

Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running [http://www.gnu.org/software/cvs CVS] which can also be unstable sometimes.
This is where the backtraces come in: if [[aMule]] crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace [[aMule]] provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

== The GNU Debugger ==

First of all, you need the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] installed. It's called ''gdb'' and you could check for that by typing ''which gdb'' in a console window. You should see something like this:

''<pre>
$ which gdb
/usr/bin/gdb
</pre>''

If you don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

''<pre>
$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])
</pre>''

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type that:
''<pre>
# emerge -av gdb
</pre>''

== Compiling [[aMule]] ==

Then, compile [[aMule]] with debugging information:

''<pre>
$ ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule
$ make
$ make install
</pre>''

If you do not want to overwrite you old copy of [[aMule]], simply do this instead:

''<pre>
$ ./configure --enable-debug --disable-optimise
$ make
</pre>''

[[aMule]] can then be run by going into the dir ''src'' and typing ''./amule''

If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.

== Create a backtrace ==

Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):
''<pre>
ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
</pre>''

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

''<pre>
$ gdb /where/to/install/aMule/bin/amule
(gdb) run
</pre>''

Now use [[aMule]] normally until it crashes. If it crashes do the following:

''<pre>
(gdb) bt
(gdb) bt full
</pre>''

Post the output of the last two commands in the [http://www.amule.org/amule/board.php?boardid=33 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The Core File ==

If your [[aMule]] executable has been compiled with debug information (--enable-debug configure flag), but you were not running it from within gdb, there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ~/.bashrc:

''<pre>
ulimit -c unlimited
</pre>''

Now, when a program crashes, suppose it generate the file core.1234 (this name can be different, but usually will start with 'core') you can enter gdb like that:

''<pre>
$ gdb /path/to/amule /path/to/core/file/core.1234
</pre>''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

(Most of the above shamelessly stolen from pure_ascii's post in backtraces forum, thanks, pure!)

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

Backtraces

2004-12-28T10:55:45Z

Phoenix:

== Introduction ==

Well, not hard to guess, this is about backtraces.

Usually, it should not be necessary for the normal user to do this. However, we might have a bad day and release a somewhat buggy version or you are running [http://www.gnu.org/software/cvs CVS] which can also be unstable sometimes.
This is where the backtraces come in: if [[aMule]] crashes, and you get an "OOPS - aMule crashed" and so on, we'd like to know. The backtrace [[aMule]] provides is not always very usefull as it contains little information, but, as usual, there's a better way: A *real* backtrace.

== The GNU Debugger ==

First of all, you need the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] installed. It's called ''gdb'' and you could check for that by typing ''which gdb'' in a console window. You should see something like this:

''<pre>
$ which gdb
/usr/bin/gdb
</pre>''

If you don't have [http://www.gnu.org/software/gdb/gdb.html GDB] installed, you will get a message like this: 

''<pre>
$ which gdb
which: no gdb in (/bin:/usr/bin:[etc])
</pre>''

If that is the case, the [http://www.gnu.org/software/gdb/gdb.html GNU Debugger] is most likely not installed on your system and you should install it before you proceed.

If your OS is [http://www.gentoo.org Gentoo Linux] you have just to type that:
''<pre>
# emerge -av gdb
</pre>''

== Compiling [[aMule]] ==

Then, compile [[aMule]] with debugging information:

''<pre>
$ ./configure --enable-debug --disable-optimise --prefix=/where/to/install/aMule
$ make
$ make install
</pre>''

If you do not want to overwrite you old copy of [[aMule]], simply do this instead:

''<pre>
$ ./configure --enable-debug --disable-optimise
$ make
</pre>''

[[aMule]] can then be run by going into the dir ''src'' and typing ''./amule''

If you are unable or unwilling to recompile, or are running a RPM version, proceed anyway, but be aware that backtraces from debugging enabled builds are much more useful to us.

== Create a backtrace ==

Now create in your home directory the file ''.gdbinit'' and put these lines into it (or you can type them in at the ''(gdb)'' prompt later):
''<pre>
ha SIGPIPE nostop noprint pass
ha SIG32 nostop noprint pass
</pre>''

For those who want to know the meaning of the previous lines:
the first one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at broken pipes;
the second one avoid [http://www.gnu.org/software/gdb/gdb.html GDB] stopping at new thread.

To create a backtrace, open a console and do the following:

''<pre>
$ gdb /where/to/install/aMule/bin/amule
(gdb) run
</pre>''

Now use [[aMule]] normally until it crashes. If it crashes do the following:

''<pre>
(gdb) bt
(gdb) bt full
</pre>''

Post the output of the last two commands in the [http://www.amule.org/amule/board.php?boardid=33 backtraces forum] with some additional comment about the circumstances the segfault happened and what [[aMule]] version you used (or checkout time for [http://www.gnu.org/software/cvs CVS]).

== The Core File ==

If your [[aMule]] executable has been compiled with debug information (--enable-debug configure flag), but you were not running it from within gdb, there is still a way to generate a backtrace, if your system was configured to generate '''core files'''.

Core files are the full memory image of a process that crashed. Your session must be properly configured, so that the system generates core files. Add the following command to ~/.bashrc:

''<pre>
ulimit -c unlimited
</pre>''

Now, when a program crashes, suppose it generate the file core.1234 (this name can be different, but usually will start with 'core') you can enter gdb like that:

''<pre>
gdb /path/to/amule /path/to/core/file/core.1234
</pre>''

and then proceed as in the last session and issue 'bt' and 'bt full'.

So, that's it, have fun with [[aMule]]

Greetings, [[User:Citroklar|Citroklar]] & [[User:Phoenix|Phoenix]]

(Most of the above shamelessly stolen from pure_ascii's post in backtraces forum, thanks, pure!)

Please read [[Using_gdb_and_valgrind|this]] to learn more about [http://www.gnu.org/software/gdb/gdb.html GDB] and [http://valgrind.kde.org Valgrind].

Using gdb and valgrind

2004-10-22T19:00:47Z

Phoenix: Updated to valgrind 2.2.0

<center><h2>by ''[[User:Phoenix|Phoenix]]''</h2></center>

The two programs, [http://www.gnu.org/software/gdb/gdb.html gdb] and [http://valgrind.kde.org valgrind], are fabulous tools to find errors in your code. The standard gnu debugger is [http://www.gnu.org/software/gdb/gdb.html gdb], very powerfull, virtually every debugger in [http://www.gnu.org GNU] is [http://www.gnu.org/software/gdb/gdb.html gdb]-based. So, you need to learn some [http://www.gnu.org/software/gdb/gdb.html gdb]. Another invaluable tool is [http://valgrind.kde.org valgrind]. It allows you to track memory usage, stopping the program whenever an invalid operation has been made.

Both [http://valgrind.kde.org valgrind] and [http://www.gnu.org/software/gdb/gdb.html gdb] can be used together, so that you can actually debug the program that is beeing analysed. This is possible due to a [http://www.gnu.org/software/gdb/gdb.html gdb] feature that makes it possible to attach any running process to a [http://www.gnu.org/software/gdb/gdb.html gdb] session.

The first step is to setup '''valgrind''', but first, some interesting links about [http://valgrind.kde.org valgrind]:

* Home page: http://valgrind.kde.org/
* Documentation: http://developer.kde.org/~sewardj/docs-2.0.0/manual.html
* How To: http://www.tldp.org/HOWTO/Valgrind-HOWTO/
* FAQ: http://valgrind.kde.org/faq.html
* Nice article explaining how to use: http://www.linux-mag.com/2003-05/compile_03.html

== Running [http://valgrind.kde.org valgrind] ==
----

I personaly use the following call:

<code>valgrind -v --tool=memcheck --leak-check=yes --db-attach=yes --num-callers=10 --suppressions=amule.sup --gen-suppressions=yes ~/programs/amule/amule-dev-cvs/src/amule --enable-stdin</code>

This way, leak-check is enabled, and whenever a problem is detected, the user will be prompted for whether he wants to start [http://www.gnu.org/software/gdb/gdb.html gdb] at the current position. This is a great moment to see the beast exactly at the moment of falilure. The parameter ''--num-callers'', which defaults to 4, is the number of backtrace lines that [http://valgrind.kde.org valgrind] shows you, 4 is too little.

Finally, there is ''--gen-suppressions'' and ''--suppressions''. Suppressions are a way that [http://valgrind.kde.org valgrind] provides us so that we don't have to see '''every''' single problem that the program has. Eventually, other libraries your program is using, like X itself, will show memory usage problems, and [http://valgrind.kde.org valgrind] will show them. So, on the first few runs of [http://valgrind.kde.org valgrind], we will have to build a suppression file, which is specified by ''--suppressions='' and we tell [http://valgrind.kde.org valgrind] to generate suppressions on screen. ''--gen-suppressions=yes'' will do this. Suppressions are a few lines that you may copy/paste in the suppressions file, all you have to do is give each suppression a name and that's it.

When set up that way, each time [http://valgrind.kde.org valgrind] finds something wrong, he will show you a few lines describing the problem and them he will ask you if you want him to generate the suppressions. If you say yes, the suppression appears on the screen, and you can copy/paste it in the suppressions file, so that next time you run valgring this error is not reported.

Now, after prompting the user for printing the suppression, [http://valgrind.kde.org valgrind] will prompt the user again whether or not he should start [http://www.gnu.org/software/gdb/gdb.html gdb]. If you say accept, [http://www.gnu.org/software/gdb/gdb.html gdb] will attach the running process and you will be debugging the program exactly at the point of the invalid operation.

== A few [http://www.gnu.org/software/gdb/gdb.html gdb] usefull commands ==
----
;'''''bt''''': backtrace, shows the stack frames (subroutine calls) that lead to the position you are now in code.
;'''''bt full''''': shows every frame with the values of the local variables, usually too much verbose, only do this if you want to send the output to another person to analyse.
;'''''up/down number''''': e.g.: ''up 5'': goes up 5 stack frames. By default, whenever you enter [http://www.gnu.org/software/gdb/gdb.html gdb], you will be placed in frame number 0. '''With the aid of the source code of the program''' you should be able to select the subroutine where you want to inspect the variables.
;'''''frame number''''': goes straight to the selected frame.
;'''''info locals''''': prints the value of all local variables belonging to the current frame.
;'''''p variable''''': e.g.: ''p *cur_src''. Prints the named variable. Usually C like syntax will be allowed here.
;'''''l''''': prints 10 lines of source code around the current line. A separate editor for source browsing is usualy better, but this can be a quick way to see the code.
;'''''help/help command''''': Do I need to explain that? :)

There are other commands, but usualy these described will suffice. It's worth mentioning that [http://www.gnu.org/software/gdb/gdb.html gdb] can be run with the core file, i.e., that big file that is produced after a crash. To do that, type

''gdb '''program_path''' '''core_file_path'''''

Also there are GUI front ends to [http://www.gnu.org/software/gdb/gdb.html gdb] that make it a little bit more friendly (like [http://kgdb.sourceforge.net kdbg]). GUI front ends are great to inspect several different variables by clicking with the mouse. But learning to use [http://www.gnu.org/software/gdb/gdb.html gdb] from the console is by far the fastest way to do the job, not to mention that you can do it '''quickly''' in a remote terminal session.

Also note that practice makes it perfect, so the only way to realy learn how to do this is by doing it. You will see that you will quickly learn how to move around [http://www.gnu.org/software/gdb/gdb.html gdb], in spite of his daunting console interface. Soon he will become your friend. :)

'''NOTE:''' [[aMule]] is a '''separate''' project from [http://www.gnu.org/software/gdb/gdb.html gdb], [http://valgrind.kde.org valgrind] or any other project refered in this text, and is '''not''' related to any of them.

Using gdb and valgrind

2004-08-13T23:28:21Z

Phoenix:

<center><h2>by ''phoenix''</h2></center>

The two programs, [http://www.gnu.org/software/gdb/gdb.html gdb] and [http://valgrind.kde.org valgrind], are fabulous tools to find errors in your code. The standard gnu debugger is [http://www.gnu.org/software/gdb/gdb.html gdb], very powerfull, virtually every debugger in [http://www.gnu.org GNU] is [http://www.gnu.org/software/gdb/gdb.html gdb]-based. So, you need to learn some [http://www.gnu.org/software/gdb/gdb.html gdb]. Another invaluable tool is [http://valgrind.kde.org valgrind]. It allows you to track memory usage, stopping the program whenever an invalid operation has been made.

Both [http://valgrind.kde.org valgrind] and [http://www.gnu.org/software/gdb/gdb.html gdb] can be used together, so that you can actually debug the program that is beeing analysed. This is possible due to a [http://www.gnu.org/software/gdb/gdb.html gdb] feature that makes it possible to attach any running process to a [http://www.gnu.org/software/gdb/gdb.html gdb] session.

The first step is to setup '''valgrind''', but first, some interesting links about [http://valgrind.kde.org valgrind]:

* Home page: http://valgrind.kde.org/
* Documentation: http://developer.kde.org/~sewardj/docs-2.0.0/manual.html
* How To: http://www.tldp.org/HOWTO/Valgrind-HOWTO/
* FAQ: http://valgrind.kde.org/faq.html
* Nice article explaining how to use: http://www.linux-mag.com/2003-05/compile_03.html

== Running [http://valgrind.kde.org valgrind] ==
----

I personaly use the following call:

<code>valgrind -v --leak-check=yes --gdb-attach=yes --num-callers=10 --suppressions=amule.sup --gen-suppressions=yes ~/programs/amule/amule-dev-cvs/src/amule --enable-stdin</code>

This way, leak-check is enabled, and whenever a problem is detected, the user will be prompted for whether he wants to start [http://www.gnu.org/software/gdb/gdb.html gdb] at the current position. This is a great moment to see the beast exactly at the moment of falilure. The parameter ''--num-callers'', which defaults to 4, is the number of backtrace lines that [http://valgrind.kde.org valgrind] shows you, 4 is too little.

Finally, there is ''--gen-suppressions'' and ''--suppressions''. Suppressions are a way that [http://valgrind.kde.org valgrind] provides us so that we don't have to see '''every''' single problem that the program has. Eventually, other libraries your program is using, like X itself, will show memory usage problems, and [http://valgrind.kde.org valgrind] will show them. So, on the first few runs of [http://valgrind.kde.org valgrind], we will have to build a suppression file, which is specified by ''--suppressions='' and we tell [http://valgrind.kde.org valgrind] to generate suppressions on screen. ''--gen-suppressions=yes'' will do this. Suppressions are a few lines that you may copy/paste in the suppressions file, all you have to do is give each suppression a name and that's it.

When set up that way, each time [http://valgrind.kde.org valgrind] finds something wrong, he will show you a few lines describing the problem and them he will ask you if you want him to generate the suppressions. If you say yes, the suppression appears on the screen, and you can copy/paste it in the suppressions file, so that next time you run valgring this error is not reported.

Now, after prompting the user for printing the suppression, [http://valgrind.kde.org valgrind] will prompt the user again whether or not he should start [http://www.gnu.org/software/gdb/gdb.html gdb]. If you say accept, [http://www.gnu.org/software/gdb/gdb.html gdb] will attach the running process and you will be debugging the program exactly at the point of the invalid operation.

== A few [http://www.gnu.org/software/gdb/gdb.html gdb] usefull commands ==
----
;'''''bt''''': backtrace, shows the stack frames (subroutine calls) that lead to the position you are now in code.
;'''''bt full''''': shows every frame with the values of the local variables, usually too much verbose, only do this if you want to send the output to another person to analyse.
;'''''up/down number''''': e.g.: ''up 5'': goes up 5 stack frames. By default, whenever you enter [http://www.gnu.org/software/gdb/gdb.html gdb], you will be placed in frame number 0. '''With the aid of the source code of the program''' you should be able to select the subroutine where you want to inspect the variables.
;'''''frame number''''': goes straight to the selected frame.
;'''''info locals''''': prints the value of all local variables belonging to the current frame.
;'''''p variable''''': e.g.: ''p *cur_src''. Prints the named variable. Usually C like syntax will be allowed here.
;'''''l''''': prints 10 lines of source code around the current line. A separate editor for source browsing is usualy better, but this can be a quick way to see the code.
;'''''help/help command''''': Do I need to explain that? :)

There are other commands, but usualy these described will suffice. It's worth mentioning that [http://www.gnu.org/software/gdb/gdb.html gdb] can be run with the core file, i.e., that big file that is produced after a crash. To do that, type

''gdb '''program_path''' '''core_file_path'''''

Also there are GUI front ends to [http://www.gnu.org/software/gdb/gdb.html gdb] that make it a little bit more friendly (like [http://kgdb.sourceforge.net kdbg]). GUI front ends are great to inspect several different variables by clicking with the mouse. But learning to use [http://www.gnu.org/software/gdb/gdb.html gdb] from the console is by far the fastest way to do the job, not to mention that you can do it '''quickly''' in a remote terminal session.

Also note that practice makes it perfect, so the only way to realy learn how to do this is by doing it. You will see that you will quickly learn how to move around [http://www.gnu.org/software/gdb/gdb.html gdb], in spite of his daunting console interface. Soon he will become your friend. :)

'''NOTE:''' [[aMule]] is a '''separate''' project from [http://www.gnu.org/software/gdb/gdb.html gdb], [http://valgrind.kde.org valgrind] or any other project refered in this text, and is '''not''' related to any of them.

Using gdb and valgrind

2004-08-13T23:27:32Z

Phoenix:

<center><h2>by ''Phoenix''</h2></center>

The two programs, [http://www.gnu.org/software/gdb/gdb.html gdb] and [http://valgrind.kde.org valgrind], are fabulous tools to find errors in your code. The standard gnu debugger is [http://www.gnu.org/software/gdb/gdb.html gdb], very powerfull, virtually every debugger in [http://www.gnu.org GNU] is [http://www.gnu.org/software/gdb/gdb.html gdb]-based. So, you need to learn some [http://www.gnu.org/software/gdb/gdb.html gdb]. Another invaluable tool is [http://valgrind.kde.org valgrind]. It allows you to track memory usage, stopping the program whenever an invalid operation has been made.

Both [http://valgrind.kde.org valgrind] and [http://www.gnu.org/software/gdb/gdb.html gdb] can be used together, so that you can actually debug the program that is beeing analysed. This is possible due to a [http://www.gnu.org/software/gdb/gdb.html gdb] feature that makes it possible to attach any running process to a [http://www.gnu.org/software/gdb/gdb.html gdb] session.

The first step is to setup '''valgrind''', but first, some interesting links about [http://valgrind.kde.org valgrind]:

* Home page: http://valgrind.kde.org/
* Documentation: http://developer.kde.org/~sewardj/docs-2.0.0/manual.html
* How To: http://www.tldp.org/HOWTO/Valgrind-HOWTO/
* FAQ: http://valgrind.kde.org/faq.html
* Nice article explaining how to use: http://www.linux-mag.com/2003-05/compile_03.html

== Running [http://valgrind.kde.org valgrind] ==
----

I personaly use the following call:

<code>valgrind -v --leak-check=yes --gdb-attach=yes --num-callers=10 --suppressions=amule.sup --gen-suppressions=yes ~/programs/amule/amule-dev-cvs/src/amule --enable-stdin</code>

This way, leak-check is enabled, and whenever a problem is detected, the user will be prompted for whether he wants to start [http://www.gnu.org/software/gdb/gdb.html gdb] at the current position. This is a great moment to see the beast exactly at the moment of falilure. The parameter ''--num-callers'', which defaults to 4, is the number of backtrace lines that [http://valgrind.kde.org valgrind] shows you, 4 is too little.

Finally, there is ''--gen-suppressions'' and ''--suppressions''. Suppressions are a way that [http://valgrind.kde.org valgrind] provides us so that we don't have to see '''every''' single problem that the program has. Eventually, other libraries your program is using, like X itself, will show memory usage problems, and [http://valgrind.kde.org valgrind] will show them. So, on the first few runs of [http://valgrind.kde.org valgrind], we will have to build a suppression file, which is specified by ''--suppressions='' and we tell [http://valgrind.kde.org valgrind] to generate suppressions on screen. ''--gen-suppressions=yes'' will do this. Suppressions are a few lines that you may copy/paste in the suppressions file, all you have to do is give each suppression a name and that's it.

When set up that way, each time [http://valgrind.kde.org valgrind] finds something wrong, he will show you a few lines describing the problem and them he will ask you if you want him to generate the suppressions. If you say yes, the suppression appears on the screen, and you can copy/paste it in the suppressions file, so that next time you run valgring this error is not reported.

Now, after prompting the user for printing the suppression, [http://valgrind.kde.org valgrind] will prompt the user again whether or not he should start [http://www.gnu.org/software/gdb/gdb.html gdb]. If you say accept, [http://www.gnu.org/software/gdb/gdb.html gdb] will attach the running process and you will be debugging the program exactly at the point of the invalid operation.

== A few [http://www.gnu.org/software/gdb/gdb.html gdb] usefull commands ==
----
;'''''bt''''': backtrace, shows the stack frames (subroutine calls) that lead to the position you are now in code.
;'''''bt full''''': shows every frame with the values of the local variables, usually too much verbose, only do this if you want to send the output to another person to analyse.
;'''''up/down number''''': e.g.: ''up 5'': goes up 5 stack frames. By default, whenever you enter [http://www.gnu.org/software/gdb/gdb.html gdb], you will be placed in frame number 0. '''With the aid of the source code of the program''' you should be able to select the subroutine where you want to inspect the variables.
;'''''frame number''''': goes straight to the selected frame.
;'''''info locals''''': prints the value of all local variables belonging to the current frame.
;'''''p variable''''': e.g.: ''p *cur_src''. Prints the named variable. Usually C like syntax will be allowed here.
;'''''l''''': prints 10 lines of source code around the current line. A separate editor for source browsing is usualy better, but this can be a quick way to see the code.
;'''''help/help command''''': Do I need to explain that? :)

There are other commands, but usualy these described will suffice. It's worth mentioning that [http://www.gnu.org/software/gdb/gdb.html gdb] can be run with the core file, i.e., that big file that is produced after a crash. To do that, type

''gdb '''program_path''' '''core_file_path'''''

Also there are GUI front ends to [http://www.gnu.org/software/gdb/gdb.html gdb] that make it a little bit more friendly (like [http://kgdb.sourceforge.net kdbg]). GUI front ends are great to inspect several different variables by clicking with the mouse. But learning to use [http://www.gnu.org/software/gdb/gdb.html gdb] from the console is by far the fastest way to do the job, not to mention that you can do it '''quickly''' in a remote terminal session.

Also note that practice makes it perfect, so the only way to realy learn how to do this is by doing it. You will see that you will quickly learn how to move around [http://www.gnu.org/software/gdb/gdb.html gdb], in spite of his daunting console interface. Soon he will become your friend. :)

'''NOTE:''' [[aMule]] is a '''separate''' project from [http://www.gnu.org/software/gdb/gdb.html gdb], [http://valgrind.kde.org valgrind] or any other project refered in this text, and is '''not''' related to any of them.

Using gdb and valgrind

2004-08-13T23:23:35Z

Phoenix:

<center><h2>by ''Phoenix''</h2></center>

The two programs, [http://www.gnu.org/software/gdb/gdb.html gdb] and [http://valgrind.kde.org valgrind], are fabulous tools to find errors in your code. [http://www.gnu.org/software/gdb/gdb.html gdb] is the standard gnu debugger, very powerfull, virtually every debugger in [http://www.gnu.org GNU] is [http://www.gnu.org/software/gdb/gdb.html gdb]-based. So, you need to learn some [http://www.gnu.org/software/gdb/gdb.html gdb]. [http://valgrind.kde.org valgrind] is another invaluable tool, that allows you to track memory usage, stopping the program whenever an invalid operation has been made.

[http://valgrind.kde.org valgrind] can be used together with [http://www.gnu.org/software/gdb/gdb.html gdb], so that you can actually debug the program that is beeing analysed. This is possible due to a [http://www.gnu.org/software/gdb/gdb.html gdb] feature that makes it possible to attach any running process to a [http://www.gnu.org/software/gdb/gdb.html gdb] session.

The first step is to setup '''valgrind''', but first, some interesting links about [http://valgrind.kde.org valgrind]:

* Home page: http://valgrind.kde.org/
* Documentation: http://developer.kde.org/~sewardj/docs-2.0.0/manual.html
* How To: http://www.tldp.org/HOWTO/Valgrind-HOWTO/
* FAQ: http://valgrind.kde.org/faq.html
* Nice article explaining how to use: http://www.linux-mag.com/2003-05/compile_03.html

== Running [http://valgrind.kde.org valgrind] ==
----

I personaly use the following call:

<code>valgrind -v --leak-check=yes --gdb-attach=yes --num-callers=10 --suppressions=amule.sup --gen-suppressions=yes ~/programs/amule/amule-dev-cvs/src/amule --enable-stdin</code>

This way, leak-check is enabled, and whenever a problem is detected, the user will be prompted for whether he wants to start [http://www.gnu.org/software/gdb/gdb.html gdb] at the current position. This is a great moment to see the beast exactly at the moment of falilure. The parameter ''--num-callers'', which defaults to 4, is the number of backtrace lines that [http://valgrind.kde.org valgrind] shows you, 4 is too little.

Finally, there is ''--gen-suppressions'' and ''--suppressions''. Suppressions are a way that [http://valgrind.kde.org valgrind] provides us so that we don't have to see '''every''' single problem that the program has. Eventually, other libraries your program is using, like X itself, will show memory usage problems, and [http://valgrind.kde.org valgrind] will show them. So, on the first few runs of [http://valgrind.kde.org valgrind], we will have to build a suppression file, which is specified by ''--suppressions='' and we tell [http://valgrind.kde.org valgrind] to generate suppressions on screen. ''--gen-suppressions=yes'' will do this. Suppressions are a few lines that you may copy/paste in the suppressions file, all you have to do is give each suppression a name and that's it.

When set up that way, each time [http://valgrind.kde.org valgrind] finds something wrong, he will show you a few lines describing the problem and them he will ask you if you want him to generate the suppressions. If you say yes, the suppression appears on the screen, and you can copy/paste it in the suppressions file, so that next time you run valgring this error is not reported.

Now, after prompting the user for printing the suppression, [http://valgrind.kde.org valgrind] will prompt the user again whether or not he should start [http://www.gnu.org/software/gdb/gdb.html gdb]. If you say accept, [http://www.gnu.org/software/gdb/gdb.html gdb] will attach the running process and you will be debugging the program exactly at the point of the invalid operation.

== A few [http://www.gnu.org/software/gdb/gdb.html gdb] usefull commands ==
----
;'''''bt''''': backtrace, shows the stack frames (subroutine calls) that lead to the position you are now in code.
;'''''bt full''''': shows every frame with the values of the local variables, usually too much verbose, only do this if you want to send the output to another person to analyse.
;'''''up/down number''''': e.g.: ''up 5'': goes up 5 stack frames. By default, whenever you enter [http://www.gnu.org/software/gdb/gdb.html gdb], you will be placed in frame number 0. '''With the aid of the source code of the program''' you should be able to select the subroutine where you want to inspect the variables.
;'''''frame number''''': goes straight to the selected frame.
;'''''info locals''''': prints the value of all local variables belonging to the current frame.
;'''''p variable''''': e.g.: ''p *cur_src''. Prints the named variable. Usually C like syntax will be allowed here.
;'''''l''''': prints 10 lines of source code around the current line. A separate editor for source browsing is usualy better, but this can be a quick way to see the code.
;'''''help/help command''''': Do I need to explain that? :)

There are other commands, but usualy these described will suffice. It's worth mentioning that [http://www.gnu.org/software/gdb/gdb.html gdb] can be run with the core file, i.e., that big file that is produced after a crash. To do that, type

''gdb '''program_path''' '''core_file_path'''''

Also there are GUI front ends to [http://www.gnu.org/software/gdb/gdb.html gdb] that make it a little bit more friendly (like [http://kgdb.sourceforge.net kdbg]). GUI front ends are great to inspect several different variables by clicking with the mouse. But learning to use [http://www.gnu.org/software/gdb/gdb.html gdb] from the console is by far the fastest way to do the job, not to mention that you can do it '''quickly''' in a remote terminal session.

Also note that practice makes it perfect, so the only way to realy learn how to do this is by doing it. You will see that you will quickly learn how to move around [http://www.gnu.org/software/gdb/gdb.html gdb], in spite of his daunting console interface. Soon he will become your friend. :)

'''NOTE:''' [[aMule]] is a '''separate''' project from [http://www.gnu.org/software/gdb/gdb.html gdb], [http://valgrind.kde.org valgrind] or any other project refered in this text, and is '''not''' related to any of them.

AMule Project FAQ:Policy

2004-07-23T11:50:05Z

Phoenix:

The [[Main_Page|aMule wiki]] is of public use. Any one can edit it's unprotected pages as long as:
*No valid information is lost.
*No useless, injuring or illegal information is added.
*No copyrighted work is submitted without permission of the owner.
*The user editting the document realizes he/she is responsible of the edit.

Please [[Special:Userlogin|register]] (if not registered already) and [[Special:Userlogin|log in]] before editting.

Please note that anyone can share [[Main_Page|aMule's wiki]]'s contents as long as it follows the [[AMule_Project_FAQ:Copyrights|GNU FDL]] it is subjected to.

Feel free to suggest, add, delete, talk, edit, register, etc... as long as you follow '''all''' of the rules mentioned above in this policy.

As a side note, make sure the contents of your edit follow your country's law (and any other environmental law you are subjected to) and the country where [[Main_Page|aMule's wiki]]'s server is placed's law (and any other environmental law it is subjected to).