os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

More markup fixes.

Browse source
This commit is contained in:
Mark Linimon 2012-11-19 05:08:07 +00:00
parent 06597c8590
commit 38dfdc36d7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=40090
1 changed files with 39 additions and 41 deletions
Download patch file Download diff file Expand all files Collapse all files

80
en_US.ISO8859-1/articles/portbuild/article.xml
View file

@ -760,7 +760,7 @@ PKG_BIN=/usr/local/sbin/pkg</programlisting>
package set. This can be accomplished with the following
invocation:</para>
<para><command><replaceable>path</replaceable>/qmanager/packagebuild <replaceable>amd64</replaceable> <replaceable>7-exp</replaceable> <replaceable>20080904212103</replaceable> <replaceable>aclock-0.2.3_2.tbz</replaceable></command></para>
<para>&prompt.root; <command><replaceable>path</replaceable>/qmanager/packagebuild <replaceable>amd64</replaceable> <replaceable>7-exp</replaceable> <replaceable>20080904212103</replaceable> <replaceable>aclock-0.2.3_2.tbz</replaceable></command></para>
</sect2>
</sect1>
@ -904,8 +904,8 @@ PKG_BIN=/usr/local/sbin/pkg</programlisting>
<title>Cleaning up a Build</title>
<para>To free up resources, you will need to clean up client machines by
running <command>build cleanup</command> command. For example:
<screen>&prompt.user; <userinput>/var/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full</userinput></screen></para>
running <command>build cleanup</command> command. For example:</para>
<screen>&prompt.user; <userinput>/var/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full</userinput></screen>
<para>If you forget to do this, then the old build
<literal>jail</literal>s will not be cleaned up for 24 hours, and no
@ -923,15 +923,15 @@ PKG_BIN=/usr/local/sbin/pkg</programlisting>
<para>You may have problem with the <command>umount</command>
commands hanging. If so, you are going to have to use the
<command>allgohans</command> script to run an &man.ssh.1;
command across all clients for that buildenv. For example:
<screen>ssh gohan24 df</screen>
command across all clients for that buildenv. For example:</para>
<screen>&prompt.user; ssh gohan24 df</screen>
will get you a df, and
<para>will get you a df, and
<screen>allgohans "umount -f pointyhat.freebsd.org:/var/portbuild/i386/8-exp/ports"
allgohans "umount -f pointyhat.freebsd.org:/var/portbuild/i386/8-exp/src"</screen>
<screen>&prompt.user; allgohans "umount -f pointyhat.freebsd.org:/var/portbuild/i386/8-exp/ports"
&prompt.user; allgohans "umount -f pointyhat.freebsd.org:/var/portbuild/i386/8-exp/src"</screen>
are supposed to get rid of the hanging mounts. You will have to
<para>are supposed to get rid of the hanging mounts. You will have to
keep doing them since there can be multiple mounts.</para>
<note>
@ -999,8 +999,8 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
<para>You can use <command>qclient</command> command to monitor the status
of build nodes, and to list the currently scheduled jobs:</para>
<para><command>python <replaceable>path</replaceable>/qmanager/qclient jobs</command></para>
<para><command>python <replaceable>path</replaceable>/qmanager/qclient status</command></para>
<screen>&prompt.user; <command>python <replaceable>path</replaceable>/qmanager/qclient jobs</command>
&prompt.user; <command>python <replaceable>path</replaceable>/qmanager/qclient status</command></screen>
<para>The
<command>scripts/stats <replaceable>${branch}</replaceable></command>
@ -1031,7 +1031,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
directory. The next time the cluster tries to build this port,
it will tar, compress, and copy the <literal>WRKDIR</literal>
to
<filename><replaceable>${arch}</replaceable>/<replaceable>${branch}</replaceable>/wrkdirs</filename>.
<filename><replaceable>${arch}</replaceable>/<replaceable>${branch}</replaceable>/wrkdirs/</filename>.
</para>
<para>If you find that the system is looping trying to build the
@ -1263,7 +1263,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
the package set was transferred successfully, remove the
package set that the new package set is to replace (in
<filename>~/w/ports/<replaceable>${arch}</replaceable></filename>),
and move the new set into place. (<literal>w/</literal> is
and move the new set into place. (<filename>w/</filename> is
merely a shortcut.)</para>
<para>For incremental builds, packages should be uploaded
@ -1428,7 +1428,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
<!-- XXX MCL obsolete -->
<para>The builds must be performed from the
<literal>packages/All</literal> directory. This directory should
<filename>packages/All</filename> directory. This directory should
initially be empty except for the Makefile symlink. If this
symlink does not exist, it must be created:</para>
@ -1608,12 +1608,13 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
3.5G on &i386;, <literal>PAE</literal>).
</para>
<para>
Required options:<screen>
Required options:</para>
<programlisting>
options NULLFS
options TMPFS</screen>
</para>
options TMPFS</programlisting>
<para>
Suggested options:<screen>
Suggested options:</para>
<programlisting>
options GEOM_CONCAT
options GEOM_STRIPE
options SHMMAXPGS=65536
@ -1622,30 +1623,29 @@ options SEMMNS=240
options SEMUME=40
options SEMMNU=120
options ALT_BREAK_TO_DEBUGGER</screen>
</para>
options ALT_BREAK_TO_DEBUGGER</programlisting>
<para>For <literal>PAE</literal>, it is not currently possible
to load modules. Therefore, if you are running an architecture
that supports Linux emulation, you will need to add:<screen>
that supports Linux emulation, you will need to add:</para>
<programlisting>
options COMPAT_LINUX
options LINPROCFS</screen>
</para>
options LINPROCFS</programlisting>
<para>Also for <literal>PAE</literal>, as of 20110912 you need
the following. This needs to be investigated:<screen>
the following. This needs to be investigated:</para>
<programlisting>
nooption NFSD # New Network Filesystem Server
options NFSCLIENT # Network Filesystem Client
options NFSSERVER # Network Filesystem Server</screen>
</para>
options NFSSERVER # Network Filesystem Server</programlisting>
</step>
<step>
<para>As root, do the usual build steps, e.g.:<screen>
<userinput>make -j4 buildworld</userinput>
<userinput>make buildkernel KERNCONF=<replaceable>${kernconf}</replaceable></userinput>
<userinput>make installkernel KERNCONF=<replaceable>${kernconf}</replaceable></userinput>
<userinput>make installworld</userinput></screen>
&prompt.root; <userinput>make -j4 buildworld</userinput>
&prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>${kernconf}</replaceable></userinput>
&prompt.root; <userinput>make installkernel KERNCONF=<replaceable>${kernconf}</replaceable></userinput>
&prompt.root; <userinput>make installworld</userinput></screen>
The install steps use <makevar>DESTDIR</makevar>.
</para>
</step>
@ -1687,10 +1687,10 @@ options NFSSERVER # Network Filesystem Server</screen>
</listitem>
<listitem>
<para>Also add the following users:<screen>
<para>Also add the following users:</para>
<programlisting>
squid:*:100:100::0:0:User &amp;:/usr/local/squid:/bin/sh
ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</screen>
</para>
ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</programlisting>
<para>Add them to <filename>etc/group</filename> as well.</para>
</listitem>
@ -1700,9 +1700,8 @@ ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</screen>
</listitem>
<listitem>
<para>In <filename>etc/crontab</filename>: add
<screen>* * * * * root /var/portbuild/scripts/client-metrics</screen>
</para>
<para>In <filename>etc/crontab</filename>: add</para>
<programlisting>* * * * * root /var/portbuild/scripts/client-metrics</programlisting>
</listitem>
<listitem>
@ -1713,21 +1712,20 @@ ganglia:*:102:102::0:0:User &amp;:/usr/local/ganglia:/bin/sh</screen>
</listitem>
<listitem>
<para>In <filename>etc/inetd.conf</filename>: add
<screen>infoseek stream tcp nowait nobody /var/portbuild/scripts/reportload</screen>
</para>
<para>In <filename>etc/inetd.conf</filename>: add</para>
<programlisting>infoseek stream tcp nowait nobody /var/portbuild/scripts/reportload</programlisting>
</listitem>
<listitem>
<para>We run the cluster on UTC. If you have not set the clock
to UTC:
<screen>cp /usr/share/zoneinfo/Etc/UTC etc/localtime</screen>
<programlisting>&prompt.root; cp /usr/share/zoneinfo/Etc/UTC etc/localtime</programlisting>
</para>
</listitem>
<listitem>
<para>Create the appropriate
<filename>etc/rc.conf</filename>. (If you are using
<filename>/etc/rc.conf</filename>. (If you are using
<literal>pxeboot</literal>, and have multiple,
different, machines, you will need to put those in
the override directories.)</para>