Menu ▾ ▴

#109 Lower the verbosity seems not working

duply
closed-invalid
nobody
verbosity (1)
5
2020-12-28
2017-06-27
Schroeffu
No

I would like to report the same bug as #80 from 2015/2016. https://sourceforge.net/p/ftplicity/bugs/80/

It seems not to be possible, change the VERBOSITY lower than default. My goal is, only receive an email from cronjob, if the duply job failed. Otherwise i get spammed every night.

The following commands seems not to set verbosity to "error" only:
duply <profile> status (or backup) -v1
duply <profile> status (or backup) --verbosity 1, and
duply <profile> status (or backup) with VERBOSITY=1 in conf-file,
all of these commands are still showing the full output of status.</profile></profile></profile>

How to fix that?
Many thanks in advance!

Discussion

  • Schroeffu

    Schroeffu - 2017-06-27

    Additional Info: yes, -v9 for debug is working, but -v0 / -v1 for errors only is not: it is the same as -v5

     
    • ede

      ede - 2017-06-28

      On 27.06.2017 22:20, Schroeffu wrote:

      Additional Info: yes, -v9 for debug is working, but -v0 / -v1 for errors only is not: it is the same as -v5

      right. proper verbosity below info is not implemented neither in duply nor in duplicity.

      you could write your duply output to a logfile though and only cat that in case duply return code is not 0 (success). like (untested)

      duply profile backup > duply.log 2>&1 || cat duply.log

      ..ede/duply.net

       
  • ede

    ede - 2020-12-28
    • status: open --> closed-invalid
     
  • ede

    ede - 2020-12-28

    duplicity issue

     

Log in to post a comment.