This minor bug was reported upstream and seems worthy of inclusion here. Patch and new ebuild are mine. Upstream bug text reproduced below. - JRG Anyone who uses flexbackup in a cron job surely gets the "syntax OK" message mailed to them each time the job runs, which is rather annoying when it runs properly. The fix is simple: "Syntax OK" is not an error, it's a regular message, and therefore it belongs in STDOUT and not STDERR. Thus, this modification: Line 2418 goes from: system("perl -c \"$configfile\""); to: system("perl -c \"$configfile\" 2>&1");
Created attachment 163527 [details, diff] Patch to redirect one specific message from stderr to stdout.
Won't this "fix" also direct real errors to stdout? From what I can tell, it redirects ALL stderr to stdout, which is not a good thing if there ARE errors. Remember, a missed warning about a backup not running will trigger the need for said backup, as much as forgetting your umbrella will trigger rain. Perhaps something like: system("/usr/bin/perl -c \"$configfile\" 2>/dev/null || /usr/bin/perl -c \"$configfile\""); It's inelegant, as it runs twice when there are problems, but won't incur any penalty as long as everything is OK, yet still report problems. (Oh, and it's immune to $PATH poisoning too)
Not in any meaningful way, no. The only place this redirection affects is a syntax check of the flexbackup.conf configuration file. In the event of a non-zero return code on the check, flexbackup correctly reports issues on stderr.
Created attachment 163615 [details] New ebuild applies the above patch.
Fixed in CVS Thanks for providing the patches, John.
