You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original debug option was for developer use, on a different system. For others to use it, it's probably better and clearer to add an argument for a dry-run, which regenerates the archive list. Or perhaps, add an option if you don't want to regenerate the archive list.
The text was updated successfully, but these errors were encountered:
If you set DEBUG=true then tarsnap-prune.sh doesn't run correctly anyway, because of this:
then
TMPFILE=/tmp/tarsnap.archives
if [ ! -f $TMPFILE ]; then
$TARSNAP --configfile /etc/tarsnap.conf --list-archives > $TMPFILE
fi
else
TMPFILE=/tmp/tarsnap.archives.$$
$TARSNAP --configfile /etc/tarsnap.conf --list-archives > $TMPFILE
fi
The problem is, if DEBUG=true in tarsnap-cron.conf then this is run:
if [ "$DEBUG" = "true" ]
then
TARSNAP="echo tarsnap"
fi
Thus /tmp/tarsnap.archives ends up with "echo tarsnap --configfile /etc/tarsnap.conf --list-archives" in it.
Given this issue is ~5 years old I don't expect any fixes, this is just here for the next person that wonders what's going on.
The original debug option was for developer use, on a different system. For others to use it, it's probably better and clearer to add an argument for a dry-run, which regenerates the archive list. Or perhaps, add an option if you don't want to regenerate the archive list.
The text was updated successfully, but these errors were encountered: