30% space in log file in private folder- can I delete it?

Discussion in 'macOS' started by Buck1, Feb 13, 2012.

  1. Buck1 macrumors member

    Dec 24, 2011
    Few days ago I installed Jaksta for downloading a stream video. I downloaded via this software several videos.

    But today I find out that I am out of space on my hdd (I have got 64gb).

    So I looked to storage info and found out that 30% of used space is "others" with muCommander I also found out that very big space is using folder private, esp. log file:


    and what is inside of this 11GB large files?


    All generated by jaksta!

    so my question is:


    Thanks so much...
  2. Buck1 thread starter macrumors member

    Dec 24, 2011
    are you sure? Now I found out, that system.log contains also other information:

  3. simsaladimbamba

    Nov 28, 2010
    Yes, it is a log file and probably went a bit psychopathic to become that big.
    Look at the link I provided, though you don't need Onyx to do it, Finder can help you deleting log files too.
  4. Buck1 thread starter macrumors member

    Dec 24, 2011
    done- much better saved 11gb of space. But when I look to storage information the files tick with "others" is still to big. Which files is fill this "others"

    I do not use iCal or iChat do not have some big emails in email.app. So where and how can I gain more space by deleting more files from "others" Which files it is?

  5. GGJstudios macrumors Westmere


    May 16, 2008
    For space issues, there are a few things you can try, some of which may or may not apply:
  6. Chorny macrumors member

    Feb 5, 2012
    Bohemian California

    I just had a similar meltdown. I had 270 GB or so free on my 1 TB internal, and something started writing 25.4 log files into the "private" folder last Saturday night around midnight, every 30 seconds for at least 6 hours; something caused the last 4GB of space to be left alone (RAM swap file maybe?); I got rid of the logs (started from external) but only reclaimed about 1/2 the missing space, and absolutely could not locate it (using DiskInventoryX for all of this.) Noticed the hard drive writing furiously and found it was writing the log files again (or still.)
    Had to try to find and back up recent files, wipe the drive, and restore from backup.

    Very frustrating and time consuming (and very hard to not worry about it striking again.)

    If you do happen to locate the rest of the missing space, and find a solution that does not involve erase/restore, please share!

Share This Page