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

Legend:
Removed from v.1.16  
changed lines
  Added in v.1.17

  ViewVC Help
Powered by ViewVC 1.1.20