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

Remove contractions.

Browse source 
Reminded by:	danger
This commit is contained in:
Mark Linimon 2007-06-21 22:40:40 +00:00
parent 9b2e3e1565
commit af51ff86f8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=30319
1 changed files with 9 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
en_US.ISO8859-1/articles/portbuild/article.sgml
View file

@ -356,7 +356,7 @@
</listitem>
</itemizedlist>
<para>If the last build finished cleanly you don't need to delete
<para>If the last build finished cleanly you do not need to delete
anything; if it was interrupted you just need to run
<literal>dosetupnodes</literal> on all clients for the
the relevant branch. <filename>errors/</filename>,
@ -524,7 +524,7 @@
of &man.tty.1; when you start the build, or use <command>ps x</command>
to identify it. You need to make sure that nothing else important
is running in this tty, e.g. <command>ps -t p1</command> or whatever.
If there isn't, you can just kill off the whole term easily with
If there is not, you can just kill off the whole term easily with
<command>pkill -t p1</command>; othewise issue a
<command>kill -HUP</command> in there by e.g.
<command>ps -t p1 | awk '{print $1}' | xargs kill -HUP</command>. Replace
@ -536,9 +536,9 @@
few minutes (check with <command>ps x</command> until they
all go away).</para>
<para>If you don't kill &man.make.1;, then it will spawn more jobs.
If you don't kill <command>dopackages</command>, then it will restart
the entire build. If you don't kill the <command>pdispatch</command>
<para>If you do not kill &man.make.1;, then it will spawn more jobs.
If you do not kill <command>dopackages</command>, then it will restart
the entire build. If you do not kill the <command>pdispatch</command>
processes, they'll keep going (or respawn) until they've built their
package.</para>
@ -553,7 +553,7 @@
build queue for that machine.</para>
<para>If you forget to do this, then the old build
<literal>chroot</literal>s won't be cleaned up for 24 hours, and no
<literal>chroot</literal>s will not be cleaned up for 24 hours, and no
new jobs will be dispatched in their place since
<hostid>pointyhat</hostid> thinks the job slot is still occupied.</para>
@ -587,7 +587,7 @@ umount: pointyhat.freebsd.org:/var/portbuild/i386/6-exp/ports: unknown file syst
umount: Cleanup of /x/tmp/6-exp/chroot/53837/compat/linux/proc failed!
/x/tmp/6-exp/chroot/53837/compat/linux/proc: not a file system root directory</screen>
The former 2 mean that that client didn't have those mounted;
The former 2 mean that that client did not have those mounted;
the latter 2 are a bug.</para>
<para>You may also see messages about <literal>procfs</literal>.</para>
@ -595,7 +595,7 @@ umount: Cleanup of /x/tmp/6-exp/chroot/53837/compat/linux/proc failed!
<para>After you have done all the above, remove the
<filename><replaceable>${arch}</replaceable>/lock</filename>
file before trying to restart the build. If you don't,
file before trying to restart the build. If you do not,
<filename>dopackages</filename> will simply exit.
</para>
@ -882,7 +882,7 @@ umount: Cleanup of /x/tmp/6-exp/chroot/53837/compat/linux/proc failed!
<para>Since the machine is shared, someone else may delete your
changes by mistake, so keep a copy of them in e.g. your home
directory on <hostid>freefall</hostid>. Don't use
directory on <hostid>freefall</hostid>. Do not use
<filename>tmp/</filename>; since <hostid>pointyhat</hostid>
itself runs some version of <literal>-CURRENT</literal>, you
can expect reboots (if nothing else, for updates).</para>