I'm no real expert on eAccelerator sadly, so I'm not sure if this would solve the rare case. It may even be a bug with eAccel but I can't be sure on that. If you change the setting and it doesn't occur again then I'd say it's worked, but it might be a cat and mouse game with trial and error unfortunately.

Hi Deceptor,

Good to see you back! :)

Really, really looking forward to seeing this picked back up again!

I'd set it to "shm_only", once you determine the optimal size of shared memory so all scripts and cached keys fit in it. I'd start with 96M, and then watch the shared memory utilization in the eAccelerator control panel.

It happend again after submitting the changes to a usergroup. And if I remember correctly, I did the same when it happend the last time!

vB Optimise doesn't directly tie in with usergroups anywhere. The only cache it will potentially handle is Phrases (if you have Phrase Cache on and haven't disabled phrase cache in the ACP), and also handle custom datastore items. Nothing is actually "set" on this page unless those phrases/datastore items aren't already cached.

If you change the usergroup all the time will the error come up every time, or just some of the times? Also try removing the affected PHP line or comment it out and see if it rectifies the issue, as said before the function isn't required.

Good to see you back Deceptor. :)

Is this mod usable for bigger forums, with 500.000 visitors per day? Or is there a turning point somewhere when the traffic is going up further?

Nothing is storing in forum/vboptimise, any idea why?

This is my best mod

most of options work but when I enable vB_Datastore_Filecache and the vB Optimise: Custom Datastore Cache, I got the following error in ACP :