Hi Peter, Thank you for your response.
I don't believe I ever turned on Growl logging (I had no idea it was there until I found the enormous log file), but it's enabled on both of my machines. From your response, it sounds like it should instead be disabled by default. Thanks again, Dan On Feb 5, 4:17 pm, Peter Hosey <[email protected]> wrote: > On Feb 5, 2011, at 16:07:26, Dan wrote: > > > I ran out of disk space on my machine yesterday, and was trying to > > figure out why. This didn't help: > > -rw-r-xr-x 1 daniel Daniel 55G Feb 5 15:19 Library/Logs/growl.log > > > I consider it a bug that there is no log rollover in Growl. > > > Contributing factors to a 55 GB growl.log: > > - First entry is from 2006 > > The logging feature is meant for debugging/troubleshooting of Growl, not > long-term use. You should turn it off using one of our logging scripts: > > > http://code.google.com/p/growl/downloads/detail?name=GrowlLoggingScri... > > Rollover is unnecessary for the logging feature's intended usage. > > If you log old notifications for later review, we are working on a > notification-history feature that will serve that purpose better. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
