On Fri, Jul 01 2022, Oswald Buddenhagen wrote: > in short, it's a mess. Fully agree with this.
> but if you find tangible evidence for isync's Timeout not working in > some other scenario, i'm all ears. > i suppose the most promising way to debug this would be running with -D > (maybe -Dn is sufficient) and saving away the logs where the process got > killed by timeout. I'm working on an unstable cell network, so packet loss or general connectivity loss is somewhat frequent. At some point I realized the cron job was getting stuck long enough to clash with the next run even after 15m. After battling with this for a while, I just ended up using timeout. But I can definitely start taking a note if you want more detailed info in where it gets stuck. _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
