tarsnapper -c /usr/local/etc/tarsnapper.conf make
Which works like it should and I get an output like this
Creating backup mail: mybackupjob-20150610-092951 3 backups are matching 0 of those can be deleted
I'm now running this in cron like so (cron seems to be running in /bin/sh on Ubuntu 15.04)
0 2 * * * PATH=$PATH:/usr/local/bin tarsnapper -c /usr/local/etc/tarsnapper.conf make >/dev/null
Which works otherwise but for some reason I still get the output (stdout) in my email by cron so the stdout redirection to /dev/null doesn't seem to work as needed.
I tried debugging by just running the command without cron using the redirection and still I get the output when running:
tarsnapper -c /usr/local/etc/tarsnapper.conf make >/dev/null
So how can I properly redirect the normal output (stdout) of this tarsnapper invocation to /dev/null?
I never had this kind of problem using
>/dev/null redirection with other commands, so it must be something to do with how tarsnapper works, right?
I know that tarsnapper is a python script that calls the tarsnap binary.
I tried searching for answers about redirecting stdout but couldn't find anything that would solve my problem.