On Tue, 2011-03-15 at 13:28 +0100, Martin Lucina wrote:
> michael.comp...@littleedge.co.uk said:
> > Hi all,
> >
> > Sorry for the long subject name, I'm going to try and keep this short
> > because it gives me a headache, hehe.
> >
> > This is some what connected to the following from the mailin
michael.comp...@littleedge.co.uk said:
> Hi all,
>
> Sorry for the long subject name, I'm going to try and keep this short
> because it gives me a headache, hehe.
>
> This is some what connected to the following from the mailing list:
> http://lists.zeromq.org/pipermail/zeromq-dev/2010-September/
Disabling the GC in that way is unfortunately not possible.
On Thu, 2011-03-10 at 21:17 +0100, Pieter Hintjens wrote:
> On Thu, Mar 10, 2011 at 8:28 PM, Michael Compton
> wrote:
>
> > I am open for correction on any of this and suggestions on how best to
> > deal with the situation...
>
> So t
On Thu, Mar 10, 2011 at 8:28 PM, Michael Compton
wrote:
> I am open for correction on any of this and suggestions on how best to
> deal with the situation...
So the conclusion is that Linux poll() always returns EINTR if there's
a user signal?
Perhaps it's possible to disable the GC at specific
Hi all,
Sorry for the long subject name, I'm going to try and keep this short
because it gives me a headache, hehe.
This is some what connected to the following from the mailing list:
http://lists.zeromq.org/pipermail/zeromq-dev/2010-September/005822.html
While developing the clrzmq2 and using
