Jason,
Yes, my patch is the most basic kind of work around. I looked at the apr
code and saw that the code implied that EAGAIN was gmond's
responsibility. I don't understand socket buffers or 0_NONBLOCK so I am
no help there.
I do not know why it is happening. My best guess is there is some
Hi Ian,
Your bug report & patch is basically to work around EAGAIN returned from
socket write calls, correct? EAGAIN is returned basically when the
socket is set to O_NONBLOCK and you have attempted a read/write on the
socket when it is not ready for that operation. The error simply means
try ag
Richard,
could you try to confirm the patch? I would then commit it for 3.0.3
Cheers
Martin
PS: Deep voice from the off " You are alone". Sorry, couldn't resist
:-)
--- Ian Cunningham <[EMAIL PROTECTED]> wrote:
> Richard,
>
> Please see the following bug. I have attach a patch to the bug that
Richard,
Please see the following bug. I have attach a patch to the bug that
seems to work for me.
http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=50
Thanks,
Ian
[EMAIL PROTECTED] wrote:
All,
I just know that no-one else is doing this, but
I updated the windows gmond wi
