aMule Forum
English => Feature requests => Topic started by: KoMpLoT on February 17, 2005, 09:33:18 PM
-
Hi everyone!! this is my first post on the forum, before I was just hanging around... :P
Now, here's my request...
is there any chances to get aMule to support different users?
that would be great!
:D
If I can help with something in the development, count on me!
-
support different users
If you mean "Can 2 users run 2 different amule(d)s on same machine" - answer is "yes, use different ports, both will have lowid"
If you mean "Can 2 users connect to same amule(d) via webserver and " answer is yes, but amule can't distinguish between them
So, pls be more presize on your question :) and tell what exactly you mean
-
lfroen, as we were discussing on irc, the main intention for this multi-user system is the to give different users the option to connect to the same amule server, but with diferent ids, so each user may have access to their own searches, to their own downloads, etc. It will be like virtual users are created.
Anyway, the downloads might (or might not) continue on the same folder for all the users.
If you can take a look at torrentflux (http://www.torrentflux.com, it's a bittorrent php gui) it allows different users to login and keeps track of all the activity in a database, using mysql.
-
Multi user system as discussed on irc will be implemeted after major release. This isn't PhD but requires changes all around the code.
track of all the activity in a database, using mysql.
Don't get carried away. Whoever implemeted this have very weird idea about "what is logfile". What kind of "activity" are we talking about :
1. User X started/paused/canceled down/upload
2. User X run search
3. User X changed preferences.
Using some imagination you can come out with some more. But, wtf do you need to mess with sql server install/maintenance/security ? Run sql server for logging ? Are you hearing yourself ?
This would have some sense if we were talking about ~10000 users and we required to generate statistic report. Even in this case, sql server is not best solution because it's relational database, not "grep -c"
-
Stay cool, lfroen, I think he was only talking about how it is implemented in torrentflux when refering to mysql. I don't think it was a serious proposal on how to implement this feature in amule... ;)
-
I don't think it was a serious proposal on how to implement this feature in amule..
I don't think so too. I commented on reffered implementation.
-
Originally posted by lfroen
I don't think it was a serious proposal on how to implement this feature in amule..
I don't think so too. I commented on reffered implementation.
as thedude0001 said, I just was trying to show the way torrentflux worked and I was trying to point that the system is nice and works fine... just that...
-
hi everybody
i've done the same sugestion in the spanish forum a few days ago. I think that it would be great, amule could work like an ftp daemon does, for example. You log in with the system username and password, and you see only your downloads, and every user could have an incoming directory in the home dir.
i think that this would be very interesting, because then you could apply quota restrictions in the users
i'm also a regular user of amulecmd, and i miss this 2 features: search, and download in a specific category.
well, finally i must say that you are doing a great job, congratulations! (a happy amule user :D)
-
every user could have an incoming directory in the home dir.
No, sorry. Not this way. Every user will have his/her file(s) in separate directory under central "Incoming" directory under "amule" user (unix user).
Why ? There're 2 main reasons.
First is permissions. It's not exactly a problem, but incorrect permissions will be revealed only after download is complete, and amule can't cp/mv file. Now what ? Remove file silently or keep it under "Temp" - user complains about "my file is lost".
Second is duplicate files. Consider 2 users want to download same file. What to do ? amule clearly can't do it "as is". Should it start to create sort of "reference counting" and upon competion copy it twice ? Or just notify second user "file already being downloaded by ". First user reaction would be "so what ? I want it too".
you could apply quota restrictions in the users
Even if you do adjust permissions correctly, and put "Incoming" under each $HOME, this will not work. Becouse incoming files are owned by user amule(d) is running under; say user "amule".
It is both complicated, OS dependent and seriously affects security. Becouse for amule to call
#include
#include
int setuid(uid_t uid);
it should be running as suid root. And this is highly not recommended
Short conclusion - multi user system will be implemented, but as "light version" - i.e. under single "real" user.
-
Why would they have Low ID? As long as each user uses different ports and those ports are not blocked incoming then they should all be High ID...
-
Because high ID is your IP address written in decimal. No matter what ports you use, you still have 1 IP. RTFM.