Add nohup to 'Start SOL Console Logging' to keep process alive.
When running in debug mode, which generates much more output, the SOL
console process would start and then die shortly after. This must have
to do with the subprocesses association with the pty of the parent.
By launching the child process with nohup, we break all ties to the
parent and eliminate this problem.
Change-Id: I25288eeceb32c683711199c5491aa291bec5c17c
Signed-off-by: Michael Walsh <micwalsh@us.ibm.com>
diff --git a/lib/utils.robot b/lib/utils.robot
index e453db5..e68dd90 100755
--- a/lib/utils.robot
+++ b/lib/utils.robot
@@ -604,7 +604,8 @@
${sub_cmd_buf}= Create OS Console Command String
# Routing stderr to stdout so that any startup error text will go to the
# output file.
- ${cmd_buf}= Catenate ${sub_cmd_buf} > ${log_file_path} 2>&1 &
+ # nohup detaches the process completely from our pty.
+ ${cmd_buf}= Catenate nohup ${sub_cmd_buf} &> ${log_file_path} &
Rdpissuing ${cmd_buf}
${rc} ${output}= Run And Return Rc And Output ${cmd_buf}
# Because we are forking this command, we essentially will never get a