|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
email when cron fails
Post 17672 by inpavan on Tuesday 19th of March 2002 07:09:07 AM
03-19-2002
yep..Thanks for the information and the script.
I tested it and it works fine.
I tested it and it works fine.
|
|
10 More Discussions You Might Find Interesting
1. Solaris
Getting ready for Sarbanes Oxley and I was told that I need to create a cron.allow file for the box so that only specified users can create cron jobs. That was easy enough, and I put in all the accounts that had scheduled cron jobs such as:
root
lp
My oracle account
A couple of programmer... (1 Reply)
Discussion started by: citrowske
1 Replies
2. UNIX for Dummies Questions & Answers
I have two different cron jobs that run on the same days. The jobs are 7 hours apart. Both jobs are set to send notification emails when they start running.
Both jobs always run successfully, but I only receive an email from the first job. I never get the email from the second job.
... (0 Replies)
Discussion started by: sasaliasim
0 Replies
3. Shell Programming and Scripting
Hi
Im very new at working with unix and this problem I simply can not understand. I know there are a lot of threads about problems with shell scripts behaving differently when run from a terminal and from a cronjob. I have tried everything(almost) but I still havent cracked this problem.
Im... (15 Replies)
Discussion started by: Nightowl
15 Replies
4. Shell Programming and Scripting
I have a very basic script that essentially sends a log file, via FTP, to a backup server. My cron entry to run this every night is:
55 23 * * * /usr/bin/archive_logs
The script runs perfectly when executed manually, and actually worked via cron for about three weeks. However, it mysteriously... (3 Replies)
Discussion started by: cdunavent
3 Replies
5. Shell Programming and Scripting
Hello,
I have added the following entry in my cron file:
* * * * * . /home/texprd/.profile>/dev/null 2>&1; echo "test" >> /home/texprd/test.log 2>&1
The cron fails ie the added command fails to append "test" in the test.log file. However if I run the command manually from the shell... (3 Replies)
Discussion started by: mahive
3 Replies
6. UNIX for Dummies Questions & Answers
Im having a problem with my ftp CRON jobs. I have another related (but not the same question in shell scripting).
My FTP CRON jobs connect to a server and drop some files off, if for some reason it cannot connect to the server (timesout/password wrong etc) instead of stopping, it tries again... (3 Replies)
Discussion started by: mokachoka
3 Replies
7. UNIX for Advanced & Expert Users
I added a shell script to cron that executes every 5-15 minutes. It's used to monitor multiple environments, so it has to ssh to each machine to check the status of that machine. Sometimes, I may have more than one instance of this script running at the same time. So, here's my problem. I've... (2 Replies)
Discussion started by: mrwatkin
2 Replies
8. Red Hat
Hi Guys...
I have a bulk email program that sends out an email to a subscribed mail list.
The list contains around 2000 addresses.
My server is Centos 5 64bit
PHP 5.2
Mysql 5.1
The program is set to send emails in batches of 100.
Cron is set to run every minute
Now for the problem:... (2 Replies)
Discussion started by: countrydj
2 Replies
9. Shell Programming and Scripting
Hi,
When run the script directly...it executes as expected. But when put it in crontab the job fails with this error:
Connection not open
08003: Connection not open
Unable to connect to the database...
how come it is not able to connect when cron job fires?... Do I need to... (7 Replies)
Discussion started by: nuthakki
7 Replies
10. Shell Programming and Scripting
Hi,
Below is my script which sends out emails.
more test.sh
1 #!/bin/ksh
2 {
3 print "From: Prod@mycomp.com"
4 # print "From: Prod@`hostname`.com"
5 # print "From: Prod@${HOSTNAME}.com"
6 print "To: me@mycomp.com"
7 print "Subject:... (5 Replies)
Discussion started by: mohtashims
5 Replies
LEARN ABOUT MOJAVE
sys::hostname::long
Sys::Hostname::Long(3) User Contributed Perl Documentation Sys::Hostname::Long(3) NAME
Sys::Hostname::Long - Try every conceivable way to get full hostname SYNOPSIS
use Sys::Hostname::Long; $host_long = hostname_long; DESCRIPTION
How to get the host full name in perl on multiple operating systems (mac, windows, unix* etc) DISCUSSION
This is the SECOND release of this code. It has an improved set of tests and improved interfaces - but it is still often failing to get a full host name. This of course is the reason I wrote the module, it is difficult to get full host names accurately on each system. On some systems (eg: Linux) it is dependent on the order of the entries in /etc/hosts. To make it easier to test I have testall.pl to generate an output list of all methods. Thus even if the logic is incorrect, it may be possible to get the full name. Attempt via many methods to get the systems full name. The Sys::Hostname class is the best and standard way to get the system hostname. However it is missing the long hostname. Special thanks to David Sundstrom and Greg Bacon for the original Sys::Hostname SUPPORT
This is the original list of platforms tested. MacOS Macintosh Classic OK Win32 MS Windows (95,98,nt,2000...) 98 OK MacOS X Macintosh 10 OK (other darwin) Probably OK (not tested) Linux Linux UNIX OS OK Sparc OK HPUX H.P. Unix 10? Not Tested Solaris SUN Solaris 7? OK (now) Irix SGI Irix 5? Not Tested FreeBSD FreeBSD OK A new list has now been compiled of all the operating systems so that I can individually keep informaiton on their success. THIS IS IN NEED OF AN UPDATE AFTER NEXT RELEASE. Acorn - Not yet tested AIX - Not yet tested Amiga - Not yet tested Atari - Not yet tested AtheOS - Not yet tested BeOS - Not yet tested BSD - Not yet tested BSD/OS - Not yet tested Compaq - Not yet tested Cygwin - Not yet tested Concurrent - Not yet tested DG/UX - Not yet tested Digital - Not yet tested DEC OSF/1 - Not yet tested Digital UNIX - Not yet tested DYNIX/ptx - Not yet tested EPOC - Not yet tested FreeBSD - Not yet tested Fujitsu-Siemens - Not yet tested Guardian - Not yet tested HP - Not yet tested HP-UX - Not yet tested IBM - Not yet tested IRIX - Not yet tested - 3rd hand information might be ok. Japanese - Not yet tested JPerl - Not yet tested Linux Debian - Not yet tested Gentoo - Not yet tested Mandrake - Not yet tested Red Hat- Not yet tested Slackware - Not yet tested SuSe - Not yet tested Yellowdog - Not yet tested LynxOS - Not yet tested Mac OS - Not yet tested Mac OS X - OK 20040315 (v1.1) MachTen - Not yet tested Minix - Not yet tested MinGW - Not yet tested MiNT - Not yet tested MPE/iX - Not yet tested MS-DOS - Not yet tested MVS - Not yet tested NetBSD - Not yet tested NetWare - Not yet tested NEWS-OS - Not yet tested NextStep - Not yet tested Novell - Not yet tested NonStop - Not yet tested NonStop-UX - Not yet tested OpenBSD - Not yet tested ODT - Not yet tested OpenVMS - Not yet tested Open UNIX - Not yet tested OS/2 - Not yet tested OS/390 - Not yet tested OS/400 - Not yet tested OSF/1 - Not yet tested OSR - Not yet tested Plan 9 - Not yet tested Pocket PC - Not yet tested PowerMAX - Not yet tested Psion - Not yet tested QNX 4 - Not yet tested 6 (Neutrino) - Not yet tested Reliant UNIX - Not yet tested RISCOS - Not yet tested SCO - Not yet tested SGI - Not yet tested Symbian - Not yet tested Sequent - Not yet tested Siemens - Not yet tested SINIX - Not yet tested Solaris - Not yet tested SONY - Not yet tested Sun - Not yet tested Stratus - Not yet tested Tandem - Not yet tested Tru64 - Not yet tested Ultrix - Not yet tested UNIX - Not yet tested U/WIN - Not yet tested Unixware - Not yet tested VMS - Not yet tested VOS - Not yet tested Windows CE - Not yet tested 3.1 - Not yet tested 95 - Not yet tested 98 - Not yet tested Me - Not yet tested NT - Not yet tested 2000 - Not yet tested XP - Not yet tested z/OS - Not yet tested KNOWN LIMITATIONS
Unix Most unix systems have trouble working out the fully quallified domain name as it to be configured somewhere in the system correctly. For example in most linux systems (debian, ?) the fully qualified name should be the first entry next to the ip number in /etc/hosts 192.168.0.1 fred.somwhere.special fred If it is the other way around, it will fail. Mac TODO
Contributions David Dick Graeme Hart Piotr Klaban * Extra code from G * Dispatch table * List of all operating systems. Solaris * Fall back 2 - TCP with DNS works ok * Also can read /etc/defaultdomain file SEE ALSO
L<Sys::Hostname> AUTHOR
Scott Penrose <scottp@dd.com.au> COPYRIGHT
Copyright (c) 2001,2004,2005 Scott Penrose. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.18.2 2005-06-25 Sys::Hostname::Long(3)