[rsnapshot-discuss] Version 1.4.2-1 WARNING verbosity-level

[Hans Sandsdalen]

Hi

I have recently upgraded to ubuntu 16.04 and version 1.4.2-1 of rsnapshot. I run rsnapshot from cron, often with the "-q" option.

According to the man-page: "-q quiet, suppress non-fatal warnings". Is it correct that this warning is fatal?

WARNING: The verbosity-level is "1" despite subsequent declaration at line xxx.

I think it is annoying since I get an email even if there are no problems.

---
Hans Sandsdalen

http://www.spacetec.no
Tlf: 97762632












CONFIDENTIALITY This e-mail and any attachment contain KONGSBERG information which may be proprietary, confidential or subject to export regulations, and is only meant or the intended recipient(s). Any disclosure, copying, distribution or use is prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in error, please delete it immediately from your system and notify the sender properly.

[Benedikt Heine]

Hi Hans,

Post by Hans Sandsdalen
WARNING: The verbosity-level is "1" despite subsequent declaration at line xxx.
I think it is annoying since I get an email even if there are no problems.

You set the verbosity twice (once in you logfile and also another time
in the arguments). So either remove the `-q` in your cronjob or comment
the verbose-line in your configuration

See here:

https://github.com/rsnapshot/rsnapshot/commit/a1b28757


~ Benedikt

[Hans Sandsdalen]

Hi

I know that I do that. When the "primary" backup is run a report is made with rsnapreport.pl which requires a verbosity_level > 4 (or 3). I've done. The other backups are run with the -q option.

When I ask for no fatal warnings, I can't understand why I need this warning.

Do I need two config-files?
---
Hans Sandsdalen

http://www.spacetec.no
Tlf: 97762632












From: "Benedikt Heine" <***@heine.rocks>
To: rsnapshot-***@lists.sourceforge.net
Sent: Thursday, 20 July, 2017 19:03:40
Subject: Re: [rsnapshot-discuss] Version 1.4.2-1 WARNING verbosity-level

Hi Hans,

Post by Hans Sandsdalen
WARNING: The verbosity-level is "1" despite subsequent declaration at line xxx.
I think it is annoying since I get an email even if there are no problems.

You set the verbosity twice (once in you logfile and also another time
in the arguments). So either remove the `-q` in your cronjob or comment
the verbose-line in your configuration

See here:

https://github.com/rsnapshot/rsnapshot/commit/a1b28757


~ Benedikt

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss

[David Cantrell]

... I run rsnapshot from cron, often with the "-q" option.
According to the man-page: "-q quiet, suppress non-fatal warnings". Is it correct that this warning is fatal?
WARNING: The verbosity-level is "1" despite subsequent declaration at line xxx.

That clearly shouldn't be fatal. And I'm pretty sure it *isn't* fatal,
and so the fact that you see it despite using -q is a bug.

I'm pretty sure you can just filter it out by piping the output from the
cron job through grep -v until it gets fixed.

[Hans Sandsdalen]

Hi

Thank you!

I made a script that I call instead of rsnapshot:

#! /bin/bash
#

RSNAPSHOT=/usr/bin/rsnapshot
$RSNAPSHOT $* 2> >(egrep -v "WARNING: The verbosity-level is \"[0-9]+\" despite subsequent declaration at line" 1>&2)

---
Hans Sandsdalen

http://www.spacetec.no
Tlf: 97762632












From: "David Cantrell" <***@cantrell.org.uk>
To: rsnapshot-***@lists.sourceforge.net
Sent: Friday, 21 July, 2017 16:06:46
Subject: Re: [rsnapshot-discuss] Version 1.4.2-1 WARNING verbosity-level

... I run rsnapshot from cron, often with the "-q" option.
According to the man-page: "-q quiet, suppress non-fatal warnings". Is it correct that this warning is fatal?
WARNING: The verbosity-level is "1" despite subsequent declaration at line xxx.

That clearly shouldn't be fatal. And I'm pretty sure it *isn't* fatal,
and so the fact that you see it despite using -q is a bug.

I'm pretty sure you can just filter it out by piping the output from the
cron job through grep -v until it gets fixed.
--
David Cantrell | top google result for "topless karaoke murders"

There is no one true indentation style,
But if there were K&R would be Its Prophets.
Peace be upon Their Holy Beards.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss