Hi, from my incomplete knowledge, I'd say that cron sends an email when a process it calls terminates with an exit code =! 0, or prints any output to stdour or stderr. So this sounds like the backintime process called from cron does not terminate =! 0 and does not print anything when its user-callback script fails. I can see that this is irritating, and contrary to expectations. We've had a related complaint before: https://github.com/bit-team/backintime/issues/1053 We'd probably need to examine if/how the exit code of the user-callback script gets handed back to the backintime process (and then to cron), or why this does not happen. Cheers, Michael On Fri, Jan 20, 2023 at 11:17:28AM +0000, c.buhtz@posteo.jp wrote:
Hey folks,
can someone please who knows good about cron have a look at this bug report. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985260
The users expect that he would got a mail if there is a syntax error in one of his user-callback scripts running by cron.
I'm not sure if this should be the default behaviour and which component is responsible for sending mails. For the letter I assume cron should do this.
So I assume this bug is not related to Back In Time. Am I wrong?
Kind Christian _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de