diff --git a/en_US.ISO8859-1/articles/portbuild/article.xml b/en_US.ISO8859-1/articles/portbuild/article.xml
index 884270d58a..632265a1ea 100644
--- a/en_US.ISO8859-1/articles/portbuild/article.xml
+++ b/en_US.ISO8859-1/articles/portbuild/article.xml
@@ -831,7 +831,7 @@ PKG_BIN=/usr/local/sbin/pkg
To free up resources, you will need to clean up client machines by
running build cleanup command. For example:
- &prompt.user; /var/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full
+ &prompt.user; /a/portbuild/scripts/build cleanup i386 8-exp 20080714120411 -full
If you forget to do this, then the old build
jails will not be cleaned up for 24 hours, and no
@@ -846,6 +846,11 @@ PKG_BIN=/usr/local/sbin/pkg
and it is less than the number of jobs that loads
thinks are in use, you are in trouble.
+
+ The following notes about mounting only apply to
+ connected nodes.
+
+
You may have problem with the umount
commands hanging. If so, you are going to have to use the
allgohans script to run an &man.ssh.1;
@@ -875,6 +880,11 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
You may also see messages about procfs.
+
+ The above is the end of the notes that apply only to
+ connected nodes.
+
+
After you have done all the above, remove the
${arch}/lock
file before trying to restart the build. If you do not,
@@ -921,7 +931,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
scripts/stats ${branch}
command shows the number of packages already built.
- Running cat /var/portbuild/*/loads/*
+ Running cat /a/portbuild/*/loads/*
shows the client loads and number of concurrent builds in
progress. The files that have been recently updated are the clients
that are online; the others are the offline clients.
@@ -958,7 +968,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
it if not.
Keep an eye on &man.df.1; output. If the
- /var/portbuild file system becomes full
+ /a/portbuild file system becomes full
then Bad Things happen.
The status of all current builds is generated periodically
@@ -1212,7 +1222,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
Most of the information in this section is obsolete
- as of 2013.
+ as of 2013 and needs to be rewritten.
Experimental patches builds are run from time to time to
@@ -1271,9 +1281,9 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
branch is the control branch, and the 8-exp
branch is the experimental patches branch):
- &prompt.user; cd /var/portbuild/i386/8-exp/errors
+ &prompt.user; cd /a/portbuild/i386/8-exp/errors
&prompt.user; find . -name \*.log\* | sort > /tmp/8-exp-errs
-&prompt.user; cd /var/portbuild/i386/8/errors
+&prompt.user; cd /a/portbuild/i386/8/errors
&prompt.user; find . -name \*.log\* | sort > /tmp/8-errs
@@ -1336,7 +1346,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
rebuild of the affected packages under the control
branch:
- &prompt.user; cd /var/portbuild/i386/8/ports
+ &prompt.user; cd /a/portbuild/i386/8/ports
The following example is obsolete
@@ -1351,7 +1361,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
The following command will set up the control branch for
the partial build:
- &prompt.user; /a/portbuild/scripts/dopackages.wrapper 8 -noportsvcs -nobuild -novcs -nofinish
+ &prompt.user; /a/portbuild/scripts/dopackages.wrapper i386 8 -noportsvcs -nobuild -novcs -nofinish
The builds must be performed from the
@@ -1359,7 +1369,7 @@ umount: Cleanup of /x/tmp/8-exp/chroot/53837/compat/linux/proc failed!
initially be empty except for the Makefile symlink. If this
symlink does not exist, it must be created:
- &prompt.user; cd /var/portbuild/i386/8/packages/All
+ &prompt.user; cd /a/portbuild/i386/8/packages/All
&prompt.user; ln -sf ../../Makefile .
&prompt.user; make -k -j<#> <list of packages to build>
@@ -3072,7 +3082,7 @@ qmanager
Note the time and failure mode (e.g., paste in the
relevant console output) in
- /var/portbuild/${arch}/reboots
+ /a/portbuild/${arch}/reboots