I have determined one cause of the problem. If there are no ports available
in your range, torrentflux *always* fails in this way.
However, it still *sometimes* fails in this way even if there are ports
available.
So it may actually be three different bugs that need to be fixed:
* The queue manager should deal more gracefully with torrent deaths
so that the manager doesn't get confused
* Need to figure out why some torrents take a few tries to start up
successfully, even when there are ports available...
* The queue manager should not start a torrent if the number of
active torrents is equal or greater to the number of ports
available. What would be *really* slick here is some sort of
useful warning message. And if there was a warning message on
"Admin -> Settings" and/or "Admin -> Queue" if the number of
torrents setting is in conflict with the maximum number of ports
that torrentflux can use.
I'll let Cameron decide if we should split that into multiple bugs or not...
each one does sound like a different piece of work to me tho.
- Tyler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
