this post was submitted on 15 Jan 2026
532 points (87.9% liked)

Programmer Humor

28439 readers
1999 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] cows_are_underrated@feddit.org 79 points 13 hours ago* (last edited 12 hours ago) (4 children)

While the meme is very funny, it is technically incorrect. Linux has two major ways of terminating a process. When Linux wants a process to terminate execution (for whatever reason) it first sends the SIGTERM signal to the process, which basically "asks" the process to terminate itself. This has the advantage, that the process gets the chance to save its state in a way, that the execution can continue at another time. If the process however ignores the SIGTERM signal at some point Linux will instead forcefully terminate the execution using the SIGKILL signal. This represents what the image shows.

Before someone gets mat at me: I know, that there are like 50 more Signals relevant to this, but wanted to keep it simple.

[–] Lemminary@lemmy.world 5 points 4 hours ago

Simple answer for us simple folk. I like it. Thank you!

[–] eldain@feddit.nl 4 points 7 hours ago

I think it is showing sigterm correctly. Sigkill wipes you from existence without leaving a body or trace of memory.

[–] Rubanski@discuss.tchncs.de 12 points 12 hours ago (4 children)

Does the "SIG" stands for "Signal"?

[–] mrunicornman@lemmy.world 9 points 7 hours ago

Special Interest Group. An internal committee convenes to decide the fate of the process.

(I don't know the answer, but I'm pretty sure it stands for signal.)

[–] SuspciousCarrot78@lemmy.world 15 points 11 hours ago (1 children)

I like to secretly imagine it stands for SIG SAUER. Bang = process ded

[–] Gathorall@lemmy.world 2 points 8 hours ago (2 children)

Eh, it works more than 80% of the time.

[–] mnemonicmonkeys@sh.itjust.works 1 points 7 hours ago

The problem with Sig is they work too oftem, particularly when you don't want them to

[–] redhat421@lemmy.world 1 points 7 hours ago

80% of the time it works every time!

You're likely bumping into processes which are blocked by IO or are zombies.

[–] cows_are_underrated@feddit.org 1 points 12 hours ago

I guess, but would have to look that up too (there are quite a lot of signals starting with SIG, so it would make sense that it is this way)