My average uptime is about 22 days until I reboot for an update or something.
I used Linux for years, and I understood that in 2008 sleep/resume on notebooks didn't properly work, but now we have 2017 - 9 years later!
Also, old laptops with dieing batteries (or new ones with always-on sensors such as fingerprint readers) have some leakage during sleep so it may be better to turn them off if you are not going to use them for a few days.
edit: resume/suspend in linux works just fine and has done so for many years (in response to eltoozero)
I've had Linux on mobile for ages and have yet to have reliable sleep/wake behavior on a dozen machines over the years.
Sleep on Linux works reliably if you run it inside a Mac VM though, FWIW! ;)
BTW: OSX has not a "pure" suspend to disc anymore and the default method is suspend to RAM when closing the lid
Which means the user loses data.
I was reporting that.
I don't mind boot times in the 20s range (X220/Fedora/cheapo SSD) too much, but I do need to close down/reboot a couple of times a day otherwise no point in encryption.
Given, I'm not a Linux user, but I don't understand this at all.
On Windows, encrypted is encrypted-- the lock screen is exactly as secure as the login screen. Are you saying that in Linux the lock screen is easily-bypassed? So you have to keep your computer logged-out when you're in a place it might get stolen?
Wasn't there a recent story about how Windows is storing keys so that it can wake up in the middle of the night and apply updates? I thought that the conclusion was that locked isn't as secure as logged out.
Above quote is from the section titled 'How to encrypt your disk in Linux' on the page at
https://theintercept.com/2015/04/27/encrypting-laptop-like-m...
I'm just a bit confused about how Windows can remove keys without messing up file handles &c when suspending to RAM.
The level of security I have now is adequate to my purpose but certainly something for others to take into consideration. Thanks for posting.