Different Crontab results on Sheeva and DC01

[Billy]

I get/got different results when calling the same perl script via crontab on Sheeva and DC01.
Im calling a perl script via Crontab

10 0 1 * * /usr/bin/perl /data/month/monpar.pl

The idea is getting every 1st of month a packet of parameters.

On sheeva I get the result as expected 1st of month at 00:10:17 eg. Sept. 01 at 00:10:17
On DC01 I get the result the month before at 20:40 eg. Aug. 31 at 20:40

The time settings seems to be correct! (for me)

It's tested to be ok on different sheevas.

Someone an idea? (maybe Boris)

Regards Billy

[Bjarne]

Hi Billy,

I also do have a DC01 and I also have the strange crontab issues.

Running this command

0 0-23/1 * * * /bin/date >> /tmp/date2.txt

I get this result

Sun Dec 16 19:30:02 CET 2012
Sun Dec 16 20:30:02 CET 2012
Sun Dec 16 21:30:01 CET 2012
Sun Dec 16 22:30:01 CET 2012
Sun Dec 16 23:30:02 CET 2012

Even this entry in the crontab did not fix it.

0 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23 * * * /bin/date
>> /tmp/date3.txt

Do you have found a solution meanwhile?

Regards,
Michael

[Billy]

Hi Michael,
I didn't found a solution yet.
But I was in contact with Boris regarding this problem.
It might be helpful that you have a problem with the crontab too to find a final solution.

Regards Billy

[wfpost]

normally it isn´t needed, because crontab should run in the su context, but have you tried using the available user option ?? >>> root

# m h dom mon dow user command
17 * * * * root run-parts --report /etc/cron.hourly

[Bjarne]

I tried it with the "root" call in front of the process to be executed - and it worked 3 times (interval 1 hour)! Then the process was not launched again ...
It's more than strange .....