On Sat, 2009-10-17 at 15:55 +0200, Alex Schuster wrote: > Michael Sullivan writes: > > > > It's all explained here : http://www.gentoo.org/doc/en/distcc.xml > > > > I read the guide when I first set up distcc, but it didn't provide > > enough detail for me to understand. I have two computers, a slow one > > and a fast one. I would like the fast one to assist the slow one. The > > fast machine's IP is 192.168.1.2, and the slow is 192.168.1.4. On the > > fast one, I'm running /etc/init.d/distccd and it's /etc/conf.d/distccd > > looks like this: > > [...] > > # Logging > > # You can change some logging options here: > > # --log-file FILE > > # --log-level LEVEL [critical,error,warning, notice, info, debug] > > # > > # Leaving --log-file blank will log to syslog > > # example: --log-file /dev/null --log-level warning > > # example: --log-level critical > > > > DISTCCD_OPTS="${DISTCCD_OPTS} --log-level critical" > > Until all is running fine, I suggest setting this to info or debug instead. > > > DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.1.0/24" > > Yup. > > > The slow machine is also running /etc/init.d/distccd. > > That does no harm, but is not necessary unless you also want the slow > machine to help the fast one. > > > Is this right? > > Looks good to me. > > Did you activate distcc on the slow client with 'distcc-config --set-hosts > 192.168.1.2'? This tells that all compilations should be done on the fast > machine. If you like the slow machine to also do some of the work, the > command could look like this: 'distcc-config --set-hosts "192.168.1.2 > 192.168.1.4/1"', meaning that the slow one does one compilation at the time, > while for the fast one there is no limit. > Adjust your MAKEOPTS in /etc/make.conf to something like the total number of > cores plus one. And be sure you have distcc in your FEATURES. > > Emerge something, and watch for "failed to distribute, compiling locally > instead" error messages in the emerge output. If there are none, distcc > seems to work. > And watch syslog on the fast machine, it should look like this (with log- > level set to notice): > > Oct 17 15:30:43 [distccd] (dcc_job_summary) client: 192.168.2.35:38681 > COMPILE_OK exit:0 sig:0 core:0 ret:0 time:1295ms x86_64-pc-linux-gnu-gcc > /var/tmp/ccache/sbc_primit.tmp.tanja.26261.i > > Wonko >
I see those lines in /var/log/messages on the fast machine: carter ~ # grep dcc_job_summary /var/log/* grep: /var/log/mailman: No such file or directory /var/log/messages:Oct 17 09:09:31 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:51319 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27537ms i686-pc-linux-gnu-gcc cmp_si.c /var/log/messages:Oct 17 09:09:32 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:51320 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27637ms i686-pc-linux-gnu-gcc extract.c /var/log/messages:Oct 17 09:09:32 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:51317 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27815ms i686-pc-linux-gnu-gcc agm.c /var/log/messages:Oct 17 09:09:32 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:51318 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:28005ms i686-pc-linux-gnu-gcc add1.c /var/log/messages:Oct 17 09:12:06 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:51323 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:143545ms i686-pc-linux-gnu-gcc dump.c /var/log/messages:Oct 17 09:12:20 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:51324 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:156242ms i686-pc-linux-gnu-gcc mul_ui.c /var/log/messages:Oct 17 09:12:27 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:51322 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:166479ms i686-pc-linux-gnu-gcc set_dfl_prec.c /var/log/messages:Oct 17 09:12:39 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:51321 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:184205ms i686-pc-linux-gnu-gcc print_raw.c /var/log/messages:Oct 17 09:18:40 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:47096 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:352543ms i686-pc-linux-gnu-gcc set_prec.c /var/log/messages:Oct 17 09:18:40 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:47094 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:375964ms i686-pc-linux-gnu-gcc mp_clz_tab.c /var/log/messages:Oct 17 09:18:40 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:47095 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:352688ms i686-pc-linux-gnu-gcc extract.c /var/log/messages:Oct 17 09:18:40 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:47097 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:337705ms i686-pc-linux-gnu-gcc ui_div.c /var/log/messages:Oct 17 09:35:20 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:39724 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:975864ms i686-pc-linux-gnu-gcc cmp_d.c /var/log/messages:Oct 17 09:35:20 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:39727 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:974682ms i686-pc-linux-gnu-gcc log1p.c /var/log/messages:Oct 17 09:35:20 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:39725 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:976914ms i686-pc-linux-gnu-gcc acosh.c /var/log/messages:Oct 17 09:35:21 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:39726 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:977982ms i686-pc-linux-gnu-gcc reldiff.c /var/log/messages:Oct 17 09:36:10 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:42898 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:43534ms i686-pc-linux-gnu-gcc div.c /var/log/messages:Oct 17 09:36:11 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:42900 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:44175ms i686-pc-linux-gnu-gcc uceil_log2.c /var/log/messages:Oct 17 09:36:11 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:42897 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:44844ms i686-pc-linux-gnu-gcc isqrt.c /var/log/messages:Oct 17 09:36:12 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:42899 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:45424ms i686-pc-linux-gnu-gcc const_euler.c /var/log/messages:Oct 17 09:36:35 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54718 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:20762ms i686-pc-linux-gnu-gcc random.c /var/log/messages:Oct 17 09:36:36 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54715 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:20853ms i686-pc-linux-gnu-gcc set_nan.c /var/log/messages:Oct 17 09:36:36 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54716 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:21481ms i686-pc-linux-gnu-gcc const_catalan.c /var/log/messages:Oct 17 09:36:36 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54717 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:20984ms i686-pc-linux-gnu-gcc pow.c /var/log/messages:Oct 17 09:37:07 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54722 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:28767ms i686-pc-linux-gnu-gcc get_d64.c /var/log/messages:Oct 17 09:37:07 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54719 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:30213ms i686-pc-linux-gnu-gcc set_sj.c /var/log/messages:Oct 17 09:37:07 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54721 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:30093ms i686-pc-linux-gnu-gcc csc.c /var/log/messages:Oct 17 09:37:07 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54720 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:30219ms i686-pc-linux-gnu-gcc modf.c /var/log/messages:Oct 17 09:37:47 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54723 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:35877ms i686-pc-linux-gnu-gcc random.c /var/log/messages:Oct 17 09:37:47 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54725 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:35893ms i686-pc-linux-gnu-gcc get_si.c /var/log/messages:Oct 17 09:37:47 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54726 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:35917ms i686-pc-linux-gnu-gcc frac.c /var/log/messages:Oct 17 09:37:48 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54724 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:36585ms i686-pc-linux-gnu-gcc next.c /var/log/messages:Oct 17 09:38:34 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54729 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:42584ms i686-pc-linux-gnu-gcc pow_ui.c /var/log/messages:Oct 17 09:38:34 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54727 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:42610ms i686-pc-linux-gnu-gcc cos.c /var/log/messages:Oct 17 09:38:34 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54730 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:42605ms i686-pc-linux-gnu-gcc dump.c /var/log/messages:Oct 17 09:38:34 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54728 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:42615ms i686-pc-linux-gnu-gcc expm1.c /var/log/messages:Oct 17 09:39:05 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54733 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27589ms i686-pc-linux-gnu-gcc set_nan.c /var/log/messages:Oct 17 09:39:05 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54734 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27286ms i686-pc-linux-gnu-gcc fits_sint.c /var/log/messages:Oct 17 09:39:05 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54732 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27693ms i686-pc-linux-gnu-gcc add1.c /var/log/messages:Oct 17 09:39:05 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54731 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:27754ms i686-pc-linux-gnu-gcc eint.c /var/log/messages:Oct 17 09:45:32 carter distccd[16790]: (dcc_job_summary) client: 192.168.1.4:54736 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:383175ms i686-pc-linux-gnu-gcc reldiff.c /var/log/messages:Oct 17 09:45:32 carter distccd[16792]: (dcc_job_summary) client: 192.168.1.4:54737 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:383184ms i686-pc-linux-gnu-gcc sgn.c /var/log/messages:Oct 17 09:45:32 carter distccd[16778]: (dcc_job_summary) client: 192.168.1.4:54738 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:383367ms i686-pc-linux-gnu-gcc lngamma.c /var/log/messages:Oct 17 09:45:45 carter distccd[16791]: (dcc_job_summary) client: 192.168.1.4:54735 COMPILE_OK exit:0 sig:0 core:0 ret:0 time:396939ms i686-pc-linux-gnu-gcc root.c but I'm still seeing problems on the slow machine: libtool: compile: i686-pc-linux-gnu-gcc -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DTIME_WITH_SYS_TIME=1 -DHAVE_LOCALE_H=1 -DHAVE_WCHAR_H=1 -DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 -DHAVE_STDINT_H=1 -DHAVE_SETLOCALE=1 -DHAVE_GETTIMEOFDAY=1 -DHAVE_LONG_LONG=1 -DHAVE_INTMAX_T=1 -DMPFR_HAVE_FESETROUND=1 -DHAVE_DENORMS=1 -DHAVE_FLOOR=1 -DHAVE_CEIL=1 -DHAVE_LDOUBLE_IEEE_EXT_LITTLE=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ATTRIBUTE_MODE=1 -DHAVE_ALLOCA_H=1 -I. -O2 -march=i686 -ffloat-store -MT eint.lo -MD -MP -MF .deps/eint.Tpo -c eint.c -o eint.o >/dev/null 2>&1 make[1]: *** [exp3.lo] Killed make[1]: *** [exp.lo] Killed make[1]: *** [frac.lo] Killed make[1]: *** [get_d.lo] Killed make[1]: *** [get_exp.lo] Killed make[1]: *** [get_str.lo] Killed Processes are being killed because the slow machine simply does not have enough RAM to do what it's trying to do. Can I do anything about this beyond expanding the RAM? I'd like to finish this sometime this century, but processes keep getting killed. I shut down xdm before I started the emerge...
