Getting Yojimbo to work with MobileMe sync
tharpold
MobileMe to properly sync my Yojimbo database from my home machine to
my office and laptop computers; nothing seems to work, and I'm nearly
resolved to the idea that it will never work. Which, of course, sorta
takes away a crucial value of Yojimbo.
Every method of resetting the sync recommended by Apple and Bare Bones
hasn't fixed this. (I believe that I've tried them all.) Shrinking the
size of my Yojimbo database (currently at 240 MB) hasn't worked. (I
thought it might as the sticking point seems to be the couple-hundred
small .pdfs I was keeping in the database; other database items
appeared mostly to make it across the sync.)
I had troubles with syncing before, as far back as Yojimbo 1.0, but
they were usually resolved by the various schemes of resetting/nuking
the sync settings -- though, to be honest, things would soon (every
month or so) get out of whack again.
More recently, MobileMe appears to report that a successful Yojimbo
sync is being/has been made, for example --
2009-03-11 09:15:47|Info|Starting Sync Session for dataclasses:
Yojimbo Items
2009-03-11 09:15:48|Info|Applying changes from MobileMe...
2009-03-11 09:15:49|Info|No changes will be applied from MobileMe for
dataclass Yojimbo Items
2009-03-11 09:15:49|Info|Waiting for Sync Engine to finish mingling
changes
2009-03-11 09:16:02|Info|Checking for Sync Engine changes for
dataclass Yojimbo Items
2009-03-11 09:16:20|Info|Received 3383 changes for dataclass Yojimbo
Items from Sync Engine
2009-03-11 09:16:20|Info|OPTIMIZE LOCK: Successfully grabbed lock
before uploading for dataclass com.barebones.yojimbo.yojimbodata
2009-03-11 09:18:01|Info|Uploading changes to MobileMe for dataclass
Yojimbo Items
2009-03-11 09:30:37|Info|This MobileMe Sync Client cannot sync at this
time - already syncing on this machine
2009-03-11 09:35:13|Info|Upload successful
2009-03-11 09:35:14|Info|The information on MobileMe for dataclass
'Yojimbo Items' is being refreshed with data from this computer
2009-03-11 09:35:16|Info|New anchor version for dataclass Yojimbo
Items = 00152
2009-03-11 09:35:27|Info|Finishing the Sync Engine session
2009-03-11 09:35:30|Info|Ended Sync Engine session
Every other app that I sync with MobileMe (Address Book, Calendars,
Keychains, etc.) works without a hitch. Only Yojimbo fails to work as
it should.
As I've no way of querying the copy of the data that is stored on
MobileMe, I can't tell if changes to the local database *have* been
successfully uploaded. I'm quite sure they're not making it across to
the remote machines.
What can I do but keep resetting everything, wiping out all sync
settings, waiting for a new "merge" to take, etc.? I grow more
convinced that Yojimbo just asks too much, or the wrong thing, of
MobileMe, and I'm on the verge of looking for a very different
solution -- i.e., one that will not use Yojimbo.
TH
cubic....@fastmail.fm
On 11 Mar 2009, at 14:58, tharpold wrote:
> What can I do but keep resetting everything, wiping out all sync
> settings, waiting for a new "merge" to take, etc.?
You can link your Yojimbo folder in ~/Library/Application Support to
one on Dropbox, and use that. There are some posts on how to do this
in the list.
I am also in that situation; nothing I tried, no matter how many times
BB advised (and very patiently and helpfully I have to say) worked in
the end, and I just didn't have the patience to continue after a
while. Thankfully though the linking to Dropbox works.
I would much rather be able to use MobileMe, but it's just not
working, and I have better things to do with my spare time than
endlessly reset preferences and re-upload my database, only to find
that it still doesn't sync. I have no idea whose fault it is and I
don't care any more - I'm just tired.
nomad
like this:
2009-03-09 10:08:23|Info|The information on MobileMe for dataclass
Items = 00013
2009-03-09 10:08:33|Info|Finishing the Sync Engine session
2009-03-09 10:08:33|Error|Could not successfully finish the Sync
Engine session: Session <ISyncConcreteSession: 0x3f8460> cancelled.
lost connection to SyncServer
2009-03-09 10:08:33|Info|Ended Sync Engine session
> I have no idea whose fault it is and I
> don't care any more - I'm just tired.
what happens.
Niels Kobschätzki
>
>
> On 11 Mar 2009, at 14:58, tharpold wrote:
>
>> What can I do but keep resetting everything, wiping out all sync
>> settings, waiting for a new "merge" to take, etc.?
>
<snip use dropbox>
Did the same. I wonder if it's BareBones fault or Apples - I guess
MobileMe-syncing is just not built for syncing the mass of data that
are used by Yojimbo.
Would be great if Apple would change the iDisk to something like the
"Dropbox" and Yojimbo would work with that then (would have the
advantage that you could use other services as well)
Niels
Chris H.
I have great sympathy when I hear MobileMe syncing horror stories,
because I know that this has been problematic for a great number of
people -- including the previous President of our Mac User Group.
I probably shouldn't curse myself by saying this, but MobileMe syncing
has been darned solid for me in general. And for Yojimbo specifically
it has been rock solid.
I have to ask you guys: Have you tried resolving your problems by
repeating the troubleshooting steps provided by BB and Apple _after_
Apple has made their most recent wave of updates to MobileMe's
backend? (Announced Feb 26 2009) And after updating all your syncing
Macs to OSX 10.5.6 using the downloaded combo updater (not software
update)? (Apple says 10.5.6 is essential for best MobileMe
reliability.)
-Chris Hart
nomad
> Apple says 10.5.6 is essential for best MobileMe
> reliability.
Leopard on my work machine, and that situation isn't likely to change
anytime soon, and there's no reason why the intermediate data storage
format up on the stupid 'cloud' should depend on what version of the
OS I'm running, as long as both sides are able to send and read the
same data.
It was all working fine for me, too, until I made the mistake of
trying to add one too many big files to my Yojimbo database on one end
(increased the size by 100MB in one go). Then it broke, and nothing
I've been able to do — including pulling those files out of the
database — has been able to fix the problem since.
Mind you, I lay the blame for this entirely on Apple. I've never seen
any evidence that Bare Bones could, in their worst tequila-shot-
induced delirium, have screwed something up this badly, but Apple?
Hoo, boy.
Niels Kobschaetzki
>
>
> I have great sympathy when I hear MobileMe syncing horror stories,
> because I know that this has been problematic for a great number of
> people -- including the previous President of our Mac User Group.
>
> I probably shouldn't curse myself by saying this, but MobileMe syncing
> has been darned solid for me in general. And for Yojimbo specifically
> it has been rock solid.
>
> I have to ask you guys: Have you tried resolving your problems by
> repeating the troubleshooting steps provided by BB and Apple _after_
> Apple has made their most recent wave of updates to MobileMe's
> backend? (Announced Feb 26 2009) And after updating all your syncing
> Macs to OSX 10.5.6 using the downloaded combo updater (not software
> update)? (Apple says 10.5.6 is essential for best MobileMe
> reliability.)
Yes. One computer is more or less set up fresh, the other one has
resetted sync-data - both are as up-to-date as it gets.
I use MobileMe nowadays only for contacts, bookmarks, ical and the
kotoeri user dictionary.
I stopped widgets when it got into an infinite-loop of creating,
deleting widgets I wanted to remove. Keychain-sync made a lot of
trouble, so much that both macs didn't work properly anymore until I
switched of sync and created new keychains…Thus it's not only Yojimbo
but Yojimbo is hard to get started to sync in the first place it seems
if your database has already some particular size.
I really thinking about quitting MobileMe when my year is over -
bookmarks can be synced via Foxmarks nowadays, contacts and calendars
via google, Dropbox is faster as the iDisk anyway - the
WebDAV-approach is just too slow and I don't want to reserve 10+GB on
my HDD for a synced one…they should have used automated version
control w/ binary diffs in the first place.
Niels
Niels
cubic....@fastmail.fm
On 12 Mar 2009, at 07:06, Chris H. wrote:
> I have to ask you guys: Have you tried resolving your problems by
> repeating the troubleshooting steps provided by BB and Apple _after_
> Apple has made their most recent wave of updates to MobileMe's
> backend? (Announced Feb 26 2009) And after updating all your syncing
> Macs to OSX 10.5.6 using the downloaded combo updater (not software
> update)? (Apple says 10.5.6 is essential for best MobileMe
> reliability.)
I tried it again a few weeks ago - I can't remember whether that was
before or after Feb 26 (didn't work of course).
To be honest I'm not going to bother again unless there's a real
indication that it is likely to succeed. Apple are always saying "yes
we've made significant improvements to MobileMe and it _really works
now, honest_". There are three or four different mechanisms for
resetting Yojimbo sync history just that I've been advised to try -
googling gives more, subtlely different - and testing all of those
takes several hours, and I have better things to do with an evening.
I'd be prepared to delete every piece of data ever on MobileMe,
unregister everything and re-upload everything from my main machine,
only that doesn't work either, I've tried. There's always something
left behind somewhere. I suspect now that the only way might be to buy
another MobileMe account, export everything from Yojimbo, wipe all my
machines, re-import everything into Yojimbo and then sync - carefully
- and while I do value MobileMe sync I'm not quite _that_ keen on it.
Chris H.
Well, a clean system install of OSX 10.5.6 on all computers that sync
to mobileme may be the ultimate solution.
Radical and one would hope unecessary, but certainly a solution that
has a high likeliness of success.
And, Nomad, that you can't understand that the syncing needs of
MobileMe have evolved over the years is troubling. Over time, certain
technical issues come to light and Apple accrues a larger database of
known issues and comes up with fixes. You should have seen the very
public proclamations at the time of the MobileMe changeover that they
required OSX 10.5.4 in order for them to support customers moving
forward (among other things, they sent out an email to all
subscribers). And since that time they have indeed been making
substantial changes to MobileMe (behind the scenes) and it is all
optimized for best results with 10.5.6. That you outright reject this
unequivocal message from Apple means you are partly responsible for
causing your own pain.
-Chris
tharpold
> I have great sympathy when I hear MobileMe syncing horror stories,
> because I know that this has been problematic for a great number of
> people -- including the previous President of our Mac User Group.
never worked as promised, from the very start. I've probably reset/
wiped/started over more than ten times in the last couple of years.
This while syncing from home (cable modem), office (T1), laptop
(Airport, in every context you can imagine); if the client machines (I
consider the home machine my Yojimbo "server") ever catch up, that has
lasted no more than a week or two; soon thereafter they move more and
more out of sync.
> I probably shouldn't curse myself by saying this, but MobileMe syncing
> has been darned solid for me in general. And for Yojimbo specifically
> it has been rock solid.
(Calendar, Address, Bookmarks and the like). It's only been Yojimbo
that doesn't work. I tried Together for awhile, and its MobileMe
syncing appeared to work, but I didn't like the UI and went back to
Yojimbo, hoping that it might work after yet one more reset...
> I have to ask you guys: Have you tried resolving your problems by
> repeating the troubleshooting steps provided by BB and Apple _after_
> Apple has made their most recent wave of updates to MobileMe's
> backend? (Announced Feb 26 2009) And after updating all your syncing
> Macs to OSX 10.5.6 using the downloaded combo updater (not software
> update)? (Apple says 10.5.6 is essential for best MobileMe
> reliability.)
ago, so, yes, running under the latest-and-greatest MobileMe, and
under 10.5.6 on all machines (always update with Combo updater.
Bare Bones has been helpful, sympathetic, etc. But the simple fact is
this: I've never been able to get this work so as to feel that I can
rely on Yojimbo fully for the tasks for which I required it. I'm stuck
for now, but am inclined to move to another solution. Dropbox may
permit me to sync Yojimbo, but I also suspect that it is time for a
more radical rethink.
Bob Withers
On Mar 12, 2009, at 10:41 PM, Chris H. wrote:
>
>
> Well, a clean system install of OSX 10.5.6 on all computers that sync
> to mobileme may be the ultimate solution.
>
> Radical and one would hope unecessary, but certainly a solution that
> has a high likeliness of success.
>
That must be a good solution - every time I've called Microsoft with a
Windows problem that's what they suggest :-)
Bob
Chris H.
On Mar 13, 11:05 am, tharpold <tharp...@machin-truc.com> wrote:
> The last time I went through one of these purges was about two weeks
> ago, so, yes, running under the latest-and-greatest MobileMe, and
> under 10.5.6 on all machines (always update with Combo updater.
>
> Bare Bones has been helpful, sympathetic, etc. But the simple fact is
> this: I've never been able to get this work so as to feel that I can
> rely on Yojimbo fully for the tasks for which I required it. I'm stuck
> for now, but am inclined to move to another solution. Dropbox may
> permit me to sync Yojimbo, but I also suspect that it is time for a
> more radical rethink.
latest OS/mobileme stuff doesn't fix it.
This truly is an ugly, vexing problem. I wish I had a magic wand for
you guys.
You might want to look at EverNote as it gets lots of praise.
-Chris
tharpold
> I'm disappointed to hear that even running clean versions of all the
> latest OS/mobileme stuff doesn't fix it.
>
> This truly is an ugly, vexing problem. I wish I had a magic wand for
> you guys.
>
> You might want to look at EverNote as it gets lots of praise.
limping along. But as soon as my schedule frees up a bit (in a month
or two), I will certainly explore the alternatives to Yojimbo, and
will likely move on and not look back again.
I've lost scores of hours on this problem in the last two years, and
have expended a lot of energy and good will. Yojimbo/MobileMe simply
doesn't work for me -- and never has worked as it was promised to
work, though there is so far as I can tell nothing unusual about my
setup in any other respect. So it's time to find something that will
work.
Long a supporter of Bare Bones (BBEdit, MailSmith before my University
forced me to stop using it), I've hoped for an update to Yojimbo that
would resolve these recurring syncing issues -- perhaps they do not
afflict a majority of users, but for those of us who do have syncing
troubles, they are crippling and nothing much fixes them -- or that
Apple would make some magical change on the back end that would take
care of things.
But I've no confidence now in either of these outcomes. I respect BB's
policy of not pre-announcing features or changes of new versions of
their software, so I won't ask for some reassurance that a fix for
this and other limitations of the app are forthcoming soon. But I'm
afraid that also means that I can have no more patience. :-(
TH
Patrick Woolsey
[...]
>Long a supporter of Bare Bones (BBEdit, MailSmith before my University
>forced me to stop using it), I've hoped for an update to Yojimbo that
>would resolve these recurring syncing issues -- perhaps they do not
>afflict a majority of users, but for those of us who do have syncing
>troubles, they are crippling and nothing much fixes them -- or that
>Apple would make some magical change on the back end that would take
>care of things.
>
First, we are not currently aware of any bugs *in Yojimbo* which interfere
with syncing, and although (software being software :-) we can't rule out
the possibility, if we do identify any such bug we'll do our best to
address same.
Second, the sync process involves multiple factors, many of which are
beyond Yojimbo's control--most prominently, network connections and the
MobileMe servers--and in our experience, it's in those places where issues
primarily arise.
In broad strokes, setting the recommended sync options and letting Sync
Services work at its own pace, will do the job almost every time.
If sync does stop working, Sync Services will often iron things out on its
own when given time; when it can't, performing the reset procedure we
provide will normally serve to set things right.
That said, in a process as complicated as data synchronization, there will
be occasions when, despite everyone's best efforts, the process just breaks.
Regards,
Patrick Woolsey
==
Bare Bones Software, Inc. <http://www.barebones.com>
P.O. Box 1048, Bedford, MA 01730-1048
Joshua Gray
Patrick Woolsey
>what about doing what omni focus does and it just uses idisk
>
In order to do that, we'd have to replace Sync Services with some other
sync mechanism.
tharpold
> tharpold <tharp...@machin-truc.com> sez:
> [...]
>
>...the sync process involves multiple factors, many of which are
> MobileMe servers--and in our experience, it's in those places where issues
> primarily arise.
BB -- they've been helpful and patient. Patrick, in particular, has
helped me several times to try to resolve my difficulties. I believe
precisely that the problem lies in some voodoo alliance of network
connections, servers, and MM settings/preference files/.clog files.
Maybe even some deeply-buried glitch in my Yojimbo database (?) If I
could purge everything and start over, I would do so. But I've tried
everything that's been recommended until now, and nothing has worked,
or worked for more than a week.
> In broad strokes, setting the recommended sync options and letting Sync
> Services work at its own pace, will do the job almost every time.
the last time I tried to get the syncing right again, following the
reset procedure recommended by BB, it's been *two weeks*. Since then,
my home computer, my office computer, and, less often, my iBook (I
don't use it every day) have tried *hourly* to sync up properly. And
have failed to do so yet.
Perhaps something is amiss with my cable modem connection from home,
my T1 line at work, the wireless connection at every coffee shop in
town and a hotel or two I've stayed at; maybe there's some data
bottleneck in any or all of these I don't understand. Or maybe there
is something fundamentally wrong with my MobileMe setup that every
reset attempt and unregistering/reregistering all of my computers
(I've tried) can't fix.
I know that MobileMe synching can work, as it works like a charm for
all of my Apple apps. It just doesn't work for Yojimbo on the three
computers I use on a daily basis. This is pretty much my only
complaint on those three computers, which seem to handle all the
local, network, and remote work I throw at them, never crash, handle
high-speed media and file transfers without a hitch, are well-cared
for, are outfitted in very typical ways, etc. The weak link is Yojimbo
and MobileMe. I wish that I could place the problem somewhere else.
TH
loeribas
all works without a glitch. I don't think Yojimbo is perfect, but it's
the best in his class, has a simple interface, and does what it
promises.
There are certainly lots of satisfied people like me. Just update your
Mac software and be positive.
;-)
Loeribas
Joshua Gray
idisk. It looks simple and should fix lots of the problems some users
are having I know I have had to reset syncing a few times because of
my database.
thank you
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google
> Groups "Yojimbo Talk" group.
> To post to this group, send email to yojimb...@googlegroups.com
> To unsubscribe from this group, send email to yojimbo-talk...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/yojimbo-talk?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
tharpold
> I believe
> precisely that the problem lies in some voodoo alliance of network
> connections, servers, and MM settings/preference files/.clog files.
> Maybe even some deeply-buried glitch in my Yojimbo database (?) If I
> could purge everything and start over, I would do so.
I exported all the .pdfs (460 = 103 MB) and images (12 = 124 MB) out
of my Yojimbo database, leaving only 16 Notes, 52 Passwords, and 1967
Bookmarks. Forced a sync up to MobileMe from my "server" Mac (my base
machine at home), overwriting data on MM with the computer's database.
That completed successfully and very quickly -- the first successful
completion of a sync in weeks. Then I forced a sync down from MM to
the other two Macs (office and laptop), overwriting data on them from
MM. That also completed quickly, though after the sync, the beachball
spun in Yojimbo for 5-10 minutes on each of the target computers --
while, I suppose, their local copies of the database were stripped
down to the newly-slimmed version.
Since then (two days ago) every change I've made to local copies on
each of the machines has synched without incident to the other copies
-- in other words, things have worked exactly as they should.
Clearly, the problem before lay in the *size* of my database (approx
200 mb), which somehow choked MM synching. (The current database is a
little over 1 MB.) However, that doesn't seem to me to be very large
if Yojimbo is to be used as anything other than a scratchpad for URLs
and a handful of text notes. On relatively speedy computers with fast
cable modem/T1/wireless connections and 1.5-2 GB of RAM, I would think
that changes to a 200 MB database could be pushed back and forth
without difficulty, even if the database has to be uploaded/downloaded
as a unit, which I presume is necessary in Yojimbo's case.
I hope now to add the images and .pdfs back in, but I'm
(understandably) wary of this:
1) Should they be added back in gradually, a few at a time, so as
not to overwhelm synching again with too large a database?
2) Won't I just be asking for a breakdown again at the point when
the size of the database crosses some -- undefined -- threshold?
On the support page for Reinvented Software's Together (a program
similar to Yojimbo in some respects), the user is warned "You cannot
sync a library that is greater than about 20% of the memory installed
on your Mac. So, for a Mac with 2GB installed, 400MB would be the
limit" -- i.e., the sync won't complete before the MM connection times
out. The user is also warned to avoid syncing individual files of
greater than a few megabytes in size. (Together stores its records as
individual, Finder-accessible files.)
I don't recall any such warnings in BB's support literature for
Yojimbo. Is Yojimbo exempt from such size limits on the database or
the files added to it? Are there yet other limits at work, such that
my Yojimbo database, of about 10% the size of my RAM, would also be
too large for synching?
TH
Chris H.
Thanks for sharing your findings. They're interesting.
Some reactions...
___ tharpold at <thar...@machin-truc.com> wrote: ___
> ... Then I forced a sync down from MM to
> MM. That also completed quickly, though after the sync, the beachball
> spun in Yojimbo for 5-10 minutes on each of the target computers --
> while, I suppose, their local copies of the database were stripped
> down to the newly-slimmed version.
>
> Clearly, the problem before lay in the *size* of my database (approx
> 200 mb), which somehow choked MM synching. (The current database is a
> little over 1 MB.) However, that doesn't seem to me to be very large
> if Yojimbo is to be used as anything other than a scratchpad for URLs
> and a handful of text notes.
issues.
> I hope now to add the images and .pdfs back in, but I'm
> (understandably) wary of this:
>
> 1) Should they be added back in gradually, a few at a time, so as
> not to overwhelm synching again with too large a database?
works out.
> 2) Won't I just be asking for a breakdown again at the point when
> the size of the database crosses some -- undefined -- threshold?
> the files added to it?
at the same time, he points out that the app isn't intended for use on
a scale that entails a massive database.
My personal feeling is, if such a product can't handle database sizes
up to at least 1 gigabyte, then it's not of much use to me. The app
is supposed to be a "catch all" for that which you find hard to
categorize/file in your life and I can easily see my personal archive
needs expanding at a rate of about 150 megabytes per year.
-Chris Hart
Niels Kobschätzki
<snip>
>> 2) Won't I just be asking for a breakdown again at the point when
>> the size of the database crosses some -- undefined -- threshold?
>
>> ... I don't recall any such warnings in BB's support literature for
>> Yojimbo. Is Yojimbo exempt from such size limits on the database or
>> the files added to it?
>
> Rich Seigel says there's no limits on Yojimbo's database size. Yet,
> at the same time, he points out that the app isn't intended for use on
> a scale that entails a massive database.
>
> My personal feeling is, if such a product can't handle database sizes
> up to at least 1 gigabyte, then it's not of much use to me. The app
> is supposed to be a "catch all" for that which you find hard to
> categorize/file in your life and I can easily see my personal archive
> needs expanding at a rate of about 150 megabytes per year.
My database grew in a year so to 800+ MB and that rate would be
constant. I save more or less only webarchives to Yojimbo because my
PDFs are handled usually by Bibdesk. Btw. bookmarks wouldn't work
because a lot of news-sites tend to move older articles to a not-
reachable area if you are not a (paid or non-paid) subscriber and I
need that stuff for research.
Iirc the discussions from over a year ago my database was quite small
in comparison to some other people whose database was at least double
that size.
Niels
nomad
> > 200 mb), which somehow choked MM synching.
>
> issues.
> > not to overwhelm synching again with too large a database?
after adding a large number of files to my database), it's pretty
clear that the problem occurs whenever there's a large quantity of
data to be exchanged. This doesn't mean that the database itself can't
be large; it simply means that the change in size since the previous
synchronisation can't be too big. So starting out with a database
whose size is below the critical threshold and then gradually adding
and synching should work.
However, that's such a pain that I'm unlikely to bother trying it.
The problem would appear to be either a timeout (takes too long to
send the big chunk o' bytes) or some kind of buffering limitation (too
much stuff at once). In either case, it's consistent with it being
Apple's problem, not Yojimbo's. Clearly, the iSync system was not
engineered to handle big gulps of data.
tharpold
> Based on the above and my own experience (in which synching broke
> after adding a large number of files to my database), it's pretty
> clear that the problem occurs whenever there's a large quantity of
> data to be exchanged. This doesn't mean that the database itself can't
> be large; it simply means that the change in size since the previous
> synchronisation can't be too big. So starting out with a database
> whose size is below the critical threshold and then gradually adding
>
> ... it's consistent with it being
> engineered to handle big gulps of data.
nice to have a firm confirmation of this (from BB or Apple), and some
practical suggestions re how to parse all this out (given that several
factors are in play -- speed of connection, size of database, size of
new additions to database, MM server response, etc.), so that a user
can avoid crossing a threshold that will result in a perpetual failure
of synchronization. I'm willing to gradually migrate my data back into
Yojimbo if I can be confident of the appropriate rate and scale of
migration.
My hope is that BB could offer us concrete advice in these respects.
Stonewall Ballard
> after adding a large number of files to my database), it's pretty
> clear that the problem occurs whenever there's a large quantity of
> data to be exchanged. This doesn't mean that the database itself can't
> be large; it simply means that the change in size since the previous
> synchronisation can't be too big. So starting out with a database
> whose size is below the critical threshold and then gradually adding
> and synching should work.
a size threshold, it's pretty small.
nomad
moment, and it seems to work well as far as it goes, but it requires a
synched starting copy; it can't merge changes (clearly, since it
doesn't know what the database internals look like). It does, however,
transfer only the minimal amount of data. Also, to ensure proper
synching, one needs to quit Yojimbo, do the synch, then go to the
other computer, synch, and start Yojimbo.
Not, unfortunately, an ideal solution.
Andrew Janjigian
nomad
> The one and
> only "hassle" is that you must remember to quit YJ on whichever machine it
> is running before opening it on another. But there is a failsafe to prevent
> conflicts, in that if you do forget, you will be unable to open another copy
> until you do.
Yojimbo, and then force a synch on one machine, so that you don't wind
up copying the lock file into your dropbox. Then, when you get to the
other side, you have to remember to synch *first*, *then* launch
Yojimbo. I'm constantly getting tripped up by this, and it's really
annoying.
Unfortunately, this is much harder than simply copying the damned
database onto an external drive and shlepping the thing back and
forth. Geez, I wish Apple had done iSync right.
Niels Kobschaetzki
>
> On Mar 25, 2:06 pm, Andrew Janjigian <ajanjig...@gmail.com> wrote:
>> The one and
>> only "hassle" is that you must remember to quit YJ on whichever machine it
>> is running before opening it on another. But there is a failsafe to prevent
>> conflicts, in that if you do forget, you will be unable to open another copy
>> until you do.
>
> No, it's more complicated than that. You have to remember to quit
> Yojimbo, and then force a synch on one machine, so that you don't wind
> up copying the lock file into your dropbox.
At least in my case syncs are happening automatically when I'm
connected to the internet. And the lock file can be copied to the
dropbox because when you close Yojimbo, it will be deleted from the
dropbox and this will be synced as well.
> Then, when you get to the
> other side, you have to remember to synch *first*, *then* launch
> Yojimbo. I'm constantly getting tripped up by this, and it's really
> annoying.
I start up my machine, wait for syncs to happen which goes rather fast
at least for me but I usually do not have slow connections available
(at least several hundred KByte down and 100 KByte up)
> Unfortunately, this is much harder than simply copying the damned
> database onto an external drive and shlepping the thing back and
> forth. Geez, I wish Apple had done iSync right.
Yp, but they didn't :(
For me dropbox is easier to use than the hard drive.
Niels
Andrew Janjigian
nomad
then wait until DropBox does it's thing, then I suppose I'm all right.
I suppose it's a marginal inconvenience, not being able to auto-launch
Yojimbo on startup, but I'll try it and see.
tharpold
increases in the database, and one's hardware/network throughput/luck
on a given day. Once things go awry, it seems to become harder to get
them working again, ever, without radical solutions.
I added back in a portion of the image files and the .pdf files that
were formerly in my database, which is now 84 MB in size. Adding these
in about 20 MB at a time (once daily) appeared to work -- that is,
synching took place without any problems.
I'm back to using Yojimbo on a regular basis, and (for the time being)
synching seems to be working. I've elected to *not* copy into the
database about 300 small .pdfs (another 40 MB, tax-related receipts),
and another 30-50 large .pdfs (50 MB, copies of journal articles I
need to read) as I'm shy of testing the sync mechanisms further. Those
I'll store somewhere else. I'm disappointed that I can't reliably
store them in Yojimbo, as it would seem ideal for that purpose.
Yojimbo is a useful tool. But I come away from a couple of years' of
trying to get it to work as promised convinced that it is, at least
for some users' configurations, *much* more limited in its potential
uses than BB claims. And it may not be possible in advance to
determine if you are one of those users, or will become one through
some mishap of the sync mechanism, because the relevant data are
undocumented.. That's regrettable.