UNIX for Dummies Questions & Answers

I need your help please
Inin a production system i found crontab entries was removed because i typed crontab -l with username corasc and didn't show anything.
i asked the administrador to restored the mentioned crontab, he restored the crontab:
The problem is when restored the crontab file is not executing any entry:
What happenned:?
i checked up the /usr/lib/cron/cron.allow and the username corasc is included, also checkup the /usr/lib/cron/cron.deny and it doesn exist

i checked up the crontab file and permissions and:
ls -lrt /var/spool/cron/crontabs/corasc
-r-------- 1 root colombia 1072 Dec 4 02:50/var/spool/cron/crontabs/corasc
BEFORE BEING REMOVED THE CRONTAB, IT WAS WORKING, si i show you the crontab lines
corasc@altamira00 : corasc > crontab -l
#Logs maintainance
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/xa -name "*.trc" -mtime +2 -exec rm -f {} \; > /dev/null 2>&1
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/ULOG -name "ULOG." -mtime +2 -exec rm -f {} \; > /dev/null 2>&1
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/MAS "*.log" -mtime +2 -exec rm -f {} \; > /dev/null 2>&1

# Generacion Pines
00 2 * * * /export/app/CO/rasc/scr/lanza_generacion_pines.sh > /dev/null 2>&1

# Informes
0 3 1 * * /export/app/CO/rasc/scr/Informe_Tarjetas.ksh > /dev/null 2>&1
52 05 08 * * /export/app/CO/rasc/scr/Informe_Tarjetas.ksh > /export/app/CO/rasc/scr/log_Tarjetas.txt > /dev/null 2>&1
# Generacion de estadisticas
5 0 * * * /export/home/corasc/scripts/EstadisticasTUX.ksh > /export/app/CO/rasc/log/EstadisticasTUX.log > /dev/null 2>&1

I'd appreciate your help thanks

Have you rebooted the system or shut down cron and restarted it? That is required on the systems I use.

Hello -

On my system (Linux 2.6 kernel) you dont have to restart cron nor the system if you change an individual crontab.

First thing I would check is the local system mail for corasc. I think by default cron errs get mailed to the user. They also go to syslog by default, if you have access.

If you look at the man page for crontab it describes a certain bug:

BUGS
Although cron requires that each entry in a crontab end in a newline character, neither the crontab command nor the cron daemon will detect this error. Instead, the crontab will appear to load nor‐
mally. However, the command will never run. The best choice is to ensure that your crontab has a blank line at the end.


Might be your issue

yrs

Michael