Timeline for Make a process unkillable on Linux
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot | replaced http://stackoverflow.com/ with https://stackoverflow.com/ | |
| Sep 5, 2015 at 8:45 | comment | added | jlliagre | @dudek An unkillable process is already an normally impractical edge case. | |
| Sep 5, 2015 at 5:54 | comment | added | muhmuhten | @jlliagre indeed, it is not. | |
| Sep 5, 2015 at 2:13 | comment | added | GregD | To elaborate on my own answer, I am assuming that you don;t have access to a root account (which, incidentally, hints this is either a toy example, a course project or malware). The precludes the idea that you could wire a kernel module for that purpose. Also note that the SIGNAL_UNKILLABLE flag is not available for normal processes and precludes some important normal operations (such as vforking) and so I would regard it as an normally-impractical edge case. | |
| Sep 4, 2015 at 23:03 | history | edited | jlliagre | CC BY-SA 3.0 | added 370 characters in body |
| Sep 4, 2015 at 22:54 | comment | added | jlliagre | @muhmuhten You are right, init is a userland process being protected against an unconditional kill. It is however not designed to be customized while there is definitely an API for kernel modules and threads. | |
| Sep 4, 2015 at 22:30 | comment | added | muhmuhten | it could be the init process | |
| Sep 4, 2015 at 16:13 | history | answered | jlliagre | CC BY-SA 3.0 |