SuperDuper Scheduling/cron failures

[dnanian]

Needless to say, SuperDuper!'s scheduling facility is older than launchd, and there's little reason to move from cron to launchd: it doesn't do this kind of thing "better", it's just "newer". (In fact, cron's been around for a very long time, and is well known and tested.)

If you want to edit the crontab, you can use "crontab -e" and remove the bad entry... but I don't know how you ended up with a 'stray'.

As far as "Backup on Mount" goes, I'm well aware of how it works, and I think you'll find it's less fragile than you imply. To make things easy to remove, all executables (etc) are kept in user accessible areas - /usr/local/bin, while traditional, is not removed when the application is removed (and the alias is updated to point at the right place each launch).

Two destination called "Backup" and "Backup 2" aren't a problem, because the actual full volume name is checked once a quick pass is made to subset the settings being tested. And we don't duplicate the functionality in the schedule driver because, well, why maintain two executables that do the same thing?

Also, we can't use one launchd daemon: it doesn't work properly in all versions of OSX.

Alas, I know about the "error" thing - it's a known, logged issue (you're the first person other than me to notice, so kudos).