Shell script not executing before backup RESOLVED
Hi all,
I'm a newbie at scripting, so please bear with me. In trying to achieve unattended backups that mount the backup disk (which is a partition on another internal hard drive, the other partition on that drive is always mounted already) before SuperDuper runs, then unmounts the backup disk when the backup is complete, I found some examples of shell scripts to do that. My test run didn't work correctly, here is the log result for the error: Code:
| 12:20:20 PM | Info | SuperDuper!, 2.5 (84), path: /Volumes/HomeDrive/Applications/Utilities/SuperDuper!.app, Mac OS 10.5.6 build 9G55 (i386) Code:
#!/bin/bash Thanks! |
The error message is "Permission denied", so you can probably fix it with chmod a+rx /Volumes/HomeDrive/Users/gina/Library/Application Support/SuperDuper!/Shell Scripts/superduper_mountdisk.sh (give "everyone" read and execute permission).
But if all you want is to mount a volume before a backup and unmount the volume afterwards, I think SuperDuper! can already do what you want by itself (no scripts needed). See the Note on p40 at the end of the “Saving and restoring settings” section of the User's Guide (accessible via the Help menu)). If the target (or source) volume for a saved settings file (for example a scheduled backup, or the default saved settings) is not mounted, SuperDuper! will try to mount it automatically. All you have to do is just unmount your target volume sometime before the next backup. The next time SuperDuper! loads the settings file that targets the volume, SuperDuper! will mount it automatically. For scheduled backups, I think it also automatically unmounts the volume iff it was automatically mounted (though the only mentions of unmount in the User's Guide refer to disk images (either local or on a network share)). |
It worked as you said, with just SuperDuper!
Wow, I had tried to just do the process and let SuperDuper do everything earlier and had the app say it couldn't find the target drive... but this time it worked, but with one problem, there was one of those "application quit unexpectedly" dialog windows waiting for me when I woke the machine up (I had set SuperDuper to sleep the computer when complete). I went ahead and let the OS compile the "report to send to Apple" so I could read the log easily... I can't figure it out. I suppose I could live with having the OS think SuperDuper is crashing everytime it quits per my scheduled instructions, but that doesn't seem right... Any guesses why that would be? Thanks for your help. Here is the beginning of the log from the crash window, the whole thing is too long for one post, I can post or send the rest if this is indeed helpful: Code:
Process: SuperDuper! [6941] |
This was likely because you have something that's causing the script command that does the sleep to crash. It's usually because of an old Power PC component/scripting dictionary or bad mouse driver input manager (Logitech - old version)... if you run again and look in your system log, it should indicate which.
|
Here is the next part that crash log, I'll post the rest in subsequent posts:
Code:
Binary Images: |
Part 3 of crash log
Code:
<8b7831b5f74a950a56cf2d22a2d436f6> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis |
Part four of crash log (last part)
Code:
<bf3fa8927b4b8baae92381a976fd2079> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink |
Yeah, doesn't really help. Run it again with the sleep command and then look at the system.log when it fails.
|
Okay... I'll do that... thanks for looking. I'll post back with what happens.
|
Dave, here's message 1 of 2-system log:
Code:
Jan 8 15:05:00 gina-marie com.apple.launchd[1] (0x40c820.cron[7610]): Could not setup Mach task special port 9: (os/kern) no access |
Message 2 of 2 - system log:
Code:
Jan 8 15:08:19 gina-marie ReportCrash[7727]: Saved crashreport to /Volumes/HomeDrive/Users/gina/Library/Logs/CrashReporter/SuperDuper!_2009-01-08-150815_gina-marie.crash using uid: 501 gid: 20, euid: 501 egid: 20 |
Quote:
Based on what Dave said ("usually because of an old Power PC component/scripting dictionary"), I suspect you need to get rid of these PowerPC OSAX bundles. You should be able to delete or move them in Finder as an administrator user:
If there are other OSAX in that folder, you might want to examine them with Finder's File > Get Info. If any report "Kind: scripting addition (PowerPC)" in the General section of the Get Info window, they are also potential problems ("Kind: scripting addition (Universal)" is OK, if there are any Intel-only ones, they probably look like "… (Intel)" and they should be OK too). |
You were on the money
Perfect. I cleaned four other files from that location as well.
Now if I can figure out how to fix the "Interfacenamer: timed out waiting for IOkit to quiese" process that makes my startup slow down, things would be perfect ;-) I just loaded Leopard two weeks ago for the first time... learning my way around. I wonder how many other pieces of PPC code are lurking around like that? Thank you so much, good support is good to find. |
Great: glad you're all set -- and thanks to Chris for the assist.
|
All times are GMT -4. The time now is 01:42 AM. |
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2024, vBulletin Solutions, Inc.