AMule Project FAQ - User contributions [en]

Webserver

2005-01-27T16:21:11Z

139.82.28.36: Installing from rpms is not a problem

== 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/''

* 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".

::'''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]

AMule devs

2004-07-16T21:41:14Z

139.82.28.36:

== The aMule Project ==
The aMule project is led by a bunch in people who toil away in front of their computers, so that you can enjoy a stable and featureful P2P client.
This page is about us.

== The Team ==
These are the people who works on aMule:

=== Developers ===

* [[User:deltaHF|deltaHF_]]:
* [[User:Jacobo221|Jacobo221]]:
* [[User:Kry|Kry]]:
* [[User:lfroen|lfroen]]:
* [[User:Madcat_|Madcat_]]:
* [[User:Phoenix|Phoenix]]: Code janitor junior.
* [[User:shakraw|shakraw]]:
* [[User:thepolish|thepolish]]: aMule tools coder
* [[User:Unleashed|Unleashed]]:
* [[User:Xaignar|Xaignar]]: Code janitor extraordinaire!
* [[User:falso|falso]]: cas coder

=== Testers ===

=== Others ===

=== Former Team-members ===
These are people who have worked on aMule in the past.
Please note that this list doesn't include the people from before [[aMule]] forked off from [[xMule]], nor does it include people from the [[lMule]] days. If you wish to learn more about those, please visit the websites of those projects.

==== Developers ====

==== Testers ====

==== Others ====

== Helping ==
We can always use another helping hand, and if you are interested, then I'd encourage you to contact us and see if you can help us. Currently, what we need the most is developers and testers, though also translators and others.

=== Becoming a Developer ===
To become a aMule Developer (tm), you'll need at the very least a working knowledge of C++, since that is the language in which aMule is written. You'll also need to learn about the GUI toolkit used by aMule: [http://www.wxwidgets.org wxWidgets].

However, we do not require that you are an expert, only that you are willing to help and willing to learn.

If you are interested, then simply drop by on [[IRC]] and let us know. Currently we use a private CVS server, but after you've submitted a patch or two you can easily get r/w access to it.

We can use your skills if you are using one of the platforms where we aim at being usable on: Nix, Macs and Windows.
And if your operating system of choice isn't on that list, then maybe you can help add it.

=== Becoming a Tester ===
We need people who are willing to create complete bug-rapports, as the standard is pretty low regarding user reports. This is rather simple, but takes patience. Please contact us on [[IRC]] for more information.

=== Becoming a Translator ===
aMule already includes translations for a number of languages, however, we'll always welcome more, and even if your language of choice has been done already, then perhaps you can help improve it. Please see the [[http://forum.amule.org/board.php?boardid=40 Translations] forum for more information, or contact us on [[IRC]].

HowTo Compile In Slackware

2004-07-09T21:12:17Z

139.82.28.36:

<center><h2>by Mike (servnov)</h2></center>

== Installing aMule on Slackware ==
----

:1)Download wxBase and wxGTK sources (.tar.gz packages) from [http://www.amule-project.net http://www.amule-project.net] or [http://www.amule.org http://www.amule.org]
::NOTE: you will need root access or equivalent to complete amule install.

:2)INSTALL:
::<code>tar -xzvf wxBase*</code>
::<code>cd wxBase*</code>
::<code>./configure</code>
::<code>make</code>
::<code>make install</code>

::<code>tar -xzvf wxGTK*</code>
::<code>cd wxGTK*</code>
::<code>./configure</code>
::<code>make</code>
::<code>make install</code>

::Grab pre-built Slackware package from http://www.linuxpackages.net/download.php?id=3038 (choose a mirror)

***IMPORTANT: you need to have installed pkgtools with slack (this is done by default).

::<code>installpkg aMule-2.0.0rc3-i686-2.tgz (or whatever current version is)</code>

::That's all!

::type 'amule' in a shell to lauch or in KDE (similar in GNOME) go to Kstart->Internet->aMule

:3)UNINSTALL:
::<code>removepkg aMule</code> (should work without version, etc.)

::then if you want get a newer aMule*.tgz version as 'installpkg' again

Hope this helps.

Catch me on IRC at irc.freenode.com channel #amule nick 'servnov'

== Final note ==
----

Building aMule itself from source (ie NOT from installpkg aMule*.tgz) usually causes many problems in Slackware, Knoppix, and a few other distros. Known possible problems:

*configure fails to build makefile :(
*wxwidgets error or similar
*package 'curl' not found or version is outdated
*crypto and many make errors

Enjoy the hard work aMule developers have done and continue to do!

Just remember you will need wxBase and wxGTK installed even when using slackware package.

Main Page

2004-07-09T20:31:38Z

139.82.28.36:

== Welcome to the FAQ of aMule Project ;-) ==

http://www.amule.org/images/logo.gif

We hope you will find some answers for your questions and problems!

aMule Team

 

== FAQs: ==

FAQ [[FAQ_aMule|on aMule]] ([[FAQ-es|Spanish]]) ([[FAQ-it|Italian]]) ([[FAQ_aMule-pt_BR|Brazilian]]) 
FAQ [[FAQ_eD2k/Kademlia|on ED2K/Kademlia]] ([[FAQ_ed2k-es|Spanish]]) ([[FAQ_ed2k-it|Italian]]) 
FAQ [[aMule_problems|on aMule common problems]] ([[aMule_problems-es|Spanish]]) 
FAQ [[FAQ_utils|on aMule's utilities]] 

 

== Help: ==

Howto [[Compilation Installation|compile/install aMule from scratch]] 
Howto [[Install-amule-freebsd|compile aMule on FreeBSD]] 
Howto [[HowTo compile on Win32|compile aMule on Windows]] 
Howto [[HowTo_Compile_In_Debian| compile aMule in Debian]] 
Howto [[HowTo_Compile_In_Slackware| compile aMule in Slackware]] 
Howto [[CryptoppDebian|make Crypto++ work on Debian]] 
Howto [[MDK10_install|install aMule in Mandrake 10]] ([[MDK10 install-es|Spanish]]) 
Howto [[Backtraces|create backtraces]] to help the [[aMule_devs|aMule devs]] 
Howto [[Using gdb and valgrind|use gdb and valgrind]] 
Howto [[Firewall|setup iptables for aMule]] 
Howto [[Ed2k links handling|handle ed2k:// links]] 
Howto [[Webserver|Webserver configuration]] for aMule >= 2.0.0rc1 
Howto [[Debian_fonts|Font problems on Debian]] 
Howto [[aMule_Project_Wikipedia:How_does_one_edit_a_page|edit a page]] 

 

== Changelogs: ==

[[Changelog_1.2.7|Latest aMule release]] 
[[Changelog_1.0_series|aMule 1.0.x]] 
[[Changelog_1.1_series|aMule 1.1.x]] 
[[Changelog_1.2_series|aMule 1.2.x]] 
[[Changelog_2.0_series|aMule 2.0.x]]

Screen

2004-06-09T20:54:34Z

139.82.28.36:

Screen is a program that lets you have many virtual console sessions in a machine. You may leave jobs running and then logout completely. Each jobs console output will be recovered later when you are back. 

Ex.: 
[guy@machine homedir]$ screen -S job1 

(Nothing seems to happen, but in fact you are now in a virtual session Do something that will take a long time and will produce console output.) 

[guy@machine homedir]$ ls 
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps 
capacete.eps fratura2.eps oito3.eps 
capaealma.eps fratura3.eps oitoduplo.eps 
capa.eps fratura4.eps oito.eps 
[guy@machine homedir]$ 

(Now type <CTRL-A><CTRL-D>. The screen clears and...)

[guy@machine homedir]$ screen -S job1 
[detached] 
[guy@machine homedir]$ 

Now, whenever you want to recover that jobs output, you do 

[guy@machine homedir]$ screen -R -S job1 

and...

[guy@machine homedir]$ ls 
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps 
capacete.eps fratura2.eps oito3.eps 
capaealma.eps fratura3.eps oitoduplo.eps 
capa.eps fratura4.eps oito.eps 
[guy@machine homedir]$ 

Here we are again. 
man screen is your friend. 
Enjoy!

Screen

2004-06-09T20:54:07Z

139.82.28.36:

Screen is a program that lets you have many virtual console sessions in a machine. You may leave jobs running and then logout completely. Each jobs console output will be recovered later when you are back. 

Ex.: 
[guy@machine homedir]$ screen -S job1 
(Nothing seems to happen, but in fact you are now in a virtual session Do something that will take a long time and will produce console output.) 
[guy@machine homedir]$ ls 
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps 
capacete.eps fratura2.eps oito3.eps 
capaealma.eps fratura3.eps oitoduplo.eps 
capa.eps fratura4.eps oito.eps 
[guy@machine homedir]$ 

(Now type <CTRL-A><CTRL-D>. The screen clears and...)

[guy@machine homedir]$ screen -S job1 
[detached] 
[guy@machine homedir]$ 

Now, whenever you want to recover that jobs output, you do 

[guy@machine homedir]$ screen -R -S job1 

and...

[guy@machine homedir]$ ls 
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps 
capacete.eps fratura2.eps oito3.eps 
capaealma.eps fratura3.eps oitoduplo.eps 
capa.eps fratura4.eps oito.eps 
[guy@machine homedir]$ 

Here we are again. 
man screen is your friend. 
Enjoy!

Screen

2004-06-09T20:49:24Z

139.82.28.36: screen: a virtual console session manager

Screen is a program that lets you have many virtual console sessions in a machine. You may leave jobs running and then logout completely. Each jobs console output will be recovered later when you are back.

Ex.:
[guy@machine homedir]$ screen -S job1
(Nothing seems to happen, but in fact you are now in a virtual session Do something that will take a long time and will produce console output.)
[guy@machine homedir]$ ls
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps
capacete.eps fratura2.eps oito3.eps
capaealma.eps fratura3.eps oitoduplo.eps
capa.eps fratura4.eps oito.eps
[guy@machine homedir]$
(Now type <CTRL-A><CTRL-D>. The screen clears and...)
[guy@machine homedir]$ screen -S job1
[detached]
[guy@machine homedir]$

Now, whenever you want to recover that jobs output, you do
[guy@machine homedir]$ screen -R -S job1

and...

[guy@machine homedir]$ ls
caminhadas_bivaques.tex.backup fratura1.eps oito2.eps
capacete.eps fratura2.eps oito3.eps
capaealma.eps fratura3.eps oitoduplo.eps
capa.eps fratura4.eps oito.eps
[guy@machine homedir]$

Here we are again.
man screen is your friend.
Enjoy!