Ask Lemmy

I definitely shut down my systems from time to time just to make sure my network is configured correctly and shit doesn't go haywire because I'd rather have that happen than the power go out and everything comes crashing down

Power Off to secure that things get updated and resetting float integers in case they would go haywire

Poweroff could use more write cycles on the SSD because it has to read everything at startup, but suspend has to keep supplying power to the RAM

for this, I would say SSD is more valuable personally, so if that was my only reason, I'd suspend to RAM every time

My computer's generally doing stuff I have it set to do, so I don't suspend to RAM

Laptop gets turned off when going outside, also encrypted

Suspend. The amount of power required to keep RAM alive is negligent.

Nearly always suspend. It just works for me and I've never had issues (Arch and Pop). I rarely, rarely have power outages so the end result is the same.

I'm lazy and use systemctl poweroff! 😆

I use poweoff generally. On my laptop, the cellular card prevents sleep, and my desktop often refuses to wake from sleep.

Honestly not much fussed about it as both systems boot so quickly that it's not much of an issue.

As for SSD longevity, again not much fussed about it. In the last 20 years I've only had 1 SSD fail so far. A 40GB drive that bought in 2007ish finally failed last year.

Haven’t needed it to, I guess even after kernel updates you can log off and log back on to set the changes.

I use suspend on my desktop every night at bed time. Running Pop. Could never be one of those with a 24/7 on desktop, too much noise.

I use a laptop, so I iust put it to sleep. I only restart it when I do updates or when the system crashes. I also turn it off (when I remember to do so...) if I leave it unattended in untrustworthy environment due to encryption.

I also have a mini PC, but I only turn it on when needed, which isn't often since I haven't really figured out what to use it for. It's running Linux Mint headless, because Mint fits my laziness. I can use it via Tailscale, but I don't really know what to do with it. So far it's been mostly useful with OpenWebRX, SDR++ server which also offers compression unlike RTL_TCP as well as being able to use any SDR++ supported SDR, and I also intended to use Navidrome on it as well. My intention was to just download full albums on there, rather than picking out individual songs, but I still have the urge to put all of it on my phone.

I use suspend with Linux Mint on my Framework 13.

I'm using suspend on my desktop running Manjaro KDE. To reduce power usage it goes to sleep after 15 minutes of inactivity and wakes up on mouse or keyboard input. Aside from some flaky kernel versions and after underclocking an unstable EXPO profile it's pretty stable, even games continue to run after wakeup.

After shutting down anything in use, I use suspend set for a 35-minute delay. Most evenings I listen to bed-time audio. Ubuntu hasn't been terribly reliable, works about 2/3 of the time.

I use the hybrid: suspend to ram, then after 2 hours, automatically suspend to disk - in the final state it uses zero power. And, if you have encrypted your drive (you DO encrypt your drives, right?!) then you need to enter passphrase on resume from hibernate, so safer if device was nicked.

I could care less about the 5 cycles from 10.000.000 total cycles (dunno the actual number) at least for my desktop.
As for my proxmox server: 5% wearout

whatever happens when I click shut off or the power button on my pc

Pop!_OS, suspend. Rebooting causes Steam to forget about my second drive and I need to reselect it. I don't need to do that if I use suspend.

Arch testing here. Suspend/Hibernate can and will break at any time, especially with newer s2idle-only systems, so I tend to keep suspending to a minimum, and also end sway before suspending.

Eg. right now I have to keep systemd-suspend etc. from freezing user.slice, as that fails and goes into an endless loop, ending in needing a hard reboot anyway.

Suspend, most of the time. I have a two handed Vulcan nerve pinch keybind that does that for the end of the day. A desktop PC doesn't have a lid, but that keybind is about as cathartic as closing a laptop.

This is actually different from how I have the desktop environment set to do it, which is the hybrid suspend/hibernate option. This gives me at least a couple of options without too much messing around. Quick shutdown: Use keyboard; Hybrid: Use GUI (which can be done by keyboard navigation too if absolutely necessary.)

The reason? There's a surprising amount of state, such as open windows, browsers, etc. that need to be set back up if coming back cold from a full power off and that bothers me more than maybe it should.

By rights, I should use the hybrid option all the time as it's technically safer, but it takes longer to power off and it actually suspends then unsuspends for a few seconds as it sets up the hibernation profile, which gives me the willies.

Also, the power grid is pretty stable here. If I was elsewhere I might be using the hybrid a lot more.

I use echo o | sudo tee /proc/sysrq-trigger

sudo halt && shutdown

If I'm shutting down it's only because there is a problem causing a lockup

I close the lid. Ubuntu 24.04, fedora 41 and Arch. All gnome.

Power off.

I use Mint btw

My work machine (Ubuntu) gets suspended at the end of the day during the week and shut down on Friday. It's a good balance between keeping my many programs running and ready and cleaning up regularly.

I always shut down my desktop pc (Arch, btw) as it takes just a few seconds to boot up.

My laptop (Arch) I shut down because suspend never worked.

I suspend so I don't have to wait for stuff to load up on boot

I just turn off the screens, and I have a usb switch to switch off my keyboard and mouse (a cheap usb flip switch + a small usb hub).

Reboots when needed.