<html><head><style type="text/css"><!-- DIV {margin:0px} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div><br>Hi,<br><br>I'm a spread newbie, so apologies if I'm missing something obvious.<br><br>I'm interested in using spread, initially at least, in some software simply to monitor the interconnectedness of a variable number of systems, possibly at different locations. spread seems like it will do this for me, in a distributed fashion (e.g. a central system won't have to have socket connections open to [or poll] all monitored systems). Let's call the group of systems a 'gang'.<br><br>So, first question is does this seem reasonable, or if not, is there other small footprint software you can recommend?<br><br>Assuming the answer to the above was 'yes' ...<br><br>It's likely that the systems in the 'gang' will grow over time. Now, my understanding is that the spread.conf files must all match &
this is enforced at spread startup time. I was hoping to use spread messages to tell everyone when someone new wanted to join the group, but I'll still need some out of band mechanism (i.e. something thru a socket) to tell the new system the spread.conf.<br><br>However, if any systems are down when the new system joins, they won't get the message about a changing spread.conf & will <br>be unable to rejoin when they come up, as their confs will be out of date. It would seem plausible that if this occurs they grab the spread.conf via the out of band machanism from one of their former contacts - but this seems to be getting a bit messy [e.g. need to make sure their former gang member hasn't switched to a different gang]<br><br>Any suggestions on a better way to manage configuation?<br><br>Thanks,<br>-Brian.<br></div></div></body></html>