[dmbrown]

I also run SuperDuper! when I'm done with my Mac, having SuperDuper! shutdown the Mac when it's done. Like Tim, when I start up the Mac the next day, Lion's resume would start SuperDuper!. I got around this problem by having SuperDuper! run a shell script when it's done, rather than shutdown the Mac. The script is very simple - it issues an Applescript command to Quit SuperDuper!, then issues a command to shutdown the computer in two minutes. The two minute delay is to allow SuperDuper! time to shutdown so it's not running when the system shuts down.

The script contains only these three lines:

#! /bin/sh
osascript -e 'tell application "SuperDuper!" to quit'
shutdown -h +2

(If you don't know how to create a shell script, put those three lines in a plain text file. Then make the file executable via the Terminal command
chmod +x pathtofile

I have noticed that an error appears in the SuperDuper! log, related to the shutdown command. I've copied it below. Perhaps Dave can shed some light on it:

| 04:31:52 PM | Info | PHASE: 3. After Successful Copy
| 04:31:52 PM | Info | ...ACTION: Restoring Spotlight state on Little Bear
| 04:31:52 PM | Info | ......COMMAND => Restoring Spotlight search indexing state on Little Bear
| 04:31:53 PM | Info | /Volumes/Little Bear:
| 04:31:53 PM | Info | Indexing enabled.
| 04:31:53 PM | Info | Indexing enabled on Little Bear
| 04:31:53 PM | Info | ...ACTION: Running shell script SuperduperShutdown.sh
| 04:31:53 PM | Info | ......COMMAND => Invoking After Copy shell script: /Users/David/Library/Application Support/SuperduperShutdown.sh
| 04:31:54 PM | Info | Shutdown at Fri Oct 28 16:33:54 2011.
| 04:31:54 PM | Error | shutdown: [pid 5279]