I'm running mbsync as part of a cron job under timeout(1). I sometimes get the following:
Error: incomplete journal entry at /path.journal:2 where the journal file looks simply truncated (probably not flushed). The actual file content is: 00000000: 320a 0000 0000 0000 0000 0000 0000 0000 2............... 00000010: 0000 0000 0000 0000 0000 0000 0000 .............. I remember asking in the list how robust the journal mechanism, but it doesn't seem reliable enough for mbsync to be SIGTERM'ed/interrupted. This is compounded by the fact that I cannot easily distinguish a network error (that I want to ignore - as it's generally transient) from an mbsync's internal error such as this. ------------------------------------------------------------------------------ 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
