On Wed, Nov 07, 2018 at 08:45:01AM +0100, William Lallemand wrote:
> Oh that's funny, the mworker_pipe_register() was supposed to be called
> once per process, that's why I put an abort() there, but that's not the case
> anymore with nbthread.
>
> Thanks Pieter.
>
> Patch attached.
applied, than
On Tue, Nov 06, 2018 at 07:13:26PM +0100, PiBa-NL wrote:
> Hi William,
>
> Something seems to have been broken by below patch series. (when using
> threads.?.)
>
> *** h1 0.0 debug|[ALERT] 309/191142 (6588) : Current worker #1
> (6589) exited with code 134 (Abort trap)
> *** h1 0.0 debu
Hi William,
Something seems to have been broken by below patch series. (when using
threads.?.)
*** h1 0.0 debug|[ALERT] 309/191142 (6588) : Current worker #1
(6589) exited with code 134 (Abort trap)
*** h1 0.0 debug|[ALERT] 309/191142 (6588) : exit-on-failure:
killing every workers w
On Tue, Nov 06, 2018 at 05:37:09PM +0100, William Lallemand wrote:
> Some improvements for the master-worker.
Thanks, whole series merged. I've replaced the warning with a qfprintf()
as we discussed so that it's less scary at boot :-) I think we'd benefit
from having ha_notice(), ha_info() and ha
Some improvements for the master-worker.
5 matches
Mail list logo