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)”
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?
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
I guess I’ll need to look into that option too. Probably won’t look into neither, though. I’m lazy.