On Wed, Feb 12, 2020 at 06:12:46AM -0500, Andy W wrote:
If I'm not explicitly calling a channel, wouldn't that section be ignored ?
it would, but without SyncState * that wouldn't matter as long as you
used both competing channels at some point (because the sync state file
name is derived from the channel name).
re-read what i wrote (pay particular attention to subjunctive forms) -
that should answer the remaining related questions.
Also, I don't have MaxMessages defined AFAIK. Is there any other place
this could be set?
no, that's why i suggested a separate instance (with a private config in
a non-standard place). that's far-fetched, but so are the symptoms you
describe.
first we need to see _all_ mbsync command lines as you are actually
using them, as these may override the config in relevant ways.
then we need to be sure that it's actually mbsync which makes the
messages disappear. i suppose you could find that out with sysdig or a
similar tracing framework.
then you would need to always run mbsync with -D and collect the logs,
to be able to examine them as soon as you notice the problem.
i suppose it would be also possible to use kprobes or something like
that to set up a breakpoint on any process that deletes any file under
Archive/cur/, but i never dug into that deep enough to know how to pull
it off.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
