12-01-2011
Quote:
Originally Posted by
methyl
Lateral thought idea.
1) Create a cron which creates a flag file at 00:01 on the first day of every month.
2) Run your cron every Wednesday but have a wrapper to exit if the flag file does not exist. If the flag file does exist, delete the flag file and run the main process.
Cool!! Thank you very much. I will do that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
i have a scripts that update an SQL DATABASE using sqlplus command.
when i run it in a interactive mode its ok but when try to run it using the crontab i get an a messege :
"Must be attached to terminal for 'am I' option"
(there is no "who am i" command in the script)
and the DB... (4 Replies)
Discussion started by: dorilevy
4 Replies
2. Shell Programming and Scripting
Is there anyway to get the start time and end time / status of a crontab job which was just completed? Of course, we know the start time of the crontab job since we are scheduling. But I would like to know process start and time recorded somewhere or can be fetched from a command like 'ps'. ... (3 Replies)
Discussion started by: thambi
3 Replies
3. UNIX for Advanced & Expert Users
Hi experts,
need your helpo.
after editing the crontab while saving the file it says-
"/tmp/crontabRlaauT" 1 line, 77 characters
cron may not be running - call your system administrator
And i checked after certain time. script in cron is not running. I got a mail in user saying... (1 Reply)
Discussion started by: thepurple
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. Shell Programming and Scripting
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Discussion started by: Cvg
9 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
Here is my command which I've scheduled to be run from crontab, but it's giving error message: rah: rahhost executable needed but not in PATH
My cmd is-
36 10 * * * /opt/IBM/dwe/db2/V9.5/bin/rah "df -m" >> /db2home/bculinux/Files/log/db.out 2>&1
Though I've added path... (5 Replies)
Discussion started by: NARESH1302
5 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Discussion started by: yohasini
8 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Discussion started by: abhi_123
7 Replies
9. Shell Programming and Scripting
Hi experts,
Need your help to schedule the script(test.sh) bi-weekly in linux machine.
script need to run at every alernate thursday at 9 am .
Please help to run the same. (6 Replies)
Discussion started by: abhigrkist
6 Replies
10. Solaris
hi,
i have crontab where i have put my db backup scripts but crontab do not run at specific time. i have checkted the scripts andwhen run the script as ./mydbbkp.sh so it successfully run and do the job but from cron it is not running whihcmeans cron is not running. i have an oracle user under... (3 Replies)
Discussion started by: janakors
3 Replies
cron(8) System Manager's Manual cron(8)
NAME
cron - The system clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
The cron daemon runs shell commands at specified dates and times. Commands that are to run according to a regular or periodic schedule are
found within the crontab files. Commands that are to run once only are found within the at files. You submit crontab and at file entries
by using the crontab and at commands. Because the cron process exits only when killed or when the system stops, only one cron daemon
should exist on the system at any given time. Normally, you start the cron daemon from within a run command file.
During process initialization and when cron detects a change, it examines the crontab and at files. This strategy reduces the overhead of
checking for new or changed files at regularly scheduled intervals. The cron command creates a log of its activities. The cron daemon
must be started from the system startup scripts because it must begin execution without a login user ID set. The cron daemon starts each
job with the following process attributes stored with the job by the invoking process: Login user ID Effective and real user IDs Effective
and real group IDs Supplementary groups
It also establishes the following attributes from the authentication profile of the account associated with the login user ID of the invok-
ing process: Audit control and disposition masks Kernel authorizations
DIAGNOSTICS
The at and batch programs will refuse to accept jobs submitted from processes whose login user ID is different from the real user ID.
FILES
Specifies the command path. Main cron directory Directory containing the crontab files. List of allowed users. List of denied users His-
tory information for cron Queue description file for at, batch, and cron
RELATED INFORMATION
Commands: at(1), crontab(1), rc0(8), rc2(8), rc3(8)
Files: queuedefs(4) delim off
cron(8)