←back to thread

macOS command-line tools you might not know about

(saurabhs.org)
2039 points Gadiguibou | 4 comments | 27 Jun 23 12:08 UTC | HN request time: 0.861s | source
Show context
brazzledazzle ◴[27 Jun 23 13:24 UTC] No.36492363[source]▶
Probably want to check your policies if using a business-owned mac. Caffeinate probably violates your security policies if it’s a decent sized company.
replies(3): >>36492485 #>>36492983 #>>36499523 #
1. computerfriend ◴[27 Jun 23 14:06 UTC] No.36492983[source]▶
You can lock the screen while caffeinated though.
replies(1): >>36494189 #
2. brazzledazzle ◴[27 Jun 23 15:22 UTC] No.36494189[source]▶
Automatic screensaver enable after a period of inactivity is considered a fail safe control.
replies(1): >>36494928 #
3. wpm ◴[27 Jun 23 16:17 UTC] No.36494928[source]▶
`caffeinate` can set assertions, the same assertions that Zoom or PowerPoint or Keynote do to stop the screen going to sleep during a meeting or presentation, the same assertions that the browsers can set during streaming video, so you absolutely can bypass whatever your admins set using `caffeinate -dmisu` which sets every assertion available.
replies(1): >>36528531 #
4. brazzledazzle ◴[29 Jun 23 23:55 UTC] No.36528531{3}[source]▶
It’s not about capabilities, it’s about policy. Willfully violating security policies is generally going to go over poorly.