-
Linux normally does a nice shutdown as well, unless you force it.
-
You can force it on windows if you really want.
I’m so tired of linux memes posted/made by people who don’t know much about windows or linux.
-
Linux programs either HAVE to be quick while receiving shutdown signal, otherwise the state will be fucked, work will be lost, and people will be mad, and program will stop being used.
-
Clicking the Windows button to force shutdown will straight up kill the program and won’t care at all.
-
deleted by creator
Epic?
I’m assuming Epic as in the healthcare charting system
deleted by creator
You can force it on windows if you really want.
Please elaborate
Shutdown.exe -r -t 00 -f
Fast , no mucking around with graceful exiting of stuff. Kicks it in the teefs
Some clarification of the command
-r #restart
-s #shutdown
-t 00 #wait 0 seconds
-f #forced
-
Windows: Has a complex and graceful shutdown process to make sure programs never close if there’s a problem with them and your computer just stalls on shutdown until you hold down the power button and completely void out the purpose of the graceful shutdown.
Ever tell a pc to shut down and come after work and it’s still waiting for click a box.
If your code can’t handle a sig9 then your code is weak
sig 9 or sig 9mm - that’s the question here
Closing correctly means the program stops NOW
i mean
Great way to damage a power cable.
Old wives’ tale. I’ve only ever yanked power cords out of the wall and I’ve yet to have one go bad on me.
Is this even true? I am fairly sure that Linux also has a graceful shutdown process, but I’ll admit I haven’t looked into it.
yeah we have SIGTERM for graceful and SIGKILL for not so graceful shutting down a process.
I hate this message
If you hit Ctrl Alt Delete very quickly in succession (I believe it’s 7 times in a row) it will bail out from a stop job and proceed with shutting down
Learned that trick because I was so tired of seeing that occur ha. Along that research I swear I recall seeing that it’s a KDE/SDDM issue but I might be getting some wires crossed on that (and thus, don’t quote me/take my word on that 😅)
Linux does give every application time to shut down correctly, but unlike windows, it won’t wait for ages until every process is down. Linux WILL shut down in a certain timeframe, whereas windows waits for years if necessary. In my old job, we all had to use windows and I had times where I clicked shut down, turned off my monitor, grabbed my stuff, left and in the next morning, the PC was still on because Notepad refused to just close lmao.
That is what infuriates me so much. Instead of just killing the process after 5 mins of waiting it just cancels the shutdown. Like fuck off with that shit.
Depending on the use case, that can be a good thing or a bad thing
Shouldn’t be the default though.
Ha, you want choice in how your OS functions?
Here, have another bing toolbar for your settings app.Man I hope next time I press windows and type an application by name, or by executable.exe I get a spinning icon then a stack of unrelated web results that are probably malware.
I don’t want my IDE with hours of work to just shut down forcibly.
If your app doesn’t respond to SIGTERM gracefully, you need to fix your app. The system did its job as documented.
Linux is actually great if you need to implement graceful shutdown with signals – I love it all around :)))
The kernel giveth, the kernel taketh away
kill commands make one feel like a Caesar
et tu, Sudo?
Except Windows doesn’t. You can send WM_CLOSE, but that may not actually bail out of the core loop. PostQuitMessage() works better for some apps, but not at all for windowless CONSOLE subsystem processes. Windows also has a lot of special behavior around generating signals in other processes. It’s a mess.
Like, every time I reboot the reboot UI complains about mysterious, unnamed processes that take suspiciously long to quit.
Having the kernel yank the process out of existence with prejudice is definitely the way to go as apps should be hardened for crashing, anyway.
