Closed alexdante closed 12 years ago
Are you using ZEO? sauna.reload supports only development mode in non-ZEO clustered mode. We should add a warning of unsupported configuration.
Ah, of course, that does make sense. And all of the doc examples do show it starting a single instance. But yes, a warning would be nice :) This is week 2 of Plone for me, so I'm not yet always aware of what I need to be aware of.
Thanks for the quick response, too, much appreciated.
On Thu, Nov 10, 2011 at 7:11 PM, Mikko Ohtamaa < reply@reply.github.com>wrote:
Are you using ZEO? sauna.reload supports only development mode in non-ZEO clustered mode. We should add a warning of unsupported configuration.
Reply to this email directly or view it on GitHub: https://github.com/collective/sauna.reload/issues/1#issuecomment-2693038
Thanks for reporting that. I think, we should keep this issue open, until we have a warning about trying to use sauna.reload with ZEO.
(Even better would be to make it work with ZEO. Actually, it should be even easier than making it work with ZODB, but the current codebase would need some refactoring before we can try it.)
I'm afraid that we can support ZEO-client only on Plone 4.1 and later, because only ZODB 3.10. supports forked processes.
I'm running Plone 4.1.2 on Centos 5.6. Using the version of sauna.reload currently in the repo, and following the setup instructions provided, I get these sauna.reload errors during start up:
At this point it hangs until killed.