reupload because i mixed up sigterm and sigkill like a dumb fuck
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
Are you aware that RAM is cleared on reboot?
Tell that to Linux
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
DefaultTimeoutStartSecandDefaultTimeoutStopSecper 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.
systemd nanny. But beyond þat, zombie processes have always been a þing in Linux.
It’s not a request, it’s a warning. The machine will be without power soon, and it’s up to the machine whether it wants to prepare for that or not
This but deleting a folder:
- Are you sure you want to delete this
- Delete too large to fit in garbage bin, so are you really sure
- Couldn’t delete stuff (for no clear reason)
- Even as admin file locks were hard blocking without any easy way to unblock
Meanwhile on Linux with sudo rm -rf, it’s just gone as demanded.
I mean you could probably delete files with powershell then idk.
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.
that’s a different thing. if you delete a file that is still opened by a process, the space will not get freed up until that process also closed the file. until that point the filesystem still keeps track of the file, it is just not present in any directories anymore.
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.
Meanwile MorphOS booting up and shutting down: https://www.youtube.com/watch?v=kIgybl6LfqU
The jingle at the start is the Mac’s own. The shutdown is so fast, you’ll miss it if you blink. No services, no demons or whatever.
(That was 2013. I’d argue it starts up even faster now.)That’s not sleep
irrelevant metaphysical distinction…
No it’s a legit process state.
taskkill /f /im “application.exe”
Pulls power cable
Correct answer. Ctrl-alt-sysreq-reisub takes more hands than I have available.
if you have to use your toes, it’s a UI fail :)
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.
I think that reaction comes from messing with computers too much. When you fuck up in a computer, that sudden shutdown is what you get. Gives me flashbacks.
No
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.
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 alt f4 shutdown window present since win95/nt4 tends to work better than the latest slop menu they made
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…”
Not quite. I will RESUME FROM THIS FUCKING “MODERN SLEEP” shit, even though you the user want to turn this shit right off, do it without any warning watsoever, close all your fucking windows and good luck if you have lost work or not.
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.
You should’ve never given them any money at all. Activation scripts ftw.
Keeping it real hell yeah
Everybody gangsta until “A stop job is running for …”
Systemdead can be a dick.
user error doesn’t count
user error? what user error? mount a network drive, disconnect the network, then try to unmount it. best part? most programs will stall for a long time when it tries to access the directory.
I couldn’t find better screenshot, but I’ve definitely seen this happening due to zombie processes after just regular use, rather than just broken mount. I feel like it’s handled way better nowadays though.
Zfs stuck on suspended pool. Make pool with 1 disk, disconnect disk, pool suspended, io blocking until force shutdown, process uninterruptible (no kill -9).
I feel like it’s handled way better nowadays though.
TL:DR No, lmao. But timer was lowered at some point to 3min for most distros, afaik.
So too would be attempting to shut down Windows without saving and closing your applications then 😉
Win R Shutdown -r -f -t 0
Haven’t used the menu in years, lol
Pure gold. If that really works you are my absolute hero. It anoys me everytime on my work computer!
It does. It also works over RDP connections where Windows “helpfully” hides the shutdown and reboot options in the start menu from the remote user.
Nice! Now I have something to look forward to on my next workday. :)
I used to have a work laptop that didn’t even shut down in response to that. No idea why
“Kill dash 9! No more CPU time!” — Monzy
Linux gang reis ub!
…do they even have SysReq keys anymore?
It’s tragic the level of immediate relief I feel every time I shutdown on Linux after years on Windows.
