| 1 |
On Friday 17 December 2010 23:23:10 Jacob Todd wrote: |
| 2 |
> Could you post your distcc config files? |
| 3 |
|
| 4 |
$ extract /etc/conf.d/distccd |
| 5 |
DISTCCD_OPTS="" |
| 6 |
DISTCCD_EXEC="/usr/bin/distccd" |
| 7 |
DISTCCD_PIDFILE="/var/run/distccd/distccd.pid" |
| 8 |
DISTCCD_OPTS="${DISTCCD_OPTS} --port 3632" |
| 9 |
DISTCCD_OPTS="${DISTCCD_OPTS} --log-level critical" |
| 10 |
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.2.0/24" |
| 11 |
DISTCCD_OPTS="${DISTCCD_OPTS} --listen 192.168.2.2" |
| 12 |
DISTCCD_OPTS="${DISTCCD_OPTS} -N 15" |
| 13 |
|
| 14 |
(Extract is just a mini-script to cut out comments.) |
| 15 |
|
| 16 |
$ cat /etc/distcc/hosts |
| 17 |
ostn.ethnet |
| 18 |
|
| 19 |
Ostn is the box that's supposed to do the compilation, but the Atom |
| 20 |
client box just doesn't bother trying distcc. If it had and I had an |
| 21 |
error in my config I'd have got an error message. |
| 22 |
|
| 23 |
$ grep distcc /etc/make.conf |
| 24 |
DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc" |
| 25 |
FEATURES="buildpkg ccache distcc fixpackages parallel-fetch userfetch" |
| 26 |
|
| 27 |
Maybe another of those features is incompatible with distcc. I'd also |
| 28 |
have expected an error message in that case, but I just get a bog- |
| 29 |
standard emerge process running locally. |
| 30 |
|
| 31 |
-- |
| 32 |
Rgds |
| 33 |
Peter. Linux Counter 5290, 1994-04-23. |
Archives