06-25-2013
You should probably try to identify and fix the root cause instead of trying to alter a standard behavior.
Why are your cron jobs generating output while asked not to ?
Can you post a sample crontab entry that exhibit the problem ?
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
Our servers were on Sun Solaris 8.1, anytime a cron job executed the user ran that job received a email of job's output. I think that the default and Administrator did not setup anything.
However, when we upgraded the OS to Sun Solaris ver.10, the cron job is no longer send a email... (2 Replies)
Discussion started by: cmnguyen
2 Replies
2. AIX
Hi,
I'm fairly new to Aix and am looking for some help on the following.
I have setup a cron job under root and want it to send the email once it's run to an external email address. I can get it to send the output in an email to me by using mail on the end of the crontab entry. But I would... (1 Reply)
Discussion started by: elmesy
1 Replies
3. Solaris
Hi,
I want to run a crontab job on solaris 10.5. I have configured the crontab accordingly
10 * * * * /scripts/dbalter.pl >> /scripts/cronout.txt
However this does not work .Then I go to /var/mail/root and find an error in the output:
From root@myserver Wed Feb 4 17:02:00 2009... (1 Reply)
Discussion started by: sonu2die4
1 Replies
4. Solaris
Hi I am new to solaris zones...........
I created a zone in solaris and i am trying to add a cron entry to that by
crontab -e but when I enter that command it is just showing 253 number.....
But when I enter crontab -l there are some entries my question is how to add cron entry??
when... (3 Replies)
Discussion started by: vijaysachin
3 Replies
5. Shell Programming and Scripting
Hi guys, not sure if this would be the right place for this but I dont where else it would go... I'm new to Unix too, so please bare with me :)
I guess first up some background on the situation. We have some scripts that run as cron jobs which monitor and check the health, etc of our servers.... (2 Replies)
Discussion started by: BrianD
2 Replies
6. Solaris
How to setup a cron job to run every 45 minutes in Solaris 5.10 (9 Replies)
Discussion started by: reyazan
9 Replies
7. Shell Programming and Scripting
Hi all,
I think this could have a simple solution, just I canīt get it so far.
I have the script below that includes several echo commands in order
to show that every part of the script have been executed. A cron job
executes this script and when is completed the output is sent by email.
... (4 Replies)
Discussion started by: cgkmal
4 Replies
8. Shell Programming and Scripting
Hi i created a cron job which invoke a shell script and output some content via email.
Some times these output are sent to the junk email folder. i want these mails to be sent to inbox with some specific font. what i have to do? (4 Replies)
Discussion started by: vidhyaS
4 Replies
9. Shell Programming and Scripting
I am using centos 6.4.
I have a few cron jobs setup and they all work fine.
However, I would like to enhance one of the crons.
This is what I have at the moment:
nice rsync -au /home/samba/wsaler/* /home/samba/wsaler.backup/wsaler.backup18pm
date | /bin/mail -s "wsaler 3:00pm backup... (8 Replies)
Discussion started by: countrydj
8 Replies
10. Shell Programming and Scripting
Team,
Would like to know what is the best script that will send you an email if cronjob did not run.
Thanks (4 Replies)
Discussion started by: kenshinhimura
4 Replies
ATRUN(8) BSD System Manager's Manual ATRUN(8)
NAME
atrun -- run jobs queued for later execution
SYNOPSIS
atrun [-l load_avg] [-d]
DESCRIPTION
atrun runs jobs queued by at(1). Root's crontab(5) must contain the line:
*/10 * * * * root /usr/libexec/atrun
so that atrun(8) gets called every ten minutes.
At every invocation, every job in lowercase queues whose starting time has passed is started. A maximum of one batch job (denoted by upper-
case queues) is started each time atrun is invoked.
OPTIONS
-l load_avg
Specifies a limiting load factor, over which batch jobs should not be run, instead of the compiled-in value of 1.5.
-d Debug; print error messages to standard error instead of using syslog(3).
WARNINGS
For atrun to work, you have to start up a cron(8) daemon.
FILES
/var/at/spool Directory containing output spool files
/var/at/jobs Directory containing job files
SEE ALSO
at(1), crontab(1), syslog(3), crontab(5), cron(8)
AUTHORS
Thomas Koenig <ig25@rz.uni-karlsruhe.de>
BUGS
The functionality of atrun should be merged into cron(8).
BSD
April 12, 1995 BSD