Reputation
272
Top tag
Next privilege 300 Rep.
Create new tags
Badges
2 15
Newest
 Necromancer
Impact
~46k people reached

Apr
12
comment How do I get rid of this power assertion from a dead process?
@Buscar웃 I don't think so. (kextstat | grep -i av didn't turn anything up.)
Apr
12
comment How do I get rid of this power assertion from a dead process?
@Buscar웃 No. Take a closer look at my question—I ask how to get rid of the assertion short of logging out or rebooting.
Apr
12
comment How do I get rid of this power assertion from a dead process?
@Buscar웃 Doesn't seem to have helped—the ghost assertion is still there. As for the MAGICWAKE line, that sounds like a wake-from-sleep-on-LAN thing (especially because of the owner=en1 bit).
Apr
12
asked How do I get rid of this power assertion from a dead process?
Apr
12
comment Is the iPhone 6 more powerful than a 1980s era Cray supercomputer?
An iPhone 6 would indeed look awesome (surprising, at least) sitting in the middle of a dedicated computing center.
Nov
16
comment How do I make OS X require my password immediately after the display is put to sleep?
An example of a log line that explicitly states that a file is being written, as in your answer, would be Nov 15 18:16:53 rainbow-dash WindowServer[78]: dumping current state to disk
Nov
16
comment How do I make OS X require my password immediately after the display is put to sleep?
Yes, my logs have similar lines in them. I said that I see nothing that explicitly says that a file is being written. device_generate_desktop_screenshot() as a function name sounds to me like the system is copying the image currently used as wallpaper, and possibly adding some effects (dimming, blurring?) or something, and then saving it in memory for later use (i.e. to show behind the password prompt later). Without official documentation, we can't say for sure what that does (or even if the name does indeed refer to a function!)
Nov
15
comment How do I make OS X require my password immediately after the display is put to sleep?
I see nothing in your log that explicitly says writing file or locking, only things that look like function|method names and memory addresses. I still don't understand why it can't simply require a password immediately after the user asks for the system to be locked. It seems trivial to me to set a flag that means we're locked now; require a password to unlock, and then do the file writing afterward.
Nov
15
revised How do I make OS X require my password immediately after the display is put to sleep?
amended question to say what I meant
Nov
15
comment How do I make OS X require my password immediately after the display is put to sleep?
Why does this prevent the system from immediately prompting for a password, though? If I catch it while it's writing this file out, shouldn't it just stop writing the file (or finish—doesn't matter, really) in the background and…throw up a password prompt? I guess I just don't see how this is relevant!
Nov
15
asked How do I make OS X require my password immediately after the display is put to sleep?
Oct
28
revised How to decrease the delay to drag and drop files into windows via Dock?
fixed a bit of formatting
Oct
28
revised How do I un-claim a Time Machine backup?
removed broken image link
Oct
17
comment My Desktop folder was “wiped”
Do a Finder Get Info on your desktop. When was it created? Is it possible that something moved it to a different location, and OS X created an empty one when you logged in?
Oct
2
awarded  Necromancer
Sep
30
awarded  Explainer
Jun
29
awarded  Popular Question
Mar
16
comment OSX Mavericks Root User
Alternately, you could do sudo -v periodically. That'll reset the timer to 15 minutes (only prompting for your password if it's already expired). You might also edit the sudoers file and raise the time limit (don't raise it too high, though).
Dec
4
awarded  Revival
Oct
20
awarded  Yearling