On Sat, Feb 06, 2016 at 01:41:16PM -0800, Scott Mcdermott wrote: > The program could possibly keep track of (mailstore, folder) tuples it > has seen already and issue a warning or halt if it sees the same tuple > twice, in order to avoid this. > yeah, that would make sense.
> What I did not realize was that patterns have to be excluded > twice (as they match on both Master and Slave side), because of > this misleading text from the manual's description of Pattern: > > The mailbox names are the same on both Master and Slave > but it *is* true for synced mailboxes. however, you have a point that for *excluded* mailboxes the identity rule does not (necessarily) apply. > (In fact, they can be completely different names if they are > given explicitly in the channel definition as I'm doing, and also > by using the 'Inbox' directive.) > these aren't Patterns. > Indeed, but atomic reads at mailbox level with Maildir are not > actually possible, so this sleep check could loop for a while > (potentially forever) if the Maildir is busy being changed by > other software. > yes, the code is commented to that effect. ;) > (Actually, my understanding is that getdents64(), if used > directly, can give all the dirents atomically if provided with a > big enough buffer, but readdir() is required for portability of > course.) > that's for just one directory. we have to read both cur/ and new/, so there are plain no guarantees. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
