AFAIK there isn't a direct way to do this. There are several alternatives though:
- Folder Actions: Create a folder action (which gets triggered upon each change in a folder) to run the
chflags
command if needed. As Folder Actions only apply to to one folder this needs an Action for every folder you create .dSYM files in
- launchd: Use
WatchPaths
to run a script whenever one of the listed paths is modified
- Hazel: Hazel is kind of like Folder Actions on steroids and allows you to create actions based on various rules
PS: cgdb isn't affected, chflags
only makes files invisible on Finder level (and in Open/Save dialogs).
Please post the make/model/specs of your machine, and especially the brand, model and firmware revision of your SSD. I have an SSD that started throwing errors after 4,900 hours of operation. Updating the firmware resolved the issue.
You can find the SSD firmware by running the Hardware Profile (or more info in About this Mac) and selecting Serial-ATA and the your SSD in the Device Tree.
Is the problem hardware or software?
I will attempt to list here a couple of possible issues, and what we need to help resolve.
If you have a second hard drive you can boot from (HDD, USB drive, etc.), please do.
- Does the problem still occur?
- If it does, does it happen on the boot device or still on the non-booted SSD?
- While booted from something other than the SSD, run any disk checking software you have, even if its just a Disk Utility/First Aid/Verify Disk
When did this problem start, and can you peg it to any action you did?
Wild process
Open Activity Monitor. First, click the drop list and change from My Processes to All Processes. Then click on the %CPU column header once (or twice) so the list shows the top CPU users at the top
Is there a run-away process at the top? If so, please let us know.
Consistency after reboot
How soon after a reboot does the disk usage start? Do you reboot with the following option checked?
If you do, reboot, but first uncheck the option.
Now that you're opening with a "fresh" login,
- how soon after reboot does the problem start?
- Is there a consistency with any programs running when this happens?
Your problem can be a lot of things, but from your initial output, I'm less inclined to think malware.
Best Answer
To reply to your question: no there isn't such a function accessible at the window manager level. It is a good suggestion to forward to Apple MacOS X feedback
Is your Mac still up?
Try:
Can you access it with
ssh
?Can you provide us a copy of the output of a:
and:
If the problem appears once more, could you try to kill the loginwindow like this: connect on your mad Mac with ssh
This uggly command:
is a trick to give you the process ID of the loginwindow process with no risk to kill the wrong guy. I'm not sure this will be enough to force a total free and reset of the GPU. Please tell me if this doesn't work so I could remove a useless and dangerous workaround.