Download sopcast-3.2.6-6.R.i686.rpm for Fedora 28 from. Install Howto. Download the latest russianfedora-nonfree-release rpm from.
Errexit cannot work on programs run in the background, so this is unsurprising - the inline command is simply starting a background process, and that (starting a background process) succeeds, even if the process itself subsequently fails. If you call wait $! Subsequently, then errexit will be able to take effect, as the wait call will exit with the exit status of the program itself. (Of course, if you can call wait $!, then this raises the question of why you were backgrounding the initial program to start with). If you always want to kill the parent script if the child fails, you can do this instead: (sp-sc-auth '$sopUrl' 8809 8908 /dev/null kill $$) & $$ evaluates to the PID of the parent shell, not the subshell, so this will act accordingly. As for the segfault itself, 'program X segfaults' is a question too vague to be addressed here.
To even start debugging that, you'd need to collect the core dump created on its failure (enabling cores if necessary), install debug symbols for sopcast, and use gdb to collect a stack trace from the core file created on failure.
Errexit cannot work on programs run in the background, so this is unsurprising - the inline command is simply starting a background process, and that (starting a background process) succeeds, even if the process itself subsequently fails. If you call wait $! Subsequently, then errexit will be able to take effect, as the wait call will exit with the exit status of the program itself.
(Of course, if you can call wait $!, then this raises the question of why you were backgrounding the initial program to start with). If you always want to kill the parent script if the child fails, you can do this instead: (sp-sc-auth '$sopUrl' 8809 8908 /dev/null kill $$) & $$ evaluates to the PID of the parent shell, not the subshell, so this will act accordingly. As for the segfault itself, 'program X segfaults' is a question too vague to be addressed here. To even start debugging that, you'd need to collect the core dump created on its failure (enabling cores if necessary), install debug symbols for sopcast, and use gdb to collect a stack trace from the core file created on failure.