[SOLVED] Ways to prevent cron e-mails from particular bash script located in cron.daily?

postcd · 08-22-2017, 07:05 AM

Hello,

i have a bash script in /etc/cron.daily/myscript

and receiving e-mails each time this script run:

Quote:

From: Anacron <root@myserver>
To: root@myserver
Content-Type: text/plain; charset="ANSI_X3.4-1968"
Subject: Anacron job 'cron.daily' on myserver
Status: R

I do not want to receive e-mails for this particular bash script.

I know i can edit bash script and output commands output STDERR/OUT to /dev/null but there is too many lines.

How can i mute these e-mails for this particular bash script or mute that bash script STDOUT/ERR please ?

I know i can create new file in /etc/cron.d and inside it add something like:
15 0 * * * root /bin/sh /etc/cron.daily/myscript >/dev/null 2>&1

But i want the bash script to stay in cron.daily, any way to do so in a simple way?

crontabs-1.10-33

TB0ne · 08-22-2017, 07:19 AM

Quote:

Originally Posted by postcd

Hello,
i have a bash script in /etc/cron.daily/myscript and receiving e-mails each time this script run:

Code:

From: Anacron <root@myserver>
To: root@myserver
Content-Type: text/plain; charset="ANSI_X3.4-1968"
Subject: Anacron job 'cron.daily' on myserver
Status: R

I do not want to receive e-mails for this particular bash script. I know i can edit bash script and output commands output STDERR/OUT to /dev/null but there is too many lines.

How can i mute these e-mails for this particular bash script or mute that bash script STDOUT/ERR please ?

I know i can create new file in /etc/cron.d and inside it add something like:
15 0 * * * root /bin/sh /etc/cron.daily/myscript >/dev/null 2>&1

But i want the bash script to stay in cron.daily, any way to do so in a simple way?

crontabs-1.10-33

Try looking at the answers in your OTHER thread about a very similar issue:
http://www.linuxquestions.org/questi...5/#post5730486

And the statement "I know i can edit bash script and output commands output STDERR/OUT to /dev/null but there is too many lines." doesn't lend credence to you having done much (if any) research on your own, as stated in the "Question Guidelines", as you've been pointed to MANY times. How many lines are in this script? And doing a global search/replace is trivial, to get statements at the end of every line...even a simple sed could do it with one line, so it's hard to believe that it's so hard, or that a cron script would have many lines at all.

Again, your last thread about this has the solution...in the post you were handed, along with the links IN that post. Here's a hint: instead of setting MAILTO to an address.....TRY SETTING IT TO NOTHING.

rknichols · 08-22-2017, 08:55 AM

At the top of the script (well, after the "#!" line), just insert the lines

Code:

exec >/dev/null
exec 2>/dev/null

That will re-define stdout and stderr for the rest of the script. If the unwanted output is just from stdout, it's probably best to leave stderr alone so that you'll still get messages if something goes wrong. It's really annoying when things fail silently.