On Sun, Oct 03, 2010 at 11:15:47AM -0400, Patricia Warwick wrote: > Some time ago I posted a question about how to disable the log file that > Growl produces. I got one suggestion which did not work. Is there an approved > way of doing this or will I need to keep deleting this file when it grows too > large? If there is no way of disabling the log file could this be made an > option for future versions?
Preference changes made outside an application while it's running, like you may have done earlier when changing Growl's preferences, can be overridden by a prefs file rewrite based on the application's in-memory state. This is more likely to happen if you change the application's preferences from within the application as well as from outside, as that's pretty much a guaranteed rewrite situation. This might work: Stop Growl first. Turn off logging as before. Restart Growl. Sadly, I need operational (as opposed to developer debug) logging, so I'm still using Growl 1.2 for its less chatty-about-rects debug log behavior. That might be an option for you as well, but only if you're totally stuck. -- 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.
