Example
shmux -o /tmp/demo -a lnregex -M 2 -t -c 'echo $$; sleep 1; if test "$$" -gt 1600; then echo "Standard Output"; else echo "Standard Error" 1>&2; fi' somehost host anotherhost randomhost oink
- Outputs will be saved under
/tmp/demo - Outputs will be analyzed on the fly, line by line
- There is a maximum limit of 2 children running at any time
- A test will be run on each target prior to running the command (to ensure things are sane)
- The command will be run on 5 target hosts:
somehost, host, anotherhost randomhost and oink - The command run will simply:
- echo its PID onto standard output
- sleep for 1 second
- echo "Standard Output" on its standard output if its PID is greater than 16000
- echo "Standard Error" on its standard error if its PID is lower than 16000
As soon as it starts, shmux spawns two children processes (shown as 2 Active)
Probably as a direct result, the load average slightly raises
This frame shows that 2 tests were completed successfully (2 OK), there is at this instant only one active child.
By default, shmux will only run the command on one target first, and then more once the first command has completed successfully.
(The careful reader will note that another child should have been spawned to run a test command. This was a minor bug which was fixed after these screen shots were taken.)
First line of output from the command running on host.
The command running on host sent output on the standard error (shown
in bold) which (by default) is considered an error by the analyzer as
shown here.
The command has also completed (shown as 1 Done).
As a result, shmux pauses.
(This default behaviour is configurable.)
Once the user presses the enter key, shmux resumes activity, spawning 2 children right away.
Another test has succeeded.
First line of output from the command running on somehost
More output from the command running on somehost,
first line of output from the command running on anotherhost.
Another target is done.
More output from the command running on anotherhost.
Another target is done.
Another test succeeds.
The last test succeeds.
First line of output from randomhost.
First line of output from oink.
More output from randomhost. As with host this is considered to
be erroneous.
At this point shmux would pause again (by default), but as there are no more work to be done, it can't do really so. (Running children cannot be paused.)
More output from oink, again, considered to be erroneous
Upon completion, shmux provides a summary of what was done.
