Hi Bill,
you wrote...
> I'm getting close.
> psync doesn't seem to set file permissions. It sets directory
> permissions, sort of.
>
> I'm looking at the browser Camino. My source file
> /Camino.app/Contents/MacOS/Camino is set to 771.
> When psync copies it, the target /Camino.app/Contents/MacOS/Camino is
> set to 644.
> When I manually set it executable, the app launches fine. Problem
> solved by hand.
> Shouldn't psync set file permissions as well? If not how can I modify
> it to do so?
I think you're seeing the result of your "-r" flag in the call to psync.
Instead of attempting to restore permissions on the remote volume it
stores the permissions data in a database, so that when you restore the
data to another machine on which users/groups line up properly with the
original machine it knows to which user/group it should assign each file
(and what the permissions on that file should be).
Hmm, clear as mud: the "-r" flag is for backing up to volumes (such as
remotely hosted volumes) where the user/group data isn't aligned with
the originating machine. It is however *preserved* so that when you
restore from that remote volume it's available. If you try to run apps
from that remote volume they won't work because of the permissions
issues you've noted.
In short: try without the "-r" if you're pushing things to, say, a
firewire drive connected to your desktop machine.
I hope this makes some sort of sense, and furthermore that it's
reasonably accurate: see the man page for psync for more info about -r.
Cheers,
Paul
