zope.conf read-only settings
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7 Setting read-only in the database storage does make a difference (in my configuration, Formulator 1.6.2 throws an exception, but that's not a ZOPE issue). Steven
Steven Hayles wrote:
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7
Not really sure what you're asking? Did you try these and find they made no difference?
Setting read-only in the database storage does make a difference (in my configuration, Formulator 1.6.2 throws an exception, but that's not a ZOPE issue).
Okay, maybe that's 'cos Formulator is trying to write to the zodb? Seriously, not sure what you're asking/explaining... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Fri, 14 Oct 2005, Chris Withers wrote:
Steven Hayles wrote:
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7
Not really sure what you're asking? Did you try these and find they made no difference?
Yes, and I've looked at the code and can't see any way they can make a difference. Wondered whether anyone else knew anything about these directives (old or future functionality?) and whether I was right in thinking they didn't do anything. If they really don't and are never intended to do anything, then they should at least have comments to that effect, and ideally be removed.
Setting read-only in the database storage does make a difference (in my configuration, Formulator 1.6.2 throws an exception, but that's not a ZOPE issue).
Okay, maybe that's 'cos Formulator is trying to write to the zodb?
I think so.
Seriously, not sure what you're asking/explaining...
Just a related observation. Steven
S.Hayles wrote:
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7
Not really sure what you're asking? Did you try these and find they made no difference?
Yes, and I've looked at the code and can't see any way they can make a difference.
Well, the obviously make some difference, or you wouldn't get errors from Formulator ;-)
Wondered whether anyone else knew anything about these directives (old or future functionality?) and whether I was right in thinking they didn't do anything. If they really don't and are never intended to do anything, then they should at least have comments to that effect, and ideally be removed.
The best place to ask is zodb-dev@zope.org...# cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Mon, 17 Oct 2005, Chris Withers wrote:
S.Hayles wrote:
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7
Not really sure what you're asking? Did you try these and find they made no difference?
Yes, and I've looked at the code and can't see any way they can make a difference.
Well, the obviously make some difference, or you wouldn't get errors from Formulator ;-)
In fact, it was setting read only in the storage configuration that caused the Formulator error, not setting zserver-read-only-mode or read-only-database. I'll try asking on the dev list. Thanks Steven
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 S.Hayles wrote:
On Fri, 14 Oct 2005, Chris Withers wrote:
Steven Hayles wrote:
AFAICS the directives zserver-read-only-mode and read-only-database just set the environment value ZOPE_READ_ONLY and no change in ZOPE's operation results. Am I right? This is ZOPE 2.7.7
Not really sure what you're asking? Did you try these and find they made no difference?
Yes, and I've looked at the code and can't see any way they can make a difference.
Wondered whether anyone else knew anything about these directives (old or future functionality?) and whether I was right in thinking they didn't do anything. If they really don't and are never intended to do anything, then they should at least have comments to that effect, and ideally be removed.
Setting the environment variable no longer has any effect, but the presence of the configuration is checked by the code which sets up zservers: if set, those servers to not create / write log or PID files. The environment variable *is* a fossil, whose former effects are now spelled out via configuration directives for the storage itself. We should remove the code which sets the environment variable, and update any docs which pretend that it is still effective. Please file a collector issue for this. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDU5TD+gerLs4ltQ4RAjLCAJwPXEbmEWXBUDJxUsXP7pHVlpoTUQCdEf3c 6WksK6zsqLpeh18+kXUrb/o= =ZaL2 -----END PGP SIGNATURE-----
participants (4)
-
Chris Withers -
S.Hayles -
Steven Hayles -
Tres Seaver