#12 Ability to log runtime errors and final result to file or syslog

[J.J.]

An issue with mbsync is that it is not friendly for scripted environments, because it's runtime/completion result cannot be easily captured -- aside from the exit code -- if not run interactively.

If sync is performed via a cron job, there's no way to later audit the results to assess correctness. There is therefore no way to have a script parse error messages and take corrective action.

If possible, could you please add a logging option.

Thanks

[Oswald Buddenhagen]

enhanced exit codes and notifications have been subject of tracker items and mailing list threads many times, so please check that.

as far as logging goes, i'm not quite sure what you expect. if an actual error occurs, mbsync will spew that out even in non-interactive mode. in fact, my own setup is completely non-interactive (and runs with the -q option).

[Oswald Buddenhagen]

no follow-up from reporter.