-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Everything is fine for the file .DCOPserver_linux-y532__0, but the owner > and group for the link .DCOPserver_linux-y532_:0 are set to "root - > root" instead of "spinymouse - users".
It is possible that the DCOP process put those files in your home directory and set the permissions to be what they are. On my Xubuntu UPMC they are owned by my user, so I am not sure what is happening there. If I am archiving my user directory, I tend to do so from another account or via a live CD/USB, but then I rarely archive my home folders. All important data lives on a server. I have an archive of the basics (.ssh .gnupg .vimrc .screenrc .bashrc) so I can get up and running quickly. But other than that I really don't care about my home directory. > > Because of -a and rsync running as root, owner and group should be > preserved?! The -a should preserve existing permissions, running as root should prevent access denied issues. Of course if extended ACLs are used, then running as root does not guarantee that you will be able to read the file, at least not without changing the ACLs first (similar to how Windows servers do file/directory ACLs). Hth, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIqplowRXgH3rKGfMRAstdAJ0ZGOPR1E6T9C0Y3r/3x7mX6pL7lwCdGfnB diiecDKNBjejgcA5wM9b8Ks= =hpDx -----END PGP SIGNATURE----- _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
