I'm looking at what it takes to deploy distcc in
large organizations that have multiple sites
(e.g. a Los Angeles office and a New York office)
with all workstations configured identically,
but with different compile clusters for each site.
You can't put the hosts list in /etc/distcc/hosts, because
each of the sites needs a different host list.

Possible solution: assuming the sites are
distinguishable by looking at the DNS domain,
have distcc look in /etc/distcc/$dnsdomain/hosts
for the hosts file.

Here's a proof-of-concept patch, including doc,
that enables this feature:
  http://kegel.com/distcc-domain.patch

Comments, anyone?  Seem useful to any other large sites out there?

(Minor complication:
It seems the recommended way to retrieve the DNS domain
is by calling gethostname(), then gethostbyname($hostname),
then scanning forward past the first dot.
distcc already calls gethostbyname() once, so it
relies on DNS working well.  How bad is it to have
it call gethostbyname() a second time?
Possibly bad enough that this behavior should be off
by default, and enabled at configure time.)
- Dan

--
Trying to get a job as a c++ developer?  See 
http://kegel.com/academy/getting-hired.html
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc

Reply via email to