I made this change and it does indeed get TimeMachineGrowler working again, but it doesn't seem to be parsing the logs properly. It only gives a notification when the backup finishes and lists the time it took as being several hours, increasing each time. (6 hours, 10 hours, 13 hours, etc) It looks like it'll take a bit more than the basic change to fix it. As near as I can tell, it simply doesn't pick up the started and cancelled log entries. Looking at the log in Console.app, they haven't changed, so something else must be causing the issue.
On Aug 30, 4:33 pm, vdubgeek <[email protected]> wrote: > I took a look at the source for TimeMachineGrowler, and found that it > wasn't parsing the system log correctly. Perhaps this is a change > with Snow Leopard? TimeMachineGrowler is looking for "/System/Library/ > CoreServices/backupd", but needs to be changed to > "com.apple.backupd". Once I made this change,timemachine > notifications resumed > > On Aug 29, 2:41 pm, Peter Hosey <[email protected]> wrote: > > > > > On Aug 29, 2009, at 12:39:40, Gary L. Gray wrote: > > > > TimeMachineGrowler isn't posting notifications and it is also > > > spiking the CPU every 7-9 seconds. It's got my fan going a pretty > > > good clip. > > > More like every ten seconds. That's how often it polls the log. > > > HasTimeMachineactually done a back-up? What if you start one > > manually, then wait at least 20 seconds, then cancel it? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
