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.
Ever? Too many times. When I think I’ve told Windows Update “yes, do all the shit, yes it’s fine, yes I’m sure, yes you can do it, yes I really want you to do it, yes I’m sure I really want you to, yes I’m sure I’m sure, yes for the umpteenth fucking time” and switched off my monitor to go home for the weekend, the number of times I’ve come in on a Monday morning just to find I have to click “yes” yet again then have to sit there watching it grind out its updates.
I just wish they’d add a checkbox, off by default, that says “yes you can do it all, just stop asking stupid fucking questions” that I can click and go home. But for some reason Microwank insist I have to sit there watching that fucking update percentage creep up then endlessly sit at “100% all is done, please wait” for no reason whatsoever.
Oh yeah and there always seem to be way more reboots needed when BitLocker is active. I’m sure 1 reboot is the norm with occasional 2’s. But with BL it’s usually 5-6 reboots.
I used to work at a place where MS would raise tickets with us and I always wanted to give them the WU treatment. But professionalism always got in the way of “This ticket is 100% complete, you must close and reopen it to continue”.
If your code can’t handle a sig9 then your code is weak
sig 9 or sig 9mm - that’s the question here
kill $SIGSAUER
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
I don’t want my IDE with hours of work to just shut down forcibly.
then surely you would not have asked your OS to shutdown? linux does what you ask
Then you might not want windows cause Windows forces updates on you whether you want them or not and break things. Linux will happily wait for you to forget for so long it breaks because the target API doesn’t accept your old ass code anymore. At least in Linux as long as I don’t forget I’m good. I sometimes forget
Linux gives processes a chance to gracefully close. However, it also will absolutely NOT allow a process to hang up the shutdown or restart procedure after a point. If you’re using systemd (which there is a good chance you are), it’ll count down. If the process hasn’t stopped in the time allotted, it gets Old Yellered.
Question, what’s the default wait time?
The default in systemd, unless your distribution has modified it either globally, or for a specific service, is 90 seconds
Closing correctly means the program stops NOW
I’ve never seen anything graceful in windows
Windows: I refuse to shut down because of a, b , c
Me: But I already clos. . .
Windows: No you didnt’t, stop lying!
Me : Well, I pressed the X and the window dissappeared.
Windows: Lol, noob. Did you never even heard of a task managers?
windows: “Can’t shut down because of the ‘Cant shut down’ notice”
me: “but…”
-
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.
Oh, p-lease, can force it my ass, Linux has never failed to shutdown on me when using plain obvious GUI method. windows - can easily hang on forever as long as computer stays powered. The point of all the memes is exactly insane windows defaults, not the things that can or can’t be done by someone with enough knowledge
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
00?
I know! I wasn’t sure when I posted it, so stuck to memory to be safe.
I reckon I’ve confused the double digits needed for the silly shutdown explanation thing (planned/unplanned, various reasons) instead…
How many seconds you’re prepared to wait for Windows to shutdown.
I’ve used a single zero and that works fine too.
Me to
If -t is specified -f is assumed and redundant, but also it will try to do graceful l, but with a patience of a cranky toddler
Not really. If -f (force) is removed windows will shutdown similar to pressing the shutdown button and will wait for your input regarding open programs. -f is needed to just just “do it” with no hesitation or response from the user.
Straight from the doc
/t <xxx> Sets the time-out period before shutdown to xxx seconds. The valid range is 0-315360000 (10 years), with a default of 30. If the timeout period is greater than 0, the /f parameter is implied.
Sooo when you use the prompt
Shutdown.exe -r -t 00
You would need the -f since we defined the timeout period as 0. Because:
If the timeout period is greater than 0, the /f parameter is implied.
I use that as a bat file so all I have to do is double click it.
and then you can growl menacingly and say ‘don’t make me get the bat, punk’
I will just do the update first /s
It was simpler using Linux to just kill things unceremoniously, but my coworkers are also consistently amazed when Epic throws a temper tantrum (rare, but it happens) and I walk over and ctrl-alt-delete and tell it to sit down and shut the fuck up until it’s ready to reboot and act right.
Epic?
I’m assuming Epic as in the healthcare charting system
☝️
-
REISUB. I own you machine, and you will do as I say. Reboot.
Linux is actually great if you need to implement graceful shutdown with signals – I love it all around :)))
Laughs in Sierra
elaborate please
old sierra DOS games, uh, they fucked up the code when exiting so they’d just crash. so they changed the error code to say “thanks for playing Kings Quest” or something similiar
sudo reboot, that way the gui gets to die in a fire, too!
Close correctly my ass, window’s priority is to piss us off.
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 😅)
Systemd moment
systemd moment in the sense that someone not affiliated with systemd used systemd to write a stop job that doesn’t terminate quickly? Or that you willingly installed software that brought along a slow stop job with it?
This is like so far away from systemd’s fault, idk, it must just be a meme right?
Wasn’t the systemd dude a Microsoft employee or something?
He wrote Pulseaudio, Avahi, and systemd before joining Microsoft, where he currently works.
So that’s the story. SystemD feels very Microsofty, though. A big, opinionated, monolith.
An excellent vid on Why systemD. https://www.youtube.com/watch?v=o_AIw9bGogo
Great talk indeed. And I will quickly acknowledge that something had to be done, and that systemd had the courage to innovate and address the issues. I just wish it did so in a more transparent way to the end user.
For instance: there’s a whole established system of dealing with logs in place. Why build a separate one just for your init system? Why binary? Why even integrate it with your init? I’m not saying storing everything on /var/log and using logrotate is ideal or even covers all use cases. But a log management system is its own thing.
That’s just an example of how systemd didn’t jive with every other subsystem in a Unix like OS. It could have been done in a Unix way - small cohesive tools that are good at one job and can be combined to do more together.
That’s where I think he missed the mark when dismissing the monolithic criticism by saying “it’s not a single binary so it’s not monolithic”. Its philosophy is monolithic.
That said, I use systemd on my machines because that’s what my do uses and I don’t think it’s a reason to swap distros. For the same reason I use Linux and not a micro kernel. I.e. philosophy is important, but implementation is importanter.
While monolithic may not be the keep is simple rule aimed for in originally in Unix/Linux, I wonder if it even matters…is there something really gained by init systems that make a difference for the average Linux user?
one of my favourite things when i switched to linux first was using the meta+Q hotkey to shutdown a program (this was with PopOS i think). with windows there is alt+F4 but some programs only use shift+alt+F4 which makes it a lot more confusing. on top of all that if youre using a laptop then its another keypress for the Fn key in some cases
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.
In order of decreasing politeness: 1, 2, 15, 9 = HUP, INT, TERM, KILL = “Please stop”, “Quit it”, “I’m warning you” and “BANG”
Hup is frequently just “hey, reread your configuration files and keep going”
9 kills all 9 lives is they way the hpunix guy explained it to me in the mid 90s
This is put so beautifully!