On 27 Oct 1999 13:40:42 -0700, Karl Anderson wrote: Karl, I think the problem is that I made the change to omit the ZSYSLOG env var in the zserver.sh script for running PCGI+ZServer and you are running the ZServer-standalone version, right? (hope, hope) Because it's only been a few hours since my uploads, I've refreshed the RPMs on my site w/o bumping the version. You can just grab the Zope-zserver-* RPM or the source RPM if you want to rebuild. I'm not sure why just running "python z2.py" still fails for you but would like to hear of your results with the new RPMs. Sorry for the hassle. And for those who are running ZServer+PCGI, there is *nothing* in the RPMs that changed other than removing the ZSYSLOG env variable. Don't bother to re-download it all over again. -Jeff Rush
"Jeff Rush" <jrush@timecastle.net> writes:
I've upgraded my systems to Red Hat 6.1 and just this morning put up new RPMs for Zope that fix problems reported to me re RH 6.1. They are Zope-2.0.1-*5*... and you can get them from:
I'm still not able to start the server without setting a ZSYSLOG_SERVER env variable and changing my syslog init script to listen at the port. I'm using redhat release 6.1-1. Are you able to run the server out of the box, and if so, any idea what the difference is with my system?
My zserver.sh (link to zserver_wo_pcgi.sh) still has the 'export ZSYSLOG="anything" line, but I still get the problem if I just run the "python z2.py" line from the command line without the ZSYSLOG_SERVER env var.