Toby Dickenson wrote:
On Thursday 12 February 2004 08:26, Dario Lopez-Kästen wrote:
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, a
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
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
Dario Lopez-Kästen wrote at 2004-2-11 09:39 +0100:
>I have some trouble doing cpu-afiinity wiht zope. I can affinitise the
>parent process just fine, however, zope forks and the children get
>spread out all over the CPUs.
Zope itself does not fork (unless you use "system", "popen" or things like
Hello,
I hope this is not the wrong list...
I have some trouble doing cpu-afiinity wiht zope. I can affinitise the
parent process just fine, however, zope forks and the children get
spread out all over the CPUs.
I do not yet wish to resort to shell-hacking the ouput of ps -ef, so I
was woderi
