02-12-2020
Again, it important to use the full paths in cron scripts (especially crontab scripts run as root, but for any user). This is true for both executables and input / output files.
Please do not use relative paths.
Rewrite your scripts with full path names and make sure your cron userid has permissions to write / read from those directories.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
How to send send body along with attachment in a mail
given below is code to send mail with attachemnt.its working fine
but i need to send some message as body of the mail.
uuencode /prod/applc/ds_data/mac/working/nullctry.csv "nullctry.csv" | mailx -s "List Of Attendance"... (6 Replies)
Discussion started by: rajendragora
6 Replies
2. AIX
Hi,
How can I send mail attachments from shell script (AIX) and have a mail body as well ?
Thanks in advance. (1 Reply)
Discussion started by: shibajighosh
1 Replies
3. Shell Programming and Scripting
Hi,
i have a file ABC, i want to mail the contents of this file and i want to make the body of the mail per my choice like this:
Hi All,
This is the Report for today.
<Browse of the File ABC>
i am using :
mailx -s "Today's Report" abcd@xyz.com << EOT
Hi All,
This is... (1 Reply)
Discussion started by: Prat007
1 Replies
4. Shell Programming and Scripting
#!/bin/ksh
file="/pkgs/roots/scripts/ISQL_op.txt"
isql -H 11.11.11.111:1111 -U myUser -P myPwd -o $file << eof
go
select * from Table1
go
eof
my cron entry
00 08 03 11 * /pkgs/roots/scripts/testc.ksh
file permission of the script is correct, i have used absolute path everywhere.
... (2 Replies)
Discussion started by: vikram3.r
2 Replies
5. Shell Programming and Scripting
Hi,
I have ascript which drops a mail with the jobs status.
here is the script:
#!/bin/ksh
mypath=/home/gaddamja
flashlogpath=/sbcimp/dyn/data/flash/log
cd $mypath
v1=`ls -lrt | grep -i checkFilesForAmber_EUR1. |tail -1 | awk '{print $8}'`
v2=`cat $v1`
cd $flashlogpath
... (1 Reply)
Discussion started by: jagadish_gaddam
1 Replies
6. Shell Programming and Scripting
HI,
After giving the mail -e name@domain.com its asking the subject : after this its enter in to the body of the mail i.e. (in edit mode)
How to end this edit process to send mail ? (2 Replies)
Discussion started by: thelakbe
2 Replies
7. Shell Programming and Scripting
how to run a script using cron job and send the output as attachment via e-mail using unix. please help me.
how my cron job entry should be?
As of now my cron job entry is to run the script at specific time,
15 03 * * * /path/sample.sh | mail -s "Logs" email_id
In the above entry, what... (8 Replies)
Discussion started by: vidhyaS
8 Replies
8. Shell Programming and Scripting
Hello All,
I wish to mail after completion of code. I would like to include subject and body in it. I am not looking to read the body from other file but willing to provide the body in the command itself. Can i do this way?
I am looking to pass some parameters to body and this will be possible... (1 Reply)
Discussion started by: forums123456
1 Replies
9. UNIX for Advanced & Expert Users
hi,
while separated they produce the usual mail alert and i can see the output...
if i write into the php script:
<?php
system('php -f /var/www/vhosts/domain.com/httpdocs/folder/script1.php');
system('php -f /var/www/vhosts/domain.com/httpdocs/folder/script2.php');
system('php -f... (0 Replies)
Discussion started by: 7stars
0 Replies
10. Shell Programming and Scripting
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Discussion started by: a1_win
10 Replies
LEARN ABOUT MOJAVE
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD