can i delete the data in the system log? it takes up 26 GB of my hard disc! help please!
can i delete the data in the system log? it takes up 26 GB of my hard disc! help please!
macbook pro, Mac OS X (10.6.8), 2.16 GHz Intel Core Duo 2GB DDR2 SDRAM
can i delete the data in the system log? it takes up 26 GB of my hard disc! help please!
macbook pro, Mac OS X (10.6.8), 2.16 GHz Intel Core Duo 2GB DDR2 SDRAM
Hi Linc,
I'd read that somewhere about the files being deleted as a rule daily, but I was switching off my computer every evening. Since I read that I've left it on and the size of my log file has stayed about the same. but it's certainly not deleted all the rest of the log!
Thnks very much for all your help and time, I relly appreciate it! I will probably have a go at putting on the discs, I'll think about it some more!
Best wishes
Denise
It should under normal circumstances be rotated the moment you reboot your computer, if you don't have it on overnight. The only time that would not happen is if you have optimizers such as Onyx, Macaroni, or AppleJack interfering with the operation. Those tools should only be used for troubleshooting a backed up system. Macjanitor used to be a tool that would clean the log files alone without affecting anything else. I've written a script that does it without having to enter the terminal called Periodic Logfile Cleanup.
Hi Brody,
Thanks for your comments, I am even more nervous of just deleting log files, even with a programe. some people say just do it and others say don't do it at all, I'm gonna be safe and not do it! thnks anyway for your imput!
As a troubleshooter of Mac OS X since the beginning, the only harm that can come of deleting a log file is that you won't be able to see software errors that might have happened since the last rotation that wipes them out automatically on a daily, weekly, monthly rotation. Since this is a system based operation that is normal, you are merely speeding that operation up. Cache files are much different. The operating system creates them to optimize its performance. Sadly the cache cleaning software does not know how to distinguish between a cache file that is being written to and open, and one that is just stagnant. As a result, since programs use it to find what they were last doing, deleting one, leaves a program hanging. System cache files are always open. Many utilities delete them indiscriminately, and cause the system to be unable to launch its own programs. Sometimes they get so bad, the programs won't launch without an erase of the entire drive. You may even find manually deleting cache files, only results in the same corrupted cache file being created on the next reboot forcing the same cache files to stop the launching from working properly. It is for this reason I say, stay clear of those cache files.
I see ok Brody, thank you! I think I'm out of my depth here!
Just an update to the problem of my disc taking up so much space. I have not checked it for some months , I decided just to leave things alone and have an attempt later on to get it sorted out. It seems that it had sorted out itself! I just checked and there is a messege saying, (on the 9th June 2013) , that
- Any comments? many thanks for advice on this, I don't want it to escalate again!
(com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
09/06/2013 19:21:41 com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
09/06/2013 19:21:41 com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
09/06/2013 19:21:41 com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
09/06/2013 19:21:41 com.apple.launchd[1] (com.apple.SystemStarter) Failed to count the number of files in "/System/Library/StartupItems": No such file or directory
09/06/2013 19:21:45 iStatLocal[155] iStat Menus Agent version 3.27 (103)
09/06/2013 19:21:47 CleanMyMacHelperTool[156] Mounted devices (
)
09/06/2013 19:21:47 CleanMyMacHelperTool[156] CleanMyMacHelperTool started as volume cleaner with cleanTrashes 1 cleanMacOSJunk 1 cleanWinJunk 1
09/06/2013 19:21:47 CleanMyMacHelperTool[156] Mounted devices (
)
09/06/2013 19:21:47 CleanMyMacHelperTool[156] CleanMyMacHelperTool exited...
09/06/2013 19:21:48 com.epson.Epusp[154] Epusp: Terminate..
09/06/2013 19:21:48 com.apple.launchd.peruser.502[123] (com.apple.Kerberos.renew.plist[149]) Exited with exit code: 1
09/06/2013 19:21:48 com.apple.launchd.peruser.502[123] (com.apple.mrt.uiagent[148]) Exited with exit code: 255
09/06/2013 19:21:49 iStatLocal[155] checkForUpdates
09/06/2013 19:21:56 rapportd[152] *** __NSAutoreleaseNoPool(): Object 0x8435a0 of class NSCFString autoreleased with no pool in place - just leaking
09/06/2013 19:21:56 rapportd[152] *** __NSAutoreleaseNoPool(): Object 0x84c640 of class NSPathStore2 autoreleased with no pool in place - just leaking
09/06/2013 19:21:56 rapportd[152] *** __NSAutoreleaseNoPool(): Object 0x843780 of class NSConcreteData autoreleased with no pool in place - just leaking
Assuming that you've backups, I would simply trash system.log.0 & empty the trash.
Logs normally seem to go system.log; system.log.0.bz2; system.log.1.bz2 etc so I can't say why you've one with that exact name, but it's not been modified since May.
OK thank Andy for your help, I have included another screen shot showing other logs taking up more space! its a bit mad! I think this may have happened when I had a new motherboard about 3 years ago.
The others look normal, & unless you notice problems or shortage of space, are better ignored.
Yes Andy after your info on the log file names thats what I thought. Do you think it's best to delete log.0 from the discsweeper app or just go to the file and delete from there? I will leave the other log files alone!
Either method should work, I've not used discsweeper to know for sure.
OK, thanks for your help Andy and thanks again to Linc and a brody for their earlier help. I'll let you know how it goes!
well discsweeper will not delete this log file. im deleting straight from the file but it seems to be stuck, but then again it's such a massive file it could take hours to delete? I don't know, what is your experience on this Andy? thanks!
can i delete the data in the system log? it takes up 26 GB of my hard disc! help please!