Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
61% Positive
Analyzed from 4371 words in the discussion.
Trending Topics
#reboot#windows#restart#more#off#don#down#uptime#days#mac
Discussion Sentiment
Analyzed from 4371 words in the discussion.
Trending Topics
Discussion (126 Comments)Read Original on HackerNews
I used to work at an office where we pair-programmed with clients all day (Pivotal Labs), and most of our computers had some sort of "automatically restart / restore from a known-good image". I liked this, as it resulted in less cruft over time, and some intentionality about what getting a computer into a productive state means. It also got me thinking of using automatic routines to accomplish goals, and not being so attached to my open tabs, etc. Let it gooo....
To be more specific about this - for those wanting to get into blogging/publishing, this could mean auto-opening the website project folder using VSCodium upon user login, so its ready to go for the morning coffee. More half the time I just close it - but as a "default", it makes it easy for me to do the thing I want to do.
It's kind of a power hog and generates a lot of heat, so I try not to run it if I won't be around.
Shut down != reboot, but you get the idea.
These days I like to turn my work Mac off at the end of the week just so I feel a literal sense of closure. It's not really the applications minimizing and running in the background; it's ME.
Red Hat Enterprise Linux[1] and Oracle (Enterprise Linux) Unbreakable Linux[2] both use it as a selling point.
This feature is still a bit ad hoc because, in most setups, rebooting a system isn't a huge burden and is much simpler than using boutique commands to live-patch it.
[-1] https://en.wikipedia.org/wiki/Ksplice
[0] https://www.ksplice.com/
[1] https://www.redhat.com/en/topics/linux/what-is-linux-kernel-...
[2] https://docs.oracle.com/en/learn/ol-ksplice/
Systemd added support in recent 2.61. Theres also now ways to have user stores, that survive across switches. https://www.phoronix.com/news/systemd-261
I used to reboot into every kernel patch but often I leave .0 running for a very long time now. They seem stable and the kernel moves fast enough nowadays there's often another .0 right around the corner. There might be exploits but they're not a valid threat model for my little desktop.
If something smaller like Mesa updates, I can reload everything simply by logging out/back in, no need for a full reboot/LUKS unlock.
Microsoft literally bought these 6 or 7 servers to migrate to IIS so they could “beat” Apache. It took more than double the servers, but after I did the initial work it was moved to a different team and I don’t know how the uptime compared.
It's also just nice to start Monday with a fresh boot.
If nothing else, it keeps me from getting to the point of 200 tabs open that I'm totally definitely going to need again "soon"
(Disclaimer: I'm aware that there may be valid reasons for this workflow, but in most cases it's just digital hoarding and the above advice is sorely needed. If you really need 1800 tabs, you know who you are and you can safely ignore me.)
Every crash cuts deep if it doesn't resume correctly.
- Install all updates
- Save tabs off to Obsidian (or Raindrop now)
- Reboot
Feels good coming in on Monday to a fresh session.
I do actually reboot occasionally these days, because the world is so serious now.
At least if you trust the NSA's advice: https://s3.documentcloud.org/documents/21018353/nsa-mobile-d...
https://checkra.in/
I think windows and Linux users usually shut down their laptops when they are done.
I believe this is because of how Mac is designed, nothing really closes. You close an app and it's just "minimized". Same behavior as with the lid, you close the lid and it suspends.
If I recall correctly, at some point, this also affected the iPhone, you were not able to "fully close" apps and they decided to add a screen so you could swipe and "close" the app (some run in the background, same as android)
"Fully closing" a process is not necessarily cleaner than letting the system allocate intelligently, despite what one's puritanical upbringing might make them believe. (Consider how artists often need a messy space to optimally hold their processes.)
Yes, that they actually got sleep working properly.
Back in the spinning rust era, though, a good unsuspend could be something like 50 times faster to get to a running computer. Possibly more, depending on what your OS needed to start up.
It is still more convenient to have my previous environment most of the time, and still faster to unsuspend than boot, but it isn't as much of an advantage as it used to be, no.
My old HP laptop had a slow-ass BIOS that I was convinced had some kind of bug. I replaced it with a brand spanking new thinkpad 2-3 months ago. Guess what? The freaking BIOS is EVEN SLOWER somehow!
They all wake up instantly from sleep.
I therefore only shut them down when I know they'll be unplugged for a while, because for some reason the HP eats through the battery even when off. If suspended, the battery will be out of juice in like two days. Haven't tried any of this with the Lenovo yet.
Suspend used to work great, but since MS figured they should copy Apple half-assedly, suspend is borken. And I have really no idea what we've gained in exchange.
Kind of reminds me of how slow Windows computers used to boot back in the Vista and 7 era.
Also, my Win11 desktop is "fast" to get from POST (which takes > 2 minutes to do RAM check on every boot with 192GB RAM) to the login screen, but it's a good few minutes from log in before windows has started all the background stuff and it's actually functional.
At one instance, I rolled over to a coworker who has just rebooted theirs and had a whole 5+ minute conversation.
Needing to shut down to me indicates something is broken.
I have a Linux server that can run for years without needing a reboot. But my laptop I just shut it down after my work is done
It doesn't require it to stay up, and if things were better at retaining state across restarts I would care less, but it's a nuisance to have to log back into things, and get things back exactly how I left them.
I often have half a dozen projects up on different virtual desktops, and leaving them how they were when I worked on it last makes it easier to get back up to speed.
EDIT: I used to leave screen sessions running on servers instead, as the workaround to having to reboot my local machine. But it's nice not to need to.
Although... 30 days is maybe a bit misleading, because I ran some heavy shaders without thinking that triggered the GPU watchdog and forced me out of my session. I think killing all user processes is almost like a reboot, although not according to uptime.
Electricity also wears down electronic components, so I think it also shortens the lifespan of your PC parts.
- You can "Quit" the application without closing all the windows, and then the next time you start the application, your windows can come back.
- You can close all the windows without "Quit"ting the application, and you don't have to wait for the application to load again in order to open a window later.
Additionally, since application lifecycle is managed separately from the open windows, apps can do cool things like saving and restoring the set of open windows through a system restart. Which Windows and Linux still haven't managed. (Maybe Windows can try to restart the processes... I think I saw that becoming an option more recently)
I've never rebooted often in general, even when I daily-drove Windows. Then, it was because it was annoying to get my preferred workspace back after a Windows restart. Now, I daily-drive macOS and I don't often reboot until the machine gets slow/janky because the machine doesn't really need a reboot until then. And I don't hate reboots as much as I would for Windows because macOS is a lot better at session restoration
The downside is that I often get shunted off into additional authentication workflows, since the prolonged delay caused by my manual approvals triggers some alerts. One of the entertainment ticket buying services is really convinced I'm committing some kind of fraud.
So, in general, I reboot everytime I start using that machine, at least once per day, sometimes more frequently.
Fun fact: in a former life, I worked for a retailer with 1000s of remotely deployed machines and no field-based tech support. One of the OSes we used back in the day had a bug that caused their license authorization service to fail after a certain amount of uptime. We had hundreds of machines that reached that uptime, all on the same day. Suffice it to say, that was not fun.
Not sure how much is that quality of dev went down vs quantity of threats went up.
As to why, I assumed it’s because security fixes are in basically every update these days. And it’s easier to change core systems with a restart than live
And I'll likely do it again.
Not always by choice. I can crash the system by playing a certain game (they still treat the Apple platform like crap).
I can also put it into limbo, with Xcode, one of the most bountiful bug farms on Earth.
Though I shouldn't use the word "common" as the occurrences are rare. My guess is 4-6 times a year over the past five years. Would love to know what causes it but the randomness of the symptoms would make investigating a bit difficult.
Do you have some unusual hardware that requires a driver, or otherwise install something that requires a driver?
it feels bad in some sense but I don't like my environment being interrupted!
Found it: "By default, Windows computers use a "Fast Startup" feature when you click Shut Down." It actually performs a sort of hibernate, saving state data of the system (but not necessarily of all running programs - that's another setting). Restart clears those state registers and begins a new, fresh Windows session.
So, ideally: Perform a Restart, not Shut Down, at the end of your day.
[1] https://www.titanium-software.fr/en/onyx.html
can't be hacked if it's completely off
can't get struck by lightning or surges if the surge-strip is flipped off
fans and spinning drives have lifetime on motors
That's not how electricity works. Hot may be open but your ground and return is not.
Lightning hit an antenna that was disconnected but near a radio and blew up the radio, the PC it was connected to, and then everything connected to the switch that was connected to the PC via cat5, and just for good measure, everything connected to an outlet on that side of the house within 15' of the computer outlet. once it gets in, it doesn't matter if stuff is off or on or whatever.
That being said, I hibernate at the end of my day. For some reason, merely closing my Dell laptop just isn't as smooth on reopen as my Mac. The startup is almost as long as a full reboot.
Did you have a different qualification in mind?
I do hibernate sometimes though, and that is pretty much the same final state power-wise as doing a shutdown (more so for my laptop as it does not keep keyboard/mouse powered in S4 and its the same with the hall effect sensor for the lid).
But today I had to power it off, I accidentally created a fork bomb changing a couple of scripts on OpenBSD.
It did not freeze the system but I could not create any more processes. shutdown(8) could not even run, so a hard power off :)
Wait, what? Why is OP using Edge on a Mac? To each their own, it just caught me as odd.
And, as Betteridge’s Corollary or whatever demands, the answer to the headline is “no”. Is this like ancient wisdom about batteries, you’ve got to run them to zero once in a while or they’ll get a “memory”? (Which, of course, hasn’t been true for, like, twenty years.)
Very rarely there's a published kernel fix leading to an exploit that could potentially affect my setup that requires rebooting, but that is exceedingly rare.
FWIW my desktop regularly reaches six months of uptime and I had a server at OVH which I kept just because I could that reached something silly like 3400 days of uptime (it just didn't reach 10 years). At some point (after maybe three years) the uptime was so cool I decided to just keep it and see how long it'd stay up (and, no, that one wasn't secure at all: kids, don't try this at home). When the fire at OVH took entire bays off, I wasn't affected so the thing kept cranking.
If we leave security concerns aside, OSes are really that stable now (unless we're talking about Microsoft products of course).
> Have You Restarted Your Computer This Week?
Now of course I've got something like 12 computers at home so it really depends which computer you're talking about. For example I've got a server with ECC memory that runs VMs and containers but... I only need it when I'm awake. So that one I typically turn off at night (for the energy consumption). I know, I know: desktop up and server down at night I must be doing something wrong right? But then it's my setup and I do what I want.