Is abort() enough to handle SIGTERM, SIGINT, SIGSEGV?

[legendbb]

Need to kill child process, if parent dies on SIGTERM, SIGINT or SIGSEGV.

Read MAN, default action to these signals are abnormal termination.

Created signal handler for these signals, send kill(child, SIGTERM) before abort().

Works as expected, just not sure if doing it this way covers all the termination actions default dispositions of those signals do.

I will need to restart the parent and repeat thousands time without reboot the system. Needs system stability.

exit() vs abort() could make some difference,
http://stackoverflow.com/questions/3...exit-and-abort

Please comment,

[Rubberman]

When you kill a parent process, no matter how, its attached children will also be terminated - no special handling required. Under other circumstances, if a child dies and the parent doesn't execute a wait() then the child will be a zombie until the parent terminates.

[histrungalot]

If you did something like:
xterm &
and then kill the old xterm, the xterm that you just started which would the a child of the first xterm and it doesn't go away. What happens in that case is the PPID of the xterm becomes 1 (init). So, if the parent goes away the child doesn't exit.

[Rubberman]

Processes can detach themselves from their parent process. This is how daemons work. Other applications, such as xterm do the same. My previous comment was for the general case, where the child process does not run as a detached process.