linuxBeLike
Wednesday, 12 Mar 2025
Exclusive insights, data, and analysis for financial market experts.
Search
Have an existing account?
Sign In
At first Linux asks nicely, but that’s your first and final warning
Linux users when you can’t terminate children:
Me killing the process of Firefox tab window I didn’t use for two months.
Usually, all processes get SIGTERM which they can react to and shutdown gracefully. Only after short time period a SIGKILL is sent. /smartass
They didn’t learn difference between kill -9, kill -15 and other signals
So that ‘swhy winzoz takes 10 min to shutdown
The longest to survive is usually task manager. It just won’t close
shot to the head 9 times.
That’s a con of windows thou, you can’t terminate processes…
The operating premise behind Linux (and all its flavors) is that both the programmers and users are expected to be of above average computer competence in their endeavors. That’s an expectation we can routinely expect to fail. 🙂
Windows: Has a complex and graceful shutdown process to…
Are you sure you want to shut down? Programs are still running?
Are you really sure?
How about now? Are you sure you still want to shut down?
Trick question! Are you not not not sure you dont want to to not shut down?
There are updates! Do you want me to come right back up again after?
Don’t worry, i’ll power up this laptop in your bag at 3am and overheat it to check for updates. Bye!
Windows: please shut down, please shut down, blue screen.
Linux: memory freed, no CPU time for you.
shutdown /s /f /p
Sorry in advance, but AKSHUALLY… it’s the other way around.
Windows just goes around killing all kinds of programs during shutdown and doesn’t care if they manage to save their progress anywhere, if a shutdown is in progress, it’ll go through. Yes, it will wait up to a minute for programs with open files, but the default action after that minute is to just ignore it and shutdown anyway.
Linux on the other hand waits for each and every subsystem to shut down properly, and if the subsystem runs into some problem doing that (maybe because a network mount is in use but went away, maybe because the program in question just doesn’t want to shut down) it can hang for DAYS if you don’t use the big red button (which rarely is red these days, but you know what I mean).
Seen systemd waiting 90 seconds for some daemon to stop before killing it. At least it’s configurable.
kill -9 command feels so powerful
One of the things I love about linux.
People shutdown linux machines?
Shots him. That was your warning shot.
That was in the past, today you aren’t even sure if Windows really shuts down or you will be out of charge the next time you boot up your device. Well I guess it’s still complex but it’s a “I won’t shut down” process.
we all cry when we
#REISUB
the machine,
#REISUB
the machine,
#REISUB
the machine.
and that’s how you kill a *ghost* process…
ba-dum-tss…
At least that way it’s designed about this so I can just unplug my pc from the power without linux exploding.
Windows NEEDS a complex and PAINFUL shutdown process SO MAYBE, JUST MAYBE programs close correctly AND THE WHOLE OS DOESN’T CRASH IN THE ATTEMPT
There, I fixed that for ya