SD 2.1: error processing extended attributes: Cannot allocate memory

[george]

priller writes, "FWIW ..... The 56,000 lines per Smart Update are in my /var/log/system.log....."

Thou not necessarily the final solution, does not running an app like Macaroni (as you mention) flush/keep the size of your system.log file under control?

[priller]

Originally Posted by george

Thou not necessarily the final solution, does not running an app like Macaroni (as you mention) flush/keep the size of your system.log file under control?

Marcaroni insures that the system.log file is rotated every 24 hours, it does not reduce the size of the daily's.

[sdsl]

There were two issues discussed in this thread:

* asl.log growing in size due to many messages being written (harmless messages generated by Mac OS X Tiger)

* system.log growing due to similar messages

The asl.log issue is resolved by the neat little script (prune log) that was provided in an earlier post by the forum administrator. It works nicely.

I think the system.log file size issue is resolved by the DAILY maintenance script. I ran it manually and before doing so my system.log had been ~ 10 Meg having grown to that size just after running SD, but after the maintenance scripts the largest system.log (including the archived ones) was under 100 kbytes, which is nothing.

So SD has provided an automated cure to the asl.log growth (just add the script to your SD run), and it looks like to me that the automated Tiger maintenance scripts (which can be activated manually via terminal or via a free program like MacJanitor), which run every night automatically, somehow shrink the size of the system.log.

SD is not the only program that affects these log files this way. I think it's a defect in the way Mac OS X handles these log files. Until Apple cleans this up, I think it's really a non issue because Dave's prune-log script and the maintenance system scripts together remove the excess file sizes.

[priller]

Log file rotation is not a resolution, it just masks the problem.

The size, in bytes, of the file is not the issue. It's the number of log entries. If you inject 56,000 lines of crap into the syslog, it makes it that much more difficult to look for real issues, like a hacker attack.

[dnanian]

We're not satisfied with the prune_log workaround, and continue to try to figure out a way to stop it from logging entirely. Sorry for the time it's taking...

[DaleMeyn]

sdsl, I'm not sure I have any of the "asl.log" problems, and use macaroni so the system.log file is probably under control. I've tried looking for these files, can't find them, even using the "find" option in the "File" menu. Where are they, I'd like to look at them and size them up? The sum of all the "log" folders I can find (in Mac HD/library and Users/home/library) is about 1.5 MB, but these don't include "asi.log" nor "system.log". Dale Meyn.

[priller]

Log files live in /var/log

[DaleMeyn]

Originally Posted by priller

Log files live in /var/log

That's my problem, where is /var/log? Can't find it even using "Find". Dale.