I am also seeing this behaviour
We see it because by default sshfs does not include the '-o idmap=user' option to translate the ownership of the remote files to that of the local user
I propose that Tomboy should append '-o idmap=user' to the sshfs command it uses, i.e.
/usr/bin/sshfs -p 22 lewiz@remoteserver:/home/lewiz/current/backup/tomboy /home/lewiz/.tomboy/sync-sshfs
should become:
/usr/bin/sshfs -o idmap=user -p 22 lewiz@remoteserver:/home/lewiz/current/backup/tomboy /home/lewiz/.tomboy/sync-sshfs
I can confirm that manually this does as I expect. Further details can be found at http://fuse.sourceforge.net/wiki/index.php/SshfsFaq under the 'What options does sshfs support?' section
I am also seeing this behaviour
We see it because by default sshfs does not include the '-o idmap=user' option to translate the ownership of the remote files to that of the local user
I propose that Tomboy should append '-o idmap=user' to the sshfs command it uses, i.e.
/usr/bin/sshfs -p 22 lewiz@remoteser ver:/home/ lewiz/current/ backup/ tomboy /home/lewiz/ .tomboy/ sync-sshfs
should become:
/usr/bin/sshfs -o idmap=user -p 22 lewiz@remoteser ver:/home/ lewiz/current/ backup/ tomboy /home/lewiz/ .tomboy/ sync-sshfs
I can confirm that manually this does as I expect. Further details can be found at http:// fuse.sourceforg e.net/wiki/ index.php/ SshfsFaq under the 'What options does sshfs support?' section