I don't go for BS like 'it was never designed to work this way'. Software is meant to be taken wherever someone would dare take it.
If you just forget the 'slow link', simply consider a 'slow machine' on a fast connection then. Out of a long build it will still be helpful to get a few object files built with it. But in many situations all the other hosts will be done and waiting for that last object before a link can begin. Same situation. Would be nice at this point to ask one of the faster machines to do the job. TTimo On 25 Aug 2003 07:29:38 +1000 Ben Elliston <[EMAIL PROTECTED]> wrote: > Timothee Besset <[EMAIL PROTECTED]> writes: > > > - Several compiles start, mostly on the local LAN, and one goes to a > > remote machine. > > - LAN stuff is done. Build system waits for linking for remote > > machine. > > - remote takes a long time. not specifically compile, but transfer > > back and forth. > > distcc was never designed to work this way. You need low latency > connections to your slave machines. > > Ben > > > __ > distcc mailing list http://distcc.samba.org/ > To unsubscribe or change options: > http://lists.samba.org/cgi-bin/mailman/listinfo/distcc > __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
