Chris Lumens

Hopefully we're just about at a point where we don't need to do anything to every test file. We're starting to have so many that it's obnoxious to do.

I've rebased this on master. It's good to go now.

Let's just go ahead and call this a draft for the moment.

What might be some good ways to test this set? I've run it through cts-lab and that's all good so far, but I'm not sure if that is really comprehensive...

Updated with a couple patches at the end, changed terminology in commit messages to refer to "new message handling", and moved some functions around. I've run everything through cts-lab and...

> We need to repeat the attrd_updater testing with newer cluster + older remote and vice versa. Testing a mixed-version cluster (older and newer cluster nodes) might also be nice...

Updated to support multiple-attribute requests. One thing I haven't tested yet is multiple clients waiting on ACKs at the same time. Everything happens so quickly that it seems difficult to...

I kind of hate to suggest it, but what about a CTSlab test for this kind of stuff?

I've just been playing around with this for a few minutes here and in my unscientific opinion, signals appear a bit sharper. That is, they stick out from the noise...

We have a long-standing project in pacemaker to move functionality from command line tools into libraries. Then the tools just wrap the library calls. I could start working on converting...