I use tarsnapper's make command for managing tarsnap backups like this:tarsnapper -c /usr/local/etc/tarsnapper.conf makeWhich works like it should and I get an output like thisCreating backup mail: mybackupjob-20150610-0929513 backups are matching0 of those can be deletedI'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/nullWhich 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/nullSo 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.
How to redirect tarsnapper output to /dev/null?
cron;io redirection;stdout