swc

commit 4ab2053e37a79b3da06b70c8abd72aae85568b83
parent c0e9489044f45440542aab10d21031a35cb20a91
Author: Michael Forney <mforney@mforney.org>
Date:   Tue, 13 Nov 2018 23:19:05 -0800

launch: Don't need to forward signals

The child process will get the signals because they are in the same
process group.

Diffstat:
M
launch/launch.c
 | 
14
--------------

1 file changed, 0 insertions(+), 14 deletions(-)
diff --git a/launch/launch.c b/launch/launch.c
@@ -199,12 +199,6 @@ handle_usr2(int signal)
 }
 
 static void
-forward_signal(int signal)
-{
-	kill(child_pid, signal);
-}
-
-static void
 handle_socket_data(int socket)
 {
 	char buffer[BUFSIZ];
@@ -467,18 +461,10 @@ main(int argc, char *argv[])
 	if (sigaction(SIGUSR2, &action, NULL) == -1)
 		die("failed to register signal handler for SIGUSR2:");
 
-	action.sa_handler = &forward_signal;
-	if (sigaction(SIGINT, &action, NULL) == -1)
-		die("failed to register signal handler for SIGINT:");
-	if (sigaction(SIGTERM, &action, NULL) == -1)
-		die("failed to register signal handler for SIGTERM:");
-
 	sigfillset(&set);
 	sigdelset(&set, SIGCHLD);
 	sigdelset(&set, SIGUSR1);
 	sigdelset(&set, SIGUSR2);
-	sigdelset(&set, SIGINT);
-	sigdelset(&set, SIGTERM);
 	sigprocmask(SIG_SETMASK, &set, NULL);
 
 	if (!vt) {