https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23571
--- Comment #34 from Jonathan Druart <[email protected]> --- (In reply to Blou from comment #33) > > Solved in my alternative patch. I chose to keep the output silent, unless > > --verbose is passed. This is the right behaviour for cronjobs, specially if > > we have the execution logged in the action_logs. > > I'd like to understand how it is "the right behavior" for a process to not > output a message when a fatal error occurs ? I've seen the option -q added > for quietness, but never to require -v to print fatal errors. > > We ran the script manually and got nothing telling us it failed. The action > logs is NOT a valid alternative for meaningful (and efficient) error > messages. As the script is (by default) only called on a daily basis, it may be relevant to send to STDERR the lock error (even without --verbose). Tomas, what do you think? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
