Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

52GB Cache file?

J

JBot

macrumors 6502
Original poster
Jan 9, 2006
271
1
Calgary.Alberta.Canada
For the past while i have been constantly running out of space on my macbook pros hdd. I would fill it up, then copy files onto my external, just so i could fill it up again a couple days later.
Yesterday i decided i was going to copy all my music off of my machine and run it solely off my external, thus freeing up 43gb of local space. It was a thing of beauty seeing that much available space sitting at my fingers, until this morning when i woke up to the oh so familiar warning message saying my startup disk is full once again. SERIOUSLY? i started up jdiskreport then went off to work.
I now sit at work, logged onto my home machine and found out where all my space went. Under LocalUser/Library/Caches there is a file called xxx.qNation.pghistory that is 52.25GB.
Now i know what youre thinking, and no there is no possible way i have 52GB of cached porn on my computer.
Upon googling the file i found nothing. Does anybody know anything about this file? Can i just destroy it, or does any app depend on this random massive file.
...If it is 52G of cached porn, is there any way i can view it? ...for research purposes only of course.
 
User WaterRoof to control ipfw2 for incoming traffic and Little Snitch for outgoing traffic. No 52GB cache files then.. ;)
 
Yeah, it's a bug in the PeerGuardian software. The devs know about it but give no word on when a new version will be available.
According to this thread the file is supposed to be capped at 256MB.

Open PG and from the menu choose "Quit Helpers".
Then quit PG.
Then you can trash the xxx.qNation.pghistory file.

This is only a temporary fix of course.
Next time you leave your torrent software running overnight PG will recreate the file and your drive will be full again.
So maybe yellow's comment is the way to go.
 
I had the same problem as this when using peerguardian, this is what I did to stop it.

Kill peerguardian.
Delete the xxx.qNation.pghistory file

From the terminal:
cd /Users/<username>/Library/Caches
touch xxx.qNation.pghistory
chmod 000 xxx.qNation.pghistory

This recreates an empty instance of the file and then removes all permissions (including write permissions) from that file. This prevents peerguardian using the file and so no more huge cache file build up.

It doesn't seem to affect peerguardian in any way but you might want to test it for yourself.

Hope this helps
 
Ooh yay... more misbehavior from the PG folks. Sigh. You know, I can't help but think that between the blacklisting of legitimate hosting providers and the incredibly craptastic software that perhaps we need a good, open, community-run replacement for PG...
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back