aMule Forum
English => Feature requests => Topic started by: gaglia on August 12, 2008, 12:59:20 PM
-
I'd find much more handy to have all the configuration options on a single conf file (i.e.: amule.conf), moreover there are options who seems to be "duplicate" in these two files... i think it makes a lot of confusion, at least to me...
For example, what happens if the template=XXXX line is different in these two files? I thought the one in remote.conf was the template used for the web interface (amuleweb) and the one in amule.conf was the template used for the desktop app... but i found that the amuleweb template doesn't change if the new template isn't specified in amule.conf too. Same issue for the hashed passwords... In sum, wouldn't it be easier to have only amule.conf for EVERY configuration option?
Another question please, can someone explain me what do i have to do to have amuleweb/amule-daemon listen only on a specific IP address in the case i have more than one on a single machine? I'd like, for instance, to have amule-daemon listen ONLY on localhost (127.0.0.1), and amuleweb listen ONLY on two different private IPs (i.e. 192.168.0.2 and 192.168.1.8). The "feature request" here is: is it possible to make a clearer (and working) distinction in the Address lines of amule.conf? Maybe with a little comments to help newbies?
Thank you very much for you work :)
-
amule.conf is used by aMule(d) and by amuleweb, when it is started by aMule.
remote.conf is used by amulecmd, amuleGUI, amuleweb and contain only information related to these programs.
I can't comment on the rest.
-
So if i have only amule-daemon running on a headless server (and amuleweb starting with it) the remote.conf file is not used at all?
-
Yes.