Add hostkey reporting interval to watchdog.

return something!

reinstall remote tarballs everytime we change our mind.

Also, make sure rusage function processes updates.

client to here.  Policies are things like only plab service slices do
rusage reports and local nodes don't check for cvsup updates, etc.
Maybe these should all be sitevars, but I didn't really want to have
20 different watchdog-related timeout values.

Note: the detection of what is a plab service slice is a hack right
now (string ends in "-20").  Kirk will be giving me a better way RSN.

Now ps will show info about the request being processed,
or the total number of requests processed when idle.

1. make sure we send an immediate isalive on startup rather than waiting
   for the first interval to pass
2. don't fall back on a tcp call on plab nodes, this just eventually hangs
   all our tmcds on flaky plab machines

Also, remove another ball of lint.

	- check intervals driven by sitevars delivered by TMCD command
	- handles rusage stats return on plab nodes
It is now a single process and executes any auxilliary scripts synchronously.
This may prove to be unwieldy in the face of long running scripts like
update.  If so, we'll have to add all that fork/exec/waitpid mucky-muck.

Random values were causing random failures on plab.
Also cleaned up some double colons in error messages.

if the pubkey is too large to fit in the default buffer.

Also added a F_MAXLOG value that you can set to force maximum logging
for a particular command.

Fix an off-by-one in the OUTPUT macro

watchdog process based on sitevars.

Also added a command flags field to take care of a couple of misc. attributes
like whether a command can be allowed from a remote site via UDP or whether
we should not perform as much logging.

Sometime we might want to offer an option on the experiment create page to
automatically setup the 4th partition for people.

For now they can run it as /usr/testbed/bin/mkextrafs

has changed.  Not a big deal when updates are 12 hours apart, but if we
shorten the interval, it will help keep gratuitous updates down.

Put a timestamp in the log when watchdog starts.

prevented ntpdrift updates

instead of outside since the BEGIN block is run first.

node id (which could be virtual).

"client-install"