I do not believe that's the case. I've left 1.3 running overnight for weeks at a time while testing and twitter still notified me, and things like that.
I would contact SuperDuper and ask them to look into it. Chris On Fri, Oct 7, 2011 at 8:06 AM, joelw135 <[email protected]> wrote: > I was able to get SuperDuper to work with 1.3 by changing the Growl > Framework to 1.2.2 version (ALMOST)! If I run a manual backup on > either of my two drives with permissions repair Growl 1.3 works fine. > But so far scheduled backups don't direct output to Growl. A little > strange to say the least as it should have nothing to do with being > scheduled or not. > > I am thinking Growl is going to sleep and not seeing the output. Is > that possible? My backups are scheduled when I am not in the office, > and I use Mailme to see if it worked or failed. > > -- > 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. > > -- 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.
