On 18-04-2008 09:37:19 +0200, Fabian Groffen wrote:
Hi Matthew, (you found a bug)
I just did an attempt to fix this in CVS stable. I'm not sure but I thought you use "current" at the moment, which means you need to wait for propagation to occur before you can try out my fix. My wannabe fix plugs a hole in code that's called upon each client connection. I'll stresstest merovingian here using a simple bash script and mclient connecting in a loop, but I'd be pleased if you could test it in your development environment which is less artificial.
This indicates Merovingian or Sabaoth leaks filedescriptors. After your 10 days it has reached the limit of maximum open files allowed by your OS. Kudos for me that Merovingian doesn't crash but properly reports this. Bad karma for me that I leak the filedescriptors somewhere, hence the too many opened files.