"Force Resume" ? How do you know it's being forced ?
 

Sometimes...I can set off a download, it'll download part way, and then it stops.....I do a rescan of my key words.....and notice that the same host that had the file before....is still present. Now, am I misinterpreting, that once you have a download slot, it's yours ? At least until either the host signs off ? Or can your slot get preempted by someone else ?

I've looked at uploads from my computer going outward....and I see whatever's going out, STAY going to whomever got that a particular slot....until the process is done......

I've tried using "Force Resume", but it seems as though that's a featureless button, because I have yet to get that thing to do a single thing for me.

What Gives....


MindSlip

Force Resume Button: If a Download is in the state of 'couldn't download' it will resume -- try to reconnect to a/the host and try to resume.
When a DL is at 0kbps it will not help pressing it. if a DL is waiting or retrying it will not help pressing it.
--
a slot can not be claimed by an other noad if in use by another.
how long a slot stays yours depends on the last communication between you and the other noad. if you canceled/killed your DL it will use the slot for someone else. if you had a 0kbps you're still connected.


mahalo

Re: "Force Resume" ? How do you know it's being forced ?
 

Query results show from some hosts even if they don't have any upload slots available. I know Gnucleus has an option to not respond with any results if no upload slots are open, but it's not enabled by default. I'm not sure exactly how other servent packages handle that.