Allo. I just moved from using a slow server running XP Pro SP2 with eMule, to a really nice fast machine (with triple the drive space) running Ubuntu and aMule. So far I must say Linux rocks. This switch over has been a week long project for me, during this time I really haven't had any Mule running untill the past day or two.
I've been having this on going tech support madness with my DSL ISP on my connection going dead for about 30 sec, then coming back to life. This happens often, around 2 to 5 times a day. After doing a bit of trouble shooting and ping pong support calls, I opted to get a new modem and see if that helps.
I set the new modem up before I stoped using eMule last week, since then I've been having no problems with my connection. Last night I added a large number of links into aMule to see how well the speeds are versus eMule (and I must say they're just as good). Problem is my DSL connection dropped 4 times today.
My guess is that the number of connections coming through my modem are flipping it out, that or my ISP is noticing the connections and simply asking my modem to fake a death, wishing that'll kill whatever P2P setup I have going (doesn't work because aMule just hops right back on) and not utilize my bandwidth to the fullest 24/7.
To test this idea out I killed aMule after the 4th disconnect, and haven't been shot down, till I restarted it back up again. I noticed that I initially setup my queue limit to something crazy that mirrored my eMule settings. I dropped the number down to 500, saved my config, and restarted aMule. The problem I'm having is that aMule passes my queue limit, right now it's at about 2600, and still going up. What do I need to do to get aMule to stick to the set limit under amule.conf? Any help on the issue would be awesome, thanks.