I had this exact problem only a month or so ago. It was the user's Apple Watch magnetic clasp that was triggering the sleep function since the laptop believed the lid had been closed when the user was waving their wrist over the laptop while typing away. Proud of myself for not taking anywhere near years resolving that! A mere 60 seconds was sufficient for me to spot that, honest.
Posts by rjstua
10 publicly visible posts • joined 16 Sep 2015
PC tech turns doctor to diagnose PC's constant crashes as a case of arthritis
Scammers steal $4 million in crypto during face-to-face meeting
Two signs in the comms cabinet said 'Do not unplug'. Guess what happened
Literally rings our bell: Scottish eggheads snap quantum entanglement for the first time
OpenAI bots smashed in their first clash against human Dota 2 pros
North Korea's antivirus software whitelisted mystery malware
Suspected drug dealer who refused to poo for 46 DAYS released... on bail
You shrunk the database into a .gz and the app won't work? Sigh
I started at a new company a while ago and did all the usual checks and measures to see how the land lies.
Backups was first. Every day we received a "Backup Complete" email, great! Backups are being done....until you look at the amount of data backed up. Approx 1GB of data was being backed up, successfully, to the single tape backup. Alarm bells started ringing, especially as the mailstore itself totals 90GB. There's no compression algo in the world that is that efficient right?!
After further investigation, it transpired that we were backing up a single database only. The database was essentially an index of what was supposed to be backed up, but not the actual files themselves. Yosemite Server Backup had decided that, despite not backing up well over 400GB of data, the fact it had backed up 1GB of an index was successful enough.....
Sorted now though, with a successful backup AND restore tests!