freebsd-ports/Tools/portbuild/scripts/reportload.sh

#!/bin/sh

b=/a/asami/portbuild
s=$b/scripts/reportload

echo -n ' chroot'
rm -rf $b/*/chroot/*

if [ -x $s ]; then
  $s &
  echo -n ' reportload'
fi
(1) Do not delete and recreate the chroot dir for every new package that is built. This saves a lot of time, especiall when the parallelism (the number of jobs per machine, not the number of machines) is low. However, the build script only blows away /usr/local and /usr/X11R6, so if there is a port that does some nasty things outside that area, all bets are off. (2) Better load balancing. Now, each machine reports its own load in a form of a text file, which the master merely aggregates to pick the lowest-loaded machine(s). Other than generally running faster (and more up-to-date) under loaded conditions, the master script will no longer hold up until a timeout when a machine goes down. 1999-01-26 03:06:24 +00:00			`#!/bin/sh`

Delete the chroot dirs before starting the load average reporting script so that a rebooting machine doesn't join the cluster in an unclean state. 1999-06-22 06:34:52 +00:00			`b=/a/asami/portbuild`
			`s=$b/scripts/reportload`

			`echo -n ' chroot'`
			`rm -rf $b//chroot/`
(1) Do not delete and recreate the chroot dir for every new package that is built. This saves a lot of time, especiall when the parallelism (the number of jobs per machine, not the number of machines) is low. However, the build script only blows away /usr/local and /usr/X11R6, so if there is a port that does some nasty things outside that area, all bets are off. (2) Better load balancing. Now, each machine reports its own load in a form of a text file, which the master merely aggregates to pick the lowest-loaded machine(s). Other than generally running faster (and more up-to-date) under loaded conditions, the master script will no longer hold up until a timeout when a machine goes down. 1999-01-26 03:06:24 +00:00
			`if [ -x $s ]; then`
			`$s &`
			`echo -n ' reportload'`
			`fi`