bug Cron on SCO 3.2

[gill1155]

Hi,

we've got a problem whith cron on OS 3.2 :

There's a shell (/etc/cleanup) starting at 05:17 and crash

the server. after testing, it seems that is the "17" whichi

is the problem. Does anybody know this bug ?

Thanks,

Gilles

 

[KenCunningham]

Gilles,

can you post the exact entry in your crontab, please? A copy of your /etc/cleanup might also provide clues.

Thanks.

 

[gill1155]

Here it is,

17 5 * * 0 /etc/cleanup > /dev/null
0 2 * * 0,4 /usr/lib/cron/logchecker
3 3 * * * /usr/lib/cleantmp > /dev/null
1 3 * * * /etc/setclk -rd1800 > /dev/null 2>&1
#5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A
0 4 * * 0 /etc/custom -V symlinks;# CUSTOM_SYMLINK_REPORT
0 0 * * 1-5 scosh cronsched -r
0 0 * * 1 scosh cronsched -wr

We have tested with different day, time and even command (on line in the crontab with find) but it's always the 17...
Strange, isn't it ?

Gilles

 

[DSMARWAY]

hi,
it could be that one of your other jobs are still running
and when your run clenatmp to remove temporary files in the specified directories , an application is using the file and can't cope so panics and crashes . we have sco 3.2 running cleantmp at 5:17 and the server does not crash.

have you tried commenting out the custom links and retrying
your cron job.

 

[gill1155]

Hi,

we did it, and now it's obvious that it's the "find" that
causes the crash. We don't know if it's a problem with the
command find or a problem in a directory ... We still keep on searching.

Thanks,

Gilles