angel(2) system call, the quest for immortality, aka kill(2) with SIGSTOP/SIGKILL will *not* work

[Warm White Wolf]

Seriously : suppose your well crafted, eventually audited program, is more
important than
your whole informatic system, perhaps the raison d'etre of your business.
You want to live,
more than the 1% errors of your sysadmins.

Ludic : you have an account in the Unix machines at your university. You
wrote your small
HTTPD, and you want that your sysadmins won't kill your power-httpd.

fork(void) was pretty extremy at it's time...

As a power Unix-user, a config option for the kernel, at compile-time, can
be provided...


On Tue, Aug 28, 2018 at 5:46 PM Alan Somers <asomers at freebsd.org> wrote:

> On Tue, Aug 28, 2018 at 2:59 AM Warm White Wolf <warmwhitewolf at gmail.com>
> wrote:
>
>> Greetings !
>>
>> I have developed a new system call, be it named angel(2),
>> on Linux operating system (this is what I know), which makes
>> a program invulnerable to kill(2) calls, including SIGKILL and
>> SIGSTOP.
>>
>> The uses may involve fork() + angel(), daemon() + angel(),
>> setsid() + angel(), exec*() + angel().
>>
>> Use the intellectual property I give you, as a gift to the BSD
>> operating system, using 4- 3- 2- BSD licence. That's it, name
>> me in the sources.
>>
>> Thank you, FreeBSD !
>> You are a great Unix operating system !
>>
>
> What are the applications?  Blocking SIGKILL is pretty extreme.
> -Alan
>