[Spread-users] Limitation for high availability systems

[Pedro Melo CUNHA]

Hi,

Well, maybe all we need is a SIGHUP kind of thing: use rsync or scp to 
distribute the files (or even spread itself after the first setup), and 
then  make SIGHUP reread the config file without the need to restart...

Best regards,

--On 27 de Maio de 2003 8:24 +1000 Joshua Goodall <joshua at roughtrade.net> 
wrote:

> On Mon, May 26, 2003 at 02:43:21PM +0000, . zist wrote:
>> What modifications would be necessary ?
>
> I don't know if I'm overcomplicating the issue or not, but with a
> dynamic configuration, you create the need for a config
> directory service so that subsequent new members both receive
> a correct configuration and get themselves consistently and
> atomically accepted into a new configuration by existing members.
>
> Of course, Spread itself is an ideal tool for building such a
> service, so there's a chicken-and-egg bootstrap issue there.
>
> You also create a need for an appropriate "floor access" protocol
> so that the credential is something other than than the server's
> public IP address.
>
>> If it's not planned or easily done by someone not familiar with the
>> internal spread
>> architecture, would there be some workaround ?
>
> You could populate your spread.conf files with a whole stack of
> not-yet-existing hosts.
>
> J
>
>
> --
> Joshua Goodall                                      "tea makes itself"
> joshua at roughtrade.net                                       - Ana Susanj
>
> _______________________________________________
> Spread-users mailing list
> Spread-users at lists.spread.org
> http://lists.spread.org/mailman/listinfo/spread-users



--
Pedro Melo Cunha - <melo at isp.novis.pt>
Novis Telecom, S.A. - Dir. Rede - ISP <http://www.novis.pt/>
Edifício Novis - Estrada da Outurela, 118 - 2795-606 Carnaxide
tel: +351 21 0104340 - fax: +351 21 0104301