/[gentoo]/xml/htdocs/doc/en/distcc.xml
Gentoo

Diff of /xml/htdocs/doc/en/distcc.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.9 Revision 1.10
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.9 2003/10/12 17:38:25 swift Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.10 2003/11/19 05:40:27 swift Exp $ -->
4 4
5<guide link="/doc/en/distcc.xml"> 5<guide link="/doc/en/distcc.xml">
6 6
7<title>Gentoo Distcc Documentation</title> 7<title>Gentoo Distcc Documentation</title>
8 8
9<author title="Author"> 9<author title="Author">
10 <mail link="lisa@gentoo.org">Lisa Seelye</mail> 10 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
11</author> 11</author>
12
13<author title="Editor"> 12<author title="Editor">
14 <mail link="vapier@gentoo.org">Mike Frysinger</mail> 13 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
15</author> 14</author>
16
17<author title="Editor"> 15<author title="Editor">
18 <mail link="erwin@gentoo.org">Erwin</mail> 16 <mail link="erwin@gentoo.org">Erwin</mail>
19</author> 17</author>
20
21<author title="Reviewer"> 18<author title="Reviewer">
22 <mail link="swift@gentoo.org">Sven Vermeulen</mail> 19 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
23</author> 20</author>
24
25<author title="Reviewer"> 21<author title="Reviewer">
26 <mail link="blubber@gentoo.org">Tiemo Kieft</mail> 22 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
27</author> 23</author>
28 24
29<license/> 25<license/>
30 26
31<version>1.2.4</version> 27<version>1.2.4</version>
32<date>October 12, 2003</date> 28<date>October 12, 2003</date>
33 29
30<abstract>
34<abstract>This document serves as a HOWTO for using distcc with Gentoo.</abstract> 31This document serves as a HOWTO for using distcc with Gentoo.
32</abstract>
35 33
36<chapter> 34<chapter>
37 <title>Introduction</title> 35<title>Introduction</title>
38 <section> 36<section>
39 <title>What is distcc?</title> 37<title>What is distcc?</title>
40 <body> 38<body>
41 <p>Distcc is a program designed to distribute compiling tasks across a network to participating hosts. It is comprised of a server, <c>distccd</c> and a client program, <c>distcc</c>. Distcc can work transparently with <uri link="http://ccache.samba.org">ccache</uri> and Portage with a little set up.</p> 39
40<p>
41Distcc is a program designed to distribute compiling tasks across a network to
42participating hosts. It is comprised of a server, <c>distccd</c> and a client
43program, <c>distcc</c>. Distcc can work transparently with <uri
44link="http://ccache.samba.org">ccache</uri> and Portage with a little set up.
45</p>
46
42 </body> 47</body>
43 </section> 48</section>
44</chapter>
45
46<chapter> 49</chapter>
50
51<chapter>
47 <title>Setup</title> 52<title>Setup</title>
48 <section> 53<section>
49 <title>Dependencies</title> 54<title>Dependencies</title>
50 <body> 55<body>
56
51 <pre caption="Distcc dependencies (2.8 through 2.10)"> 57<pre caption="Distcc dependencies (2.8 through 2.10)">
52&gt;=sys-apps/portage-2.0.46-r11 58&gt;=sys-apps/portage-2.0.46-r11
53<codenote>Distcc-2.11 and on require &gt;=sys-apps/portage-2.0.49-r6</codenote> 59<codenote>Distcc-2.11 and on require &gt;=sys-apps/portage-2.0.49-r6</codenote>
54&gt;=sys-devel/gcc-config-1.3.1 60&gt;=sys-devel/gcc-config-1.3.1
55sys-apps/shadow 61sys-apps/shadow
56<codenote>(As of version 2.8 and up until 2.11) And the following optional dependencies when you have <i>gtk</i> in your <i>USE</i> flags</codenote> 62<codenote>(As of version 2.8 and up until 2.11) And the following optional dependencies when you have <i>gtk</i> in your <i>USE</i> flags</codenote>
57&gt;=x11-libs/gtk+-2.2.1 63&gt;=x11-libs/gtk+-2.2.1
58</pre> 64</pre>
65
59 <pre caption="Distcc Dependencies (post 2.11.1)"> 66<pre caption="Distcc Dependencies (post 2.11.1)">
60&gt;=sys-apps/portage-2.0.49-r6 67&gt;=sys-apps/portage-2.0.49-r6
61&gt;=sys-devel/gcc-config-1.3.1 68&gt;=sys-devel/gcc-config-1.3.1
62sys-apps/shadow 69sys-apps/shadow
63<codenote>In this revision you may chose between a Gnome and GTK GUI monitor, they have the following added dependencies</codenote> 70<codenote>In this revision you may chose between a Gnome and GTK GUI monitor, they have the following added dependencies</codenote>
64<codenote>For GTK:</codenote> 71<codenote>For GTK:</codenote>
65&gt;=x11-libs/gtk+-2.0.0 72&gt;=x11-libs/gtk+-2.0.0
66&gt;=gnome-base/libglade-2.0.0 73&gt;=gnome-base/libglade-2.0.0
67x11-libs/pango 74x11-libs/pango
68<codenote>For Gnome:</codenote> 75<codenote>For Gnome:</codenote>
69&gt;=x11-libs/gtk+-2.0.0 76&gt;=x11-libs/gtk+-2.0.0
70&gt;=gnome-base/libglade-2.0.0 77&gt;=gnome-base/libglade-2.0.0
71x11-libs/pango 78x11-libs/pango
72&gt;=gnome-base/libgnomeui-2.0.0.0 79&gt;=gnome-base/libgnomeui-2.0.0.0
73&gt;=gnome-base/libgnome-2.0.0 80&gt;=gnome-base/libgnome-2.0.0
74</pre> 81</pre>
75 </body> 82
76 </section>
77 <section>
78 <title>Installing Distcc</title>
79 <body>
80 <p>Installing Distcc is very easy. Simply set your USE flags and <i>emerge distcc</i>. But, there's a couple of options you should know about.</p>
81 <p>Distcc ships with a graphical monitor to monitor tasks that your computer is sending away for compilation. If you use Gnome then put 'gnome' in your USE flags. However, if you don't use Gnome and would still like to have the monitor then you should put 'gtk' in your USE flags.</p>
82 </body> 83</body>
83 </section> 84</section>
84 <section> 85<section>
86<title>Installing Distcc</title>
87<body>
88
89<p>
90Installing Distcc is very easy. Simply set your USE flags and <c>emerge
91distcc</c>. But, there's a couple of options you should know about.
92</p>
93
94<p>
95Distcc ships with a graphical monitor to monitor tasks that your computer is
96sending away for compilation. If you use Gnome then put 'gnome' in your USE
97flags. However, if you don't use Gnome and would still like to have the
98monitor then you should put 'gtk' in your USE flags.
99</p>
100
101</body>
102</section>
103<section>
85 <title>Setting up Portage to use Distcc</title> 104<title>Setting up Portage to use Distcc</title>
86 <body> 105<body>
106
107<p>
87 <p>Setting up distcc is very easy to do with Portage. Follow these simple steps on each computer you want to use distcc on:</p> 108Setting up distcc is very easy to do with Portage. Follow these simple steps on
109each computer you want to use distcc on:
110</p>
111
88 <pre caption="Integrating Distcc and Portage"> 112<pre caption="Integrating Distcc and Portage">
89# <i>emerge distcc</i> 113# <i>emerge distcc</i>
90# <i>nano -w /etc/make.conf</i> 114# <i>nano -w /etc/make.conf</i>
91</pre> 115</pre>
92 <impo>If you use distcc-2.11.1 or greater with &gt;=portage-2.0.49-r6, then all you need to do as far as setup is to set your hosts (see next code block), modify MAKEOPTS in <path>/etc/make.conf</path>, and add 'distcc' to FEATURES in <path>/etc/make.conf</path>.</impo>
93 <note>Edit your FEATURES flags to include &quot;distcc&quot;</note>
94 <note>You should also uncomment the PORTAGE_TMPDIR line in <path>/etc/make.conf</path>.</note>
95 <note>Set <i>DISTCC_DIR=${PORTAGE_TMPDIR}/portage/.distcc</i> near the end of the file (last line is okay)</note>
96 116
97 <p>Next you have to specify what hosts you want to use. To do this you can use the <c>distcc-config</c> command to set the list of hosts. Here is an example of some hosts that might be in your list:</p> 117<impo>
118If you use distcc-2.11.1 or greater with &gt;=portage-2.0.49-r6, then all you
119need to do as far as setup is to set your hosts (see next code block), modify
120MAKEOPTS in <path>/etc/make.conf</path>, and add 'distcc' to FEATURES in
121<path>/etc/make.conf</path>.
122</impo>
123
124<note>
125Edit your FEATURES flags to include &quot;distcc&quot;
126</note>
127
128<note>
129You should also uncomment the PORTAGE_TMPDIR line in
130<path>/etc/make.conf</path>.
131</note>
132
133<note>
134Set <c>DISTCC_DIR=${PORTAGE_TMPDIR}/portage/.distcc</c> near the end of the file
135(last line is okay).
136</note>
137
138<p>
139Next you have to specify what hosts you want to use. To do this you can use
140the <c>distcc-config</c> command to set the list of hosts. Here is an example
141of some hosts that might be in your list:
142</p>
143
98 <pre caption="Examples of host definitions"> 144<pre caption="Examples of host definitions">
99192.168.0.1 192.168.0.2 192.168.0.3 145192.168.0.1 192.168.0.2 192.168.0.3
100192.168.0.1/2 192.168.0.2 192.168.0.3/10 146192.168.0.1/2 192.168.0.2 192.168.0.3/10
101192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4 147192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4
102@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3 148@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3
103</pre> 149</pre>
104 <p>It may all look complicated, but in most cases a variant of line 1 or 2 will work. An explanation of each line is: Line 1 is just a space-delimited list of hosts that will use default everything. Line 2 is a list of hosts that specifies the maximum number of jobs (by use of the /N) to send that host at any given time (specified with the <c>/n</c>). Since most people won't be using lines 3 or 4, I'll <uri link="http://distcc.samba.org/man/distcc_1.html">point you to</uri> the distcc docs for more information.</p> 150
151<p>
152It may all look complicated, but in most cases a variant of line 1 or 2 will
153work. An explanation of each line is: Line 1 is just a space-delimited list
154of hosts that will use default everything. Line 2 is a list of hosts that
155specifies the maximum number of jobs (by use of the /N) to send that host at
156any given time (specified with the <c>/n</c>). Since most people won't be
157using lines 3 or 4, I'll <uri link="http://distcc.samba.org/man/distcc_1.html">
158point you to</uri> the distcc docs for more information.
159</p>
160
161<p>
105 <p>A sample command to set the hosts (for line 1) is:</p> 162A sample command to set the hosts (for line 1) is:
163</p>
164
106 <pre caption="Sample command to set the hosts"> 165<pre caption="Sample command to set the hosts">
107# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i> 166# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i>
108</pre> 167</pre>
109 168
110 <p>The final step to integrating distcc into Portage is to re-open your <path>/etc/make.conf</path> and edit <c>MAKEOPTS</c> to include <c>-jN</c> (where N is an integer). Typically you will want to set this to the total number of processors in your network plus one.</p> 169<p>
170The final step to integrating distcc into Portage is to re-open your
171<path>/etc/make.conf</path> and edit <c>MAKEOPTS</c> to include <c>-jN</c>
172(where N is an integer). Typically you will want to set this to the total
173number of processors in your network plus one.
174</p>
175
111 <pre caption="Final steps in make.conf"> 176<pre caption="Final steps in make.conf">
112# <i>nano -w /etc/make.conf</i> 177# <i>nano -w /etc/make.conf</i>
113MAKEOPTS=-jN 178MAKEOPTS=-jN
114</pre> 179</pre>
180
181<impo>
115 <impo>Don't forget to start the distcc daemon! <c>/etc/init.d/distccd start</c></impo> 182Don't forget to start the distcc daemon! <c>/etc/init.d/distccd start</c>
183</impo>
184
116 </body> 185</body>
117 </section> 186</section>
118 <section> 187<section>
119 <title>Setting up Distcc to Work With Automake</title> 188<title>Setting up Distcc to Work With Automake</title>
120 <body> 189<body>
121 <p>This is in some cases easier than the Portage setup. What you have to do is update your <c>PATH</c> environmental variable to include <path>/usr/lib/distcc/bin</path> before where gcc (<path>/usr/bin</path>). However, there is a caveat. If you use ccache you have to put distcc after the ccache part. Like so:</p> 190
191<p>
192This is in some cases easier than the Portage setup. What you have to do is
193update your <c>PATH</c> environmental variable to include
194<path>/usr/lib/distcc/bin</path> before where gcc (<path>/usr/bin</path>).
195However, there is a caveat. If you use ccache you have to put distcc after
196the ccache part. Like so:
197</p>
198
122 <pre caption="Setting your path"> 199<pre caption="Setting your path">
123# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 200# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
124</pre> 201</pre>
125 <p>Then, as you would normally type <c>make</c>, you would type <c>make -jN</c> (where N is an integer). A safe number to use for N varies on your network and the types of computers you are using to compile. For me, I have a dual processor P3 and a K6-2/400 that compile everything for my desktop (a 1200MHz Athlon Thunderbird) and I use -j5. Test your own settings to find the right number.</p> 202
203<p>
204Then, as you would normally type <c>make</c>, you would type <c>make -jN</c>
205(where N is an integer). A safe number to use for N varies on your network
206and the types of computers you are using to compile. For me, I have a dual
207processor P3 and a K6-2/400 that compile everything for my desktop (a 1200MHz
208Athlon Thunderbird) and I use -j5. Test your own settings to find the right
209number.
210</p>
211
126 </body> 212</body>
127 </section> 213</section>
128</chapter>
129
130<chapter> 214</chapter>
215
216<chapter>
131 <title>Cross-Compiling</title> 217<title>Cross-Compiling</title>
132 <section> 218<section>
133 <title>A Note on Cross-Compiling</title> 219<title>A Note on Cross-Compiling</title>
134 <body> 220<body>
135 <p>Cross-compiling is using one architecture to build programs for another architecture. This can be as simple as using an Athlon (i686) to build a program for a K6-2 (i586), or using a Sparc to build a program for a ppc.</p> 221
222<p>
223Cross-compiling is using one architecture to build programs for another
224architecture. This can be as simple as using an Athlon (i686) to build a
225program for a K6-2 (i586), or using a Sparc to build a program for a ppc.
226</p>
227
136 </body> 228</body>
137 </section> 229</section>
138 <section> 230<section>
139 <title>A Personal Note on Cross-compiling</title> 231<title>A Personal Note on Cross-compiling</title>
140 <body> 232<body>
141 <p>I'd love to be able to help out on the Gentoo Cross-compiling effort, but I don't have any non-x86 machines. I can create things that work <e>in theory</e>, but I have to rely on other people to test what I write. That works to an extent, but it's tough. ;-)</p> 233
234<p>
235I'd love to be able to help out on the Gentoo Cross-compiling effort, but I
236don't have any non-x86 machines. I can create things that work <e>in
237theory</e>, but I have to rely on other people to test what I write. That
238works to an extent, but it's tough. ;-)
239</p>
240
241<p>
142 <p>In the near future I hope to acquire a Sparc of some type to put Gentoo on so I can play around in-house.</p> 242In the near future I hope to acquire a Sparc of some type to put Gentoo on so
243I can play around in-house.
244</p>
245
143 </body> 246</body>
144 </section> 247</section>
145</chapter>
146
147<chapter> 248</chapter>
249
250<chapter>
148 <title>Using Distcc to Bootstrap</title> 251<title>Using Distcc to Bootstrap</title>
149 <section> 252<section>
150 <title>Step 1: Setup on New Box</title> 253<title>Step 1: Setup on New Box</title>
151 <body> 254<body>
152 <p>Next, you have to boot your new box with a Gentoo Linux LiveCD and follow all of the steps up until the bootstrapping. Then proceed with a little preliminary setup on the new box.</p> 255
256<p>
257Next, you have to boot your new box with a Gentoo Linux LiveCD and follow all
258of the steps up until the bootstrapping. Then proceed with a little preliminary
259setup on the new box.
260</p>
261
153 <pre caption="Preliminary Setup"> 262<pre caption="Preliminary Setup">
154<codenote>Here we add distcc to FEATURES</codenote> 263<codenote>Here we add distcc to FEATURES</codenote>
155# <i>nano -w /etc/make.conf</i> 264# <i>nano -w /etc/make.conf</i>
156<codenote>Add &quot;distcc&quot; to FEATURES</codenote> 265<codenote>Add &quot;distcc&quot; to FEATURES</codenote>
157<codenote>Modify MAKEOPTS in <path>/etc/make.conf to include -jN (as described above)</path></codenote> 266<codenote>Modify MAKEOPTS in <path>/etc/make.conf to include -jN (as described above)</path></codenote>
158</pre> 267</pre>
268
269<p>
159 <p>Then add the distcc user to your <path>/etc/passwd</path>:</p> 270Then add the distcc user to your <path>/etc/passwd</path>:
271</p>
272
160 <pre caption="Add the distcc user to /etc/passwd"> 273<pre caption="Add the distcc user to /etc/passwd">
161# <i>echo "distcc:x:240:2:distccd:/dev/null:/bin/false" &gt;&gt;/etc/passwd</i> 274# <i>echo "distcc:x:240:2:distccd:/dev/null:/bin/false" &gt;&gt;/etc/passwd</i>
162<codenote>Do not forget the `<i>&gt;&gt;</i>'</codenote> 275<codenote>Do not forget the `<i>&gt;&gt;</i>'</codenote>
163</pre> 276</pre>
277
164 </body> 278</body>
165 </section> 279</section>
166 <section> 280<section>
167 <title>Step 2: Getting Distcc</title> 281<title>Step 2: Getting Distcc</title>
168 <body> 282<body>
283
284<p>
169 <p>Next you will want to issue the following command inside the chroot on the new box.</p> 285Next you will want to issue the following command inside the chroot on the new
286box.
287</p>
288
170 <pre caption="Getting Distcc on the new box"> 289<pre caption="Getting Distcc on the new box">
171# <i>emerge --nodeps distcc</i> 290# <i>emerge --nodeps distcc</i>
172</pre> 291</pre>
292
173 </body> 293</body>
174 </section> 294</section>
175 <section> 295<section>
176 <title>Step 3: Setting Up Distcc Itself</title> 296<title>Step 3: Setting Up Distcc Itself</title>
177 <body> 297<body>
298
299<p>
178 <p>Now set up distcc itself...</p> 300Now set up distcc itself...
301</p>
302
179 <pre caption="Final distcc setup"> 303<pre caption="Final distcc setup">
180# <i>/usr/bin/distcc-config --install</i> 304# <i>/usr/bin/distcc-config --install</i>
181# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i> 305# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
182</pre> 306</pre>
183 <p>distcc should be set up now to bootstrap! Continue the official install guide, and don't forget to re-emerge distcc after <c>emerge system</c>.</p> 307
308<p>
309distcc should be set up now to bootstrap! Continue the official install guide,
310and don't forget to re-emerge distcc after <c>emerge system</c>.
311</p>
312
184 </body> 313</body>
185 </section> 314</section>
186</chapter>
187
188<chapter> 315</chapter>
189 <title>Troubleshooting</title> 316
190 <section>
191 <title>Mozilla and Xfree</title>
192 <body>
193 <p>As you emerge various packages, you'll notice that they aren't being distributed (and indeed aren't being built in parallel). This is because the developers of Mozilla and Xfree .ebuilds disabled parallel building because it is known to cause problems. This isn't necessarily a distcc problem.</p>
194 <p>That isn't to say that sometimes distcc will cause a package to fail to compile.</p>
195 </body>
196 </section>
197 <section>
198 <title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
199 <body>
200 <p>With such a long title any explanation here is almost irrelevent. However, if you plan to use distcc across hosts that have the <uri link="http://www.gentoo.org/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do not, you will run into problems.</p>
201 <p>The solution requires a little foresight on your part; you have to run <c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of which are a good thing to do since for the most part the protections offered by both packages is a good thing and is transparent to the user.</p>
202 </body>
203 </section>
204 <section>
205 <title>Mixed GCC Versions</title>
206 <body>
207 <p>If you have differing versions of GCC on your hosts, there will likely be very weird problems. The solution is to make certain all hosts have the same GCC version.</p>
208 </body>
209 </section>
210</chapter> 317<chapter>
318<title>Troubleshooting</title>
319<section>
320<title>Mozilla and Xfree</title>
321<body>
211 322
323<p>
324As you emerge various packages, you'll notice that they aren't being distributed
325(and indeed aren't being built in parallel). This is because the developers of
326Mozilla and Xfree .ebuilds disabled parallel building because it is known to
327cause problems. This isn't necessarily a distcc problem.
328</p>
329
330<p>
331That isn't to say that sometimes distcc will cause a package to fail to compile.
332</p>
333
334</body>
335</section>
336<section>
337<title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
338<body>
339
340<p>
341With such a long title any explanation here is almost irrelevent. However, if
342you plan to use distcc across hosts that have the <uri
343link="http://www.gentoo.org/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri>
344and some that do not, you will run into problems.
345</p>
346
347<p>
348The solution requires a little foresight on your part; you have to run
349<c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to
350enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of
351which are a good thing to do since for the most part the protections offered
352by both packages is a good thing and is transparent to the user.
353</p>
354
355</body>
356</section>
357<section>
358<title>Mixed GCC Versions</title>
359<body>
360
361<p>
362If you have differing versions of GCC on your hosts, there will likely be very
363weird problems. The solution is to make certain all hosts have the same GCC
364version.
365</p>
366
367</body>
368</section>
212<chapter> 369</chapter>
370
371<chapter>
213 <title>Distcc Extras</title> 372<title>Distcc Extras</title>
214 <section> 373<section>
215 <title>Distcc Monitors</title> 374<title>Distcc Monitors</title>
216 <body> 375<body>
217 <p>Distcc ships with two monitors. The text-based one is always built, it is called <c>distccmon-text</c>. Running it for the first time can be a bit confusing, but it is really quite easy to use. If you run the program with no parameter it will run once. However, if you pass it a number it will update every N seconds, where N is the argument you passed.</p> 376
218 <p>The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c> in your <c>USE</c> flags. This one is GTK+ based and runs in an X environment, and it is quite lovely.</p> 377<p>
378Distcc ships with two monitors. The text-based one is always built, it is
379called <c>distccmon-text</c>. Running it for the first time can be a bit
380confusing, but it is really quite easy to use. If you run the program with no
381parameter it will run once. However, if you pass it a number it will update
382every N seconds, where N is the argument you passed.
383</p>
384
385<p>
386The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c>
387in your <c>USE</c> flags. This one is GTK+ based and runs in an X environment,
388and it is quite lovely.
389</p>
390
391<p>
219 <p>There is a caveat to using these programs. If you want to monitor any emerge, you have to start the monitor like so:</p> 392There is a caveat to using these programs. If you want to monitor any emerge,
393you have to start the monitor like so:
394</p>
395
220 <pre caption="Starting the monitors"> 396<pre caption="Starting the monitors">
221# <i>DISTCC_DIR=/path/to/distccdir distccmon-text N</i> 397# <i>DISTCC_DIR=/path/to/distccdir distccmon-text N</i>
222<codenote>Or you can start the graphical monitor...</codenote> 398<codenote>Or you can start the graphical monitor...</codenote>
223# <i>DISTCC_DIR=/path/to/distccdir distccmon-gnome</i> 399# <i>DISTCC_DIR=/path/to/distccdir distccmon-gnome</i>
224</pre> 400</pre>
225 <impo>If you are using Portage and used the above example, this will be <c>DISTCC_DIR=/var/tmp/portage/.distcc</c>.</impo> 401
226 <note>If you aren't using Portage you do not need to specify DISTCC_DIR (i.e., just type distccmon-text N).</note> 402<impo>
403If you are using Portage and used the above example, this will be
404<c>DISTCC_DIR=/var/tmp/portage/.distcc</c>.
405</impo>
406
407<note>
408If you aren't using Portage you do not need to specify DISTCC_DIR (i.e., just
409type distccmon-text N).
410</note>
411
227 </body> 412</body>
228 </section> 413</section>
229</chapter>
230
231<chapter> 414</chapter>
415
416<chapter>
232 <title>Future Plans for Distcc and Gentoo</title> 417<title>Future Plans for Distcc and Gentoo</title>
233 <section> 418<section>
234 <title>distcc-subnetscan</title> 419<title>distcc-subnetscan</title>
235 <body> 420<body>
236 <p><c>distcc-subnetscan</c> is a perl program in development that will scan a subnet for hosts that have a participating distcc daemon. Even this will be enhanced to test if the daemon on a remote host will conform to a specific <c>CHOST</c> setting to make cross-compiling easier.</p> 421
422<p>
423<c>distcc-subnetscan</c> is a perl program in development that will scan a
424subnet for hosts that have a participating distcc daemon. Even this will be
425enhanced to test if the daemon on a remote host will conform to a specific
426<c>CHOST</c> setting to make cross-compiling easier.
427</p>
428
429<p>
237 <p>The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/distcc/distcc-subnetscan/distcc-subnetscan.pl">right here</uri> until a more formal home can be found.</p> 430The perl script is being kept at <uri link="http://dev.gentoo.org/~lisa/distcc/distcc-subnetscan/distcc-subnetscan.pl">
431right here</uri> until a more formal home can be found.
432</p>
433
238 </body> 434</body>
239 </section> 435</section>
240 <section> 436<section>
241 <title>distcc-config</title> 437<title>distcc-config</title>
242 <body> 438<body>
243 <p><c>distcc-config</c>, the userland configuration tool for distcc is out of date. Soon it will be rewritten to be brought up the current version of distcc.</p> 439
440<p>
441<c>distcc-config</c>, the userland configuration tool for distcc is out of date.
442Soon it will be rewritten to be brought up the current version of distcc.
443</p>
444
244 </body> 445</body>
245 </section> 446</section>
246</chapter> 447</chapter>
247
248</guide> 448</guide>

Legend:
Removed from v.1.9  
changed lines
  Added in v.1.10

  ViewVC Help
Powered by ViewVC 1.1.20