On 2 Sep 2002, Oscar Esteban <[EMAIL PROTECTED]> wrote: > The objective would be to give some load to each host. [....]
It already does what you described. :-) Check the manual. > *1 - An idea which comes to mind while writing, which is too large to > embed above. I'm not sure about the possible usefulness of storing > preprocessed jobs in the servers, that is, preprocessing more jobs than > the allowed load would permit compiling. E.g.: let's allow two gcc > instances in each host in any given moment, let's have two hosts. The > client can preprocess six source files AND send them to the servers; two > of them (one for each server) will not trigger a compilation until a > running gcc has finished. I can think of this being good as an > optimization in case of a communications bottleneck; if so (working with a > slow link) distcc would not be very useful... That's an interesting idea; I'll add it to the list. -- Martin _______________________________________________ distcc mailing list [EMAIL PROTECTED] http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
