On Thursday 12 February 2004 08:26, Dario Lopez-Kästen wrote:
> Dieter Maurer wrote:
> > Zope itself does not fork (unless you use "system", "popen" or things
> > like that; in these cases, you do not want to bind the children to the
> > same processor).
>
> Well, I had that impression as well, but here is the output of ps on my
> machines (edited for cruft-removal):
>
> UID  PID   PPID  C STIME TIME CMD

> zope 32538 14379 0 Feb09 00:02:32 python2.1 z2.py -X -w NNNN
> zope 32539 32538 0 Feb09 00:00:00 python2.1 z2.py -X -w NNNN
> zope 32541 32539 0 Feb09 00:00:09 python2.1 z2.py -X -w NNNN
> zope 32542 32539 0 Feb09 00:00:11 python2.1 z2.py -X -w NNNN
> zope 32543 32539 0 Feb09 00:01:52 python2.1 z2.py -X -w NNNN
> zope 32544 32539 0 Feb09 00:01:41 python2.1 z2.py -X -w NNNN
>
> that is more than 2 processes for a single instance...

one of them is the supervisor process that restarts the main zope process if 
it crashes.

the others are all threads of one process. one main medusa thread, and 4 
publisher threads.

-- 
Toby Dickenson


_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to