(In reply to comment #3) > The Synthesis binfile issue is still open. Fixed now with libsynthesis: commit a9d907d78ca0eba61f6796093770bdf049edb498 Author: Patrick Ohly <firstname.lastname@example.org> Date: Tue Jul 22 16:24:08 2014 +0200 autotools: bump Linux/SyncEvolution sub-version for /dev/null binfiles commit 15f4f871da86802ea24dee34e1cfea56cafb804b Author: Patrick Ohly <email@example.com> Date: Tue Jul 22 15:59:10 2014 +0200 binfile: /dev/null datadir path When the client already knows that it is never going to sync again or the next sync will have to be a slow sync anyway, then the binfile client files are not needed. Suppressing writing of them is useful on devices with flash memory to avoid flash wearout. The specific use case is PBAP caching in a car's head unit. When setting "/dev/null" as datadir, the platform layer will avoid creating the files and instead keep their content in memory. This is required (and sufficient) for syncing once, which will close and later read from some files at least once. Therefore the data cannot be thrown away completely. And SyncEvolution: commit 834c1e7a6b4d319c5853da217f3f3d0f8a944565 Author: Patrick Ohly <firstname.lastname@example.org> Date: Tue Jul 22 16:04:03 2014 +0200 ephemeral sync: don't write binfile client files (FDO #55921) When doing PBAP caching, we don't want any meta data written because the next sync would not use it anyway. With the latest libsynthesis we can configure "/dev/null" as datadir for the client's binfiles and libsynthesis will avoid writing them. The PIM manager uses this for PBAP syncing automatically. For testing it can be enabled by setting the SYNCEVOLUTION_EPHEMERAL env variable.