On Tue, 6 Apr 2021 14:42:28 -0500, Dale wrote: > > cron only sends an email if the job produces any output. If the script > > follows the *nix principle of succeed quietly, fail noisily, you > > should only get emails when things go wrong. However without seeing > > your mail-backup script, it is hard to say what needs to change. > > > > The "|| true " part means this cron task will always return success, > > even if the script fails, which possibly is not what you want. > > > > > > > My script, if one wants to call it that, just has rsync commands in it. > It doesn't get fancy. I literally copy the commands from Konsole and > paste them in my text file. I make it executable and that's my script. > I wouldn't even think it rises to a bash thing even tho it is at the > top, cron likes it that way. For years, I been doing it manually. I > just wanted to automate the thing a bit.
But what are the rsync commands and what information does cron mail you? Without this information, we can only make wild guesses as to what is going on. As a first wild guess though, rsync has a --quiet option that means it only outputs error messages, are you using this? As John said, your cron script only calls the backup script, so you may as well put that in cron.hourly. -- Neil Bothwick ...Advert for restaurant: "Exotic foods for all occasions. Police balls a speciality."
pgp3YI58o6QnE.pgp
Description: OpenPGP digital signature
