Package: rsnapshot Version: 1.4.0-1 Severity: wishlist Dear Maintainer,
First off, let me say that, I like this new feature of rsnapshot grabbing the rsync output and logged in the 'logfile' set in rsnapshot.conf. Since this does what I was doing before with 1.3. With earlier versions of rsnapshot, one could grab the rsync output to a file. With 'loglevel 2' set in the rsnapshot.conf. For example: $ rsnapshot -v hourly >> rsnapshot-hourly.log 2>&1 Would then send an email daily. Which would include the output of rsnapshot and rsync; just showing what was rsync'ed and deleted. And would also log to the 'logfile' set in rsnapshot.conf, the rsnapshot output. With version 1.4, the above no longer works. Due to this change[0,1]. [0] https://github.com/rsnapshot/rsnapshot/pull/46 [1] https://github.com/bebehei/rsnapshot/commit/68cc6b95d2e47ee5ff9561b11e9ff1977dc02197 Since rsnapshot now grabs the rsync output. Now setting 'loglevel 4' in the rsnapshot.conf, the rsnapshot and rsync output; just showing what was rsync'ed and deleted. Both are now logged in the 'logfile' set in rsnapshot.conf. Just like I was doing above with earlier versions of rsnapshot. For example: $ rsnapshot -v alpha Setting the 'loglevel' lower than 4, in the rsnapshot.conf and the rsync output is not grabbed by rsnapshot. Also can not be grabbed to another file. It seems the only way to grab the rsync output to a different file, with version 1.4. Is to use rsnapshot without using the '-v' option with 'loglevel 4'. Or using the '-V' option. But either of those options, gives way too much information. Just want/need what was rsync'ed and deleted, like explained and is done above. For example: $ rsnapshot alpha >> rsnapshot-alpha.log 2>&1 $ rsnapshot -V alpha >> rsnapshot-alpha.log 2>&1 The above also grabs the rsync output and is logged to the 'logfile' set in rsnapshot.conf. Again with too much information. *NOTE: Notice that omitting the '-v' option gives more output, due to not lowering the 'loglevel 4' set in rsnapshot.conf. When using the '-v' option, verbosity is lowered; presumably to 2 in this case. Which is fine by me, since rsnapshot grabs only the rsync output that was rsync'ed and deleted. Take a look at bug #794343[0] for more information. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794343 Also regardless of the 'loglevel' set in the rsnapshot.conf. The '-V' option always outputs too much information. Also commented out 'loglevel' to see what affect this would have. Which was, as suspected nothing is logged in the 'logfile' set in rsnapshot.conf. While still not being able to grab the rsync output. Please document this. With the upgrade to 1.4, was testing to see if bug #717451[0] was actually fixed this time ;) Since did not see the rsync output as explained above. Thought that bug #717451 was still an issue. After reading the rsnapshot 1.4 changelog[1] and doing some more reading. Figured out that bug #717451 was fixed and rsnapshot was grabbing the rsync output. Also if possible, please add an option in the rsnapshot.conf and/or on the command line. For the user to also be able to grab the rysnc output to another file, like was possible with 1.3. Just showing what was rsync'ed and deleted. While still being logged in the 'logfile' set in rsnapshot.conf. [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717451 [1] https://github.com/bebehei/rsnapshot/blob/master/ChangeLog Thank You, Michel -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rsnapshot depends on: ii liblchown-perl 1.01-3 ii logrotate 3.8.7-2 ii perl 5.20.2-6 ii rsync 3.1.1-3 Versions of packages rsnapshot recommends: ii openssh-client [ssh-client] 1:6.7p1-6 rsnapshot suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
