cron daily, on the fs node (ops) as root. Uses lots of configure variables
so that it does the right thing in any installation, without any
customization.

One possible caveat regarding quotas: If FS_NODE != USERNODE, they don't
have a login on the fs machine. So checking their quota won't work unless
the rpc.rquotad(8) daemon is running on FS_NODE, which we currently don't
do.

In order to do this right, I had to add a new configure var,
FS_WITH_QUOTAS, that has a space separated list of file systems that have
quotas enabled. (Ie the default is 'FS_WITH_QUOTAS="/q /users"'.) It
doesn't have any default, since I couldn't come up with a reasonable one.
All the defs files have been updated appropriately to define this new
variable.

options in the future, they'll get this one too.

Obviously, this won't scale to too many sites, so we'll have to
figure something else out.

Before:
The main defs file (ie for configure) had an entry for WWWDEFS that
pointed to a <@WWWDEFS@>-defs.php3 file in the www/ directory. The www
defs file loaded some values about web pages, URLs, and some web
configuration parameters.

Problem:
Anything that was only in the www defs file was not accessible in the rest
of the universe (ie perl, C, and any other non-web-page scripts). For
instance, you couldn't have a perl script send an email to a user with a
link to the web site.

Solution:
Nuke all the www-defs files, move any important values into the main
configure, and change the web defs infrastructure to respect that. This
also meant adding about 3 lines each to all of the configure defs files.
(There really are about 10 new values you can change in your defs file,
but in almost all cases, the default values are the right thing.)

Upgrading:
External sites will need to move a few variables from their www-defs file
into their configure defs file. The example file should make it pretty
obvious. They may also want to customize some of the other vars that are
mentioned in configure.in and www/defs.php3.in .

sense to comment the hell out of these files than to have
descriptions elsewhere (setup.txt)

Also, I want people to use these rather than the defaults, because the
defaults actually have some Utah-specific stuff, like $TBMAINSITE=1,
and enabling SFS and NSE support.