On Thu, Oct 27, 2016 at 10:15:27PM +0200, Yuri D'Elia wrote: > It's hard to reproduce at will. The incomplete journal is consistently > the INBOX folder of an outlook365 server. But this is because this is > also the slowest folder to sync, and thus most likely to be interrupted. > you wouldn't have gotten it several times already if it was hard. it seems to me that it would be sufficient to interrupt it while it is fetching the message list.
> As for truncation, this might still happen if the file is not fsynced > explicitly at critical transaction points (including before fclose). > you're not getting truncation, but data corruption, as that's what appending a number of null bytes is. thers is _no_ standard that permits this without an interim system crash, fsync or not. > I would actually be pretty happy to have two (or more) ORed flags for > the exit status as many tools already do, in order to distinguish the > broad categories. > that's doable, but there are still some grey zones in the interpretation. for example, dns lookup failure is generally a permanent error - except when it's actually caused by a network failure. in principle there are separate error codes for that, yet somehow i'm regularly getting NXDOMAIN in this case. certainly something botched in the setup of the dns proxy on my host or router, but still real. ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
