Hi Martin, Why not? Multicast is very usefull in this situation, all the clustered environment are using multicast to join member to the cluster.
Probably is not a good idea to add multicast support directly in distcc (lots of work compared to benefits). But, Simon, I think that you can write for your own use a "back end" utility to find available distcc servers. I'd like to do it too, but I don't have the time now, if I'll code anything I'll shere it with you (and to everybody :-). Martin what do you think? Is it possible (and profittable)? Regards Antenore. 2006/2/6, Martin Pool <[EMAIL PROTECTED]>: > On 2 Feb 2006, Simon B <[EMAIL PROTECTED]> wrote: > > Hi There, > > > > 1st up, many thanks for this excellent utility, it's making my headaches > > not go away, but at least come on a little quicker ;-)) > > > > Have you considered using a multicast address for listening? It could > > be one way of getting around the hassle of having to set distcc hosts..? > > distcc uses tcp connections to carry the requests and responses, and > multicast doesn't work with tcp, only udp. multicast udp could be good > for checking the load of servers or seeing if they have a cached result. > > -- > Martin > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (GNU/Linux) > > iD8DBQFD50KVPGPKP6Cz6IsRAp/pAJ9ii1SlfQQDk19/2HsRRkUS/9wdCwCeKZ6K > cxcOrtuXHDBAVqfupN4xx/8= > =loGS > -----END PGP SIGNATURE----- > > > __ > distcc mailing list http://distcc.samba.org/ > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/distcc > > __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc
