OK to delete console.log files?

Discussion in 'General Mac Discussion' started by CalfCanuck, Feb 10, 2005.

  1. macrumors 6502a

    Joined:
    Nov 17, 2003
    #1
    Was trying to tighten up my iBook G4 hard drive, and came across 1.4 GB of console.log files.

    Is there any reason I should not delete these? Are they merely descriptive of past events or does the system need them?

    Seems a bit of a waste of good HD storage to me, but want to check it out here before I do something rash! ;)
     
  2. macrumors G3

    Joined:
    Jul 23, 2002
    Location:
    Sol III - Terra
  3. macrumors 68030

    Platform

    Joined:
    Dec 30, 2004
    #3
    Why is it good to keep the console.log :confused: and OK to get rid of console.log.#
     
  4. thread starter macrumors 6502a

    Joined:
    Nov 17, 2003
    #4
    Thanks!

    My console.log.1-0 are 1.27 GB, while the console.log is only 4 KB.

    I'm curious what causes a new log file to begin, as the old files range in size from 4 KB to 972 MB ...
     
  5. macrumors 604

    ravenvii

    Joined:
    Mar 17, 2004
    Location:
    Melenkurion Skyweir
    #5
    Or you can just leave your computer on overnight (not sleeping), and OS X's maintainence cron jobs will take care of it for you.
     
  6. macrumors G3

    Joined:
    Jul 23, 2002
    Location:
    Sol III - Terra
    #6
    console.log is the current file and if something goes wrong, it'll be good to have around to look at.
     
  7. Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #7
    When you log in, a new console.log for your session is created and the old ones are rotated. If you have a laptop, chances are you sleep it constantly and don't logout/restart/login/etc very often, so your logs don't get rotated very often.
     
  8. macrumors 68030

    Platform

    Joined:
    Dec 30, 2004
    #8
    So that would be the reason for him havin so much log files :confused:
     
  9. macrumors 68030

    Platform

    Joined:
    Dec 30, 2004
    #9
    Thanks

    But as mention earlier does OS X do the fixing job for you if you leave your system on for a long time :confused:
     
  10. Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #10
    Upon further reflection, it's more likely that the log gets rotated at logout. I'm not sure yet.

    He will never have more then 10 archived console logs.. but their size is an indication that something is potentially wrong with the system. Something was complaining bitterly and splatting to the console, which increased their size. And if whatever splats 5MB of crap into the console.log daily, and it's 1 month between actual reboots/relogs/whatever, you're looking at 155MB of wasted space. Then the log gets auto-magically rotated when you logout(/in?), and say you have 10 of them.. poof.. that's 1.6GB worth of disk space eaten up by your logs.
     
  11. Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #11
    Nope, I was right the first time.. console.log is rotated and recreated at login.
     
  12. thread starter macrumors 6502a

    Joined:
    Nov 17, 2003
    #12
    Thanks for the info.

    The log files did seem to have calmed down a lot lately, so I'll be keeping an eye on them (as a example of how healthy my system is).

    I'm not sure why the logs didn't clean themselves out, though, as I do sometimes leave the machine on overnight for a Retropspect backup.
     
  13. Moderator emeritus

    yellow

    Joined:
    Oct 21, 2003
    Location:
    Portland, OR
    #13
    Console.log isn't touched by the overnight scripts. Peruse /etc/daily, /etc/weekly, and /etc/monthly for confirmation.
     

Share This Page