Answer :

SIGSTOP and SIGKILL are signals that processes cannot recognize and respond to. Similar to SIGSTOP, SIGTSTP can be intercepted and handled  process.

A process that is ready for SIGCONT is stopped in its tracks by the SIGSTOP and SIGTSTP signals. The process isn't always operating, so it can't execute the code to terminate when you send it a SIGTERM. Additionally, there are the signals SIGTTIN and SIGTTOU, which are produced by the TTY layer when a backgrounded process tries to read from or write to the terminal. In any case, they will stop (suspend) the process, much like SIGTSTP, even if they are stuck. Your CtrlZ sends a SIGTSTP to the process, but it doesn't seem to be working anymore. Rsyslogd primarily handles these issues, therefore it suspends the process while waiting for a SIGCONT or SIGKILL signal. The solution in this case is to also transmit SIGCONT after your SIGTERM so that the process can receive and process the signal.

Learn more about process here :

https://brainly.com/question/29559108

#SPJ4