I’ve recently fixed numerous cron problems and it should work much better
now. The question, of course, is when the newer version will be released.
That I don’t have an answer for. The “cron stopped abnormally” error is
related to how cron and crontab speak to eachother. Cron sets up some
shared memory when it starts and puts it’s pid there. Then crontab can
send it a SIGHUP to get it to re-read the crontabs. For some reason, crontab
sometimes fails to attach the shared memory properly and thinks that cron
is not running. I believe this to be fixed now so hopefully the next release
will solve it. For now, you can try stopping and restarting cron to see if
Applications Mail Group <firstname.lastname@example.org> wrote:
Cron was ported to QNX6 and it had many wrinkles to iron out. These bugs are known and cron will be fixed in the near future.
Alain Bonnefoy <> email@example.com> > wrote:
It’s seems that cron works for some peoples.
It seems that cron works when it wants for some others.
Sure that cron doesn’t work at all for me!
root entries are never started and executing crontab for simple user
crontab: cron stopped abnormally
which is wrong, of course!
Does anybody have an explication?
“You’re bound to be unhappy if you optimize everything” - Donald Knuth