[systemd-devel] Sending a SIGABRT to PID1

Lennart Poettering lennart at poettering.net
Sun May 3 17:39:21 PDT 2015

On Sun, 03.05.15 17:54, Víctor Fernández (vfrico at gmail.com) wrote:

> Ok, Thanks for your reply.
> But, just out of curiosity, why init process gets down with a SIGABRT and
> not with a SIGKILL (9), being this a signal which cannot be caught, blocked
> or ignored?

The kernel refuses to deliver SIGKILL to PID 1. I mean, it's a signal
that cannot be caught by userspace anyway, and hence it would without
exception result in machine halt, and hence the kernel eats it up...

I am pretty sure it's pretty irrelevant whether the kernel delivers it
or not, but they chose not to...


Lennart Poettering, Red Hat

More information about the systemd-devel mailing list