toresolution.blogg.se - Run grandperspective as root

#RUN GRANDPERSPECTIVE AS ROOT UPDATE#
#RUN GRANDPERSPECTIVE AS ROOT FULL#
#RUN GRANDPERSPECTIVE AS ROOT MAC#

GrandPerspective will show you a nice graphical representation of disk usage, showing every copy of each file on the backup, so if you have a huge 5 gig file that's changed 5 times, you'll see 6 big blocks.

If you backup your main disks to a drive called "Backup Drive", then scan Backup Drive/Backups.backupdb/Yourcomputername

Use GrandPerspective to scan your backup of your drive.

The best way I've found to hunt down and remove files from backups is this: Find the file or folder, right/control-click and choose either delete that backup, or delete all backups (versions) of the file.

#RUN GRANDPERSPECTIVE AS ROOT UPDATE#

so I've just changed it to 1 - that may help a little (or at least buy more time before it goes silly)įor some reason inside PDApp.log verbosity is defaulting to 4 - there should be some other magic xml value to be set in the prefs that will override that - but I can't find any reference to it anywhere and the XML for this file seems to be completely undocumented by Adobe (that I can find) - so if anyone else sees anything that would help at least reduce the verbosity of this stuff then please update this seems to be a common problem, and when AAM goes wrong (possibly when it can't reach Adobe CC - but I can't prove that) - these logs fill up quicker than you can blink.You can remove files from backups by viewing the enclosing folder in the Finder, then enter Time Machine. I'm not 100% sure which way the number goes or indeed if the logging level parameter applies to all logs - but I'm guessing that making the number lower will reduce the verbosity somewhere. However, I'm *trying* a slightly different approachĮdited: ~/Library/Application\ Support/Adobe/AAMUpdater/1.0/AdobeUpdaterPrefs.dat (it's an xml file - so any friendly text editor will work - vi is your pal) If you want to disable the auto updates - take a look here (this is a widely published link to solve this problem if you spend some time googling) and works fine: Disable auto-updates | Application Manager | IT administrators You can do some things to control the logs with ~/Library/Application Support/Adobe/AAMUpdater/1.0/AdobeUpdaterPrefs.dat

#RUN GRANDPERSPECTIVE AS ROOT FULL#

Then I ran grand perspective to find why the disk was suddenly full - the result you see in the previous post, just deleted the excess logs and rebooted the machine - all fine again.Īt this point I decided to do some reading and found the following: I killed the AAM process (using Applications/Utilities/Activity Monitor - which is where you could see it going awol and chewing up CPU and disk) - but for those of you comfortable with Terminal ps and good old kill will do just fine So my log files are in ~/Library/Logs (guessing they got shifted recently) - mine went ballistic last night when AAM went into a very silly place and decided to spent the entire night writing log entries. If one sticks out (in my case, it was "/private") you can change the command to:Īgain, this will give you another list of folders with their sizes. This will tell you the size of every folder at the "root" level of your computer. PS: for others of you who may have related problems trying to find mystery huge files, you can run a command in terminal:

Is there some way of controlling this monster? Can I stop it? Or at least limit the maximum size this file can grow to?

I chatted with support and they told me since I use Fireworks they can't help me and to ask here. I already know I can delete the file, but of course I don't want it happening again. Lots of forum reading and snooping around my system later, I discovered that a file called /private/var/root/Library/Logs/PDApp.log was to blame, and was in fact 185GB (out of my available HDD space of 256GB. GrandPerspective and Disk Inventory X showed my total hard drive space at about 60GB, but GP showed "miscellaneous used space" at 180GB.

#RUN GRANDPERSPECTIVE AS ROOT MAC#

After months of fighting and deleting my own files, I finally ran out of space on my mac (OS X 10.10.3) and was stopped dead.