/etc/init.d/zope-2_6_4 stop doesn't really stop zope's server. It should terminate all the python pids zope leaves lying around. Any modifications to zope-config don't appear until zope is stopped manually, zapped if necessary, and restarted. Reproducible: Always Steps to Reproduce: 1.emerge zope 2.echo ZOPE_OPTS='-u zope' >> /etc/conf.d/zope-2_6_4 3./etc/init.d/zope-2_6_4 start 4.wait a bit 5./etc/init.d/zope-2_6_4 stop Actual Results: run top or ps and check out all the little zope python kiddies! run a browser to http://localhost:8080/ <-- zope is still running! To really stop zope I had to kill them by hand. Expected Results: /etc/init.d/zope* stop should terminate zope entirely. ZServer should not run after zope is stopped.
i can't reproduce this. probably i need to say that i use the 2.6.4-r2 ebuilds (currently in bugs.gentoo.org)
This whole thing came about because zope-config --zpasswd was accepting changes without errors, but when I did /etc/init.d/zope* restart, zope wouldn't stop, so I could never log in. Maybe the problem was in zope-config. Anyway, I can't reproduce it now, either, although at the time I was doing it remotely on a server that was also compiling openoffice-ximian, so maybe I just wasn't leaving enough time for zope to kill all the python babies.
if it happens again reopen
