When calling external scripts (bash for example), I get child process exited abnormally, like below. If I add the "&" at the end of the scripts, it would be okay of course like stated in the guide page. I do not want to add the & because I need the script to be completely done first, error or not, before I can move on. I don't want the process to run in the background for particular scripts. From my limited researching, I see this error is expected if the script is exited with a negative return code or it's not "0", so the installer take that as an error and reported it this way? I like to know how can we "fix" this error, or somehow tell the installer that the script with exit code "1234" is okay.
07-09-2019 10:42:49: Error running /bin/sh "scripts.sh": child process exited abnormally
<!-- Append & to the arguments so the program is executed in the background and the parent process, the installer, can successfully end. If you do not launch it in background, the installer will remain running until the launched application is closed -->
Please sign in to leave a comment.