aboutsummaryrefslogtreecommitdiffstats
path: root/Tools
diff options
context:
space:
mode:
authorlinimon <linimon@FreeBSD.org>2010-12-01 10:23:14 +0800
committerlinimon <linimon@FreeBSD.org>2010-12-01 10:23:14 +0800
commit6f6c66f4e43ba08c6aadd04c315bbb9075429286 (patch)
treefe9a5ed2841a3732fb71758d141c7bd2c96f6f41 /Tools
parent3d11265a44d1674cac89be4c0d96deb6542c8832 (diff)
downloadfreebsd-ports-gnome-6f6c66f4e43ba08c6aadd04c315bbb9075429286.tar.gz
freebsd-ports-gnome-6f6c66f4e43ba08c6aadd04c315bbb9075429286.tar.zst
freebsd-ports-gnome-6f6c66f4e43ba08c6aadd04c315bbb9075429286.zip
Add some debug code to attempt to work around the "too many stale chroots"
problem, until it can be correctly understood and fixed.
Diffstat (limited to 'Tools')
-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}"