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

#!/bin/sh

if [ "$1" != "start" ]; then exit; fi

pb=/var/portbuild
s=$pb/scripts/reportload

echo -n ' chroot'
rm -rf $pb/*/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`

Make sure you're given the "start" argument before trying to start the script. 2000-09-27 00:58:31 +00:00			`if [ "$1" != "start" ]; then exit; fi`

Pull in configuration variables from /var/portbuild/portbuild.conf. /var/portbuild is the new designated home of the portbuild setup, and is expected to be a symlink to wherever you choose to put the stuff. Also, change reportload to use /var/portbuild to store temporary files. Seems there are some bugs in the null mount code that make the files inaccessible if you are using an NFS root. 2000-09-27 01:41:44 +00:00			`pb=/var/portbuild`
			`s=$pb/scripts/reportload`
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
			`echo -n ' chroot'`
Pull in configuration variables from /var/portbuild/portbuild.conf. /var/portbuild is the new designated home of the portbuild setup, and is expected to be a symlink to wherever you choose to put the stuff. Also, change reportload to use /var/portbuild to store temporary files. Seems there are some bugs in the null mount code that make the files inaccessible if you are using an NFS root. 2000-09-27 01:41:44 +00:00			`rm -rf $pb//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`