How to make bart-logger silent?

[bhmevik]

When running bart-logger, it prints

<module 'bart.slurm' from '/usr/lib/python2.7/site-packages/bart/slurm.pyc'>

on stdout/stderr. When running it as a cron job, that output ends up as an email. It would be nice to have bart-logger not print anything except on errors/warnings. Is that possible?

[edelmann]

Hi, I'm deeply sorry for the late reply - another project consumed most of my time and energy for a while.

----- On 14 Nov, 2017, at 17:22, Bjørn-Helge Mevik notifications@github.com wrote:

When running bart-logger, it prints <module 'bart.slurm' from '/usr/lib/python2.7/site-packages/bart/slurm.pyc'> on stdout/stderr. When running it as a cron job, that output ends up as an email. It would be nice to have bart-logger not print anything except on errors/warnings. Is that possible?

Yes. Since I couldn't find any use of having that <module ...> information written anywhere, other than debugging, I turned it from a print statement into a logging.debug(): 590a56c And then I made 'INFO' the default log level: 46bc0db Wrt. priting errors/warnings: Currently most warnings and errors go to the log file only - would it be helpful if they were written to stderr too? Erik

[bhmevik]

Thanks! I'll test the changes.
Wrt errors/warnings: I think having errors on stderr as well might be a good idea, but not warnings. Typically bart would be run many times a day, and warnings will just produce too much noise, IMO.

[edelmann]

OK, thanks for the input. I ended up making the "errors/warnings to stderr"-thing configurable; in the config file, set stderr_level=ERROR to have errors written on stderr. If you would want warnings too, set it to 'WARNING' instead. If you want nothing on stderr, leave it unset. (Except, errors that happen before logging has been set up will be written on stderr no matter what) Erik

…

----- On 20 Feb, 2018, at 13:41, Bjørn-Helge Mevik notifications@github.com wrote:

Thanks! I'll test the changes. Wrt errors/warnings: I think having errors on stderr as well might be a good idea, but not warnings. Typically bart would be run many times a day, and warnings will just produce too much noise, IMO. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #27 (comment)