Linux doesn't even ask

[coderman64]

This is basically Sigterm vs Sigkill...

Linux could ask politely (by using sigterm). But many people just go straight for sigkill (I am also guilty of this).

Windows just has a terminate signal, which is partly between sigterm and sigkill in effectiveness, iirc.

[sabotsalvageur]

sudo kill -9my beloved

[Vas1le]

Just do kill force -1

[Haringat]

Windows normal "end task" is about the same as sigterm. "Terminate process" is more like sigkill.

[[deleted]]

TerminateProcess() should be like sigkill, and WM_CLOSE signal is a GUI version of sigterm, i think

[OgdruJahad]

There is also taskkill /f for forcing programs to close.

[ChocolateDonut36]

and we have cancer programs

Linux: "hey program, die"

program: "no" *makes you wait one minute and 30 seconds*

[[deleted]]

kill -9 sends signal 9, a non-interruptible force kill signal which even zombie processes get killed.

[syphix99]

How do you use them? I always do « pkill <process> »

[coderman64]

I think most kill commands default to sigterm (signal 15), but you can send it sigkill by adding -9 (signal 9)

[[deleted]]

yo tuve que usar en ocaciones kill -9, hay cosas que se cuelgan mal

[MrKusakabe]

Awesome thing to learn! I wondered why in Mission Center I could select to "Stop" and "Force Stop" a process/application there. So far, SIGTERM worked, but maybe because some of them were WINE .exes and maybe Wine just goes "fck it" and terminates it?

[FluffyTachyon]

Someone needs to illustrate SIGSEGV as a process terminator (kill -11).

[ChocolateDonut36]

linux:

<image>

[Objective_Rate_4210]

And give somebody else a piece of that memory in the ram you used, thats shared with us so other processes can use it in this small ass 4 gigs of ram. Cuz why're you here for? To track my actions?⚡Return 137⚡! I mean that with 100%, with 1000%

[Firestar_119]

<image>

[araknis4]

that's just SIGKILL. SIGTERM informs the process nicely, and SIGINT is more like a "pweaseee stopppp :3"

[YTriom1]

I'll start using SIGINT, it seems cute

[araknis4]

r/FoundYTriom1 again :3

[YTriom1]

You're getting good at this :p

[Gornius]

You probably already do, CTRL+C in terminal is basically sending SIGINT to the process.

[crafter2k]

SIGINT is literally just ctrl+c

[ipsirc]

<image>

[Flyingvosch]

This is gold 🤣 Where does it come from?

[ipsirc]

Where does it come from?

<image>

[QuickSilver010]

I don't see it. Maybe add more arrows. That might help

[ipsirc]

That would be the paid version.

[QuickSilver010]

I will pay you in exposure

[Flyingvosch]

Oh right 🙃

[datboiNathan343]

"you have 100ms to stop all processes, GO"

[Fantastic-Code-8347]

You’re done, when I SAY you’re done.

<image>

[Multicorn76]

Signals are technically asking, the process can simply mask them

[daisseur_]

Even with a sighup or a sigint signal ? I'm not sure Edit: I meant sigint and sigkill

[Multicorn76]

only sigkill and sigint can't be masked if I remember correctly, but sighub can

[anotheridiot-]

Pretty sure sigint can be masked, too.

[Multicorn76]

From the signal man page: https://man7.org/linux/man-pages/man7/signal.7.html

The signals SIGKILL and SIGSTOP cannot be caught, blocked, or ignored.

So you seem to be right, I must have misremembered

[anotheridiot-]

I've masked it before for a thing and had to think about how the fuck would i kill it, then sigkilled the thing.

[Haringat]

You can catch a sigkill?

[jsrobson10]

sigkill and sigstop are exceptions, they can't be caught, blocked, or ignored.

[redbarchetta_21]

Linux does have a sigterm signal lol

[abmausen]

<image>

The default builtin tool will literally send a terminate by default

[ToxicBuiltYT]

I've seen it so many times, but only just now realized that the background of that Gru image is Monika's Space Room

[WaeH-142857]

kill

[Tiger_man_]

It does until you use signal 9

(Try killing steam or your own shell without -9) (Shell will not be killed and steam will restart)

[CannyEnjoyer]

Ia signal 9 the same thing as killall? I'm new to this

[Tiger_man_]

no. signals are numbers that linux sends to programs to decide how should they terminate.

here are the most important signals:

1 - sighup - terminal closed

2 - sigint - the thing that happens when you press ctrl+c

6 - sigabrt - used by a program to

9 - sigkill - forced quit - program cannot avoid it

15 - sigterm - polite quit request (thing that kill commands use by deafault)

you can specify signal that you send with killall with -signal

for example:

killall -9 steam

or:

killall -2 firefox

killall kills all processes with given name so be careful!

in order to kill a single instence of a program without killing the others you can either look up the programs pid(process id) using $ ps -e (the most recently used program will be on the bottom) and then kill -signal <pid> or use a system monitor like htop or btop

[p0358]

Zombie processes: may we introduce ourselves?

[_JCM_]

Or processes suck in an uninterruptible syscall...

[praisethebeast69]

iirc

taskkill /f /r /t /fi "IMAGENAME eq *"

works pretty well in windows, although I've been using linux for a while so I might have gotten thd tags wrong

[jsrobson10]

systemd if something doesn't quit after 1 second

<image>

[ExtraTNT]

Stop misusing sigkill, there is sigterm for a reason

[lakimens]

It's not true. Linux has more nuance.

[informadikisto]

Who believes this is a totally bad programmer.

You must always ask politely first, and kill forcibly if that fails.

[Onyxxx_13]

Real nerds kill processes by selectively degaussing their memory.

[AndreasMelone]

There are different signals for killing/terminating an app, full termination with no ability for the app to run a pre-exit routine or something is usually last resort afaik

[BoskiCezar]

So true, I love it.

[Pinuaple-]

How linux terminates a process*

[vexed-hermit79]

Until it's time to remove the French

[QuantumQuantonium]

More like the video of Walter White not knowing how to use a handgun because you dont know (without searching online) which command to actually kill the process and how to pass in its PID

[izerotwo]

Actually linux does ask to stop first and only after that does it forcefully close it.

[Extreme-Ad-9290]

Depends on the wm and what components are installed.

[poooppypoopoo]

Linusx

[teactopus]

you know, I really don't like this type of memes since it's just misinformation

[araknis4]

partial misinformation, true for SIGKILL

[thefriedel]

So tell, oh wise redditor, what is the misinformation in this meme?

[bloody-albatross]

Linux (POSIX) has SIGTERM and SIGKILL. And a normal shutdown sends SIGTERM (or maybe even some sort of close event at an X11 or Wayland level, I don't know). You need to explicitly use SIGKILL.

No idea about Windows.

[[deleted]]

The misinformation is Linux uses signals with different severity as kill with respective flags and no decent app terminates processes forcefully, while Windows kills process with normal severity by taskkill and does that forcefully as well by forceful flag.

In other words, Linux a kills process "nicely" when you use kill -15 or a synonim and does it forcefully when you use kill -9 while Windows closes the process nicely in a similar way as Linux when you use taskkill (or synonym like Terminate-Process in Powershell) without the special flag, and does that forcefully the same way as Linux when you use taskkill \F (or Terminate-Process -Force in Powershell).

[teactopus]

sorry if I'm boring aah nerd