How does cron work:
according the doc, I created what is needed to start cron (I think),
without cron.allow, cron.deny first. So, only root can use crontab.
As root I’ve created an entry with crontab -e.
When I start cron, I get the following message
#cron -v &
#cron: ** started Tue …
cron: unauthorized crontab root
Then, I’ve created an empty cron.deny. So, everybody can create an
entry.
If I invoke crontab with any parameter, cpu usage goes to 100% and
doesn’t return!
Thanks,
Alain.
Er, we’re looking into some cron problems right now.
Did you run crontab as root? There was a packaging error
where it should be suid root.
Also, there was a build error in cron and crontab where
they use the old QNX4 style of /usr/spool/cron rather than
the new /var/spool/cron, so you should create a /usr/spool/cron
directory.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:
How does cron work:
according the doc, I created what is needed to start cron (I think),
without cron.allow, cron.deny first. So, only root can use crontab.
As root I’ve created an entry with crontab -e.
When I start cron, I get the following message
#cron -v &
#cron: ** started Tue …
cron: unauthorized crontab root
Then, I’ve created an empty cron.deny. So, everybody can create an
entry.
If I invoke crontab with any parameter, cpu usage goes to 100% and
doesn’t return!
Thanks,
Alain.
–
cburgess@qnx.com
Be careful !
We are using cron to make a backup everyday but we can see that the cron
doesn’t run everyday !
Colin Burgess a écrit dans le message <98lfvr$73o$1@nntp.qnx.com>…
Er, we’re looking into some cron problems right now.
Did you run crontab as root? There was a packaging error
where it should be suid root.
Also, there was a build error in cron and crontab where
they use the old QNX4 style of /usr/spool/cron rather than
the new /var/spool/cron, so you should create a /usr/spool/cron
directory.
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
How does cron work:
according the doc, I created what is needed to start cron (I think),
without cron.allow, cron.deny first. So, only root can use crontab.
As root I’ve created an entry with crontab -e.
When I start cron, I get the following message
#cron -v &
#cron: ** started Tue …
cron: unauthorized crontab root
Then, I’ve created an empty cron.deny. So, everybody can create an
entry.
If I invoke crontab with any parameter, cpu usage goes to 100% and
doesn’t return!
Thanks,
Alain.
\
cburgess@qnx.com
Colin Burgess a écrit :
Er, we’re looking into some cron problems right now.
Did you run crontab as root? There was a packaging error
where it should be suid root.
Yes, I tried, entries are created, but I always get:
cron: crontab update …
#cron: unauthorized crontab root
and the task are not started!
Also, there was a build error in cron and crontab where
they use the old QNX4 style of /usr/spool/cron rather than
the new /var/spool/cron, so you should create a /usr/spool/cron
directory.
it’s done yet!
–
cburgess@qnx.com
Have you tried adding root to cron.allow?
Yes, I tried, entries are created, but I always get:
cron: crontab update …
#cron: unauthorized crontab root
and the task are not started!
–
cburgess@qnx.com
Colin Burgess a écrit :
Have you tried adding root to cron.allow?
Yes, I tried, entries are created, but I always get:
cron: crontab update …
#cron: unauthorized crontab root
and the task are not started!
–
cburgess@qnx.com
Well, it seems ok with a cron.allow. humm… not in accordance with the
doc.
Anyway, it seems that the tasks are not allways started… not precise
infos at this moment.
Thanks,
Alain.