I would not share the cache folder of a symfony application. The risk for dead locks is too big, like you have experienced it.
I would do this: - define the cache folder to a local and not shared directory like / tmp/someproject/cache - purge all your caches when you have deployed something (otherwise a webserver may not have a up-to-date cache) Am 28.07.2009 um 17:56 schrieb CaffeineInc: > > do you use a plugin class for handling the session interface, or did > you build your own? > > like sfMySQLiSessionStorage ?? > > On Jul 28, 5:19 pm, Eno <symb...@gmail.com> wrote: >> On Tue, 28 Jul 2009, CaffeineInc wrote: >>> Yeah, we have to share the files over NFS because otherwise we'd >>> have >>> to share the sessions between the servers... and that won't work >>> because the database session plugin was broken for me - it just >>> drops >>> all sessions, and won't cleanup after itself... >> >>> That bug however was a while ago but i've been really afraid to >>> try it >>> since. We get quite a bit of traffic.... >> >> Sharing session files over NFS seems like a bad idea to me. >> >> We run a high traffic site (load-balancers, several web servers, >> several >> image servers, three database servers, etc), and we use MySQL for >> sharing >> sessions. I might add, that this has worked for us since symfony >> 0.6, so >> Im not sure what bugs you're referring to. >> >> Should be a simple case of adding the session table to your database >> servers and then configuring each application server to use it. >> >> -- > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
