[tomboy-list] starting tomboy // sync issues

[Andrew Conkling]

On Dec 1, 2007 11:28 AM, Sandy Armstrong <sanfordarmstrong at gmail.com> wrote:

> On Nov 30, 2007 2:49 PM, Matt Price <matt.price at utoronto.ca> wrote:
> > i'm having lots of trouble with the sshfs sync feature, sometimes the
> > "fuse: mountpoint is not empy" error described here:
> >
> > > https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/152978
> > and sometimes a less obvious failure.  neither of the fixes in the bug
> > report work for me.  (fusermount -u ~/.tomboy/sync-sshfs, and
> > rm -f ~/.tomboy/sync-sshfs/lock ).  While it'd be great to figure out
> > what's going wrong ( & i'd be happy to help with that), for now i
> > figured i'd just try to sync via unison.  so i am thinking a simple
> > script like :
>
> I would try using Conduit before using Unison.  Unison will simply not
> work correctly without a lot of work.  Thanks for reporting the bugs
> with Tomboy sync...I should be able to get back to fixing all of these
> bugs very soon (I've been on a bit of a hiatus).


Before Tomboy introduced its own sync stuff, I had been Unison without much
problem. I already had an SSH server going, so it was really no big deal for
me. That's pretty much the only overhead I can think of with it; I think
it's a pretty fantastic product overall.

I'll have to check out the Conduit project in general. But would that work
any better in this case? I mean, wouldn't you still need to kill the Tomboy
process and restart it to reflect any new/deleted notes that would show up
after syncing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.beatniksoftware.com/pipermail/tomboy-list-beatniksoftware.com/attachments/20071201/81b453b6/attachment.htm