Hello Matthew! >> Talking again about the bug here: It is really hard to find and only >> appears _sometimes_ and when clicking through the backend of Typo3. > This intermittency is very weird, and the application-specificity worries > me too. You're saying that if you put the exact same Apache > configuration in front of a pile of static content, the problem never > asserts itself?
I just searched the error.log's of the ~100 domains running on this particular server. And look, I found one other "no groups file?" error. It happened when someone was trying to take a look into his AWStats statistics. But this was the only error besides the Typo3 related errors the last 2 weeks (mc does not support searching in compressed logfiles ;-) ). There are a lot of secured directories on this server. Mostly Webalizer directories, but also administrative directories for our customers. Maybe coincidence, maybe not. But I was sure that this only happens with Typo3. I was not correct. Regards, Martin
