Signal understanding

[Empair]

Hi

i need explanation ... how it is possible this:

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <string.h>
#include <errno.h>
#include <fcntl.h>
#include <sys/wait.h>


void handler_readPipe(int sig)
{
    printf("I have signal ... \n");
}


int main () 
{
    int pid = fork();
    if(pid == -1)
    {
        return -1;
    }


    if(pid == 0)
    {
        sleep(5);
        kill(getppid(), SIGUSR1);
    }
    else
    {
        struct sigaction sa;
        sa.sa_handler = &handler_readPipe;
        sa.sa_flags = SA_RESTART;
        sigaction( SIGUSR1, &sa, NULL );
        sleep(10);
        printf("Message affter kill\n");
    }
   return(0);
}

How it is possible, if I kill a parent from a child, the process will run to the end anyway ... how is it possible to execute the line: printf ("Message affter kill \ n");

I have signal ... 
Message affter kill

[Salem]

Despite the name, kill doesn't kill a process per se.
Whether a process actually dies depends on the nature of
a) the signal being sent.
b) what signal handling the recipient task has installed.

For example, SIGKILL is always fatal to the recipient task (you cannot catch SIGKILL).

Ordinarily, the default action of USR1 is indeed to terminate the process.
signal(7) - Linux manual page

But you added a handler for it, so now your process runs your desired function, and then resumes (and no, this isn't what SA_RESTART means).
sigaction(2) - Linux manual page

[hamster_nz]

The important point you are missing is that most system calls can fail with EINTR

EINTR The call was interrupted by a signal before any data was read;
see signal(7).

In the case of sleep():

RETURN VALUE
Zero if the requested time has elapsed, or the number of seconds left to sleep, if the call was interrupted by a signal
handler.