Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[skolnick]

Hi!

I just noticed that aMule will run amuleweb when found in the PATH, but if for some reason it's not in the PATH, then aMule will not run it. I would like aMule had a way to select the path to amuleweb, so it can run from non-standard places.

Thanks.

[lfroen]

No. Webserver configuration is already over-complicated with 3 (three!) passwords. Adding such obscure option makes no good.

[Kry]

Meh, lfroen. We can check the selected path if exists, and run with standard paths if it fails.

[lfroen]

Kry, usability of amule already suffered from many options. For webserver, for example I would like to see only 1 (one!) option "Turn it on/off". Option for choosing executable have no sense for wast majority of users.
I know, however, what kind of problem skolnik met (because I have it too). When I run compiled amule it fails to find amuleweb in path (it's not there, it's in compilation directory). To solve this kind of problem we can supply command line option of environment variable. But GUI - no no.

[Kry]

I said nothing about GUI. We have GUIless config options.

[Vollstrecker]

And for your "We have 3 passwords"-problem, I think about a soluton with pam.

[skolnick]

Hmm...Thanks for your replies guys, just one question: I fail to see the three passwords:
1 amuleweb itself
2 external connections of amule[d]
3
Which is the third password? OK, what I was thining is exactly what lfroen dislikes. I thought about a textbox in the remote tab of preferences telling "amuleweb executable" and instead of executing the amuleweb from the path, that would be run instead. I do not see that as big problem, however you guys have a bigger picture of the issue, and may have a better solution. Regarding lfroen's complain of having too many options for amuleweb, I think that those options are necessary, since amule is more complex than emule (for example). Emule has no EC, no emuled, no emulegui..it's a simpler program, therefore simpler to control, just an on/off for their emuleweb works fine. I thought then, that an "option" for amule[d] to look for amuleweb in its own folder would be cool, I mean, besides $PATH, amule could look into ./ for amuleweb. That would solve lfroen's and my issue, and would also include no more options for users. Even, for normal users it would have no problem, since normally amule and amuleweb both reside in the same bin folder

Regards.

[lfroen]

OK, let's count passwords AGAIN:
1. EC password
2. Webserver password
3. Webserver "low-rights" password

I think that those options are necessary,

And I think, having 3 passwords is counter-intuitive.

since amule is more complex than emule

Not really. From a user point of view, both have webserver, and on Windows 1. amuled is irrelevant and 2. who's using command line anyway.

I mean, besides $PATH, amule could look into ./ for amuleweb.

This is match better solution that gui option

And for your "We have 3 passwords"-problem, I think about a soluton with pam

Ahhhhh, now I will have to configure PAM?! Do you know that root access needed to do that? So, you mean that in order to configure tiny webserver I will have to type root password each time?
So, instead of 3 passwords I will have type 4. 3 for amuleweb, 1 for PAM.

[Kry]

I said nothing about GUI. We have GUIless config options.

[Vollstrecker]

Ahhhhh, now I will have to configure PAM?! Do you know that root access needed to do that? So, you mean that in order to configure tiny webserver I will have to type root password each time?
So, instead of 3 passwords I will have type 4. 3 for amuleweb, 1 for PAM.

Not really, I thought more about selcting existing users to have access. for querieng the users and verifying their pass no root access is needed. But there are three other things I have to do before I have concrete thoughts about that.

[skolnick]

OK, let's count passwords AGAIN:
1. EC password
2. Webserver password
3. Webserver "low-rights" password

You're right, lfroen, I had no taken low-rights password into account. However, I see very few solutions to this issue with too many passwords. The ones I see are:
1. Implement user/password or,
2. Remove "low rights" password and make EC password = administrative user password or,
3. Same as 2 but leaving the low rights password (that leaves us with 2 passwords, however)
That's the solutions I get, but I'm sure you will have a better one

1. amuled is irrelevant and 2. who's using command line anyway.

I do not see it as irrelevant, simply the emule team has not taken the time to implement it, since I think many people would like an eMule service, that starts with no user intervention, and can be controlled via web, just like amuled. Also, for me amuled is a daemon, is independant of commandline or not, is just the daemon.

I mean, besides $PATH, amule could look into ./ for amuleweb.

This is match better solution that gui option

I'm glad you see this as a good option. I just would like to know what Kry and the rest of the team think about all this.

[phoenix]

I think that if you want aMule to look at "./" you should start it like this:

PATH=.:$PATH amule

[lfroen]

However, I see very few solutions to this issue with too many passwords.

I see another solution. By definition, EC password is "admin password", so we left with only 2: Admin password and view-only password for amuleweb. View-only user should be disabled by default, hence it need no second password (by default).
Result: only 1 (one) password.

PATH=.:$PATH amule

Phoenix is right, 3 lines script will solve the problem.

Slightly off-topic:

Since I think many people would like an eMule service

For what exactly purpose ? eMule can start without user intervention and it can be controlled through web server, which it have built-in. You probably mean "start without user logged-in", that is case where service matter. However, very few people run Windows without user logged in. While technically possible, I personally never met such in my entire life. Nobody logout from home PC and those who want server are smart enough not to run Windows on it.

[skolnick]

However, I see very few solutions to this issue with too many passwords.

I see another solution. By definition, EC password is "admin password", so we left with only 2: Admin password and view-only password for amuleweb. View-only user should be disabled by default, hence it need no second password (by default).
Result: only 1 (one) password.

It's the solution 3 I posted before. But I do like that solution. It's simple, and efficient.

Regards.

[phoenix]

PATH=.:$PATH amule

Phoenix is right, 3 lines script will solve the problem.

Hum? It's a single line, type it just like that at the command prompt. Ok, maybe what you folks want is:
youruser@yourmachine$ PATH=/path/to/amule/executables:$PATH amule<ENTER>

Cheers!