Difference between revisions of "AMuleGUI"
(add info about controlling a daemon on Unix/Linux) |
Vollstrecker (Talk | contribs) m (Typo) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | <center> | ||
| + | '''English''' | | ||
| + | [[AMuleGUI-de|Deutsch]] | ||
| + | </center> | ||
| + | |||
aMuleGUI allows you to administrate [[aMuled]] remotely and it has a user interface that looks exactly like good old [[aMule]]. If your connection is too slow try to use [[aMuleCMD]]. | aMuleGUI allows you to administrate [[aMuled]] remotely and it has a user interface that looks exactly like good old [[aMule]]. If your connection is too slow try to use [[aMuleCMD]]. | ||
| − | '''WARNING:''' It is still somewhat buggy (2.0.3). | + | '''WARNING:''' It is still somewhat buggy (2.0.3). (This is still true in 2.1.0; |
| − | for example, it doesn't support comments about files, and it crashed on me a few times. | + | for example, it doesn't support comments about files, and it crashed on me a few times. If only it worked, it would be a great way to have aMule run all the time in the background, as a daemon, with the GUI coming and going as you like). |
| − | '''NOTE:''' You must have [[External Connections]] enabled in order to be able to connect to [[aMuled]]. | + | '''NOTE:''' You must have [[External Connections]] enabled in order to be able to connect to [[aMuled]]. More important, you need to set a password for the connections. And if you only want to control it from the local machine, set the interface address to 127.0.0.1 (the loopback interface), which can only be reached from the local machine. |
See also [[FAQ_amulegui|aMuleGUI FAQ]]. | See also [[FAQ_amulegui|aMuleGUI FAQ]]. | ||
Latest revision as of 16:10, 23 September 2008
English | Deutsch
aMuleGUI allows you to administrate aMuled remotely and it has a user interface that looks exactly like good old aMule. If your connection is too slow try to use aMuleCMD.
WARNING: It is still somewhat buggy (2.0.3). (This is still true in 2.1.0; for example, it doesn't support comments about files, and it crashed on me a few times. If only it worked, it would be a great way to have aMule run all the time in the background, as a daemon, with the GUI coming and going as you like).
NOTE: You must have External Connections enabled in order to be able to connect to aMuled. More important, you need to set a password for the connections. And if you only want to control it from the local machine, set the interface address to 127.0.0.1 (the loopback interface), which can only be reached from the local machine.
See also aMuleGUI FAQ.
