[omniORB] Multiple Interface Selection and omniNames

[Michael]

Wernke zur Borg wrote:
>> -----Original Message-----
>> Sent: 06 December 2007 13:12
>> Subject: Re: [omniORB] Multiple Interface Selection and omniNames
>>
>> On Thursday 6 December, "Wernke zur Borg" wrote:
>>
>>>> "ignoreport" is the key
>>>> ... 
>>>>
>>>> Christian Hansen wrote:
>>>>> I would like to know how to configure omniNames to 
>> properly run on a
>>>>> machine with 2+ network interfaces.
>>>>> ...
>>> I am not sure why -ignoreport should be required to get the desired
>>> behaviour. To my understanding -ORBendPoint should be 
>> sufficient. Why
>>> would the additional listening on the default port do any harm?
>> Without the -ignoreport, omniNames uses the port 
>> specification from the
>> command line or omniNames redo log to add its own 
>> -ORBendPoint argument
>> to the command line. It adds it at the start of the arguments, so it
>> takes precedence over the one you add yourself. By default, only the
>> first endpoint is published in IORs, meaning the one that 
>> gets published
>> is the wrong one.
>>
> 
> I was under the wrong impression that publishing IORs is not an issue
> for omniNames because it only publishes what has been stored by binding
> clients. But taking a closer look, of course it publishes its own
> NamingContexts, therefore it does make sense. 
> 
Of course it does :) Maybe this should be put in an FAQ someday, because almost everybody
in Christian's situation struggles with it at least once...

> Thanks for the clarification!
> 
> Wernke
> 
> _______________________________________________
> omniORB-list mailing list
> omniORB-list at omniorb-support.com
> http://www.omniorb-support.com/mailman/listinfo/omniorb-list