Re: [Zope] Why does Zope run multiple instances of z2.py by default?
I'm running Zope2.6.2 on RH9 as well and see the same thing at start up time. I don't know enough about the Zope startup process to explain why they spawn the child but it usually terminates on it's own after the start up process has finished. My assumption is that, being a threaded process, it spawns a child to handle any requests/subprocesses so that it isn't blocked from receiving new requests while current ones are being handled. Lee
From: Tim Edwards <Tim.Edwards@hwe.com.au> To: "'zope@zope.org'" <zope@zope.org> Subject: [Zope] Why does Zope run multiple instances of z2.py by default? Date: Thu, 20 Nov 2003 17:54:30 +1100
Hi,
I was just wondering why Zope runs multiple threads of z2.py by default? For example in my ps listing I have:
zope 18183 1 0 10:25 ? 00:00:00 /home/zope/Zope/bin/python /home/zope/Zope/z2.py -u zope -f - p - zope 18184 18183 0 10:25 ? 00:00:10 /home/zope/Zope/bin/python /home/zope/Zope/z2.py -u zope -f - p -
However one of my colleagues only has a single zope instance appear in his ps listing on his machine. His zope installation still runs fine. We are running Zope on Red Hat Linux 9. Does something like this make a difference?
Thanks
Tim Edwards
Trainee Analyst Programmer Henry Walker Eltin Phone: 02 9887 6327 Fax: 02 9887 2412 Email: tim.edwards@hwe.com.au
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
_________________________________________________________________ Groove on the latest from the hot new rock groups! Get downloads, videos, and more here. http://special.msn.com/entertainment/wiredformusic.armx
On Thu, Nov 20, 2003 at 07:07:46PM +0000, Lee J. McAllister wrote:
My assumption is that, being a threaded process, it spawns a child to handle any requests/subprocesses so that it isn't blocked from receiving new requests while current ones are being handled.
The process forks to form a daemon process and the actual Zope server; the daemon process then can restart the Zope serevr at will (in case it dies or is restarted explicitly). The Zope server itself doesn't fork to deal with requests; it handles those with a pre-allocated thread pool. -- Martijn Pieters | Software Engineer mailto:mj@zope.com | Zope Corporation http://www.zope.com/ | Creators of Zope http://www.zope.org/ ---------------------------------------------
participants (2)
-
Lee J. McAllister -
Martijn Pieters