Michael, et al, I personally do not like the idea of putting the --randomize flag in the hosts file. I say, "let the hosts file be the hosts file". Instead, I much prefer that all behavior modifications go on the command-line, or in a "resource configuration" file -- i.e., a dot-rc file, like .distccrc.
Alternatively, we could fold the hosts file and the dot-rc file into one file, with a uniform syntax: hosts: <list of hosts> randomize_hosts: true other_configurable_option: 7 etc: "et cetera" Vic --- "Donohue, Michael" <[EMAIL PROTECTED]> wrote: > Hi, > > I have submitted two patches that add options to the host file. I am > not sure if this is generally an accepted way of configuring things with > distcc. I followed Dan Kegel's lead by looking at his randomized hosts > code, but I also notice that his code hasn't been accepted into the main > distribution. I am now looking at implementing creat-locking, instead > of locking, and I would like to know the right way to make this > configurable, so I can see how it performs. > > > > I prefer the hosts file because the hosts file controls the canonical > name all clients use, and the locking mechanism is part of that. > > > > Michael > > > > > __ > distcc mailing list http://distcc.samba.org/ > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/distcc __________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc