On Fri, Dec 19, 2014 at 03:50:45PM +0100, Tomas Tintera wrote:
> There is a great option MaxMessages for things like this, but it
> automatically erases ("deletes") the messages from the slave store,
> while I would need to keep the expired messages intact (or even
> better, to erase them on the master store and keep them on the slave).
>
given that the effect of MaxMessages is one of the only two asymmetries
of master and slave i can think of (the other being the effect of
SyncState *), why don't you just swap the channels? (note that this will
invalidate your sync state. you can salvage it with some awk magic.)
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
