Re: [SyncEvolution] [os-libsynthesis] Evolution Sync-UI Periodic Sync
On Mo, 2011-01-24 at 00:40 +0000, David Vredenburgh wrote:
I have set up sync-ui to get my contacts/calendar into Evolution and
it all
works well. However, I cannot find any documentation on the sync-ui tool (I am
on Ubuntu 10.04 running Gnome) to answer my newbie question of *when* does the
synchronization occur?
You are right, and we know about this limitation. Unfortunately there
was no time to do anything about it:
http://bugs.meego.com/show_bug.cgi?id=1020
Clearly it happens whenever I hit the button, but does it
periodically sync
other times? Does Evolution automatically trigger a sync whenever a contact or
calendar event change?
It's time based. You need to enable it explicitly via a checkmark in the
sync-UI. You can tune the intervals via the command line or config
files:
autoSync:
Controls automatic synchronization. Currently,
automatic synchronization is done by running
a synchronization at regular intervals. This
may drain the battery, in particular when
using Bluetooth!
Because a peer might be reachable via different
transports at some point, this option provides
detailed control over which transports may
be used for automatic synchronization:
0 - don't do auto sync
1 - do automatic sync, using whatever transport
is available
http - only via HTTP transport
obex-bt - only via Bluetooth transport
http,obex-bt - pick one of these
autoSyncInterval:
This is the minimum number of seconds between two
synchronizations that has to pass before starting
an automatic synchronization. Can be specified using
a 1h30m5s format.
Before reducing this interval, consider that it will
increase resource consumption on the local and remote
side. Some SyncML server operators only allow a
certain number of sessions per day.
The value 0 has the effect of only running automatic
synchronization when changes are detected (not
implemented yet, therefore it basically disables
automatic synchronization).
autoSyncDelay:
An automatic sync will not be started unless the peer
has been available for this duration, specified in seconds
or 1h30m5s format.
This prevents running a sync when network connectivity
is unreliable or was recently established for some
other purpose. It is also a heuristic that attempts
to predict how long connectivity be available in the
future, because it should better be available long
enough to complete the synchronization.
Defaults are 30 minutes for autoSyncInterval and 5 minutes for the delay
(this really should be in the "--sync-property ?" output!).
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.