On Wed, Aug 04, 2021 at 06:20:33PM +0200, Uwe Kleine-König wrote:
A bigger context of the logs of an older run can be found at
https://www.kleine-koenig.org/~uwe/syncmail.log
ok, that's "interesting": the job not only takes lots of wall time, it
also consumes huge amounts of cpu time. something is seriously fishy in
that setup. first to check would be whether it's ssh or mbsync (and if
it's the latter, whether it's openssl or something else).
I saw mbsync write to one of its files at 100% yesterday while the ssh
tunnel was already gone.
This was before I suspended the machine, and some time after wakeup
today, the loss of 460840 messages was reported from that process.
ok, now i want to see the -D logs from an event like that, bracketed by
timestamps.
Would it make sense to put my maildir into a git repo (including the
mbsync files) and commit after each run?
that's an interesting idea. in particular, this could be used to verify
that notmuch doesn't mess up anything in the synced folders.
Is there a more suitable place where I can read about how mbsync tracks
mail than the source code to understand the content of these files?
nope. everything is in sync.c. load_state() is probably most helpful, as
it also provides insight into the journal's meaning.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
