I am running a dualcore Intel iMac with OSX 10.4.10, and admittedly a pile of addons (Default Folder, FinderPop, APE, Macaroni,..).
Psyncx exhibits the "Crash on second execution" problem discussed in other threads. That is: I boot Psyncx, run a backup of a folder successfully, but if I then click to run the backup again, Psyncx crashes -- and does so without leaving anything in the var/psync.log file that "runpsync" writes to.
Dunno if this is related or not, but I get that silly "enter your root password" dialog, and there is no place for me to type the password. Psyncx (the first time thru) seems to run fine without that password, other than runpsync being unable to write to /var/log/psync.log because root owns that directory. I fixed that by creating the file and chown-ing to myself, and setting the permission bits appropriately.
By the way: I modified runpsync script to append, rather than overwrite, the log file. I recommend this change to everyone -- it's easy enough to manually delete the log file if desired.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A summary of an email I sent David a couple of months ago:
----
Some "challenges" I'm still having with PsyncX are:
- when I begin a backup, Terminal gives the usual request alert for authentication, but runs anyway, ignoring the alert
- AppleScript files are still being corrupted (I have submitted two sets of samples)
- If a folder has been moved or renamed, the backup folder is not deleted and an error results:
/Volumes/DriveName/Pictures/Forest Images : Directory not empty at /usr/local/bin/psync line 145.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am running a dualcore Intel iMac with OSX 10.4.10, and admittedly a pile of addons (Default Folder, FinderPop, APE, Macaroni,..).
Psyncx exhibits the "Crash on second execution" problem discussed in other threads. That is: I boot Psyncx, run a backup of a folder successfully, but if I then click to run the backup again, Psyncx crashes -- and does so without leaving anything in the var/psync.log file that "runpsync" writes to.
Dunno if this is related or not, but I get that silly "enter your root password" dialog, and there is no place for me to type the password. Psyncx (the first time thru) seems to run fine without that password, other than runpsync being unable to write to /var/log/psync.log because root owns that directory. I fixed that by creating the file and chown-ing to myself, and setting the permission bits appropriately.
By the way: I modified runpsync script to append, rather than overwrite, the log file. I recommend this change to everyone -- it's easy enough to manually delete the log file if desired.
A summary of an email I sent David a couple of months ago:
----
Some "challenges" I'm still having with PsyncX are:
- when I begin a backup, Terminal gives the usual request alert for authentication, but runs anyway, ignoring the alert
- AppleScript files are still being corrupted (I have submitted two sets of samples)
- If a folder has been moved or renamed, the backup folder is not deleted and an error results:
/Volumes/DriveName/Pictures/Forest Images : Directory not empty at /usr/local/bin/psync line 145.