I am having some problems with cron entries running when I am not expecting them to run. This is an ACID distribution and the crontab is set from the root account (crontab -l | crontab -e | etc.).
My crontab file looks like (with the questionable lines commented out). The starting comments were taken from a search for CENTOS 5 crontab man page. Just what am I missing??
···
#
# Fields - KF5VH
#
# minute - any integer from 0 to 59
# hour - any integer from 0 to 23
# day - any integer from 1 to 31 (must be a valid day if a month is specified)
# month - any integer from 1 to 12 (or the short name of the month such as jan or feb)
# dayofweek - any integer from 0 to 7, where 0 or 7 represents Sunday (or 3 letter name like Mon)
# command - the command to execute
#
*/5 * * * * /etc/asterisk/scripts/wxzip/Alert0
10,25,40,55 * * * * /etc/asterisk/SANITYBOOT/sanityboot
03 02 * * * /sbin/ntpdate pool.ntp.org >> /etc/asterisk/LOG/ntptimelog
# 07 00 * * 1 /etc/asterisk/scripts/WXA/oobuild 44
# 58 23 * * 1 /etc/asterisk/scripts/WXA/ooclear 50
# 07 00 * * 2 /etc/asterisk/scripts/WXA/oobuild 43
# 58 18 * * 2 /etc/asterisk/scripts/WXA/ooclear 50
# 06 00 1-7 * 4 /etc/asterisk/scripts/WXA/oobuild 46
# 58 18 1-7 * 4 /etc/asterisk/scripts/WXA/ooclear 50
The first two lines should run on Monday. The second two lines should run on Tuesday.
The last two lines should run on the first Thursday of each month.
Cron is running as documented, but it is not a good thing. Where all other time parameters are AND'ed, Day of Week and Day are OR'ed. So the elegant solution seems to be ...
Anyone think the source code should be changed?
...STeve - KF5VH
···
On 4/4/2016 12:57 PM, Steve Mahler wrote:
I am having some problems with cron entries running when I am not expecting them to run. This is an ACID distribution and the crontab is set from the root account (crontab -l | crontab -e | etc.).
My crontab file looks like (with the questionable lines commented out). The starting comments were taken from a search for CENTOS 5 crontab man page. Just what am I missing??
#
# Fields - KF5VH
#
# minute - any integer from 0 to 59
# hour - any integer from 0 to 23
# day - any integer from 1 to 31 (must be a valid day if a month is specified)
# month - any integer from 1 to 12 (or the short name of the month such as jan or feb)
# dayofweek - any integer from 0 to 7, where 0 or 7 represents Sunday (or 3 letter name like Mon)
# command - the command to execute
#
*/5 * * * * /etc/asterisk/scripts/wxzip/Alert0
10,25,40,55 * * * * /etc/asterisk/SANITYBOOT/sanityboot
03 02 * * * /sbin/ntpdate pool.ntp.org >> /etc/asterisk/LOG/ntptimelog
# 07 00 * * 1 /etc/asterisk/scripts/WXA/oobuild 44
# 58 23 * * 1 /etc/asterisk/scripts/WXA/ooclear 50
# 07 00 * * 2 /etc/asterisk/scripts/WXA/oobuild 43
# 58 18 * * 2 /etc/asterisk/scripts/WXA/ooclear 50
# 06 00 1-7 * 4 /etc/asterisk/scripts/WXA/oobuild 46
# 58 18 1-7 * 4 /etc/asterisk/scripts/WXA/ooclear 50
The first two lines should run on Monday. The second two lines should run on Tuesday.
The last two lines should run on the first Thursday of each month.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
You should be able to find the source to the version of cron and fix it. According to the allstarlink.org web site, ACID is "Old/Obsolete Distros (no longer supported)"
Steve
···
On 04/04/2016 09:14 PM, Steve Mahler wrote:
I'll answer my own question ...
Cron is running as documented, but it is not a good thing. Where all
other time parameters are AND'ed, Day of Week and Day are OR'ed. So
the elegant solution seems to be ...
Anyone think the source code should be changed?
...STeve - KF5VH
On 4/4/2016 12:57 PM, Steve Mahler wrote:
I am having some problems with cron entries running when I am not
expecting them to run. This is an ACID distribution and the crontab
is set from the root account (crontab -l | crontab -e | etc.).
My crontab file looks like (with the questionable lines commented
out). The starting comments were taken from a search for CENTOS 5
crontab man page. Just what am I missing??
#
# Fields - KF5VH
#
# minute - any integer from 0 to 59
# hour - any integer from 0 to 23
# day - any integer from 1 to 31 (must be a valid day if a month is
specified)
# month - any integer from 1 to 12 (or the short name of the month
such as jan or feb)
# dayofweek - any integer from 0 to 7, where 0 or 7 represents Sunday
(or 3 letter name like Mon)
# command - the command to execute
#
*/5 * * * * /etc/asterisk/scripts/wxzip/Alert0
10,25,40,55 * * * * /etc/asterisk/SANITYBOOT/sanityboot
03 02 * * * /sbin/ntpdate pool.ntp.org >>
/etc/asterisk/LOG/ntptimelog
# 07 00 * * 1 /etc/asterisk/scripts/WXA/oobuild 44
# 58 23 * * 1 /etc/asterisk/scripts/WXA/ooclear 50
# 07 00 * * 2 /etc/asterisk/scripts/WXA/oobuild 43
# 58 18 * * 2 /etc/asterisk/scripts/WXA/ooclear 50
# 06 00 1-7 * 4 /etc/asterisk/scripts/WXA/oobuild 46
# 58 18 1-7 * 4 /etc/asterisk/scripts/WXA/ooclear 50
The first two lines should run on Monday. The second two lines
should run on Tuesday.
The last two lines should run on the first Thursday of each month.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
down to the bottom of the page. Enter your email address and press
the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a
message to the list detailing the problem.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
down to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message
to the list detailing the problem.
--
"Anything is possible if you don't know what you are talking about."
1st Law of Logic
You should be able to find the source to the version of cron and fix it. According to the allstarlink.org web site, ACID is "Old/Obsolete Distros (no longer supported)"
Steve
On 04/04/2016 09:14 PM, Steve Mahler wrote:
I'll answer my own question ...
Cron is running as documented, but it is not a good thing. Where all
other time parameters are AND'ed, Day of Week and Day are OR'ed. So
the elegant solution seems to be ...
Anyone think the source code should be changed?
...STeve - KF5VH
On 4/4/2016 12:57 PM, Steve Mahler wrote:
I am having some problems with cron entries running when I am not
expecting them to run. This is an ACID distribution and the crontab
is set from the root account (crontab -l | crontab -e | etc.).
My crontab file looks like (with the questionable lines commented
out). The starting comments were taken from a search for CENTOS 5
crontab man page. Just what am I missing??
#
# Fields - KF5VH
#
# minute - any integer from 0 to 59
# hour - any integer from 0 to 23
# day - any integer from 1 to 31 (must be a valid day if a month is
specified)
# month - any integer from 1 to 12 (or the short name of the month
such as jan or feb)
# dayofweek - any integer from 0 to 7, where 0 or 7 represents Sunday
(or 3 letter name like Mon)
# command - the command to execute
#
*/5 * * * * /etc/asterisk/scripts/wxzip/Alert0
10,25,40,55 * * * * /etc/asterisk/SANITYBOOT/sanityboot
03 02 * * * /sbin/ntpdate pool.ntp.org >>
/etc/asterisk/LOG/ntptimelog
# 07 00 * * 1 /etc/asterisk/scripts/WXA/oobuild 44
# 58 23 * * 1 /etc/asterisk/scripts/WXA/ooclear 50
# 07 00 * * 2 /etc/asterisk/scripts/WXA/oobuild 43
# 58 18 * * 2 /etc/asterisk/scripts/WXA/ooclear 50
# 06 00 1-7 * 4 /etc/asterisk/scripts/WXA/oobuild 46
# 58 18 1-7 * 4 /etc/asterisk/scripts/WXA/ooclear 50
The first two lines should run on Monday. The second two lines
should run on Tuesday.
The last two lines should run on the first Thursday of each month.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
down to the bottom of the page. Enter your email address and press
the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a
message to the list detailing the problem.
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll
down to the bottom of the page. Enter your email address and press the
"Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email
confirmation. If you have trouble unsubscribing, please send a message
to the list detailing the problem.