Growl 1.1.1 and "mailme"

[dnanian]

Nothing hidden, Ed, no...

[edoates]

Originally Posted by dnanian

Nothing hidden, Ed, no...

OK, I've tried all sorts of things, and the SuperDuper 2.1.4 and Growl 1.1.1 is different on three different machines, to wit:

One my old G5 Quad, MailMe works as expected with Grown 1.1.1, and SuperDuper 2.1.4 (OS X 4.10)

On one new iMac Intel 2.83 24" (10.4.10), SuperDuper Growl MailMe works on GUI invoked backups, but doesn't even get registered (as observed in Console) if SuperDuper! is run via its schedule.

On the other new iMac, SuperDuper! Growl MailMe are sent for all backups, except the "From" field is SIZE=<some number: here is the text:

Subject: Preview
Date: September 28, 2007 9:35:51 AM PDT
From: SIZE=1720
To: xxxxxx@xxxx.xxx

This was a 100% clean installation: wiped everything and installed from scratch.

So, where does Growl pick up the "from" field? And why might SuperDuper! not be registering correctly when started from a schedule?

My suggestion to SuperDuper!: depending on Growl for notifications is OK, if Growl was more predictable. Growl 1.1.1 changed quite a few items (the LOG option is gone, and mailme operates...wierdly).

I may be a software guy, but I don't want to be diagnosing this stuff (I've got enough work to do). So, please integrate email notifications into SuperDuper directly. That way, YOU are in control of this critical operation. Right now, I have to go to each machine to verify that the backups worked on schedule (startup SD, check the log manually). In an automated world, that should not be the case.

Or, alternatively, give me post SD options for failed and succeeded instead of just one as exists now. Then I could use scripting to send the emails, put something on the screen, etc. Growl is now just too flakey and out of your control.

Eddie O

[dnanian]

Thanks for the suggestions, Ed: have you reported the problem to the Growl people?

(Yes, Growl is out of our control. But so is any mechanism we'd use to really send mail, OSX itself, your drives, antivirus, applescript... lots and lots of stuff!)

[edoates]

Originally Posted by dnanian

Thanks for the suggestions, Ed: have you reported the problem to the Growl people?

(Yes, Growl is out of our control. But so is any mechanism we'd use to really send mail, OSX itself, your drives, antivirus, applescript... lots and lots of stuff!)

I sent essentially the same email to growl (sans "suggestion").

While it is true that a bunch of stuff is outside your control, growl adds yet another layer. I think if you added check boxes for "run this script on success" and "run this script on failure" that that particular feature of OS X used to start up the scripts is pretty generic and will be stable over time. And suspect scripts created by Automator (and Apple product included with OS X) will also be stable, but under control of the user.

Interestingly, prior to Growl integration and automounting disk drives, I had a script surrounding the entire SuperDuper process. The only problem was determining if the copy was OK or not. When SuperDuper ends, does it return a code to an invoking script which indicates completion status? Perhaps just add some Automator actions?

Ed

[dnanian]

If you're running scheduled, you can "patch into" the scheduled copy script. Search around on the forum and you'll find the methods...

[edoates]

Originally Posted by dnanian

If you're running scheduled, you can "patch into" the scheduled copy script. Search around on the forum and you'll find the methods...

Thanks. I think that's the way: create an "application" via Automator to create the mail note and to send it.

Eddie O

[hadleyhope]

Did you fix the Growl 1.1.1 issue. I have the same problem, the mailme notification for a successful scheduled copy does not get set. Again all was working fine before the growl update. I am running on a new iMac.

[hadleyhope]

I have noticed that MailMe continues to work with other applications.