Implement "exec-on-exit" command #26
Assignees
Milestone
Comments
nrdvana
added a commit
that referenced
this issue
Feb 21, 2014
Commands are no longer states. They may divert flow to a state though, like the statedump command. Commands are simpler, and just return true/false to indicate success or failure, and the caller handles displaying the error message. There are also a lot of helper functions to reduce the code needed for each one. The logic for overflow is much more sensible now, and the timeouts for a full pipe are configurable with a new command "comm.event_timeout". The terminate command has been revised to match the new API doc. Since the default is now to exit with an error code (since abrupt termination is mostly an error) I updated all the testcases to look for that code. The exec-on-exit feature now supports passing an argument list to the target. They can be specified on the commandline as a single tab-delimited argument. Logging is now actually asynchronous. (formerly forgot to set non-blocking on the file handle) The testing library now properly handles SIGPIPE when writing to a daemonproxy that dies. fixes #24, refs #26, refs #27, refs #23
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This command should set the exec-on-exit argument list (which can also be specified on the command line).
The text was updated successfully, but these errors were encountered: