Re: [Bug-gnubg] Multiprocessing queries

[Olivier Baur]

Le mercredi, 4 juin 2003, à 16:51 Europe/Paris, Ian Shaw a écrit :

> Will the "master" be able to tell when new "slaves" are available? I 
> am likely to be able to start a rollout, then later set up more 
> processors when my colleagues go home.
> Will it cope with slaves being switched off mid-operation? My 
> colleagues are happy for me to use their PCs on the understanding that 
> they are free to interrupt GnuBg without warning me.

I've added a "slave availability notification" mechanism; I've expanded 
the "pu slave" command to:

pu slave (<ip-address> | <hostname> | *) [:<tcp-port>]

So, starting a slave with the "pu slave master.gnu.org:100" will make 
it notify its availability to master.gnu.org on port 100; "pu slave 
*:200" will make the slave notify its availability to all gnubg masters 
on the local IP network, on port 200 (IP broadcast); notifications are 
sent every 10 secs.

As soon as a master receives an availability notification from a slave, 
it tries to add it as remote processing unit. This can happen even 
while a rollout is already in progress.

This will also help automatically (re)connecting all available slaves 
when you (re)launch the master gnubg.

Changes commited to CVS branch-muti.


-- Olivier