i'm using amuled, amuleweb and amulecmd from CVS 20050707 and noticed a strange behavior of amulecmd. When i use the command SetUpBWLimit amulecmd always resets the amule.conf values Reconnect and Autoconnect to zero. Probably too when SetDownBWLimit is used but didn't test that but i guess it could happen every time amulecmd writes into amule.conf.
Yay, boolean bug again... I'll check it.
Another strange thing is that i dont need a password for amulecmd and amuleweb anymore.
All remote applications (amulecmd, amuleweb, amulegui) use the remote.conf file by default. EC password, host, port, language, etc are stored in it.
In my amule.conf i have defined passwords for the values Password and PasswordLow. Switching UseLowRightsUser from 0 to 1 doesn't change anything.
These settings are for entering the web interface. There is always a "full rights/admin user" and optionally a "low rights/guest user". Guest user can only watch things, cannot make any changes - like cancelling downloads, etc.
It seems like it is possible to launch the webserver in two ways.
Yes, it is. Even more ways. read `man amuleweb` for more information. Basically three ways to start webserver:
[list=1]
- Typing `amuleweb` in the console. It will read configuration from ~/.aMule/remote.conf
- Starting with the -L or --load-settings command-line argument, in which case EC preferences will be read from remote.conf, and after connection webserver preferences will be queried from amule(d). (those that you can set in Preferences->External Connection)
- Letting amule(d) start the webserver, in which case all preferences will be read from amule.conf (to stay consistent with the preferences set in the GUI).
[/list=1]