AMule Project FAQ - User contributions [en]

HowTo Compile aMuled

2005-05-23T14:29:10Z

80.58.32.171:

<center> '''English''' | [[HowTo_Compile_aMuled-es|Español]] </center>

== 1st ==

'''NOTE:''' If you have already installed [[wxWidgets|wxGTK]] 2.5.4 or higher, jump directly into the [[#2nd|second step]], since [[wxGTK]] 2.5.4 includes [[wxBase]] 2.5.4. Note that [[aMuled]] will not compile with earlier versions of [[wxWidgets]], such as version 2.4.2!

Download [[wxBase]] 2.5.4 or higher from http://www.wxWidgets.org
unpack it, and do as user
*''./configure --prefix=/usr/''
'''NOTE:''' If you want [http://www.unicode.org Unicode] support you need to give the ''--enable-unicode'' flag to the configure script.
*''make''
as root
*''make install''
*''ldconfig''

== 2nd ==

*Download [[aMule]] 2.0.1 from http://www.amule.org/files/files.php?cat=19
Don't use version 2.0.0-rc8, there was a severe bug in it concerning [[aMuled]]!

Unpack it, and do as user
*''./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon''
*''make''
as root
*''make install''

That's it. You now have a working [[aMuled|aMule-daemon]] in ''/usr/local/bin'' 
Now you need to configure it. To create the ''~/.aMule/amule.conf'' file, which is the preferences file, run [[aMuled]] once. 
The ''~/.aMule'' directory and the ''~/.aMule/amule.conf'' file will be created in the home directory of the user that ran [[aMuled]]. 
::'''NOTE:''' In [[aMule]] versions previous to 2.0.0 the ''~/.aMule/amule.conf'' file was ''~/.eMule''. 
You probably want [[aMuleWeb]] to control your [[aMuled|daemon]]. To be able to use that you need to enable [[External Connections]]. Check [[Webserver-1.2.x|this article]]. 
I know it's for 1.2.x but since you dont have a GUI to setup everything this is what you want. 
Also read the [[FAQ_amuled|aMuled FAQ]], since some setup things are metioned there.

== Where to report problems and questions? ==

For Problems or Questions just report on [http://forum.amule.org aMule forum] or join [[IRC]] channel [irc://irc.freenode.net/amule #amule] at [irc://irc.freenode.net irc.freenode.net]

[[User:Stefanero|Stefanero]]

If you're compiling on a [[Debian]] installation, and configure can't find ''wx-config'', make sure to install packages ''libwxgtk2.5-dev'', and ''libwxgtk2.5.3''.

HowTo Compile In Gentoo

2005-05-21T14:03:16Z

80.58.32.171:

Compiling a recent version of [[aMule]] on [http://www.gentoo.org Gentoo] should be a breeze by just typing
''emerge amule''
but due to several facts it isn't quite that easy right now. So here's a little Step-by-Step explanation. Please read the whole document before doing anything as there are several ways you can use and each of them will have a different outcome.

'''Note:''' currently Diego "Flameeyes" Pettenò (non-official devel) is trying to make the [[aMule]] emerge easier. Please take a look at [http://bugs.gentoo.org/show_bug.cgi?id=71108 Gentoo Bug #71108] for further information. The new ebuild requires, at minimum, [[wxGTK]] 2.5, but there is another ebuild for [[wxGTK]] 2.5 (also from Diego) which should allow to safely unmask that version.

== Available eBuilds ==

The eBuild for [[aMule]]-2.0.1 can be found here:
http://bugs.gentoo.org/show_bug.cgi?id=71108

The eBuild for [[aMule CVS]] can be found here:
http://forum.amule.org/thread.php?sid=&postid=30548

== Stable [[aMule]] from portage ==

If you just ''emerge amule'' you will install the version of [[aMule]] that [http://www.gentoo.org Gentoo] considers stable. This version is amule-1.2.8 which is over 12 months old, lacks several bugfixes and features which could seriously lower your downloads or make it impossible to connect to some servers. So this option is not really a good option.

== Unstable [[aMule]] from portage ==

[http://www.gentoo.org Gentoo] classifies amule2.0.0rc ebuilds as unstable because they are ReleaseCandidates. The latest one available is ''amule2.0.0rc7''. There is an (unofficial) ebuild for rc8, but rc8 depends on ''wxGTK2.5.3'' to build the [[aMuled|aMule daemon]] and ''wxGTK2.5.3'' is hardmasked in portage.

However, if rc7 is "new enough" for you enter the following things as root into a console:

<code>mkdir /etc/portage (this could give an error message if the directory already exists, just ignore that) 
echo 'net-p2p/amule ~x86' >> /etc/portage/package.keywords 
emerge -av amule</code>

However rc7 is getting quite old now, so it is the best thing to use either rc8 or even a recent cvs tarball and compile amule manually.

== Recent [[aMule]] manual installation ==

By default, [http://www.gentoo.org Gentoo] uses ''gtk2'' in all recent profiles. When it comes to [[wxGTK]] (which is needed by [[aMule]]), this can be some trouble. The recent stable [[wxGTK]] in portage is ''wxGTK2.4.2'' which should never be linked against ''GTK2''. It causes random crashes, freezes, unpredictable behaviour and may even harm your pet dog!

So there are two possible ways to go: choose ''wxGTK2.4.2'' linked against ''GTK1.2'' (which should be fine for everybody who doesn't want to use [[aMuled]], the [[aMuled|aMule daemon]]) or choose ''wxGTK2.5.3'' linked either against ''GTK1.2'' or ''GTK2'' (for those who want to try [[aMuled]] as [[aMuled]] doesn't work with [[wxGTK]] prior to 2.5.3).

Another thing is unicode support: You can't enable unicode support when using ''GTK1.2'' and enabling unicode with ''GTK2'' causes huge memleaks (100MB and more in 24h). So I will just disable it in these examples.

== [[wxGTK]] 2.5.3 - 2.6.0 ==

If you want to use amuled then you need, at least, ''wxGTK2.5.3''. Currently, the only version not hard masked in Portage is [[wxGTK]] 2.4.2 due to problems when compiling with [http://www.opengl.org OpenGL] support in [[wxGTK]] 2.5.3. But as [[aMule]] is no 3D egoshooter, we can safely disable [http://www.opengl.org OpenGL] support and use it anyway. To do so enter the following into a console as root:

<code>mkdir /etc/portage (this may give you an error if the directory already exists, just ignore that) 
echo 'x11-libs/wxGTK ~x86' >> /etc/portage/package.keywords </code>

If you want to use ''GTK1.2'' (recommended): 
<code>echo 'x11-libs/wxGTK -gtk2 -unicode -opengl' >> /etc/portage/package.use </code>

If you want to use ''GTK2'' (not thoroughly tested yet): 
<code>echo 'x11-libs/wxGTK -unicode -opengl' >> /etc/portage/package.use </code>

<code>emerge -av wxGTK</code>

== [[wxGTK]] 2.4.2 ==

If you don't want to use [[aMuled]] then ''wxGTK2.4.2'' is just fine for. You only need to tell it that it should link against ''GTK1.2''. To do this grab a console and enter (as root):

<code>mkdir /etc/portage (this may give you an error if the directory already exists, just ignore that) 
echo 'x11-libs/wxGTK -gtk2 -unicode' >> /etc/portage/package.use 
emerge -av wxGTK</code>

This should (re-)emerge ''wxGTK2.4.2'' linked against ''GTK1.2''. Now you can go on to [[HowTo_Compile_In_Gentoo#compiling_amule|compiling aMule]].

== Compiling [[aMule]] ==

Grab either ''amule2.0.0rc8'' from http://www.aMule.org or (specially if you want to use [[aMuled]]) a recent [[aMule CVS|CVS tarball]] from http://amule.hirnriss.net. Untar it by entering <code>tar -xvjf aMule-foo.tar.bz2</code> and go into the newly created directory.

Review <code>./configure --help</code> for a summary of all configure options. Pick the ones you want and run (as an example building, the monolithic client and [[aMuleCMD]]) 
<code>./configure --enable-amulecmd</code>

Review the configure output for errors and if everything seems fine type <code>make</code>. Once [[aMule]] is done compiling change to a root account and type <code>make install</code> to install [[aMule]]. Now you're done and can start enjoying your [[aMule]] experience.

Webserver

2005-01-26T14:23:55Z

80.58.32.171:

=== Previous notes ===

If you installed [[aMule]] via [http://www.debian.org deb] or [http://www.rpm.org RPM] package, the [[aMuleWeb|webserver]] source is not included.
Since some few files are needed from the sources to set-up [[aMuleWeb|amuleweb]], please visit http://www.amule.org and download the [[aMule]] tar.gz package for your packaged [[aMule]] version.

== Set a [[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/''

*Go to "Preferences"->"Remote Controls" (in [[aMule]]) and...
**Enable "Accept External Connections".
**Enable "Use TCP ports instead of unix local sockets".

::'''NOTE:''' On some early [[aMule]] 2.0.0-rcX versions the above two 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.

*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]

User:Ken

2005-01-20T08:32:16Z

80.58.32.171:

'''[[aMule]] tester & [[AMule_devs|dev]] ;)'''

[[aMule]] concerns:
*[http://macosx.apple.com MacOS X] [[aMule]]r

How to launch VNC with aMule at Linux boot

2004-09-07T03:16:57Z

80.58.32.171: layout, links, contents, typos...

<h2>''By [[User:Frankk|Frankk]]''</h2>

This describes a very simple configuration to launch [http://www.redstonesoftware.com/vnc.html VNC] at [http://www.kernel.org Linux] startup (as a specified user). [[aMule]] will be launched automatically with [http://www.redstonesoftware.com/vnc.html VNC].
This will work in [http://www.slackware.com Slackware] and distro based on the same init method. If someone knows how to modify it to make it work under other distros you are welcome to add it to this page. Thanks.

Add the ''rc.vnc'' script to ''/etc/rc.d''

Modify user according to the user running [[aMule]]. 
The ''rm /tmp/.X11-unix/X$theScreen'' is there in case the server crashes or your mother/wife removes the power plug cleaning the room... ;-)

''<pre>
#!/bin/sh
#
# Startup/Stop script for vncserver.
#

#Here, the choosen user to run amule
theUser=choosenuser
#And here, the choosen screen to run the vncserver
theScreen=1

case "$1" in

'start')
if [ -f /tmp/.X11-unix/X$theScreen ]; then rm /tmp/.X11-unix/X$theScreen; fi
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"
;;

'stop')
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver -kill :$theScreen"
;;

*)
echo "Usage: /etc/init.d/rc.vnc { start | stop }"
;;

esac
</pre>''

Make it executable with:

''<pre>chmod 755 /etc/rc.d/rc.vnc</pre>''

Modify the following files:

In ''/etc/rc.d/rc.local'' add:

''<pre>
# Start VNC server
if [ -x /etc/rc.d/rc.vnc ]; then
. /etc/rc.d/rc.vnc start
fi
</pre>''

In ''/etc/rc.d/rc.6'' add:

''<pre>
# Shut down the VNC server
if [ -x /etc/rc.d/rc.vnc ]; then
/etc/rc.d/rc.vnc stop
fi
</pre>''

In ''~/.vnc/xstartup'' (in home directory of the user specified above) add (change with your preferred [[aMule]] startup script):

''<pre>amule &</pre>''

== On [http://www.debian.org Debian] Woody ==

Run (as root):

''apt-get install vncserver xvncviewer''
''apt-get install vncserver flwm''

There is no support for ''~/.vnc/xstartup'' so, instead, use ''$vncStartup'' in ''.vncrc'' to determine a xstartup-script (this replaces your ''~/.xsession'' file).

For more information, read ''man vnc.conf''

For example, in a Woody/Sarge/Sid: 
Login as the user who is going to run [[aMule]] 
''mkdir ~/.vnc/'' 
Create the ''~/.vnc/xstartup'' file, with the next content 

<pre>
/usr/bin/flwm &
/usr/bin/amule &
/usr/bin/amule &
</pre>

With sone versions of [http://www.redstonesoftware.com/vnc.html vncserver], it's necessary to launch at least twice the [[aMule]]. The [http://flwm.sourceforge.net flwm] is an optional window manager.

Create the file ''~/.vncrc'' with the next content: 
Login as the user and run ''xvncviewer :1'' to create the password file and debug possible probelms (the logs are under the ''~/.vnc/'' dir
''<pre>
$vncStartup = "/home/amule/.vnc/xstartup";
$geometry ="800x600";
</pre>''
(replace ''/home/amule'' for the home of the user running [http://www.redstonesoftware.com/vnc.html VNC])

To show the [[aMule]] window, run:
''<pre>
xvncviewer localhost:1
</pre>''

== [http://www.mandrake.com Mandrake] 10.0 ==

The script from [[User:Frankk|Frankk]] is the one I use, but you can customize the size of the [http://www.redstonesoftware.com/vnc.html VNC] server :
''<pre>
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen"
</pre>''
add
''<pre>
/bin/su - $theUser -c "PATH=/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /usr/bin/vncserver :$theScreen -geometry 1240x980"
</pre>''
or whatever value.

Personaly, I use as xstartup script ([http://www.icewm.org iceWM] is really nice and so CPU-cheap) :
<pre>
#!/bin/sh
starticewm&
amule
</pre>

To start [http://www.redstonesoftware.com/vnc.html VNC] at startup, I called the previous script ''/etc/init.d/amulevnc'' and chmod to 744 (''chmod 744 /etc/init.d/amulevnc'' as root). 
Instead of modifying ''/etc/rc.d/rc.vnc'', I added links in the corresponding ''/etc/rc$RUNLEVEL.d'' directories. 
It's quite simple to understand how it works: 
Each directory represents a runlevel, and contains links to the scripts from ''/etc/init.d'' which need to be run/stop. 
For instance, the link ''/etc/rc5.d/S55sshd'' to ''/etc/init.d/sshd'' will start ''sshd'' on runlevel 5,
whereas ''/etc/rc6.d/K25sshd'' linked to ''/etc/init.d/sshd'' will stop it in runlevel 6. 
You get it? Links starting with 'KXX' will stop a service, and those starting with 'SXX' will start them. The number will define the order.

So to run [http://www.redstonesoftware.com/vnc.html VNC] on startup, just do (as root :-) )
''<pre>ln -s /etc/init.d/amulevnc /etc/rc5.d/S99amule
ln -s /etc/init.d/amulevnc /etc/rc6.d/K02amule</pre>''
and you're all set!

PS: This method should work on systems other than [http://www.mandrake.com Mandrake], give it a test.

Questions & comments: ''air_1 '''at''' libertysurtf.fr''