Mark Nipper wrote: >>I will set up a Cherokee backport for Sarge as soon as I finish some >>other packaging-related chores (i.e., I have still not upgraded the >>package to 0.4.26), and will tell you here. > > I'm actually using Apache 2.1 built locally for the time > being on my mirror server until Cherokee stabilizes a bit more. But > if you do package 0.4.26 soon (before 0.4.27 comes out anyway), > please try to apply Alvaro's patch for the symlink bug I reported > both to the Debian BTS and this list. He didn't post the patch to > the list I don't think, but I assume it's in a CVS/SVN tree or some > such someplace. I'm sure he can provide a diff to 0.4.26 if need > be.
Actually, it was just a one line patch; but anyway, I hope we will release 0.4.27 within this week. > I don't recall if I mentioned the problem with certain > threads going wild with the CPU and it may even be related to the > symlink bug. But if you want any more information on that, I can > most likely reproduce the problem with 0.4.26. I had written a > script to check for individual thread CPU usage previously so I > could restart Cherokee when this happened as subsequent requests > (probably the ones handed off to these certain pegged threads) would > just timeout and not return any data. Do you know if that problem occurs only with those broken dirlist requests? I have not detected that problem before, and it does not make sense for me if it only happens on that situation. :-? -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
