A lot of our tests are written in a multi-host fashion using rhts-sync-block and rhts-sync-set to schedule/order commands running across multiple servers.  

When we are writing and testing them, this means we have to manually watch and press enter on the blocks after a set would have run.  Although useful functionality, it would help also if there was a way to automate the "set".  Something that the "block" could see it without having to run the scripts as jobs in beaker.

So, a manual way to automate rhts-sync-block/set functionality outside of a beaker job, (I think), is what I'm talking about.  Or maybe just some functionality to replicate locally on the servers in question the mechanism that provides the rhts-sync function in a job?

A more complicated additional request here might be setting traps so that automated rhts-sync stop when a specific state is seen from a specific host.  That too might be even more useful for troubleshooting larger, more complicated test suites.

Thanks,
Scott