Re: [Tipc-discussion] tipc-config is here

[Jon M. <jon...@er...>]

Regards /jon

hek...@ya... wrote:

>Hi Jon,
>
>That is so cool !
>
>I've been waiting for this for a long time. So now we can
>simply "insmod tipc.o" and later on application can invoke
>"tipc-config" (or some IOCTLs ?) to dynamically change
>the node address ? Just want to make sure that after the
>node address has been set by "tipc-config" it can still
>be changed later by "tipc-config" for any time, right ? 
>
Yes, you can change the address at any time. The only limitation
now is that when you do that TIPC "forgets" about the activated
interfaces, so they will have to be enabled again. This is relatively
easy to fix with a patch: let tipc-config read the enabled bearers (a
string), keep the string on the stack, and re-apply it automatically
on TIPC once the address has been changed. But I had to draw the line
somewhere... (You are welcome to fix this, of course)

>
>I'm thinking of a scenario where a cluster is formed
>dynamically and the node address of an old node can be
>changed to avoid conflict with a newly joined "node".
>
>A side issue is that I found latest CVS has only linux-2.6
>support. Is linux-2.4 support planned to be dropped ?
>Anyway I've ported it to linux-2.4 since I have to use 2.4
>for a while.
>
Yes, the 2.4 support has been dropped, since in involves too
much extra work to keep it alive. We still try to keep all
environment dependencies isolated to a few files, though,
so it is a doable task to do this, if you really need it.

>
>Thanks
>
>Kevin
>
>
>--- Jon Maloy <jon...@er...> wrote:
>  
>
>>Hi all,
>>I have now checked in my new code for dynamic configuration of TIPC.
>>There are more changes than I really appreciate in one single delivery,
>>but it seems to work fairly well so far, and I think it was necessary to 
>>have
>>it done.
>>
>>Major changes:
>>
>>1: No module parameters anymore, -everything must be done via
>>   the new user-land tool "tipc-config" that comes with the package.
>>2: TIPC can be executed in single-node mode without any initial
>>    configuration at all. It will use the special node address <0.0.0>
>>    for single-node use, but this must be set to a real address before
>>     running in network mode.
>>3: A few bugs, primarily related to manager.c, but also to routing
>>    of named messages were fixed.
>>
>>tipc-config is far from being perfect yet, and can certainly be improved
>>both regarding readability and robustness, but it works well for the
>>basic cases, such as setting own node address and enabling/disabling 
>>interfaces.
>>Even the other commands have been tested,and work under normal
>>cirumstances.
>>Have a look at the command interface, -I have tried to make it as
>>comprehensible as possible, but I am very open for improvement
>>suggestions.
>>
>>Enjoy(?) /Jon
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: GNOME Foundation
>>Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
>>GNOME Users and Developers European Conference, 28-30th June in Norway
>>http://2004/guadec.org
>>_______________________________________________
>>TIPC-discussion mailing list
>>TIP...@li...
>>https://lists.sourceforge.net/lists/listinfo/tipc-discussion
>>    
>>