On Mon, May 4, 2015 at 3:40 AM, Lennart Poettering lenn...@poettering.net
wrote:
On Sun, 03.05.15 19:10, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Sun, May 3, 2015 at 6:54 PM, Víctor Fernández vfr...@gmail.com
wrote:
Ok, Thanks for your reply.
But, just out of curiosity, why
On Sun, 03.05.15 17:54, Víctor Fernández (vfr...@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
On Sun, 03.05.15 19:10, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Sun, May 3, 2015 at 6:54 PM, Víctor Fernández vfr...@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
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?
PD: I definitely not try the command above
2015-05-03 17:22 GMT+02:00 Lennart Poettering
On Sun, 03.05.15 17:18, Víctor Fernández (vfr...@gmail.com) wrote:
Hello
I'm using rigth now a Manjaro distribution (derived from arch). Making some
test, i've discovered that sending SIGABRT (6) to PID 1 (systemd) will
cause system to enter on unstable mode:
after doing this, the system
Hello
I'm using rigth now a Manjaro distribution (derived from arch). Making some
test, i've discovered that sending SIGABRT (6) to PID 1 (systemd) will
cause system to enter on unstable mode:
after doing this, the system reboot graphic server (at least, it request to
login again) and if you
On Sun, May 3, 2015 at 6:18 PM, Víctor Fernández vfr...@gmail.com wrote:
Hello
I'm using rigth now a Manjaro distribution (derived from arch). Making
some test, i've discovered that sending SIGABRT (6) to PID 1 (systemd) will
cause system to enter on unstable mode:
after doing this, the
On Sun, May 3, 2015 at 6:54 PM, Víctor Fernández vfr...@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?
pid 1 is allowed to catch
