Hi,
wrt
https://bugzilla.redhat.com/show_bug.cgi?id=909341
I suggest 2 possible fixes.
1) To provide some intermediate simple script, for instance rhq-background-launcher.sh:
#!/bin/sh
$@&
and then calling the launch script with ./rhq-background-launcher.sh
${path_to_standalone.sh}
I was trying it and it solves the problem (trying it only in terminal, but it should work
also for the case agent has executed the script).
2) Search for the "trap" commands in the launch script (they are the culprit)
and comment them out before the execution, then uncomment them out (or create a temp. copy
just for 1 usage).
I think the fix should be hidden to the end user. If you have any other suggestions please
respond to this email.
JK