OK, problem resolved. I admit that it was user error. What I couldn't understand was that I was getting notified on one machine when Superduper completed a copy. But not on another machine. I *thought* Growl was set up identically on both. But it wasn't. In Application Notifications, you have to select the task. On the machine where it wasn't working, I selected the "Scheduled Copy Succeeded" task, and, oops, instead of "Always", it was set to "Application Decides". On the machine that worked it was set to "Always". So somehow, that selection got switched.
Why SuperDuper decides not to let Growl report a scheduled copy it is kinda strange. But that's what's going on. So my Growl is now growling, and I'm not purring. Thanks for your help. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/d/optout.
