On Thu, 07 Apr 2005, Ken Murchison wrote:
> Would one of you please bugzilla this with the patch below and any
> others that you might have, so Derrick and I won't forget about it?
Will do.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness
Henrique de Moraes Holschuh wrote:
On Thu, 07 Apr 2005, Jules Agee wrote:
Henrique de Moraes Holschuh wrote:
I remember squashing a bug on Debian's 2.1 master code that caused it not
to
process *all* available messages at every interaction (instead, it
processed
only one). This caused messages t
Henrique de Moraes Holschuh wrote:
On Thu, 07 Apr 2005, Jules Agee wrote:
Wow, I'm surprised this hasn't been fixed upstream yet... I had this
problem about a year ago.
That was probably my fault. After your report, and your heads up that
master was processing only one message per interaction, I
On Thu, 07 Apr 2005, Jules Agee wrote:
> Wow, I'm surprised this hasn't been fixed upstream yet... I had this
> problem about a year ago.
That was probably my fault. After your report, and your heads up that
master was processing only one message per interaction, I did a fast
spot-look on the 2.
On Thu, 07 Apr 2005, Jules Agee wrote:
> Henrique de Moraes Holschuh wrote:
> >I remember squashing a bug on Debian's 2.1 master code that caused it not
> >to
> >process *all* available messages at every interaction (instead, it
> >processed
> >only one). This caused messages to pile up in busy
Henrique de Moraes Holschuh wrote:
I remember squashing a bug on Debian's 2.1 master code that caused it not to
process *all* available messages at every interaction (instead, it processed
only one). This caused messages to pile up in busy sites and triggered the
above issues. As I said, I think
On Thu, 07 Apr 2005, Wolfgang Powisch wrote:
> What should be the expected behaviour when reaching the maxchilds limit.
No more children are spawned, with a possible off-by-one error (i.e. you
could end up with maxchilds+1 children, but that's it).
> What's the reason for the negative worker numb
Wow, I'm surprised this hasn't been fixed upstream yet... I had this
problem about a year ago.
The master process runs in a loop, checking it's communication pipes
with all the different types of child processes it spawns, keeping track
of the child processes, and distributing work to them. The
