aMule Forum
English => Multiplatform => Mac OSX => Topic started by: lechatlisse on July 03, 2005, 03:18:39 PM
-
Hi there,
i am a recent and very happy convert to aMule. Thank you so much to the developers for building OS X binaries, this is the sort of thing we need: don't give up !!!
A few questions:
-I have been experiencing the lowID issues posted in another OS X thread that is supposed to relate only to Tiger 10.4.1, where the client is allocated a lowID after some time, and you have to quit and restart to get HighID again.
I have come from the edonkey2000 mac client where you constantly get blacklisted from servers due to bad code in the program. Is this a concern with aMule at all. Would the lowID have anything to do with the client behaving aggresively and being blacklisted from servers... Just a thought, although I presume that it would be listed in the log if that were the case.
-i have a selection of rarer files I like to put on 'release' share mode to give them priority in the uploads and become the 'official' sharer for those files. Does this affect my current downloading, would it affect my speeds as I will not be uploading much of the files I'm currently downloading. Could this hamper my download speed ??
-I plan on running 2 aMule clients on seperate computers on my network with seperate ports assigned to each computer. Will this hinder things in any way, or affect my credits ???
Thanks in advance for your replies ??
-
heho
to 1.
the lowID has only todo with your port 4662 being reachable or not...so nothing with aggressive or something
to 2.
the release mode does not affect your downloads that muhc. it only gets you credits for the people you upload to, this might help later when you want to download again from them a different file...
to 3.
nope, as long as they dont run on the same port no problem. just be sure that your router/modem can handle so many requests and connections otehrwise it might crash
stefanero
-
1. As stefanero said, this problem isn't a problem with servers banning aMule. There's a bug, apparently in Apple's code, which causes aMule to stop accepting the connections that other computers are trying to make at port 4662.
3. Running two mules on one network connection will work fine, but it is somewhat inefficient. First, the two aMules will compete for your bandwidth. To avoid total saturation of your line, you will want to limit each to only a portion of the line. However, there may be times when one isn't using all that it's allowed to, but the other won't be able to "know" that and take advantage of the slack.
Also, you are making inefficient use of the credits you're earning. One of your clients might be trying to download from a source where it has no credits, while your other client has been uploading to that source and has earned many credits.
If you can run all of your downloads from one computer, you will solve these problems and maximize the efficiency of your aMule.