/[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.46
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.46 2013/07/24 20:03:06 swift Exp $ -->
4 4
5<guide link="/doc/en/distcc.xml"> 5<guide disclaimer="obsolete" redirect="https://wiki.gentoo.org/wiki/Distcc">
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> 11</author>
12 12<author title="Editor">
13 <mail link="vapier@gentoo.org">Mike Frysinger</mail>
14</author>
15<author title="Editor">
16 <mail link="erwin@gentoo.org">Erwin</mail>
17</author>
18<author title="Editor">
19 <mail link="swift@gentoo.org">Sven Vermeulen</mail>
20</author>
21<author title="Editor">
22 <mail link="pylon@gentoo.org">Lars Weiler</mail>
23</author>
13<author title="Reviewer"> 24<author title="Reviewer">
14 <mail link="swift@gentoo.org">swift@gentoo.org</mail> 25 <mail link="blubber@gentoo.org">Tiemo Kieft</mail>
15</author> 26</author>
16
17<author title="Reviewer"> 27<author title="Editor">
18 <mail link="blubber@gentoo.org">blubber@gentoo.org</mail> 28 <mail link="nightmorph"/>
19</author> 29</author>
20 30
31<abstract>
32This document serves as a HOWTO for using distcc with Gentoo.
33</abstract>
34
35<!-- The content of this document is licensed under the CC-BY-SA license -->
36<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
37<license/>
38
21<version>1.1</version> 39<version>3</version>
22<date>September 08, 2003</date> 40<date>2013-07-24</date>
23
24<abstract>This document serves as a HOWTO for using distcc with Gentoo.</abstract>
25 41
26<chapter> 42<chapter>
27 <title>Introduction</title> 43<title>Introduction</title>
28 <section> 44<section>
29 <title>What is distcc?</title> 45<title>What is distcc?</title>
30 <body> 46<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> 47
48<p>
49Distcc is a program designed to distribute compiling tasks across a network to
50participating hosts. It is comprised of a server, <c>distccd</c>, and a client
51program, <c>distcc</c>. Distcc can work transparently with <uri
52link="http://ccache.samba.org">ccache</uri>, Portage, and Automake with a
53little setup.
54</p>
55
32 </body> 56</body>
33 </section> 57</section>
34
35 <section> 58<section>
36 <title>Dependancies</title> 59<title>Using distcc to bootstrap</title>
37 <body> 60<body>
38 <pre caption="Distcc Dependancies"> 61
39&gt;=sys-apps/portage-2.0.46-r11 62<p>
40&gt;=sys-devel/gcc-config-1.3.1 63If you are planning on using distcc to help you bootstrap a Gentoo
41&gt;sys-apps/shadow 64installation, make sure you read the section <uri link="#bootstrapping">Using
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> 65distcc to Bootstrap</uri>, which is situated further down in this document.
43&gt;=x11-libs/gtk+-2.2.1 66</p>
44 </pre> 67
45 </body> 68</body>
46 </section> 69</section>
47</chapter> 70</chapter>
48 71
49<chapter> 72<chapter>
50 <title>Setup</title> 73<title>Setup</title>
51 <section> 74<section>
52 <title>Setting up Portage to use Distcc</title> 75<title>Dependencies</title>
53 <body> 76<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> 77
55 <pre caption="Integrating Distcc and Portage"> 78<p>
79In order to use Distcc, all of the computers on your network need to have the
80same GCC versions. For example, mixing 3.3.x (where the x varies) is okay, but
81mixing 3.3.x with 3.2.x <b>may</b> result in compilation errors or runtime
82errors.
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">
56# <i>emerge distcc</i> 104# <i>emerge distcc</i>
105</pre>
106
107<impo>
108Remember, you must be sure to install distcc on all of your participating
109machines.
110</impo>
111
112</body>
113</section>
114<section>
115<title>Setting up Portage to use Distcc</title>
116<body>
117
118<p>
119Setting up Portage to use distcc is easy. Execute the following steps on
120each system that should participate in the distributed compiling:
121</p>
122
123<pre caption="Integrating Distcc and Portage">
124# <i>emerge distcc</i>
57# <i>nano -w /etc/make.conf</i> 125# <i>nano -w /etc/portage/make.conf</i>
58<codenote>Edit your FEATURES flags to include &quot;distcc&quot;</codenote> 126<comment>(Set N to a suitable number for your particular setup)</comment>
127<comment>(A common strategy is setting N as twice the number of total CPUs + 1 available)</comment>
128MAKEOPTS="-jN"
129<comment>(Add distcc to your FEATURES)</comment>
130FEATURES="distcc"
59 </pre> 131</pre>
60 132
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> 133</body>
134</section>
135<section>
136<title>Specifying Participating Hosts</title>
137<body>
138
139<p>
140Use the <c>distcc-config</c> command to set the list of hosts. Here is an
141example of some hosts that might be in your list:
142</p>
143
62 <pre caption="Examples of host definitions"> 144<pre caption="Examples of host definitions">
63192.168.0.1 192.168.0.2 192.168.0.3 145192.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 146192.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 147192.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 148@192.168.0.1 @192.168.0.2:/usr/bin/distccd 192.168.0.3
149<comment>(There are also several other methods of setting up hosts. See the
150distcc manpage for more details.)</comment>
151<comment>If you wish to compile on the local machine you should put 'localhost'
152in the hosts list. Conversely if you do not wish to use the local machine to
153compile (which is often the case) omit it from the hosts list. On a slow
154machine using localhost may actually slow things down. Make sure to test your
155settings for performance.</comment>
67 </pre> 156</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> 157
69 <p>A sample command to set the hosts (for line 1) is:</p> 158<p>
159It may all look complicated, but in most cases a variant of line 1 or 2 will
160work.
161</p>
162
163<p>
164Since most people won't be using lines 3 or 4, I'll <uri
165link="http://distcc.samba.org/man/distcc_1.html">refer to</uri> the distcc
166docs (man distcc) for more information, which includes being able to run distcc
167over an SSH connection.
168</p>
169
170<p>
171For instance, to set the first line in the previous example:
172</p>
173
70 <pre caption="Sample command to set the hosts"> 174<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> 175# <i>/usr/bin/distcc-config --set-hosts "192.168.0.1 192.168.0.2 192.168.0.3"</i>
72 </pre> 176</pre>
73 177
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> 178<p>
75 <pre caption="Final steps in make.conf"> 179Edit <path>/etc/conf.d/distccd</path> to your needs and be sure to set the
76# <i>nano -w /etc/make.conf</i> 180<c>--allow</c> directive to allow only hosts you trust. For added security,
77MAKE_OPTS=-jN 181you should also use the <c>--listen</c> directive to tell the distcc daemon
182what IP to listen on (for multi-homed systems). More information on distcc
183security can be found at <uri
184link="http://distcc.samba.org/security.html">Distcc Security Design</uri>.
185</p>
186
187<impo>
188It is important to use --allow and --listen. Please read the distccd manpage
189or the above security document for more information.
190</impo>
191
192
193<p>
194Now start the distcc daemon on all the participating computers:
195</p>
196
197<pre caption="Starting the distcc daemon">
198<comment>(Add distccd to the default runlevel)</comment>
199# <i>rc-update add distccd default</i>
200<comment>(Start the distcc daemon)</comment>
201# <i>/etc/init.d/distccd start</i>
78 </pre> 202</pre>
203
79 </body> 204</body>
80 </section> 205</section>
81 <section> 206<section>
82 <title>Setting up Distcc to Work With Automake</title> 207<title>Setting up Distcc to Work With Automake</title>
83 <body> 208<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> 209
210<p>
211This is, in some cases, easier than the Portage setup. What you have to do is
212update your <c>PATH</c> variable to include <path>/usr/lib/distcc/bin</path>
213in front of the directory that contains <c>gcc</c> (<path>/usr/bin</path>).
214However, there is a caveat. If you use ccache you have to put distcc after
215the ccache part:
216</p>
217
85 <pre caption="Setting your path"> 218<pre caption="Setting your path">
86# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i> 219# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
220<comment>(You can put this in your ~/.bashrc or equivalent file to have the PATH
221set every time you log in)</comment>
87 </pre> 222</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> 223
224<p>
225Then, as you would normally type <c>make</c>, you would type <c>make -jN</c>
226(where N is an integer). The value of N depends on your network and the types
227of computers you are using to compile. Test your own settings to find the
228number that yields the best performance.
229</p>
230
89 </body> 231</body>
90 </section> 232</section>
91</chapter> 233</chapter>
92 234
93<chapter> 235<chapter>
94 <title>Cross-Compiling</title> 236<title>Cross-Compiling</title>
95 <section> 237<section>
96 <title>A Note on Cross-Compiling</title>
97 <body> 238<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> 239
240<p>
241Cross-compiling is using one architecture to build programs for another
242architecture. This can be as simple as using an Athlon (i686) to build a
243program for a K6-2 (i586), or using a Sparc to build a program for a ppc. This
244is documented in our <uri link="/doc/en/cross-compiling-distcc.xml">DistCC
245Cross-compiling Guide</uri>.
246</p>
247
99 </body> 248</body>
100 </section> 249</section>
250</chapter>
251
252<chapter id="bootstrapping">
253<title>Using Distcc to Bootstrap</title>
101 <section> 254<section>
102 <title>A Personal Note on Cross-compiling</title> 255<title>Step 1: Configure Portage</title>
103 <body> 256<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> 257<!--
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> 258Note that this will need to become a link to the old 2005.1 networked handbooks
259once the 2006.0 handbooks are released. Until then, the link can stay.
260-->
261<p>
262Boot your new box with a Gentoo Linux LiveCD and follow the <uri
263link="/doc/en/handbook/handbook-x86.xml?part=1">installation instructions</uri>
264up until the bootstrapping part. (See the <uri
265link="/doc/en/faq.xml#stage12">Gentoo FAQ</uri> for more information about
266bootstrapping.) Then configure Portage to use distcc:
267</p>
268
269<pre caption="Preliminary Setup">
270# <i>nano -w /etc/portage/make.conf</i>
271<comment>(Add distcc to the FEATURES</comment>
272FEATURES="distcc"
273<comment>(Modify MAKEOPTS to include -jN, where N is twice the number of CPUs
274+1 available)</comment>
275MAKEOPTS="-jN"
276</pre>
277
278<pre caption="Setting your path">
279# <i>export PATH="/usr/lib/ccache/bin:/usr/lib/distcc/bin:${PATH}"</i>
280</pre>
281
106 </body> 282</body>
107 </section> 283</section>
284<section>
285<title>Step 2: Getting Distcc</title>
286<body>
287
288<p>
289Install distcc:
290</p>
291
292<pre caption="Getting Distcc on the new box">
293# <i>USE='-*' emerge --nodeps sys-devel/distcc</i>
294</pre>
295
296</body>
297</section>
298<section>
299<title>Step 3: Setting Up Distcc</title>
300<body>
301
302<p>
303Run <c>distcc-config --install</c> to setup distcc:
304</p>
305
306<pre caption="Final distcc setup">
307<comment>(Substitute host1, host2, ... with the IP number(s) of the
308participating hosts)</comment>
309# <i>/usr/bin/distcc-config --set-hosts "localhost host1 host2 host3 ..."</i>
310<comment>An example: <i>/usr/bin/distcc-config --set-hosts "localhost
311192.168.0.4 192.168.0.6"</i></comment>
312</pre>
313
314<p>
315Distcc is now set up to bootstrap! Continue with the official installation
316instructions and <e>do not forget</e> to re-emerge distcc after <c>emerge
317system</c>. This is to make sure that all of the dependencies you want are
318installed as well.
319</p>
320
321<note>
322During bootstrap and <c>emerge system</c> distcc may not appear to be used.
323This is expected as some ebuilds do not work well with distcc, so they
324intentionally disable it.
325</note>
326
327</body>
328</section>
108</chapter> 329</chapter>
109 330
110<chapter> 331<chapter>
111 <title>Known Problems With Distcc</title> 332<title>Troubleshooting</title>
112 <section> 333<section>
113 <title>Portage Doesn't Work With Distcc</title> 334<title>Some Packages Don't Use Distcc</title>
114 <body> 335<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> 336
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> 337<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> 338As you emerge various packages, you'll notice that some of them aren't being
339distributed (and aren't being built in parallel). This may happen because the
340package's Makefile doesn't support parallel operations or the maintainer of the
341ebuild has explicitly disabled parallel operations due to a known problem.
342</p>
343
344<p>
345Sometimes distcc might cause a package to fail to compile. If this happens
346for you, please <uri link="http://bugs.gentoo.org">report</uri> it to us.
347</p>
348
118 </body> 349</body>
119 </section> 350</section>
120 <section> 351<section>
121 <title>Mozilla and Xfree</title> 352<title>Mixed GCC Versions</title>
122 <body> 353<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> 354
124 <p>That isn't to say that sometimes distcc will cause a package to fail to compile.</p> 355<p>
356If you have different GCC versions on your hosts, there will likely be very
357weird problems. The solution is to make certain all hosts have the same GCC
358version.
359</p>
360
361<p>
362Recent Portage updates have made Portage use <c>${CHOST}-gcc</c> instead of
363<c>gcc</c>. This means that if you're mixing i686 machines with other types
364(i386, i586) you will run into problems. A workaround for this may be to
365<c>export CC='gcc' CXX='c++'</c> or to put it in <path>/etc/portage/make.conf</path>.
366</p>
367
368<impo>
369Doing this explicitly redefines some behaviour of Portage and may have some
370weird results in the future. Only do this if you're mixing CHOSTs.
371</impo>
372
373
125 </body> 374</body>
126 </section> 375</section>
376<section>
377<title>-march=native</title>
378<body>
379
380<p>
381Starting with GCC 4.3.0, the compiler supports the <c>-march=native</c> switch
382which turns on CPU autodetection and optimizations that are worth being enabled
383on the processor the GCC is running at. This is a problem with <c>distcc</c> as
384it allows mixing of code optimized for different processors (like AMD Athlon and
385Intel Pentium). <e>Don't</e> use <c>-march=native</c> or <c>-mtune=native</c> in
386your <c>CFLAGS</c> or <c>CXXFLAGS</c> when compiling with <c>distcc</c>.
387</p>
388
389</body>
390</section>
127</chapter> 391</chapter>
128 392
129<chapter> 393<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> 394<title>Distcc Extras</title>
206 <section> 395<section>
207 <title>Distcc Monitors</title> 396<title>Distcc Monitors</title>
208 <body> 397<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> 398
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> 399<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> 400Distcc ships with two monitors. The text-based one is always built and is
401called <c>distccmon-text</c>. Running it for the first time can be a bit
402confusing, but it is really quite easy to use. If you run the program with no
403parameter it will run once. However, if you pass it a number it will update
404every N seconds, where N is the argument you passed.
405</p>
406
407<p>
408The other monitor is only turned on if you enabled <c>gtk</c> or <c>gnome</c>
409in your <c>USE</c> flags. This one is GTK+ based, runs in an X environment
410and it is quite lovely. For Gentoo the GUI monitor has been called
411<c>distccmon-gui</c> for less confusion. Elsewhere it may be referred to as
412<c>distccmon-gnome</c>.
413</p>
414
212 <pre caption="Starting the monitors"> 415<pre caption="Starting the monitors">
213<i>sudo -u portage distccmon-text N</i> 416# <i>distccmon-text N</i>
214<codenote>Or you can start the graphical monitor...</codenote> 417<comment>(Or)</comment>
215<i>sudo -u portage distccmon-gnome</i> 418# <i>distccmon-gui</i>
216<note>If you aren't using <c>userpriv</c> in your FEATURES, you should not use the '-u portage' part.</note> 419<comment>To monitor Portage's distcc usage you can use:</comment>
420# <i>DISTCC_DIR="/var/tmp/portage/.distcc/" distccmon-text N</i>
421<comment>(Or)</comment>
422# <i>DISTCC_DIR="/var/tmp/portage/.distcc/" distccmon-gui</i>
217 </pre> 423</pre>
424
425<impo>
426If your distcc directory is elsewhere, change the DISTCC_DIR variable
427accordingly.
428</impo>
429
218 </body> 430</body>
219 </section> 431</section>
220</chapter>
221
222<chapter> 432</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> 433</guide>

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

  ViewVC Help
Powered by ViewVC 1.1.20