On Tue, Sep 23, 2008 at 11:08:51PM +0200, Ferry Toth wrote: > Package: unison > Version: 2.27.57-1+b1 > Severity: normal > > I am trying to sync over ssh as an ordinary user. The folders contain files > with different owners, however I am always a > member of the group that has rw access to the files. > > Since I want to sync owner/group/permission I have set owner = yes and group > = yes in the profile. I have carefully > created user and group accounts on both machines, with identical numeric ids. > Still I have set numericids = false, in > case of future mistakes. > > Now when the ownership of a file is changed on one side, unison tries to > chown the file on the other side - as intended. > However, since I am not the su the chown command fails. > > I believe this is not the intended behavior when syncing file ownership. > > Note: I have tried running sudo unison, but this fails because root does not > have a certificate required to connect to > the remote ssh. > > Proposed behavior: make unison perform a sudo chown and request a passwd from > the user when needed. >
Humm, this "proposed behavior" really doesn't make sense (lot of problem: what if we are running under GTK, what if user don't have sudo installed, what if the sudo has to be performed remotely...) Moreover, you just have to tell ssh to use the right key/user in .ssh/config or specify it directly on the command line, or override the sshcmd by a script of your own to use the right user/key. I really think this issue is not at all related to unison but to UNIX rights in general. I think you should run unison as root to perform the chown (just fix the the certificate problem). If you really need assistance to fix your ssh invocation, i can give you the command line. I think I will close this bug, because I am really not sure this is a bug... Sorry, Regards Sylvain Le Gall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
