Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
reupload because i mixed up sigterm and sigkill like a dumb fuck
also yes i know shutdown typically uses sigterm and waits nicely, but it doesn't take 45 seconds for no damn reason like windows
also sigkill is funnier
hoss
Windows: the shutdown mechanism cannot execute correctly because this process is still running:
ShutDownProcess
Definitely not a systemd based distro in the meme
Maybe something I don't know, but I send kill commands through btop all the time on a systemd based machine.
The point here is that SystemD's natural behavior is to send SIGTERM then wait an eternity.
Those "service XY is shutting down (5sec/2min)" messages you sometimes get on shutdown are coming from SystemD not waiting for 3 seconds like the meme suggests, but waiting for minutes before giving up and switching over to SIGKILL instead.
Can I somehow set this timer to thirty seconds instead of three minutes and up?
There is the option to explicitly set DefaultTimeoutStartSec and DefaultTimeoutStopSec per systemd service.
If you don't specify it in a service file, the default values from /etc/systemd/system.conf (both set to 90s) will be used, so you can change those values to 30s, too, to affect all services (that don't have their limit set explicitly) globally.
Reverse meme when it's time to install the updates.
Windows in that case is "I MUST REBOOT IMMEDIATELY PREPARE TO LOSE ALL UNSAVED DATA IN 3. 2. 1..."
When I switched to win 10, I actually gave them more money to get the pro version for access to the group policy editor so I could control updates and never have to deal with my PC telling me it's time to restart on its own. Because I was stupid.
When it came time to switch to Win 11, I did the much more sensible thing and installed Fedora instead. I started with cinnamon and even though I ended up disliking it also, it was still way better than the windows experience.
Ironic. Because a bug on CachyOS KDE made the shut down button in the quick menu disappear. Nobody in their community could help me or explain why. Generally I would say support is rather spotty with CachyOS in general. Of course you can shut it down in many other ways but that was my preferred one. So I just lived with it and instead used ctrl+alt+delete for a while until the button magically returned one day.
I'm kind of a linux noob, and i currently run catchyos and there are some things i don't really understand. Last time i used linux is like 10 years ago, and i read and experienced that a really big plus on linux compared to windows is that you don't need to restart when yoj install or update, but on catchy, you need to restart almost every update, which is almost every day it seems. Another thing that puzzles me is that every now and then, i restart for the update and wander off, and when i come back i don't use the pc anymore and want to shut it down, but in the log in screen there is no shut down button, just a restart button.
Nowadays, many linux distros restart to apply system updates, because it's more stable. But many linux users still make memes like "haha stoopid windows restarts on update"
CachyOS based on Arch, with basically arch repos, so it have rolling release with frequent kernel updates. And yes, you need to reboot your system to apply kernel update, so CachyOS (cause it targets casual audience) explicitly prompts to user that reboot is needed, to avoid weird arch quirks like losing ability to connect new usb devices after kernel update (arch is quirky like that). Better safe than sorry.
You can just, well, not update that frequent. My server also running arch, I update it like, each couple of months, updated packages will just pile up and go in one update, that the beauty of rolling release (the ugly side is that no one tests if big update like that will work or not, so you may end up with dead system or it just wont update for example, lmao).
"YOU CAN'T SHUT DOWN YET, STEAM STILL RUNNING" -Win10, literally every time.
The fuck?
I've had it yell at me because it couldn't close some dialog window that explorer opened because I was trying to shut it down
The number of times I've told my work laptop to shut down on Friday, and found it still running on Monday is too damn high. And it's usually because I had two instances of VSCode running, and when they got closed they both tried to run an update, and the setup processes interfered with each other. The resulting dialog window prevents shutdown.
Every workday using Windows is just further validation for running Linux on my own hardware.
Don't be a pussy and sigkill process number 1.
Had the pleasure of installing some HPE proprietary crap on RHEL the other day.
After the cli installer ran it printed: rebooting now.
It then killed PID 1 to force the reboot ...
We were flabbergasted. Why would the first and only method of asking the system to reboot be to shoot the system in the head?
I was installing something decades ago that set the default runlevel to 6 and inserted itself as a runlevel 6 service. It would reboot until it had finished the changes it wanted to make and then set the runlevel back. Weirdest trash software. The service stayed to "apply updates on reboot"
I'm glad I don't have to work there anymore.
I don't know what comment section or post are talking about. Default timer for systemd on arch is 3 minutes (and I think it's default for most distros). Whenever some service fails to quit on reboot, system will stuck for 3 minutes until systemd decide to kill it. I need to manually configure it lower to like, 10 seconds, cause there shit ton of services that always fails to quit.
And not like I'm using old pentium - my system build on AM5 with amd 7700x, 128gb of 5600MT\s ram and 7900xtx, with kingston nvme pcie4 ssd's on top of that. It's literally "best case scenario".
also true for boot (not from suspended state), in my experience.
windows: wait, let me display the windows logo for 10 seconds, then show a spinny circle, then show the lock screen, then when you try to enter your password, it loads your user profile for another 5 minutes before it shows your desktop icons
linux: click the power button -> 1.5 seconds later i see the lock screen. enter password and it's just there.
It's tragic the level of immediate relief I feel every time I shutdown on Linux after years on Windows.
I had to update a Windows 11 work laptop after not touching it for nearly a year. I click 'shut down' from the start menu and nothing happens. What? Try it again. Nothing again.
I have to hold down the power button before the screen shows a "slide to shut down" screen now. How did Microslop fuck up the 'shut down' so badly.
I love how the design is so bad now we're missing the days when shutting down the computer required the "Start" button.
The first time I shutdown a Linux computer, I thought I broke something it happened so fast.
Been doing Linux for decades. sudo reboot is still very jarring.
Same. I still feel like I should be parking the heads on my 10mb hard drive. Honestly at this point, I'm too embarased to ask if there is a proper way to send my servers for a reboot, and I cross my fingers I can log back in.
Three whole seconds? Ain't nobody got time for that shit
Xkill is my favorite. I prefer aiming the gun and pulling the trigger myself
Reboot
Windows: save all your woooork. What apps you had open? How would I know?
Linux: it's all saved in ram, don't worry. It'll be like you never rebooted
Nah man. "kill" doesn't shut the system down quickly. This is the "instant death" way - the kernel reset gun - no shutdown scripts, no disk sync, just reset to BIOS boot sequence, instantly:
As root:
echo 1 > /proc/sys/kernel/sysrq echo b > /proc/sysrq-trigger
If you change out the "b" in the second command for "o" it will just halt the kernel instead of rebooting. Still switched on, but the system is doing absolutely nothing.
I used to use this trick all the time to test high availability server clusters.
This but deleting a folder:
Meanwhile on Linux with sudo rm -rf, it's just gone as demanded.
Partially true. The difference is that in Linux, when you delete a file, you're just removing the directory entry (potentially just one of many entries that point to the same data). The filesystem doesn't actually remove the data and reclaim space until all open handles are closed and no remaining directory entries point to the data.
Any running processes that have the file open are able to continue to read and write that data via the handle despite the directory entry being removed, until the handle is closed.
I think a file delete just removing an adress and not the actual data is common to all OSes. That's why to safely erase data from a disk it is recommended to fully overwrite the disk with random data, potentially multiple times.
If you delete a still opened file on Linux then the file will disappear for all processes which didn't already open it, all programs that did already open it can still read and write to it and the file on disk will never be overwritten (as in, used for other files) as long as there's still a process with the file open.
Simplifying how it works: The file you see is a link to the actual file(inode), when a program opens a file using this link they get a copy of the link. As long as one link/copy of it still exist the file won't be deleted. When a program closes all its links get cleaned up so on shutdown all files which only have processes referring to them get marked as deleted.
[HKEY_CURRENT_USER\Control Panel\Desktop]
"AutoEndTasks"="1"
Look what they need to mimic a fraction of our power
Gonna make Lemmy pissed off, but installed on my machine Nobara, Cachy and Mint at some point. All of them had comparable if not worse boot and shutdown times to Windows 10. xD ( And worse performance in games but that's due to having old Nvidia GPU xD )
I had a systemd bug delay shutdown for 2 mins every time for a very long time on Debian. Never managed to fix it, Fedora did not have the same issue fortunately.