On Wed, Sep 24, 2008 at 01:51:16PM +0200, Ferry Toth wrote: > > Sylvain, > > For security reasons I would prefer not to invoke unison from root, however I > can understand there are complications to sudo from unison on client and > server > side. > > For now it seems I need to sudo chown manually on the offending files. > > Maybe the issue can be put on the wish list?
Sorry, to insist, but you will have exactly the same problem with rsync for example. So, you should fill a wish list bug against every file synchronizer (including ftp mirroring stuff)... I don't see anything specific to unison regarding this problem... That is why it is not a bug or a wishlist bug related to unison. Concerning security reason, invoking "sudo" is not a solution at all... (you will still give root access to unison -- even remotely). If you want a "safer" alternative to all this -- without invoking sudo in Unison, you can go with solution like: dump every rights in a "rights.txt" (getfacl -R .) before unison start, run unison, and restore rights (setfacl --restore=rights.txt). If you have conflicting rights you will need to solve the conflict between the two host... (note that in the method above, you can replace "unison" by "rsync" or anything you want). Regards Sylvain Le Gall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
