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

Three whole seconds? Ain't nobody got time for that shit

Definitely not a systemd based distro in the meme

A stop job is running for User Manager for UID 1000 (12s / 2 mins)

Maybe something I don't know, but I send kill commands through btop all the time on a systemd based machine.

Does that guy have frontbutt?

https://lemmy.zip/comment/26874835

Waow based based based based based

I prefer Windows giving programs time to shut down properly. You can always click on 'shutdown anyways' or whatever the button is called. Also what kind of programs do you run that take 45 seconds to shut down?

Unlikely. That is usually meant to depict his massive bulge.

I think you can set the default stop job timer lower?

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.

That's actually the default on Linux as well. This meme just gets shared every other week, perpetuating the myth. OP seems to be aware of that.

If you use Emby Desktop, when it's full screen it interrupts all shutdown commands. Only GUI option is 'cancel', running shutdown remotely fails.. Just need to exit full screen but who the hell decided an Electron app was more important than my choices

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.

( 1min 59s / 2 mins )

...

( 2 mins / 3 mins )

???

systemd nanny.
But beyond þat, zombie processes have always been a þing in Linux.

It doesn't "give time" it just waits indefinitely, and if the program doesn't terminate your laptop will just sit there until the battery dies. This has to be one of the dumbest aspect of Windows, and god knows there are many

You can change that, but there is a maximum time when it just kills the job.

(5min 7s / no limit)

Shieeet

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.

In general, it's true that Linux doesn't need to restart for most updates. However, if you get a power cut right in the middle of an update, that could leave your OS in a really bad state. Therefore, for safety reasons, some distros (apparently including CachyOS) do updates in a 'safe mode' on boot, so that if there's a power cut it just rolls back cleanly.

In short, how exactly distros approach updates differ slightly. A tradeoff between safety and convenience.

That’s not sleep

this will be done in three seconds

Hah! Fractions of that

Getting Amos vibes...

Don't be a pussy and sigkill process number 1.

"YOU CAN'T SHUT DOWN YET, STEAM STILL RUNNING" -Win10, literally every time.

The fuck?

I may be weird but I always like opening a terminal and I have sdn aliased to shutdown now

You’re not that guy…

I am that guy

Yes and a broken knee

Too much typing. Real men just press Alt+SysRq+L.

sudo halt

Step 1: order a 101% kb

Pardon my ignorance, how does halting the kernel help? We're you seeing if other instances jump in for the halted one?

hoss

That's because it first send sigterm, then sigkill. Then it gives up and let the kernel handle it...

Happens on my BTRFS disk's unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.

So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.

In those cases there's an easy solution.

Step 1: sigh

Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive

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

Just bind update/shutdown to a key you don't press often, like keypad insert.

yay --noconfirm ; sudo shutdown now

Any problems with update, computer is put straight out of its misery. Bang.

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.

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.

It's tragic the level of immediate relief I feel every time I shutdown on Linux after years on Windows.

You mean in the context of high availability?

tl;dr: It's to test if the cluster fail-over configuration is working properly.

So this was before things like Kubernetes or Terraform were a thing, so had to be done by the operating system itself. The simplest HA cluster is made of two nodes, one in "active node", the other "passive". The active node does all the work, and the passive node just keeps its data synchronised with the active node. I used to use DRBD for this, which is a system for copying writes to the active node over a network link to the passive node. That only gives you a "second, up-to-date copy" which is not that useful on its own - you also need a way to automatically switch over to using the passive node if the active one "dies", and for that I used to use "heartbeat", which simply passes packets back and forth between the two cluster members - ping-pong style - and if the passive node notices that the active node hasn't sent its scheduled packet for, say, 10 seconds, it cuts it off the current active node (kills it), and promotes itself to the active role, thus preserving the service. Killing the "other node" is necessary to stop data corruption or user requests going to a node that can't actually service them, and is called STONITH - Shoot The Other Node In The Head. STONITH can involve an electronically controlled switch, which literally cuts off power to the "other" node, or can isolate it on the network, by shutting down its network ports on the switch, or in a VM setup, sending a notification to the hypervisor to kill the VM.

The reason you need to be able to kill the kernel on the active node, is that when you manually shut down the active node, it automatically informs the passive node that it's going down, known as an "orderly fail-over", and you're not actually testing if the heartbeat fail-over works, you're just testing an orderly fail-over. Killing the active node's kernel tests that the passive node is properly configured to take over during a catastrophic failure of the active node. You can watch the heartbeat status go from "up" to "down", and then see the passive node decide to take over, promote itself and bring up its services, and begin processing requests.

To make sure it's all working, you need to test orderly fail-overs first, from both nodes, then test disorderly fail-overs both ways, by using the kernel gun on the active node.

Things moved on from Heartbeat-based HA clusters to multimode clusters managed by Corosync and other software, enabling other strategies to be employed. This was eventually supplanted by "orchestration" systems like Kubernetes, and proprietary Virtual Cloud systems that move this functionality to the platform rather than the operating system.

irrelevant metaphysical distinction...

No it’s a legit process state.

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..."

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!

Does that shutdown windows via terminal? Cool, didn't knew that. But I haven't used windows since 2011, so... 😁