Difference between revisions of "Multi user"
Woutermense (Talk | contribs | merge | delete) |
Woutermense (Talk | contribs | merge | delete) (→aMule user) |
||
| Line 18: | Line 18: | ||
Give the user a name, set a password, do not tick the 'Disable User Login' option. | Give the user a name, set a password, do not tick the 'Disable User Login' option. | ||
[[Image:Adding_amule_user.PNG]] | [[Image:Adding_amule_user.PNG]] | ||
| + | |||
| + | ===Bootscripts=== | ||
| + | Next we need initscripts to get aMule started every time we boot our server. A good example for OpenSuSE is: | ||
===Server hardware example=== | ===Server hardware example=== | ||
Revision as of 23:54, 12 December 2008
Contents
Howto setup aMule for multi-user purposes
This article is made to show you how to make optimal use of your internet bandwidth by sharing aMule with multiple users. Often when an internet connection is shared between many persons bandwidth problems occur. People want to download or share files. So p2p applications are installed and the downloadfest can begin. Very soon all upload bandwidth is consumed by these applications and browsing and other useful things you can do with the internet become impossible or really annoying.
Basically, bandwidth restriction of users is a nuisance. Users are not happy because they have too little (in their opinion). A good idea would be to share the same p2p application with all the users. This not only makes it possible to control the upload bandwidth that is spent to p2p, also it can save a lot of energy because only 1 computer has to be turned on all the time to share files.
So what do we need to attain this goal? This is a short list of requirements:
- Server to run amuled on.
- aMuleGUI clients compiled for the OS's that different users have installed.
- A method of handling ed2k:// links remotely.
- Optional some method of traffic shaping.
Basic server configuration
If you already have a server, read on, else skip ahead to the server hardware example. I only have experience with the OpenSuSE 10.3 operation system so I will use this in my examples to explain things.
aMule user
Firstly it is important to always run the aMuleD in a restricted environment. So we create a user for aMule. Fire up Yast and get to the user management.
Give the user a name, set a password, do not tick the 'Disable User Login' option.
Bootscripts
Next we need initscripts to get aMule started every time we boot our server. A good example for OpenSuSE is:
