![]() |
|||||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
#13
|
|||||
|
|||||
Quote:
For "fun" I deleted the ~/Library/Application Support/SuperDuper!/Copy Scripts/Standard Scripts symlink (which worked okay), tried Undo, and Finder griped "The operation cannot be completed because you do not have sufficient privileges for some of the items." Whoops. Reminds me of potentially devastating side effects of omitting the "-h" option on Unix ch{own,grp,mod} commands (OS X versions are susceptible) when symlinks are involved, which an impressive number of root-enabled Unix sysadmins don't realize as they're using those commands (often recursively). My favorite traditional example: Code:
% ls -l /etc/passwd foo -rw-r--r-- 1 root wheel 1374 8 Dec 2003 /etc/passwd lrwxr-xr-x 1 me me 11 22 Jun 16:07 foo -> /etc/passwd % sudo chown me foo Password: % ls -l /etc/passwd foo -rw-r--r-- 1 me wheel 1374 8 Dec 2003 /etc/passwd lrwxr-xr-x 1 me me 11 22 Jun 16:07 foo -> /etc/passwd Quote:
Quote:
Quote:
Quote:
Issue with exclude: The main "Backup - all files" script excludes var/db/BootCache.playlist and var/db/volinfo.database, but those files exist on the destination volume. Not sure if the original backup or the SU copied 'em since I only noticed after the latter. Thanks for responding to my VersionTracker feedback. Hope I didn't sound like I was giving misinformation about the way script editing worked. About the capacity check... after posting I thought of mentioning that a simulation mode would be convenient for certain scenarios with backup media storage planning, as I'm currently doing, especially when the the space rules for dealing with disk image files aren't known. For example, I tested creating a disk image of the system volume (~19GB) on another volume with ~25GB free. If I'd let that run it would have overflowed, as expected. A simulation, safely running non-inactively for an hour or two then warning that the real deal would have failed, would have been nicer than having to manually interact and abort. And/or is it possible for the temporary volume to use space on a different volume than the image file's final destination? Several visits to the hdiutil man page have failed to reveal a way of doing that. Whew. That covers everything and then some for today. ![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|