OK, so maybe I am completely misguided about how cron is supposed to work,
but I kind of thought it was supposed to launch one instance of a task at
the specified time. On my bottom-most entry I put a trace within the
/ub/1/.profile file that it is supposed to run and find over 100 instances
per second of a launch for each of the first 8 seconds of the matching time.
Any thoughts of best practices to get only one launch per cron entry?

Thanks,
Bill Watson
[EMAIL PROTECTED]

[EMAIL PROTECTED] ~]# crontab -l -u otto
#       @(#) root 90.1 00/05/01
#
# The Minute after the Hour is first
# The Hour to run on is second
# The third entry is the day of the month (1-31)
# The fourth entry is the month of the year (1-12)
# The Day of the week to run is fifth (0=sunday)
# The sixth entry is the program to run
#
00 20 * * * /ub/1/.profile 1>/ub/1/otto1.err 2>/ub/1/otto2.err
#
10 21 * * * /usr/bin/unibasic -f /ub/1/portallevict
11 21 * * * /usr/bin/unibasic -f /ub/1/portallevict
12 21 * * * /usr/bin/unibasic -f /ub/1/portallevict
13 21 * * * /usr/bin/unibasic -f /ub/1/portallevict
14 21 * * * /usr/bin/unibasic -f /ub/1/portallevict
#
30 21 * * * /ub/1/.profile 1>/ub/1/otto1.err 2>/ub/1/otto2.err
#
00 04 * * 1-5 /ub/1/.profile 1>/ub/1/otto1.err 2>/ub/1/otto2.err
#


_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to