09-05-2017
ever considered using at command?
The idea in your job execution, to do self execution by calling itself in 45 days using at...
I dp that sometimes...
This User Gave Thanks to vbe For This Post:
10 More Discussions You Might Find Interesting
1. Programming
i have shell script. when i run in normail mode..it run ok but when i use crontab command to set that program run in certain time it give an error.
error 'SQLPLUS cannot execute'
what the problem.i already set all the correct path and use both root and normal id but still cannot execute properly. (1 Reply)
Discussion started by: zikronz
1 Replies
2. Shell Programming and Scripting
Hi,
I need to execute a URL through crontab. Please could you help me to.
I need something like
15 0 * * * http://www.mysite.com/index.php.
Is it possible.
If not, how can I execute a script from another server..
Any help will be appritiatable.
Many thanks,
Nissar.P.K (2 Replies)
Discussion started by: nissar
2 Replies
3. UNIX for Dummies Questions & Answers
hello. we are porting over from HPUX Shell to Linux.
my default shell is bash so i can no longer schedule to execute a sh script in crontab.
can anyone pls help me out? I searched the site but didnt find any details.
thanks! (1 Reply)
Discussion started by: jigarlakhani
1 Replies
4. UNIX for Dummies Questions & Answers
Hi guys, my first post time here, so hello to everyone :)
I've got a problem running one of my scripts at work. I can get crontab working on simple scripts (i.e. one that just outputs date to a temp file). but it won't correctly execute the script i want to use.
My script is a PHP script. It... (6 Replies)
Discussion started by: renegadeice
6 Replies
5. HP-UX
Hi all,
I need to run a shell script every 6 days using crontab. I've been searching a bit and found the following syntax for this:
* * */6 * * /apps/temp/maxx.sh > /apps/temp/maxx.log 2>&1
respectively
* * 0/6 * * /apps/temp/maxx.sh > /apps/temp/maxx.log 2>&
Unfortunately when trying to... (8 Replies)
Discussion started by: Endo
8 Replies
6. UNIX for Advanced & Expert Users
Hi,
on AIX 6.1, I put in crontab ,execution of myscript. But it sends back the following error :
myscript.sh: rman: not found
And in myscript I have :
rman catalog rman/**@rep target / LOG=file.log << EOF
run
{
allocate channel t1 type disk;
.........
}
exit
EOF... (1 Reply)
Discussion started by: big123456
1 Replies
7. Red Hat
Dear!
I've 2 scripts backup Oracle database in crontab environment, however, I found they did not execute. The cron is here
$ crontab -l
30 2 * * 0 sh /cloudbck/level0/level0.sh
19 3 * * * sh /cloudbck/level1/level1.sh
Then, I tried to find how did they not run by looking up... (8 Replies)
Discussion started by: trantuananh24hg
8 Replies
8. Red Hat
Greetings/
I have a script listed in my roots crontab
07 9 * * * /opt/HLRSDATA_2010_OCT/HLRS_Scheduler_sp.sh > /opt/HLRSDATA_2010_OCT/logs/HLRTKJob.log
This script contains the following
#!/bin/bash
echo HLRSData Scheduler
cd /opt/HLRSDATA_2010_OCT
/usr/bin/java -Xms32m -Xmx1024m -cp... (6 Replies)
Discussion started by: RedSpyder
6 Replies
9. Shell Programming and Scripting
Dear All.
I have a scripts which does many task like house keeping, moving file to different location and loading the data into oracle.
I run this scripts daliy manually , I decided to put it into cron. I have put the scripts into crantab but the behaviour of the scripts have changed. it... (2 Replies)
Discussion started by: guddu_12
2 Replies
10. Shell Programming and Scripting
Hello All,
I have a crontab schedule and its executing a script that is calling another script and does not execute.
Crontab : ***** /test.sh
and in test.sh
/usr/local/file.sh
and in file.sh
webproxy -l 192.168.1.151
But when I run the script (test.sh) directly it works. But using... (1 Reply)
Discussion started by: Shaan_Shaan
1 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)