I can attest to that. I’ve been trying to figure out why my Kinonite install is killing KDE repeatedly without mercy…
Other unixes are over there like “hey, I kill just as much as Linux does!”
This is blatantly false, 99% of Gnu/Linux distros actually have systemd nicely asking the processes to terminate themselves, it just doesn’t take longer than ~10 seconds usually.
This meme would imply a sigkill.
Edit: the distros that don’t use systemd likely don’t do any such thing either, I just don’t know about them.
Kernel will happily kill processes if it’s out of memory, regardless of systemd or whatever. But in general Linux first asks nicely for the program to shut down and if it doesn’t comply then it’s SIGKILL time.
Which IMO is a most reasonable order of operations
Except on the Linux systems I’ve used, when I ask it to shut down, it shuts down no matter what. Windows and macOS let programs stop the shutdown process indefinitely (when shutdown/reboot are invoked the usual way).
I think that’s what the meme is trying to get at.
That would depend on the DE I suppose, on GNOME it’ll show open programmes and wait 60 seconds for the user to intervene IIRC.
Still doesn’t kill them though and asks them to properly terminate themselves which allows them to take care of everything.
Yeah, I run
i3and headless servers, so it’spowerofforrebootfor me. Always works as advertised.
I wish that was the case, I’ll often find my Linux desktop running because the os failed to shut something down.
poweroffandrebootwork as advertised for me, but I’m running headless homelab servers and a laptop withi3. Maybe DEs/GUI shutdown is more subtle?I’ve had containers which are locked up and won’t respond to SIGKILL or any other signal. I don’t think It should be possible with a regular process, though.
Yeah, I’m kinda sick of seeing this false information on
this subthe linuxmemes community. It’s a surprisingly common meme subject somehowThis ain’t the Linux memes com
that’s why I edited
ah I misunderstood you then, my bad 😅
*clicks shut down on windows
*goes to boot computer up into the morning… sees message ‘attempting to close programs’
fu microsoft
*clicks sleep on windows
*computer turns itself on in the middle of the night and starts playing YouTube
fuck you ms
That’s almost certainly because you’ve got wake on LAN enabled in your BIOS settings and something else on your network wants to have a late-night chat with your computer.
yeah wake on lan is pretty hard to accidentally trigger.
Why would random software be sending packets with 0xFFFFFFFFFFFF + mac*16?
The MAC-specific magic packet is an optional mode for wake on LAN, not a mandatory one. Plenty of network adapters forward packets to the OS if wake on LAN is enabled and let the OS decide whether it only wants to respond to magic packets, and by default when wake on LAN is enabled, there are other kinds of packet Windows responds to, e.g. Address Resolution Protocol, which lots of routers use to check whether devices are still connected. It’s not supposed to wake the machine, especially if S0 sleep is enabled, but it can, especially if it’s done excessively.
A magic packet is any packet using any protocol with that string in it. And the os cannot respond to a wake-on-lan packet, because the os is not running at the time; the computer is powered off. The os is later informed, via acpi, of the reason it was woken up, should it bother to check. If you don’t want a magic packet, then any packet will wake the system up. I am not aware of any alternatives. Extensions, yes. But not alternatives
Or they’re using S0 sleep and the computer is waking itself up to update
When Windows wakes itself up to do things like that, it wakes itself to a different sleep level where it can still do things but the machine isn’t visibly on. That’s the whole point of S0 sleep. If it’s fully waking itself up to do things, then either S0 sleep is disabled or there’s a firmware bug affecting the motherboard that means certain actions during S0 sleep will exit sleep (which is more common than it should be).
WinKey+R
Shutdown -s -f -t 0
If you do shutdown -s -t 1 you can skip the -f and it’ll shutdown after 1 second.
Can I get a breakdown of the meaning of this?
Win + R: opens run dialog to run the next command
shutdown -s -f -t 0: cli shutdown command where -s is poweroff, -f is force, and -t 0 is a timeout of 0
Mate, you’re lucky you still got that secure boot manager thingy… drops from my disks far too often.
Can I uninstall the bootloader Mr. Linux?
Hell yes you can! Let’s try it and see what happens!
boots into the BIOS/UEFI
Happens all the time. Usually accompanied by installing an updated version at the same time. You can uninstall your kernel too, try it.
Hard operating systems make strong men
I don’t see an article linked for the relevant headline, but when I first installed linux (I use Arch btw) on my desktop, it didn’t come with swap auto-configured by the install helper ArchInstaller, but did come with oomkiller and also with 4/16GB of zram preconfigured. With three displays and three different kind of browsers open I ran out of memory when launching a game fairly quickly, and of course oomkiller went to town. Not only that, but because of stupid zram it also seemed to be stuck on an endless loop of not being able to kill something.
Oomkiller you say? I’ve never used the installer…
There are apps that don’t close gracefully when asked by systemd in my experience. I’ve often forgotten to close one and been stuck waiting 90s for a watchdog to timeout so the app gets killed.
This is not a problem unique to windows.
