RE: [Zope] RE: No Access file found.
-----Original Message----- From: Chris Larson [mailto:clarson@changeling.com] Sent: Tuesday, April 06, 1999 2:32 PM To: Zope Mailing List; Zope Dev List Subject: [Zope] RE: No Access file found.
Anyone? Anyone? Bueller?
OK. Allow me to clarify. Is there any way to redirect the path for the 'access' path when it should be somewhere other than INSTANCE_HOME? Say, for example, I have multiple instances of Zope databases, with one Zope install, and I want to use a single superuser, or access file. Not what Im' doing, but closer to a mebbe-real-world use. As far as I can tell, Zope wants 'access' located at '../INSTANCE_HOME'. Any ideas? Or am I just wrong (And/Or, that is).
'fraid to tell ya that INSTANCE_HOME is hard wired into the code. We're not likely to change that lest we want to get the 'evil eye of Jim'. But seriously, it is a pretty good idea to have something like this in one place, for us at least, not you. I cannot therefore recommend that you modify your Zope. I also cannot recommend that you would modify it in lib/python/AccessControl/User.py in the Super class around line 270 or so. -Michel
Or any ideas for getting around NFS problems without putting '/var' in /tmp?
Thanks,
Chris
OK. After finally getting my ISP to migrate me to a server with a current Python, I once again leap into the fray. I've placed my 'var/' into '/tmp/', to get around NFS, and updated my instance home to /tmp. Now I have a shiny new problem to play with. Zope can't see 'access'. Is the path to access assumed from INSTANCE HOME, or is there some place I can specify it? (I'd kinda rather avoid putting it in /tmp, ya know?). And before ya ask, yes there _is_ an access file in /---my-path---/cgi-bin/Zope-1.10.2-src/, and it does contain a "superuser:" style entry. I've included the traceback, and my Zope.cgi below.
Any help would be much appreciated.
Chris
PS Any comments on using '/tmp' to contain 'var/' as an NFS bypass? '/tmp' is not mounted via NFS.
The traceback ----------- Sorry, a SERIOUS APPLICATION ERROR occurred.<p> <!-- Traceback (innermost last): File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/ZPublisher/ Publish.py, line 877, in publish_module File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/ZPublisher/ Publish.py, line 325, in publish File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/ZPublisher/ Publish.py, line 616, in get_module_info File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/Main.py, line 93, in ? File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/OFS/Applica tion.py, line 96, in ? File /---my-path---/cgi-bin/Zope-1.10.2-src/lib/python/AccessContr ol/User.py, line 273, in ? ImportError: ('InstallError', 'No access file found - see INSTALL.txt')
-->
My 'Zope.cgi' ----------- #!/---my-path---/cgi-bin/Zope-1.10.2-src/pcgi/pcgi-wrapper PCGI_NAME=Main PCGI_MODULE_PATH=/---my-path---/cgi-bin/Zope-1.10.2-src/lib/p ython/Main.py PCGI_PUBLISHER=/---my-path---/cgi-bin/Zope-1.10.2-src/pcgi/pc gi_publisher.py PCGI_EXE=/usr/bin/python PCGI_SOCKET_FILE=/tmp/var/pcgi.soc PCGI_PID_FILE=/tmp/var/pcgi.pid PCGI_ERROR_LOG=/tmp/var/pcgi.log PCGI_DISPLAY_ERRORS=1 BOBO_REALM=Zope BOBO_DEBUG_MODE=1 INSTANCE_HOME=/tmp
_______________________________________________ Zope maillist - Zope@zope.org http://www.zope.org/mailman/listinfo/zope
(For developer-specific issues, use the companion list, zope-dev@zope.org - http://www.zope.org/mailman/listinfo/zope-dev )
Anyone? Anyone? Bueller?
OK. Allow me to clarify. Is there any way to redirect the path for the 'access' path when it should be somewhere other than INSTANCE_HOME? Say, for example, I have multiple instances of Zope databases, with one Zope install, and I want to use a single superuser, or access file. Not what Im' doing, but closer to a mebbe-real-world use. As far as I can tell, Zope wants 'access' located at '../INSTANCE_HOME'. Any ideas? Or am I just wrong (And/Or, that is).
'fraid to tell ya that INSTANCE_HOME is hard wired into the code. We're not likely to change that lest we want to get the 'evil eye of Jim'. But seriously, it is a pretty good idea to have something like this in one place, for us at least, not you.
I cannot therefore recommend that you modify your Zope. I also cannot recommend that you would modify it in lib/python/AccessControl/User.py in the Super class around line 270 or so.
I've been meaning to bug you guys (DC) about this. Some how, and I'm not really sure how it happened, maybe it was hard drive glitch or something like that caused a line in _my_ lib/python/AccessControl/User.py to change from f=open('%s/access' % INSTANCE_HOME, 'r') to f=open('%s/access' % SOFTWARE_HOME, 'r') and ever since that happened I've been able to manage multiple instances of zope, each with their own database, with one superuser account. Oh and I belived the access file moved to zope/lib/python as well, must be related to that same hard drive glitch I was talking about. It was freaky, but turned out to be really useful if you know what I mean. --------------------------------------------------- - Scott Robertson Phone: 714.972.2299 - - CodeIt Computing Fax: 714.972.2399 - - http://codeit.com - ---------------------------------------------------
participants (2)
-
Michel Pelletier -
Scott Robertson