Linux tarball didn't include pcgi in the path specified (it was in Zope/pcgi/bin instead of Zope/pcgi). When I compiled pcgi all was fine, but it didn't work. Changing the reference in Zope.cgi to the /bin path fixed that. Sanity Checker says: sanity checker spits this out: module not found: /home/zope/lib/python/Zope If I cahnge the module (PCGI_PATH) to look like v. 1.0 (and to match the PCGI Docs) /home/zope/lib/python/Main.py the sanity checker says: error attempting: 'from cgi_module_publisher import publish_module' The real problem is that no matter how I try to access the web page I get: (102) failure during connect The pcgi.log says Mon Aug 9 16:33:14 1999 pcgi-wrapper: Connection refused (102) failure during connect No errors show up in the Apache logs. At 4:35 PM -0400 8/9/99, Reed Wade wrote:
<x-flowed> I did run into a problem with the control panel for the /Zope object not working right with the recommended rewrite rule.
conf/http.conf contains--
RewriteEngine on RewriteCond %{HTTP:Authorization} ^(.*) RewriteRule ^/Zope(.*) /opt/gnn/zope/servers/10001/apache/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
# the original (and more correct) rule was #RewriteRule ^/Zope/(.*) /opt/gnn/zope/servers/10001/apache/cgi-bin/Zope.cgi/$1 [e=HTTP_CGI_AUTHORIZATION:%1,t=application/x-httpd-cgi,l]
cgi-bin/Zope.cgi looks like --
[...]
</x-flowed>
# # # _____________________________________________ Joshua Brauer Box 915 http://www.brauer.org Fort Collins, CO 80522 Fax: (419) 793-4120 _____________________________________________ In flying I have learned that carelessness and overconfidence are usually far more dangerous than deliberately accepted risks. -- Wilbur Wright in a letter to his father, September 1900 _____________________________________________________