Sponsored Content
Full Discussion: Cronjob to notify by mail
Top Forums Shell Programming and Scripting Cronjob to notify by mail Post 302467882 by Chubler_XL on Sunday 31st of October 2010 10:14:08 PM
Old 10-31-2010
Example cron config
Code:
# On the 1st of the month at 8am notify Task 2 jobs
0 8 1 * * /usr/local/bin/mynotify 2
 
# On the 1st and 15th of the month at 7:30am Task 1 jobs
30 7 1,15 * * /usr/local/bin/mynotify 1
 
# On Friday at 11:15pm notify Task 3 jobs
15 23 * 5 /usr/local/bin/mynotify 3
 
# On 1st Apr (1st Quarter) at 8am notify Task 4 jobs
0 8 1 4 * /usr/local/bin/mynotify 4

For quarterly checks you are probably best of creating 1 job for each of the 4 dates (see 1st April above).

Now you just need to write your "mynotify" script that accepts a task number and sends the emails out. It can read your config files.

Code:
$ cat tasks_list.txt
1:1,2,3:Check windows servers' health:Peter Bill
2:4,5:Check the mail server's health:James
3:6,7,8:Check linux server's health:Bill

$ cat name.txt
Bill bill@xxx.com
Peter peter@xxx.com
James james@xxx.com

$ cat mynotify 
TASK=$1
TODO=$(grep "^$TASK" tasks_list.txt)
[ -z "$TODO" ] && exit
JOBS=$(echo $TODO | cut -f2 -d:)
TITLE=$(echo $TODO | cut -f3 -d:)
WHO=$(echo $TODO | cut -f4 -d:)
echo $WHO | tr ' ' '\n' | while read USR
do
    EMAIL=$(grep "^$USR " name.txt | cut -f2 -d' ')
    echo mail to $USR \($EMAIL\)  subject $TITLE  jobs $JOBS  
done

$ ./mynotify 1
mail to Peter (peter@xxx.com) subject Check windows servers' health jobs 1,2,3
mail to Bill (bill@xxx.com) subject Check windows servers' health jobs 1,2,3


Last edited by Chubler_XL; 10-31-2010 at 11:32 PM..
This User Gave Thanks to Chubler_XL For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

process pager - by cell phone or just e-mail notify

hi all.. i need any help. i want to create in my crontab a simple script for verify any process and notify for the status in my e-mail or cell phone. anybody help me? (9 Replies)
Discussion started by: squash
9 Replies

2. UNIX for Advanced & Expert Users

mail from Cronjob

Hi, I'm having a HP UX 11i and 11.0 . I've given the cron access to one of the user. Now he is getting mails on errors only and not on success on execution of the command. How can i make sure that the mail is sent in both the cases of success and failure. Also the mail is going to the lotus... (6 Replies)
Discussion started by: i2admin
6 Replies

3. Post Here to Contact Site Administrators and Moderators

Notify of a new thread

Hi, I wish to be notified whenever there is a new thread posted on any of the forums or atleast the forums that I have registered to. Can this be done. How? I am sure there must be a way to do this, and I feel this is how the moderators must be doing. I know I may not be eligible enough to be... (5 Replies)
Discussion started by: linuxpenguin
5 Replies

4. UNIX for Dummies Questions & Answers

Notify Command.

Hi, I am using the NOTIFY command and I am getting the emails.. I tried MAILX and e-mail is being sent. I want to use NOTIFY to see if my jobs are completed or not. Am I missing something.. All your ideas are greatly appreciated.. Thanks Venky (2 Replies)
Discussion started by: venkyA
2 Replies

5. Shell Programming and Scripting

Cronjob - Redirect mail output to file, LINES & COLUMNS

I currently have an expect script that issues the 'mail' command and sends an 'x' when it receives the & prompt from mail to quit. The expect script is able to do stty rows 100 columns 200 < $spawn_out(slave,name) to set up the number of columns and rows. I would like to get rid of the expect... (0 Replies)
Discussion started by: jharvey
0 Replies

6. UNIX for Advanced & Expert Users

Notify Me when job fail using cron

I would like to be notified when an Informix dbexport job fails on a TRU64 system. My idea is to send an email via telnet, but can only get telnet to do it interactively. I can do the following steps on my UNIX box interactively, but cannot send an email with a script. Can someone help? Is there... (3 Replies)
Discussion started by: ejaggers
3 Replies

7. Shell Programming and Scripting

Using mail command to notify the status of script

Can someone please help me with this script, I'm trying to create system backup on AIX, for this I want to first mount the filesystem if it is not mounted, then create the backup and unmount the filesystem but I'm having problem while using the mail command to notify the status of filesystem... (9 Replies)
Discussion started by: mbak
9 Replies

8. Shell Programming and Scripting

notify-send does not notify real time

Hi, I am having a little trouble getting notify-send to work the way I would like it to. I am using ubuntu - karmic koala 2.6.31-19-generic #56-Ubuntu SMP So here's the problem run the following commands one after the other. notify-send -i info -t 100000 -- "Hi" "world" & notify-send -i... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

9. UNIX for Dummies Questions & Answers

how to cancel a cronjob if the cronjob still running

hi everyone I'm newbie in this forum hope I can get some help here :) I have a command in crontab that executed every 1 minute sometime this command need more than 1 minute to finish the problem is, the crontab execute this command although it's not finish processing yet and causing the system... (7 Replies)
Discussion started by: 2j4h
7 Replies

10. Shell Programming and Scripting

A notify-send Question --

Greetings. I've come across a bit of a problem with notify-send syntax; and wondered if anyone out there had found a solution in the woodpile somewhere :) Here's the snippet which is giving me trouble:notify-send 'Text to display' image_data 300, 300, , , , , /etc/image.pngOutput:Invalid... (0 Replies)
Discussion started by: LinQ
0 Replies
queuedefs(4)							   File Formats 						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1 A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.11 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 06:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy