02-22-2012
crontab job issues with export command
Hi all,
I have sevaral jbos with bunch of export commands like
export VARIABLE=value.
They work perfectly when I run manually but when I try to run from crontab it stops right at this export command.
But when I replace these export with these, crontab job works fine.
VARIABLE = value; export VARIABLE.
Is there a way to make crontab job work with the orginal way of exporting ( export VARIABLE=value). I have 100+ like this and don't want to send time modifying all these.
Thanks in advance.
mkneni
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have cornjob was scheduled at 1:00 AM everyday. It has been running fine since last Saturday. But it didn't run since Saturday. Because of daytime saving time change it didn't ran?
Please send me your thoughts.
Thanks in adavance.
Moe (3 Replies)
Discussion started by: Moe
3 Replies
2. Shell Programming and Scripting
Hi,
i need to schedule a script to run at 6.10AM everyday.I tried to do this way.
#!bin/ksh
10 06 * * 0-6
sh /tmp/ss/script/daily_file_check.sh
And at the command prompt I did
>crontab -e cron.txt
I'm not sure whether this is the right way.
Can anyone please tell me how to... (4 Replies)
Discussion started by: kumarsaravana_s
4 Replies
3. Shell Programming and Scripting
Hello Gurus,
I've been tasked with solving a problem at my new job and I'm stumped. We've got a script that dynamically builds an oracle export parameter files and then runs export from the shell. it runs fine when using the shell, but will NOT run (fails in one spot everytime) when entered... (1 Reply)
Discussion started by: jsheehan223
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
down here part of the scheduled job in crontab (AIX Version 5)
i have problem running jspPRE-ALL.
i verrify permissions and privileges (the others job are working good)
if i run the job in command line it work correctly
#
# Aggiornamento doni e continuity
00 02 * * 2-6... (5 Replies)
Discussion started by: ilpasta
5 Replies
5. Solaris
I am having some issues with my cronjobs not running in solaris 10.
Cron is running:
~> ps -ef | grep cron
root 202 1 0 Jul 18 ? 0:01 /usr/sbin/cron
bender 1646 1562 0 01:57:49 syscon 0:00 grep cron
crontab -l lists the cronjob and I *think* its in the... (8 Replies)
Discussion started by: ippy98
8 Replies
6. Shell Programming and Scripting
I would like to execute my script at 17.30 and 23.00 using crontab, could anybody help me out!!
Thanks in Advance!! (1 Reply)
Discussion started by: jatanig
1 Replies
7. Shell Programming and Scripting
I wrote a quick little script that will eventually end up as a cron job to export rrd files for my cacti server.
Here is the script:
#!/bin/bash
rm -rf /backup/cacti_xml/*
cd /var/www/html/rra
ls -1 *.rrd | awk '{print "rrdtool dump "$1" > /backup/cacti_xml/"$1".xml"}' | sh -x
Is there... (5 Replies)
Discussion started by: TheBigAmbulance
5 Replies
8. Shell Programming and Scripting
I have a ksh script that does the following
1. Script executes and creates an output file from a sql query
2. That output file is an input file to the script
3. generates an html file to email to DBA receipients
The following syntax works at the command line
... (1 Reply)
Discussion started by: JolietJake
1 Replies
9. SuSE
Hello,
This is my first posting in Linux world.
I have SLES 11.
I've created a file 'packdisk-scandisk.txt' file under /var/opt/Teradata/bteqdba.
The content of the file is,
cat /var/opt/Teradata/bteqdba/packdisk-scandisk.txt
output over /var/opt/Teradata/bteqdba/TAREAS_DBA.log... (2 Replies)
Discussion started by: JDBA
2 Replies
10. UNIX for Dummies Questions & Answers
hell all:
i am trying to test a crontab job for snmpwalk but it is not working:
here is crontab:
*/1 * * * * root /root/snmpwalk.sh
for the script, it is very simple:
#!/usr/local/bin/bash
/usr/local/bin/snmpwalk -v 2c -c public 100.10.10.10 (6 Replies)
Discussion started by: ipfreak
6 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