State:
6 torrents in download tab: 2 torrents running, 1 error@too many files open, 3 not started
1 torrent in upload tab: running

Going to files tab on the errored torrent> deselecting some folders> going to another view, i.e. files on another torrent> going back to view on files on errored torrent> alle files are back selected.

This "problem" might have something to do with that 'too many files open error'.
What i'am thinking is:

- Why is this 1024 files open limitation so small?

- Five minutes ago, KTorrent labeled and stopped a second torrent as "error too many files open", so that makes only one torrent downloading(30 files, folder counted also) and one seeding(one file).
This is something to look at IMO, getting a torrent out of business when you're not behind the box is not very usefull.

stoeptegel wrote:State:
6 torrents in download tab: 2 torrents running, 1 error@too many files open, 3 not started
1 torrent in upload tab: running

Going to files tab on the errored torrent> deselecting some folders> going to another view, i.e. files on another torrent> going back to view on files on errored torrent> alle files are back selected.

This "problem" might have something to do with that 'too many files open error'.
What i'am thinking is:

- Why is this 1024 files open limitation so small?

Those are operating system limits, you can change them with ulimit.

- Five minutes ago, KTorrent labeled and stopped a second torrent as "error too many files open", so that makes only one torrent downloading(30 files, folder counted also) and one seeding(one file).
This is something to look at IMO, getting a torrent out of business when you're not behind the box is not very usefull.

The problem is that it is much nicer to keep files open when you are using mmap. If we have to close a file, we have to unmap everything which was mapped into memory from that file.

Seeing that I allready unload inactive chunks, this might not be that difficult, to implement a 'only open a file when it is needed'

This turns out to be a lot easier then expected, we now close cache files which are not needed, and reopen them when they are needed.

This will not prevent you from hitting the limit, but it should only happen in very exceptional situations.

George wrote:Those are operating system limits, you can change them with ulimit.

Yeah i read that in another section on the forum
It was something like $ ulimit -a

When i tried to set the number to 1200 for a test, it said i didn't got the rights to do that, i sudo'ed my way off course but that gave me a respond that ulimit command wasn't found.
So it kind of beatted me out there.

This turns out to be a lot easier then expected, we now close cache files which are not needed, and reopen them when they are needed.

This will not prevent you from hitting the limit, but it should only happen in very exceptional situations.

Usefull to me
This can avoid the problem when the queuemanager is handling and activating the torrents a bit.
Thanks!