Registered Member
|
I'm runnin Ktorrent 3.2. I did check the changlog for 3.2.1, but didn't see the error mentioned and haven't tried the newer version yet. In any event, any time I get the following error, Ktorrent crashes.
xxxx has been stopped with the following error: Cannot open /media/oneofmyntfsdrives: Too many open files where xxxx is the filename and oneofmyntfsdrives is an external usb NTFS drive. I've been getting this error a LOT. |
Moderator
|
|
Registered Member
|
It's not error in kTorrent. It's error in Linux configuration. Driver-independent error. Just google this words and you will find answer on your problem because I don't remember right answer.
There is system constant which limit amount of active connections to files. You will rise value of this constant. I had this problem on Ubuntu 8.10 but quickly fixed it. George I propose to add some local help-files and write here about of common bugs. When one of these bugs appear -- kTorrent will automatically open window with description of this bug. Also you can try to add button "more..." with description to popup text or add action on click on error icon. Common errors like this must have some local descriptions with advice "how to resolve this problem". User should understand roots of problem. Maybe he just allow too much active connections, maybe system limit is too low. Also you can add check for max possible connections and forbid adding more connections then system can handle with some short description near about this limit.
What isn`t remembered never happened. Memory is merely a record. You just need to rewrite that record.
|
Registered Member
|
|
Registered Member
|
|
Registered Member
|
Settings -> Configure KTorent... -> Network and look for "Global connection limit".
Try to do next: sudo nano /etc/sysctl.conf Search for fs.file-max and set high value (e.g., 200000). If there is no fs.file-max them add it. fs.file-max = 200000 Now reboot your PC. Also you can try next command: sudo ulimit -n 102400 But as I know you need to perform this command on each reboot. So, you need to add this command into init.d script or something similar.
What isn`t remembered never happened. Memory is merely a record. You just need to rewrite that record.
|
Registered Member
|
|
Registered Member
|
|
Registered Member
|
Aarrgh!
I completely forgot about proper way... I just installed fresh 9.04 and found proper fix again. 1. Remove fs.file-max. Default value is 300000+ and there is no reason to change it. At least check it with this command: cat /proc/sys/fs/file-max 2. Open file /etc/security/limits.conf Add there: * soft nolimit 300000 * hard nolimit 300100 3. Reboot. After reboot use command ulimit -n to check ulimit value. After these changes this error was fixed for me.
What isn`t remembered never happened. Memory is merely a record. You just need to rewrite that record.
|
Registered users: bartoloni, Bing [Bot], Evergrowing, Google [Bot], ourcraft