aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: [NOTBUG] 1.2.6: weird permission problems  (Read 2984 times)

DexterF

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 54
[NOTBUG] 1.2.6: weird permission problems
« on: March 10, 2004, 02:49:53 PM »

I keep getting errors like "Too many open files, cannot open logfile", followed by
"Too many open files, cannot write to /PATH/Temp/xxx.part" (lots of these)

After I was told this might be due to the files sitting on vfat I converted the Incoming/Temp partition to xfs to find the error stays the same.

Going back to 1.2.4 solves the problem immediately.
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: [NOTBUG] 1.2.6: weird permission problems
« Reply #1 on: March 10, 2004, 11:13:10 PM »

too many new conn / 5 sec .. ?!?

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: [NOTBUG] 1.2.6: weird permission problems
« Reply #2 on: March 11, 2004, 03:34:20 AM »

seems to be solved by: http://www.cs.wisc.edu/condor/condorg/linux_scalability.html

means.. not an amule prob ;)

greets

bootstrap

  • Guest
Re: [NOTBUG] 1.2.6: weird permission problems
« Reply #3 on: March 11, 2004, 10:40:34 AM »

/me is using 1.2.6 since release and i don't have that kind of problems.
My temp/incoming are mounted on a raid0 with ext3.

What irritates me a little is that you say a downgrade to 1.2.4 solves the problem. Afaik 1.2.4 uses the same files as 1.2.6, so there shoud be no difference at all regarding that issue.
Logged

DexterF

  • Jr. Member
  • **
  • Karma: 0
  • Offline Offline
  • Posts: 54
Re: [NOTBUG] 1.2.6: weird permission problems
« Reply #4 on: March 11, 2004, 01:32:37 PM »

Myup, seems like the proc/ulimit settings solved this issue.
Thanks to deltaHF for pointing out.
Logged