05-16-2007
Thanks for suggestions. Actually , my crontab looks like as follows
00 18 * * 1-6 kdshell/remove_flag_files 1>kdlog/remove_flag_files_`date|awk '{print $2 $3 $4}'`.log 2>&1
They are already redirect the log information into a log file. This is stable existing system. I don't want to touch the script , Moreover , our client won't allow us to touch crontab script at all. So I wanted to know any other possibility without touch existing script. I think this is reason some organzation are going for Autosys or Control-M sechudling tool whould would show the start time and end time of the job in the their logs.
-Thambi
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm writing a script and have become stuck trying to define a variable (COMP) by adding an elapsed time (ELAPSE e.g 00:55) to a start time (START e.g 23:50).
Can anybody give me a solution as to how I can get a completion time in hh:mm from the variables above?
thanks
Richard (4 Replies)
Discussion started by: rik1551
4 Replies
2. Shell Programming and Scripting
Hello All,
Below mentioned is my log file.
I want to make a script which ask for start time and then end time and then search particular word between those lines.
Like
start time:2
end time: 4
and then search all values starting from cell 84 between this time.
Please Help
... (2 Replies)
Discussion started by: wakhan
2 Replies
3. Shell Programming and Scripting
Hi,
Can anyone help me how can I get the line that between the start time and end time.
file1.txt
15/03/2009 20:45:03 Request: - Data of this line
15/03/2009 20:45:12 Response: - Data of this line
15/03/2009 22:10:40 Request: - Data of this line
15/03/2009 22:10:42 Response: - Data of... (1 Reply)
Discussion started by: tanit
1 Replies
4. Shell Programming and Scripting
Hey!
I'm working on a script that will add a user, create some configfiles, and add a crontab for the user.
The crontab looks like the following:
@reboot /home/user/program config.conf &
I would like for this process to start at the end of my script under the corresponding username by... (0 Replies)
Discussion started by: noratx
0 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
Can we get to know the start time and end time of execution of a script? (This script doesn't write any logs.) I mean, is there any built in process logs to track these records? (2 Replies)
Discussion started by: siba.s.nayak
2 Replies
6. Shell Programming and Scripting
Hello All,
I have a problem calculating the time difference between start and end timings...!
the timings are given by 24hr format..
Start Date : 08/05/10 12:55
End Date : 08/09/10 06:50
above values are in mm/dd/yy hh:mm format.
Now the thing is, 7th(08/07/10) and... (16 Replies)
Discussion started by: smarty86
16 Replies
7. UNIX for Dummies Questions & Answers
Hi guys,
How can I specify the start and end time of a cron job. And my start time and end time are specified by minutes. For example, I want to set up a cron runs every 3 minutes from 18:40 to midnight. How can i do this please? Many thanks
Best regards,
Clu (4 Replies)
Discussion started by: clu
4 Replies
8. Shell Programming and Scripting
Oracle Enterprise Linux
We want to track how long a process takes to complete its execution. This is what we want in the schell script
Before the process is started , get the time with date, hours and minutes
execute the process
After the process has ended , get the time with date,... (5 Replies)
Discussion started by: omega3
5 Replies
9. Programming
Dear team
I am using DB2 and wish to capture the ETL status on daily basis so that i can run the query and share the details in xls format to respective mail ids .
Currently i am using below query but this displays table name and counts for latest run.
select name ,CARD from... (0 Replies)
Discussion started by: Perlbaby
0 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable
in the crontab, if such exists).
Additionally, cron checks each minute to see if its spool directory's modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time on all crontabs and reload those which have changed. Thus cron need not
be restarted whenever a crontab file is modified. Note that the crontab(1) command updates the modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD