Marlyse Comte said: >e basically told me the only solution I have is to set ALL my >files which I want to backup over the network to CHMOD 777 and THAT I >definitely was NOT willing to do. That's just a silly response.
>I had been happy before with "Synchronize!" - before OSX I had gotten >several clients of mine to use that application because I had loved it >for many years and it had served me well. It just didn't perform well - >for me - under OSX and in my networked environment. Well, if you log in over the network, Synchronize of course need to be logged in as high priv as it needs to get anything done, which isn't completely trivial to do over afp. If you're logged in as you, you should check that all the files needing backing up are fully readable by that account under which you're logged in at the other machine *and* that they are not open. The latter is a bigger problem than permissions, IMHO. >But since I use "Super Duper!" things look sunny again, you can even >write scripts and schedule it and I can easily make backups over a >network. I seriously doubt that it can do anything the account it being logged in as (on the other machine) can't do. Any problem you hint at here, is rooted (pardon the pun) in the fact you need to regard how OS X work permissions. What special unique problems did Synchronize add that doesn't stem from accounts and permissions? > The other application which works well is R-Sync, just that one >does not have a scheduling solution if I remember correctly. There's always Cronnix. R-Sync X, the app (is that what you meant?) has some bugs in it, I believe. I run my own rsync instead. I still need to use scripts for exporting info from open files, however. Which is why I'm looking into this. PM 5.2.3 Swedish | OS X 10.3.9 | Powerbook G4/400Mhz | 1GB RAM | 30GB HD
