[omniORB] omniNames on Solaris 2.6 with 2 IP addresses
Brendan Cully
brendan@kublai.com
Wed, 12 Aug 1998 20:59:15 -0400
Ah yes, that did the trick. The socket was never being set to blocking
again, on account of a misplaced brace, so recv was getting EAGAIN errors.
How about that, looking at the source code!
Thanks,
Brendan
On Wed, Aug 12, 1998 at 10:56:36AM +0100, Sai-Lai Lo wrote:
> You did say April snapshot! Yes, there is a bug introduced into that
> snapshot which affects only Solaris 2.x. I forgot about it until now.
> This was discussed on the mailing list at the end of June.
>
> Should be in the bug page. The patch is in:
>
> http://www.orl.co.uk/omniORB/archives/1998-06/0039.html
>
> Sai-Lai
>
>
> Brendan Cully <brendan@kublai.com> writes:
>
> > Okay, I've tried using this variable. I find that when I try to bind to the
> > primary IP on the machine (corresponding to interface hme0) I get exactly
> > the same errors I got before... but when I bind to the second interface
> > (hme0:1), the example files generate system exceptions (as opposed to
> > the intermittend COMM_FAILURE messages I was getting used to). When I get
> > back to work I'll dig up the exact text of the message, and see whether I
> > can get more details from the exception.
> >
> > Is it just having two IP addresses, or can it be related to Solaris 2.6,
> > which I guess is not an official stable platform...
>
>
> --
> Dr. Sai-Lai Lo | Research Scientist
> |
> E-mail: S.Lo@orl.co.uk | Olivetti & Oracle Research Lab
> | 24a Trumpington Street
> Tel: +44 223 343000 | Cambridge CB2 1QA
> Fax: +44 223 313542 | ENGLAND