Dan, I remember reading that caveat. But, I'd like to know more: Why doesn't having DISTCC_DIR on NFS work well? Are there known problems with file locking and NFS? Other reasons? Problems that I could fix with some work?
I'm not giving up so easily... :-) Vic --- Daniel Kegel <[EMAIL PROTECTED]> wrote: > Victor Norman wrote: > > --- Daniel Kegel <[EMAIL PROTECTED]> wrote: > > > >>I don't think you should be sharing a .distcc directory between > >>multiple users. It's not a common configuration, and there are > >>sure to be problems. > > > > Does "the community" agree? I thought this was the recommended setup. > > http://distcc.samba.org/faq.html#monitor-nfs says > "Having DISTCC_DIR on NFS doesn't work well at the moment. > Please set DISTCC_DIR to a local directory instead." > > > If I don't share a common .distcc directory then how do I solve my > worst-case > > scenario: 15 developers suddenly have to compile the entire tree. They all > put > > only the best hosts into their host files (because, after all, they each > want a > > really fast compile), and they all start up their compilation. The result > is a > > bunch of blocked distcc tcp connects to machines with long tcp "listen" > queues, > > and ultimately, very slow compiles... > > Easy. Give up on the idea of having fast and slow machines in the cluster. > Toss out all the slow ones. Treat all the remaining machines as identical. > Randomization then does the trick for you. > - Dan > __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/distcc
