aMule is an eMule-like client for the eD2k and Kademlia networks, supporting multiple platforms.

aMule is an eMule-like client for the eD2k and Kademlia networks, supporting multiple platforms.

−

==Installation==

+

== Installation ==

+

aMule can be installed with package {{Pkg|amule}}, available in the [[official repositories]].

aMule can be installed with package {{Pkg|amule}}, available in the [[official repositories]].

−

'''amuled''' is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK), aMuleWeb, or aMuleCmd.

+

{{ic|amuled}} is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK+), aMuleWeb, or aMuleCmd.

−

==Services==

+

== Services ==

−

The package provides two systemd services: amuled and amuleweb. First you need to configure it. You need to provide passwords for external connection and admin password for amuleweb. Please see section below for more config information.

+

−

Then services be started as

+

The package provides two ''systemd'' [[daemon|services]]: {{ic|amuled}} and {{ic|amuleweb}}. First you need to [[#Configuration|configure]] it. You need to provide passwords for external connection and admin password for {{ic|amuleweb}}. Start {{ic|amuled}} service and {{ic|amuleweb}} if you require it. Enable them to start aMule every boot.

−

# systemctl start amuled

+

−

# systemctl start amuleweb

+

−

Once '''amulweb''' service is started it is available at {{ic|http://127.0.0.1:4711}} (or with external address of your host).

+

Once {{ic|amulweb}} service is started, it is available at {{ic|http://127.0.0.1:4711}} (or with external address of your host).

−

==Configuration==

+

== Configuration ==

−

At package installation time a new user account '''amule''' created. This account is used to run systemd services.

+

+

At package installation time a new user account '''amule''' created. This account is used to run ''systemd'' services.

All configuration and temporary files are kept in amule home directory {{ic|/var/lib/amule}} among them:

All configuration and temporary files are kept in amule home directory {{ic|/var/lib/amule}} among them:

Line 25:

Line 24:

* config file for amuleweb {{ic|/var/lib/amule/.aMule/remote.conf}}

* config file for amuleweb {{ic|/var/lib/amule/.aMule/remote.conf}}

−

At the package instalation time pacman generates a simple amule.conf file with preset external connection password. The same password is used for amuleweb config file. One can use the password for connecting amule from other remote clients such as amule-gui.

+

At the package instalation time ''pacman'' generates a simple {{ic|amule.conf}} file with preset external connection password. The same password is used for ''amuleweb'' config file. One can use the password for connecting amule from other remote clients such as ''amule-gui''.

−

To generate password please run:

+

To generate password, run:

−

$ echo -n <your password here> | md5sum | cut -d ' ' -f 1

+

$ echo -n ''your password here'' | md5sum | cut -d ' ' -f 1

−

The output of the above command is the encrypted password. Now you edit the config file by adding following lines under section [ExternalConnect]:

+

The output of the above command is the encrypted password. Now you edit the config file by adding following lines under section {{ic|[ExternalConnect]}}:

{{hc|1=/var/lib/amule/.aMule/amule.conf|2=

{{hc|1=/var/lib/amule/.aMule/amule.conf|2=

[ExternalConnect]

[ExternalConnect]

Line 40:

Line 39:

# chown amule:amule -R /var/lib/amule

# chown amule:amule -R /var/lib/amule

−

==amuleweb==

+

== amuleweb ==

−

{{Note|amuleweb provides much less features than amulegui (and displays much less info on downloads), and it has to ask for password quite often (unless your browser could save it). It is therefore advisable to use amulegui instead (which starts up very fast as well), and if you decide to do so, you could skip this step.}}

+

−

===Create configuration files===

+

{{Note|''amuleweb'' provides much less features than ''amulegui'' (and displays much less info on downloads), and it has to ask for password quite often (unless your browser could save it). It is therefore advisable to use amulegui instead (which starts up very fast as well), and if you decide to do so, you could skip this step.}}

−

Start amuleweb too using the user you just created to create the configuration file:

Note that here, the <password here> is the unencrypted password you used to configure amuled. <web password here> is the unencrypted for the log in on the web interface. This command will write configuration file as such.

+

=== Create configuration files ===

+

+

Start ''amuleweb'' too using the user you just created to create the configuration file:

Note that here, the ''password here'' is the unencrypted password you used to configure amuled. ''web password here'' is the unencrypted for the log in on the web interface. This command will write configuration file as such.

{{Tip|If the default URL for nodes.dat for Kad network does not work, you can get URL from there: [http://nodes-dat.com]}}

{{Tip|If the default URL for nodes.dat for Kad network does not work, you can get URL from there: [http://nodes-dat.com]}}

Contents

Installation

amuled is a full featured aMule daemon, running without any user interface (GUI). It is controlled by remote access through aMuleGUI (GTK+), aMuleWeb, or aMuleCmd.

Services

The package provides two systemdservices: amuled and amuleweb. First you need to configure it. You need to provide passwords for external connection and admin password for amuleweb. Start amuled service and amuleweb if you require it. Enable them to start aMule every boot.

Once amulweb service is started, it is available at http://127.0.0.1:4711 (or with external address of your host).

Configuration

At package installation time a new user account amule created. This account is used to run systemd services.

All configuration and temporary files are kept in amule home directory /var/lib/amule among them:

config file for amuled /var/lib/amule/.aMule/amule.conf

config file for amuleweb /var/lib/amule/.aMule/remote.conf

At the package instalation time pacman generates a simple amule.conf file with preset external connection password. The same password is used for amuleweb config file. One can use the password for connecting amule from other remote clients such as amule-gui.

To generate password, run:

$ echo -n your password here | md5sum | cut -d ' ' -f 1

The output of the above command is the encrypted password. Now you edit the config file by adding following lines under section [ExternalConnect]:

Do not forget that all files under /var/lib/amule should be owned by amule user.

# chown amule:amule -R /var/lib/amule

amuleweb

Note: amuleweb provides much less features than amulegui (and displays much less info on downloads), and it has to ask for password quite often (unless your browser could save it). It is therefore advisable to use amulegui instead (which starts up very fast as well), and if you decide to do so, you could skip this step.

Create configuration files

Start amuleweb too using the user you just created to create the configuration file:

Note that here, the password here is the unencrypted password you used to configure amuled. web password here is the unencrypted for the log in on the web interface. This command will write configuration file as such.

Tip: If the default URL for nodes.dat for Kad network does not work, you can get URL from there: [1]