You are right that (one of) the problem starts with the rysnc transfer. Strangely, when a windows PC with a "My Documents" folder is rsynced to the backup PC (linux) using basic (cw)rsync, that folder becomes read only for the myname user on the backup PC (unlike all the other regular folders). That read only setting is preserved by dirvish on the image. When dirvish tries to expire that image, it cannot delete the My Documents folder because it is read only.
The other problem is simply that most of the time dirvish creates the images as read/write for myname (my logon name). But every now and then it creates the image as owned by root (so I cannot open it, and dirvish cannot access it next time it runs). If I run dirvish as root using the sudo command then all images are owned by root. I can open them as root by using super user but it is inconvenient. Can I add user, group and read/write requirements to the conf file? ie could I choose myname as user and read/write as the permission. The I could run as root while ensuring that the images were readable by myname. By the way, how does rsync preserve the original ownership (eg fred) and permissions while creating new ones (eg myname) on the backup PC? Seems the file has two lots of ownership details. Does it store the original ownership data somewhere in the file while using the new ownership on the backup PC. Excuse my ignorance. -- View this message in context: http://www.nabble.com/Permissions-tp20262208p20290121.html Sent from the Dirvish mailing list archive at Nabble.com. _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
