7.2 SuSe stock Zope setup
Hay SuSE guys: I reported this a while back. It appears that the zope installation with 7.2 is misconfig'd. Fresh install (again) of apache and zope results in the same behaviour. Zope can be run two ways. With a standalone ZServer on port 8080 or via pcgi and apache:80. Both options are provided for by Yast1. When Zope is started in Yast1 but "not" with PCGI support, the default apache runs on port 80 with no redirection. Yast sets PCGI support to "no" This is the way it is supposed to work. However..:) Using this setup leaves apache functionless, ie: it simply hangs and then reports, (102) Error The resource you requested is temporaily unvailable. Further, the suse localhost docs, are available via the /static/ switch as documented by SuSE. However this behaviour is "supposed" to happen when Yast activates "PCGI Support" _not_when this is set to "no pcgi support" Why apache reports a (102) error is not known. I've repeated this scenario three times befor reporting it the second time to make sure as this is new to me. Possibly its associated with a call to zope.conf (which is used for redirection) (Im only guessing to be helpfull) found in /var/lib/zope Question: How do I use yast to start and stop Zope at boot time "without" PCGI support and have the stock apache and Zope install both functional. One on port 80 and the later on port 8080 as described in the docs. Naturally its possible to intall Zope from source, but Im not used to seeing errors in SuSe......:) If I am doing something incorrect, perhaps others have a solution. Best regards Chris H.
participants (1)
-
Chris Herrnberger