/[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.3 Revision 1.25
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.3 2003/09/08 08:09:02 blubber Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/distcc.xml,v 1.25 2005/01/16 16:23:30 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@gentoo.org</mail> 10 <mail link="lisa@gentoo.org">Lisa Seelye</mail>
11</author>
12
13<author title="Editor">
14 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
15</author>
16
17<author title="Editor">
18 <mail link="erwin@gentoo.org">Erwin</mail>
19</author>
20
21<author title="Editor">
22 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
23</author>
24
25<author title="Editor">
26 <mail link="pylon@gentoo.org">Lars Weiler</mail>
11</author> 27</author>
12 28
13<author title="Reviewer"> 29<author title="Reviewer">
14 <mail link="swift@gentoo.org">swift@gentoo.org</mail>
15</author>
16
17<author title="Reviewer">
18 <mail link="blubber@gentoo.org">blubber@gentoo.org</mail> 30 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
19</author> 31</author>
20 32
33<abstract>
34This document serves as a HOWTO for using distcc with Gentoo.
35</abstract>
36
37<!-- The content of this document is licensed under the CC-BY-SA license -->
38<!-- See http://creativecommons.org/licenses/by-sa/1.0 -->
39<license/>
40
21<version>1.1</version> 41<version>1.10</version>
22<date>September 08, 2003</date> 42<date>2005-01-16</date>
23
24<abstract>This document serves as a HOWTO for using distcc with Gentoo.</abstract>
25 43
26<chapter> 44<chapter>
27 <title>Introduction</title> 45<title>Introduction</title>
28 <section> 46<section>
29 <title>What is distcc?</title> 47<title>What is distcc?</title>
30 <body> 48<body>
31 <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> 49
50<p>
51Distcc is a program designed to distribute compiling tasks across a network to
52participating hosts. It is comprised of a server, <c>distccd</c>, and a client
53program, <c>distcc</c>. Distcc can work transparently with <uri
54link="http://ccache.samba.org">ccache</uri> and Portage with a little work.
55</p>
56
32 </body> 57</body>
33 </section> 58</section>
34
35 <section> 59<section>
36 <title>Dependancies</title> 60<title>Using distcc to bootstrap</title>
37 <body> 61<body>
38 <pre caption="Distcc Dependancies"> 62
39&gt;=sys-apps/portage-2.0.46-r11 63<p>
40&gt;=sys-devel/gcc-config-1.3.1 64If you are planning on using distcc to help you bootstrap a Gentoo installation,
41&gt;sys-apps/shadow 65make sure you read the section <uri link="#bootstrapping">Using distcc to
42<codenote>(As of version 2.8) And the following optional dependancies when you have <c>gtk</c> in your <c>USE</c> flags</codenote> 66Bootstrap</uri>, which is situated further down in this document.
43&gt;=x11-libs/gtk+-2.2.1 67</p>
44 </pre> 68
45 </body> 69</body>
46 </section> 70</section>
47</chapter> 71</chapter>
48 72
49<chapter> 73<chapter>
50 <title>Setup</title> 74<title>Setup</title>
51 <section> 75<section>
76<title>Dependencies</title>
77<body>
78
79<p>
80In order to use Distcc, all of the computers on your network need to
81have the same GCC versions. Mixing 3.3.x (where the x varies) is okay, but
82mixing 3.3.x and 3.2.x <b>will</b> result in your programs having errors in them.
83</p>
84
85</body>
86</section>
87<section>
88<title>Installing Distcc</title>
89<body>
90
91<p>
92There are a couple of options you should be aware of before you start
93installing distcc.
94</p>
95
96<p>
97Distcc ships with a graphical monitor to monitor tasks that your computer is
98sending away for compilation. If you use Gnome then put 'gnome' in your USE
99flags. However, if you don't use Gnome and would still like to have the
100monitor then you should put 'gtk' in your USE flags.
101</p>
102
103<pre caption="Installing distcc">
104# <i>emerge distcc</i>
105</pre>
106
107</body>
108</section>
109<section>
52 <title>Setting up Portage to use Distcc</title> 110<title>Setting up Portage to use Distcc</title>
53 <body> 111<body>
54 <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> 112
113<p>
114Setting up Portage to use distcc is easy. Execute the following steps on
115each system that should participate in the distributed compiling:
116</p>
117
55 <pre caption="Integrating Distcc and Portage"> 118<pre caption="Integrating Distcc and Portage">
56# <i>emerge distcc</i> 119# <i>emerge distcc</i>
57# <i>nano -w /etc/make.conf</i> 120# <i>nano -w /etc/make.conf</i>
58<codenote>Edit your FEATURES flags to include &quot;distcc&quot;</codenote> 121<comment>(Set N to a suitable number for your particular setup)</comment>
122<comment>(A common heuristic strategy is twice the number of total CPUs + 1)</comment>
123MAKEOPTS="-jN"
124<comment>(Add distcc to your FEATURES variable)</comment>
125FEATURES="distcc"
59 </pre> 126</pre>
60 127
61 <p>Next you have to specify what hosts you want to use. To do this you can use the <i>distcc-config</i> command to set that list of hosts. Here is an example of some hosts that might be in your list:</p> 128</body>
129</section>
130<section>
131<title>Specifying Participating Hosts</title>
132<body>
133
134<p>
135Use the <c>distcc-config</c> command to set the list of hosts. Here is an example of
136some hosts that might be in your list:
137</p>
138
62 <pre caption="Examples of host definitions"> 139<pre caption="Examples of host definitions">
63192.168.0.1 192.168.0.2 192.168.0.3 140192.168.0.1 192.168.0.2 192.168.0.3
64192.168.0.1/2 192.168.0.2 192.168.0.3/10 141192.168.0.1/2 192.168.0.2 192.168.0.3/10
65192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4 142192.168.0.1:4000/2 192.168.0.2/1 192.168.0.3:3632/4
66@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3 143@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3
144<comment>(There are also several other methods of setting up hosts. See the
145distcc manpage for more details.)</comment>
67 </pre> 146</pre>
68 <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 maxmimum 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> 147
69 <p>A sample command to set the hosts (for line 1) is:</p> 148<p>
149It may all look complicated, but in most cases a variant of line 1 or 2 will
150work.
151</p>
152
153<ul>
154 <li>Line 1 is just a space-delimited list of hosts</li>
155 <li>
156 Line 2 is a list of hosts that specifies the maximum amount of jobs (by
157 defining the <c>/N</c> setting) to send that host at any given time
158 </li>
159</ul>
160
161<p>
162Since most people won't be using lines 3 or 4, I'll <uri
163link="http://distcc.samba.org/man/distcc_1.html">point you to</uri> the distcc
164docs for more information.
165</p>
166
167<p>
168For instance, to set the first line in the previous example:
169</p>
170
70 <pre caption="Sample command to set the hosts"> 171<pre caption="Sample command to set the hosts">
71# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3</i> 172# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i>
72 </pre> 173</pre>
73 174
74 <p>The final step to integrating distcc into Portage is to re-open your <path>/etc/make.conf</path> and edit <c>MAKE_OPTS</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> 175<p>
75 <pre caption="Final steps in make.conf"> 176Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the
177<c>--allow</c> directive to allow only hosts you trust. For added security, you should also use the <c>--listen</c>
178directive to tell the distcc daemon what IP to listen on (for multi-homed
179systems). More information on distcc security can be found at <uri link="http://distcc.samba.org/security.html">Distcc Security
180Design</uri>.
181</p>
182
183<p>
184Now start the distcc daemon on all the participating computers:
185</p>
186
187<pre caption="Starting the distcc daemon">
188<comment>(Add distccd to the default runlevel)</comment>
189# <i>rc-update add distccd default</i>
190<comment>(Start the distcc daemon)</comment>
191# <i>/etc/init.d/distccd start</i>
192</pre>
193
194</body>
195</section>
196<section>
197<title>Setting up Distcc to Work With Automake</title>
198<body>
199
200<p>
201This is, in some cases, easier than the Portage setup. What you have to do is
202update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</path>
203in front of the directory that contains <c>gcc</c> (<path>/usr/bin</path>).
204However, there is a caveat. If you use ccache you have to put distcc after
205the ccache part:
206</p>
207
208<pre caption="Setting your path">
209# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
210</pre>
211
212<p>
213Then, as you would normally type <c>make</c>, you would type <c>make -jN</c>
214(where N is an integer). The value of N depends on your network and the types
215of computers you are using to compile. For me, I have a dual processor P3 and
216a K6-2/400 that compiles everything for my desktop (a 1200MHz Athlon
217Thunderbird) and I use -j5. Test your own settings to find the number that
218yields the best performance.
219</p>
220
221</body>
222</section>
223</chapter>
224
225<chapter>
226<title>Cross-Compiling</title>
227<section>
228<title>A Note on Cross-Compiling</title>
229<body>
230
231<p>
232Cross-compiling is using one architecture to build programs for another
233architecture. This can be as simple as using an Athlon (i686) to build a
234program for a K6-2 (i586), or using a Sparc to build a program for a ppc.
235</p>
236
237</body>
238</section>
239<section>
240<title>An Introduction to Cross-Compiling</title>
241<body>
242
243<p>
244If you want to give cross-compiling a try you can to follow <uri
245link="http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO">The Cross Compile
246HOWTO</uri>; Crossdev is deprecated.
247</p>
248
249</body>
250</section>
251</chapter>
252
253<chapter id="bootstrapping">
254<title>Using Distcc to Bootstrap</title>
255<section>
256<title>Step 1: Configure Portage</title>
257<body>
258
259<p>
260Boot your new box with a Gentoo Linux LiveCD and follow the <uri
261link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
262up until the bootstrapping part. Then configure Portage to use distcc:
263</p>
264
265<pre caption="Preliminary Setup">
76# <i>nano -w /etc/make.conf</i> 266# <i>nano -w /etc/make.conf</i>
267<comment>(Add distcc to the FEATURES variable)</comment>
268FEATURES="distcc"
269<comment>(Modify MAKEOPTS to include -jN with N an appropriate integer)</comment>
77MAKE_OPTS=-jN 270MAKEOPTS="-jN"
78 </pre> 271</pre>
79 </body> 272
80 </section>
81 <section>
82 <title>Setting up Distcc to Work With Automake</title>
83 <body>
84 <p>This is in some cases easier than the Portage setup. What you have to do is update your <c>PATH</c> envvar 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>
85 <pre caption="Setting your path"> 273<pre caption="Setting your path">
86# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 274# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
87 </pre> 275</pre>
88 <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 varries 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> 276
89 </body> 277</body>
90 </section> 278</section>
279<section>
280<title>Step 2: Getting Distcc</title>
281<body>
282
283<p>
284Before the installation of distcc, a user called distcc must be added to the
285<path>/etc/passwd</path>:
286</p>
287
288<pre caption="Create user distcc">
289# <i>echo "distcc:x:240:2:distccd:/dev/null:/bin/false" &gt;&gt; /etc/passwd</i>
290</pre>
291
292<impo>
293It is important to note that adding users like this is very bad. We only do
294it here because there is no <c>useradd</c> utility (which you normally use for
295adding users) yet at this stage of installation.
296</impo>
297
298<p>
299Install distcc:
300</p>
301
302<pre caption="Getting Distcc on the new box">
303# <i>USE='-*' emerge --nodeps sys-devel/distcc</i>
304</pre>
305
306</body>
307</section>
308<section>
309<title>Step 3: Setting Up Distcc</title>
310<body>
311
312<p>
313Run <c>distcc-config --install</c> to setup distcc:
314</p>
315
316<pre caption="Final distcc setup">
317<comment>(Substitute host1, host2, ... with the IP number(s) of the participating hosts)</comment>
318# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
319<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost 192.168.0.4 192.168.0.6"</i></comment>
320</pre>
321
322<p>
323Distcc is now set up to bootstrap! Continue with the official installation
324instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge
325system</c>. This is to make sure that all of the dependencies you want are
326installed as well.
327</p>
328
329<note>
330During bootstrap and <c>emerge system</c> distcc may not appear to be used.
331This is expected as some ebuilds do not work well with distcc, so they
332intentionally disable it.
333</note>
334
335</body>
336</section>
91</chapter> 337</chapter>
92 338
93<chapter> 339<chapter>
94 <title>Cross-Compiling</title> 340<title>Troubleshooting</title>
95 <section> 341<section>
96 <title>A Note on Cross-Compiling</title> 342<title>Mozilla and Xfree</title>
97 <body> 343<body>
98 <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> 344
345<p>
346As you emerge various packages, you'll notice that some of them aren't being
347distributed (and aren't being built in parallel). This is because the
348developers of the Mozilla and Xfree ebuilds intentionally disable parallel
349building because it is known to cause problems.
350</p>
351
352<p>
353Sometimes distcc might cause a package to fail to compile. If this happens
354for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us.
355</p>
356
99 </body> 357</body>
100 </section> 358</section>
101 <section> 359<section>
102 <title>A Personal Note on Cross-compiling</title> 360<title>A Mixture of hardened-gcc and non-hardened-gcc Hosts Will Be Faulty</title>
103 <body> 361<body>
104 <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> 362
105 <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> 363<p>
364With such a long title any explanation here is almost irrelevent. However, if
365you plan to use distcc across hosts that have the <uri
366link="/proj/en/hardened/etdyn-ssp.xml">PaX/hardened-gcc</uri> and some that do
367not, you will run into problems.
368</p>
369
370<p>
371The solution requires a little foresight on your part; you have to run
372<c>hardened-gcc -R</c> on the host that has PaX/hardened-gcc, or you have to
373enable PaX protections in your kernel and <c>emerge hardened-gcc</c>. Both of
374which are a good thing to do since for the most part the protections offered
375by both packages is a good thing and is transparent to the user.
376</p>
377
106 </body> 378</body>
107 </section> 379</section>
380<section>
381<title>Mixed GCC Versions</title>
382<body>
383
384<p>
385If you have different GCC versions on your hosts, there will likely be very
386weird problems. The solution is to make certain all hosts have the same GCC
387version.
388</p>
389
390<p>
391Recent Portage updates have made Portage use <c>${CHOST}-gcc</c> instead of
392<c>gcc</c>. This means that if you're mixing i686 machines with other types
393(i386, i586) you will run into problems. A workaround for this may be to
394<c>export CC='gcc' CXX='c++'</c> or to put it in <path>/etc/make.conf</path>,
395but that needs testing. If it works for you please email me,
396<mail link="lisa@gentoo.org">Lisa Seelye</mail>.
397</p>
398
399</body>
400</section>
108</chapter> 401</chapter>
109 402
110<chapter> 403<chapter>
111 <title>Known Problems With Distcc</title>
112 <section>
113 <title>Portage Doesn't Work With Distcc</title>
114 <body>
115 <p>This heading is a misnomer, really. The only thing that doens't work is the monitoring programs (<c>distccmon-text</c> and <c>distccmon-gnome</c>) with the standard distcc source. The reason for this is that distcc relies on the <c>TMPDIR</c> envvar, but Portage reassigns that.</p>
116 <p>The solution to this is a patch that changes the dependancy to <c>DISTCC_TMPDIR</c>. The patch is automatically applied to distcc. If you don't want to use <path>/tmp</path> (the default) you can reassign <c>DISTCC_TMPDIR</c>.</p>
117 <p>You may also notice that Distcc does not work with some packages. This can be a result of several things, such as an error in the .ebuild (Using <c>make</c> instead of <c>emake</c>) or an error in the program's Makefile, which the next section addresses.</p>
118 </body>
119 </section>
120 <section>
121 <title>Mozilla and Xfree</title>
122 <body>
123 <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>
124 <p>That isn't to say that sometimes distcc will cause a package to fail to compile.</p>
125 </body>
126 </section>
127</chapter>
128
129<chapter>
130 <title>Using Distcc to Bootstrap</title>
131 <section>
132 <title>Step 1: Build the Tarball</title>
133 <body>
134 <p>This section is helpful if you want to use Distcc during the Gentoo installation. Surprisingly it isn't that hard. What you'll need is another computer running Gentoo and a way to transfer a tarball to your new system (I use scp).</p>
135 <p>First you have to build a tarball of Distcc and include a library (<c>/usr/lib/libpopt.so.*</c>).</p>
136 <pre caption="Building the tarball">
137<i># USE='-gtk -selinux' emerge --buildpkg distcc
138# mkdir -p /tmp/distcc/usr/lib
139# cp /usr/portage/packages/sys-devel/distcc-DISTCC_VERSION.tbz2 /tmp/distcc/
140# cp /usr/lib/libpopt.so.* /tmp/distcc/usr/lib
141# cd /tmp/distcc
142# tar cfzv distcc.tar.gz *</i>
143<codenote>Be sure you replace DISTCC_VERSION with the version (and Gentoo revision) of Distcc, <c>like 2.10-r1</c></codenote>
144 </pre>
145 </body>
146 </section>
147 <section>
148 <title>Step 2: Setup on New Box</title>
149 <body>
150 <impo>Do not forget to start sshd and reset the root password for the LiveCD!</impo>
151 <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 procede with a little preliminary setup on the new box.</p>
152 <pre caption="Preliminary Setup">
153<codenote>Here we add distcc to FEATURES</codenote>
154<i># echo "FEATURES=\"\${FEATURES} distcc\"" >> /etc/make.conf</i>
155<codenote>You can also use <c>nano</c> to edit <c>/etc/make.conf</c> and manually add distcc to FEATURES.</codenote>
156<i># echo "MAKEOPTS=\"\${MAKEOPTS} -jN\"" >> /etc/make.conf</i>
157<codenote>Just like above, you can use <c>nano</c> to edit <c>/etc/make.conf</c> and manually change MAKEOPTS.</codenote>
158 </pre>
159 <p>Then add the distcc user to your <c>/etc/passwd</c>:</p>
160 <pre caption="Add the distcc user to /etc/passwd">
161<i># echo "distcc:x:240:2:distccd:/dev/null:/bin/false" >>/etc/passwd</i>
162<codenote>Do not forget the `<c>&gt;&gt;</c>'</codenote>
163 </pre>
164 </body>
165 </section>
166 <section>
167 <title>Step 3: Copy the Tarball</title>
168 <body>
169 <p>Next you will want to copy the distcc tarball that you made.</p>
170 <pre caption="Copy the tarball to the new box">
171<codenote>Execute this on the "old" box</codenote>
172<i># scp /tmp/distcc/distcc.tar.gz root@ip.of.new.box:/mnt/gentoo/</i>
173<codenote>Substitute <c>ip.of.new.box</c> for your new box's IP</codenote>
174 </pre>
175 </body>
176 </section>
177
178 <section>
179 <title>Step 4: Unpacking the Tarball</title>
180 <body>
181 <pre caption="Unpack the tarball">
182<i># tar xvfz distcc.tar.gz
183# tar xvfjp distcc-DISTCC_VERSION.tbz2</i>
184<codenote>Be sure you replace DISTCC_VERSION with the version (and Gentoo revision) of Distcc, <c>like 2.10-r1</c></codenote>
185 </pre>
186 </body>
187 </section>
188
189 <section>
190 <title>Step 5: Setting Up Distcc Itself</title>
191 <body>
192 <p>Now set up distcc itself...</p>
193 <pre caption="Final distcc setup">
194<i># /usr/bin/distcc-config --install
195# /usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
196 </pre>
197
198 <p>distcc should be set up now to bootstrap! Continue the official install guide, and dont forget to re-emerge distcc after <c>emerge system</c>.</p>
199 </body>
200 </section>
201</chapter>
202
203
204<chapter>
205 <title>Distcc Extras</title> 404<title>Distcc Extras</title>
206 <section> 405<section>
207 <title>Distcc Monitors</title> 406<title>Distcc Monitors</title>
208 <body> 407<body>
209 <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> 408
210 <p>The other monitor is only turned on if you enabled <c>gtk</c> in your <c>USE</c> flags. This one is GTK+ based and runs in an X environment, and it is quite lovely.</p> 409<p>
211 <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> 410Distcc ships with two monitors. The text-based one is always built and is
411called <c>distccmon-text</c>. Running it for the first time can be a bit
412confusing, but it is really quite easy to use. If you run the program with no
413parameter it will run once. However, if you pass it a number it will update
414every N seconds, where N is the argument you passed.
415</p>
416
417<p>
418The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c>
419in your <c>USE</c> flags. This one is GTK+ based, runs in an X environment
420and it is quite lovely.
421</p>
422
212 <pre caption="Starting the monitors"> 423<pre caption="Starting the monitors">
213<i>sudo -u portage distccmon-text N</i> 424# <i>distccmon-text N</i>
214<codenote>Or you can start the graphical monitor...</codenote> 425<comment>(Or)</comment>
215<i>sudo -u portage distccmon-gnome</i> 426# <i>distccmon-gnome</i>
216<note>If you aren't using <c>userpriv</c> in your FEATURES, you should not use the '-u portage' part.</note> 427<comment>To monitor Portage's distcc usage you can use:</comment>
428# <i>DISTCC_DIR=`portageq envvar DISTCC_DIR` distccmon-text N</i>
429<comment>(Or)</comment>
430# <i>DISTCC_DIR=`portageq envvar DISTCC_DIR` distccmon-gnome</i>
217 </pre> 431</pre>
432
433<impo>
434Notice the backticks above. <c>portageq</c> is a part of Portage that will
435return a piece of information (in this case what DISTCC_DIR is set to). For
436simplicity, most users can use <c>DISTCC_DIR=/var/tmp/portage/.distcc
437distccmon-text N</c>
438</impo>
439
218 </body> 440</body>
219 </section> 441</section>
220</chapter>
221
222<chapter> 442</chapter>
223 <title>Future Plans for Distcc and Gentoo</title>
224 <section>
225 <title>distcc-subnetscan</title>
226 <body>
227 <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>
228 <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>
229 </body>
230 </section>
231 <section>
232 <title>distcc-config</title>
233 <body>
234 <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>
235 </body>
236 </section>
237</chapter>
238
239</guide> 443</guide>

Legend:
Removed from v.1.3  
changed lines
  Added in v.1.25

  ViewVC Help
Powered by ViewVC 1.1.20