summaryrefslogtreecommitdiff
path: root/Tools/portbuild
diff options
context:
space:
mode:
authorMark Linimon <linimon@FreeBSD.org>2010-12-01 02:23:14 +0000
committerMark Linimon <linimon@FreeBSD.org>2010-12-01 02:23:14 +0000
commit439a77bd9057b24c88dc0d9428567bb23eb51a7d (patch)
tree61b4f856d85d6dd589f2a0d806bb0a787e81e956 /Tools/portbuild
parent- Update to 4.0.2 (diff)
Add some debug code to attempt to work around the "too many stale chroots"
problem, until it can be correctly understood and fixed.
Notes
Notes: svn path=/head/; revision=265483
Diffstat (limited to 'Tools/portbuild')
-rwxr-xr-xTools/portbuild/scripts/reportload7
1 files changed, 7 insertions, 0 deletions
diff --git a/Tools/portbuild/scripts/reportload b/Tools/portbuild/scripts/reportload
index 1d18043340a2..4088bb867395 100755
--- a/Tools/portbuild/scripts/reportload
+++ b/Tools/portbuild/scripts/reportload
@@ -22,6 +22,13 @@ for i in squid disk; do
fi
done
+# XXX MCL DEBUG 20100727
+# on occasion, a machine winds up with a huge number (> 300) of chroots.
+# When this happens, the following command takes more than a minute, and
+# pointyhat will pound it to death, resulting in 'kern.ipc.maxpipekva
+# exceeded; see tuning(7)'. So, as a workaround until the reason for the
+# stale chroots is understood, limit the time we allow this to run.
+ulimit -t 10
num=$(echo $(ls -1d ${scratchdir}/*/*/*/used ${scratchdir}/*/*/chroot/*/used 2>/dev/null| wc -l))
echo "arch=${arch}"