Right now buffbot 0 in gCLI does exactly the same as buffbot 1 (runs one buffbot cycle). It would be nifty if buffbot 0 ran a cycle but skipped the regular 1 minute delay at the end of that cycle.
The buffbot sleeps for a minute at the end of each iteration - even if it has just completed the last iteration and is about to exit. That seems silly. Revision 10254 does not sleep in that case.
