Transcript:
Two panel meme.
Top panel: Woman in the front seat of a car screaming at a child in the rear seat. She’s saying “Why can’t you just shutdown?”
Bottom panel: A child screaming “A stop job is running for Session c2 of user … (1:30 / no limit)”
One of the reasons i like the new atomic/immutable distros is you can just power cycle with little worry of bricking your system, even if a system update is running.
Wtf is this Linux shit I see all the time on this dumpster fire of Reddit knockoff site? Is that like a breed of dog? I’m not a furry, personally, but my life partner is, I think, that might be his cover, I still haven’t figured it out, but you fucking furbies n shit gotta stop advertising your weird shit to kids, cuz then they grow up to be like me, and no one wants that shit, bro.
if my PC takes more than 15 seconds to shut down im flipping the power switch
That too takes 15 seconds.
I hope my installation of Mint doesn’t start acting up, because I don’t want to learn whatever it is half y’all are talking about.
I just want it to work, and so far it has.
The only problem I’ve had is nvidia driver updates breaking Blender. So, I need to restore and tell update to ignore that one.
Same, my shutdowns take about about two seconds, although suspend can sometimes take about six seconds (but normally one).
I’m on Gentoo, so it’s probably a leaner install than most.
systemctl poweroff <3
> doesn’t want to learn about Linux > runs Gentoo
So I should wish for my computer to start acting up so I can have an educational experience attempting to fix it? No thanks, there’s less frustrating ways to learn.
Also, if you’re trying to go for a greentext-style formatting, put two spaces at the end of your first line.
I am lucky enough to not have had any problems with calling a shutdown… just now with a problem I recently learned where my desktop treats shutdown as reboot. Definitely gotta look into that.
I did have such problems. I just turned off the PSU. 😂
I think I figured out my issue, literally a few minutes ago. I’ve never really dealt with ethernet, so I just learned my bios might have some sort of “wake up on lan” setting enabled that stops me from fully shutting down.
Why would I ever want something like that, though?
Why would I ever want something like that, though?
I should look into wake on lan for my media center so I wouldn’t have to run downstairs to the living room to turn it on if I want to browse my photo/video collection.
I prefer keeping it off when it’s not in use.
Wouldn’t it be more efficient in that case to have some sort of remote* suspend+resume? Saves you the hassle of the bootup and shutdown procedure, when suspend saves most of the relevant energy.
[*] where “remote” can be “hook a tripwire from your room to the keyboard”, at least for the wakeup
That’s what
kill -9is for.Recently I had to reboot to fix a zombie process (caused by a GPU crash, not sure if it was hardware or the driver). When shutting down systemd waited 2 minutes for all process to be killed and then another 2 minutes for the specific zombie process.
What happened when you called
kill?Absolutely nothing. kill -9, SIGCHLD to the parent which was pid 1, relogged my graphical session. After I rebooted I had the thought that I should have tried removing and reinserting the amdgpu module to avoid a reboot. I couldn’t start new mpv processes so shit was pretty fucked lol.
Dang. That’s a good one.
This actually got me to go track down the
systemdservice that has been responsible for being unresponsive and causing a 90-second shutdown delay way more often than it should.Do you really want technical details?
In my case it’s the MPRIS service that’s supposed to provide playback control on media players and related software.
… and so now it’s disabled to see what, if anything, breaks without it. So far, none of the media apps I regularly use seem to be affected (browsers, a computer emulator, DOSBox, VLC).
It looks to be Bluetooth-associated based on the package it’s installed with, and I don’t need Bluetooth 99.9%+ of the time, so it might be a while, if ever, before I notice anything wrong.
systemd-analyze ?
“Ask systemd what’s wrong with systemd” feels like “ask Grok what is bad about child sexual abuse” lol.
I have less issues with that than i do shit getting slow at startup. I hunted down a PAM problem (that I didn’t even configure) for a couple of days of my spare time. 5 minutes startup, i could feel my hail/nails growing between power on and Graphical.
Huh, used to see this regularly, but have not seen it for a few years now…
On Windows I get a “some apps are preventing shutdown…”. With a list of apps. The app that is stopping shutdown? It’s called “shutting down”. Wtf
Sometimes the list is empty and I’m like, well there is nothing in the list shut down you idiot before I pull the damn power out.
Idk if this is a hot take but „no limit“ should straight up not exist. Just set a limit and blow the whole PC up when it takes too long.
Due to what I call some quirks (but what other people call “good, sane, excellent design decisions”), you can set a hard timeout… that can be flatly ignored by systemd for various reasons that might or might not be obvious. In that case it will happily show you
<current timer> / <timeout>, then move to<current timer> / <timeout * 2>, and so on.Because that, for some reasons, makes a lot of sense to some people that are not me.
systemd
Lennart Poettering deserves all the hate he gets and then some…
Lots of things make no sense to some people that are me.
Just set the limit to something sane like 2³² seconds!
Now you’re thinking with squares!
I’m ngl if I see this shit, I just hard power-cycle the machine. I ain’t got time for that.
I’ve never see it, who sets it? I only have two processes that are like it and blth wait for 1:30
I’ve seen it for hardware/driver stuff
Yup, as happened during my most recent linux suicide, dracut just waits infinitely for a device to mount (tho it drops into a emerg shell after like 3 mins or so).
This is the way.
Finger hovering over power button
“I’m giving you one last chance”
That can hit any time, not just in shutdown. At bootup, when suspending, etc. This message and the wait time is so bad. Systemd basically implemented Windows Update waitouts on Linux! It’s incredible!
Switching from systemd to sysvinit solved that pretty nicely.
You didn’t solve the problem. You only ignored it. Systemd does exactly what it’s instructed to do. If a program takes longer it waits if it’s instructed to do so. It’s well defined and predictable. Much better than a random assortment of bash scripts. And it’s incredibly customizable. If the defaults don’t fit you, you can easily override them without touching the main unit itself.
Oh no, I solved the problem: I uninstalled systemd. It’s systemd who is ignoring things, such as the longstanding history of Unix and Linux (research what happened between systemd and screen, tmux, dtach).
I don’t think that’s true. Bootup and suspending don’t need stopping things like that.
Source: I use systemd btw
Oh but it’s not just stopping things, starting things is subject to the same issue also:
A start job is running for "wait for network to be available"(attached to a network interface that is not necessarily connected at bootup)
Systemd is just special.
Ubuntu 17
systemd still does not solve it
Well I guess that tells you everything.
Don’t mask or disable the systemd service.
Edit /etc/netplan/01-netcfg.yaml and add optional: true to any devices that may not always be available.
That’s absolutely systemd’s fault. In any Linux system the only network interface that can (more or less) always trusted to be available and complete a full initialization sequence is
loAbsolutely nothing else.(The worse if you happen to have a WiFi that autoconnects but does it across the same SSID to different endpoints, but that one is wpa_supplicant’s fault if I’m not mistaken. Systemd just makes it worse)
It depends on whether you’re a server or PC. For PCs (as in personal computing) I agree systemd-networkd-wait-online.service should be disabled. For servers, I think it’s plausible that you require a network to be at all meaningful, especially if there’s some sort of database.
Eh, the only kind of server that I think you absolutely need full networking (address, iptables, routing, maybe even DNS) to be “meaningful” would be a database replica. Anything else, there is full use to partial network configuration: anything small enough that lets in a network connection someone else can use to diagnose (eg.: you can have a server that can spin up a meaningful session with only address and netmask, not routing).
That said, I’ve never seen a server, with or without systemd, set to wait for all possible network interfaces that are present to be fully configured… would me emotional murder with something like wireguard that by necessity has a depends on another interface’s routing. Usually with just
loplus any one available interface, it tends to suffice.
Pov: my brain at night
Transcript:
Top: A woman in a parked car screaming at a child in the back seat
Caption:
Why can’t you just SHUTDOWN ?Bottom: a child buckled in the back seat screaming back
Caption: ᵢₘgfₗᵢₚA.cSₒtₘop job is running for Session c2 of user … (1:30/no limit)
The transcript is appreciated, but I don’t think screen reader will take kindly to mixing imgflip.com and A stop job is running.
It was meant to be a joke
Hold on I’ll add a transcript to the body.
