04-05-2006
setting up cron job for month end week report
Hi all,
Needs your help in scheduling a cron job for the below mentioned requirement. Just let me know if anybody has a similar job running as mentioned below:
Month end reports - Report of all items created in a parent table that were created during the week.
Presently this report runs every saturday as part of cron
20 03 * * 6 $HOME/job/weekly_logs.sh > $HOME/log/weekly_logs.log
Requirement:
In case month end(30 or 31) falls any day other than Friday/Saturday, we might have to run adhoc report to get models created from last run Saturday till 31st.
We need to automate this adhoc running - From the last run date(saturday) till month end(we can run <1st of next month)
Regards,
Bhups
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Is it possible to use cron to schedule a job that will run the first 3 Sunday's during a month in addition to the last day of the month? (3 Replies)
Discussion started by: cpete
3 Replies
2. UNIX for Dummies Questions & Answers
Dear all
How can I schedule the cronjob to be run sometime at every first Sunday at every month? I have the edit the cronjob every month now, thanks (2 Replies)
Discussion started by: shanemcmahon
2 Replies
3. UNIX for Dummies Questions & Answers
Hello,
it is possible to setup two cron jobs to run at different frequencies?
I have a cron job which runs from monday -friday every 5 mins .I also want to have one more cron job which runs on a sunday..
It it possible to have?
Thanks (5 Replies)
Discussion started by: valluvan
5 Replies
4. Shell Programming and Scripting
I am running AIX 5.3 with the default shell as ksh.
I would like to know how to run a cron job on this system the last calendar day of the month. I found an example, but, I'm not sure if it will work with AIX and ksh...
02 16 * * * && /home/user/job-eom.kshI also need to be able to run a... (2 Replies)
Discussion started by: jthompson333
2 Replies
5. UNIX for Advanced & Expert Users
my colleague was asking about this:
is there a way to run a cron job biweekly, like a script five.sh
to run every *OTHER* Friday within November
its part about every other Friday we cant find any documentation.
thx
L (8 Replies)
Discussion started by: lydiaflamp
8 Replies
6. Shell Programming and Scripting
Hello,
basically I'm looking after a way of showing how many time is left to the end the day, week, month...
I can't seem to figure this out, so could one of you skilled guys tell me how should this be approached?
Examples:
Time left:
Day: 12h 12m 11s
Week: 4d 12h 12m 11s
Month:... (4 Replies)
Discussion started by: TehOne
4 Replies
7. Shell Programming and Scripting
I needed a cron job to run on the second to last friday of every month. Our servers are running HP-UX, and the HP-UX date command is pretty basic and does not have all of the fancy options that Linux date command does, and it does not have the ability at all to return future dates. So I had to... (0 Replies)
Discussion started by: lupin..the..3rd
0 Replies
8. Shell Programming and Scripting
Hello,
I'm on FreeBSD 8.2-STABLE shell and I was trying the following cron entry for end of month:
59 23 * * * && /home/user/eomt.sh >/dev/null 2>&1
I get the following error
Subject: Cron <user@shell>
eomt.sh contains the following codes
#!/bin/sh
rm /home/user/tst/logs/* &&... (9 Replies)
Discussion started by: user`
9 Replies
9. UNIX for Dummies Questions & Answers
Hi Expert
Please help me to set a cron job schedule,
Ihave a job that run every 3rd Friday of the month at 1030am.
I tried to set up like this, but the job still runs every friday at 1030am.
I want the job to run every 3rd Friday of the month at 1030am only
30 10 15,16,17,18,19,20,21... (2 Replies)
Discussion started by: kaibiganmi
2 Replies
10. AIX
Hi,
Actually scheduled my test scripts on test severs as shown below. They are supposed to run on 3rd sunday of every month.
Unfortunately it ran on 2nd sunday of the month (suspecting that it will run every sunday). I am sorry if I miss something. Could you please let me know if I did any... (1 Reply)
Discussion started by: System Admin 77
1 Replies
LEARN ABOUT HPUX
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and crontab
SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
[njob[nice[nwait
The fields in this line are:
q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by
(see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined
queues.
njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see
cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed
by setting the variable to 1 in the file.
nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). The default
value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that
job's queue, or because more than 100 jobs were running in all the queues (see njob above).
EXAMPLES
Consider the following file:
The file is interpreted as follows:
The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of
1.
Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds
before trying again to run it (see cron(1M)).
The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2.
If a job cannot be run because too many other jobs are running, will wait 90 seconds before trying again to run it.
All other queues can have up to 100 jobs running simultaneously. They will be run with a value of 2, and if a job cannot be run because
too many other jobs are running, will wait 60 seconds before trying again to run it.
SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4).
STANDARDS CONFORMANCE
queuedefs(4)