I’m trying to figure out why cron isn’t running my job.
I started cron with -v and got
cron: time 23:04:00, alarm 3361
cron: time 00:01:00, alarm 86341
Is alarm the number of second for the next job?
Is it possible to cron do display what it’s trying to run and from what file
it’s reading.
What I don’t understand is I have no job at 23:04:00.
What does ‘crontab -l’ give you? Are you starting cron with the -L option?
“Mario Charest” <nowheretobefound@8thdimension.com> wrote in message
news:cnvhin$3h2$1@inn.qnx.com…
I’m trying to figure out why cron isn’t running my job.
I started cron with -v and got
cron: time 23:04:00, alarm 3361
cron: time 00:01:00, alarm 86341
Is alarm the number of second for the next job?
Is it possible to cron do display what it’s trying to run and from what
file
it’s reading.
What I don’t understand is I have no job at 23:04:00.
“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:co2105$2cn$1@inn.qnx.com…
What does ‘crontab -l’ give you?
0 6 * * * (sh /u/mcharest//bin/auto_build)
Are you starting cron with the -L option?
Yes. What I don`t understand is this used to work, I even had the output of
auto_build in the mailbox, but now nada.
Last night there was a new ouput:
cron: time 00.01:0, alarm 86341
This makes sense. I`ll increas trace level tonigh to see which programs are
started trough the tracebuffer
“Mario Charest” <> nowheretobefound@8thdimension.com> > wrote in message
news:cnvhin$3h2$> 1@inn.qnx.com> …
I’m trying to figure out why cron isn’t running my job.
I started cron with -v and got
cron: time 23:04:00, alarm 3361
cron: time 00:01:00, alarm 86341
Is alarm the number of second for the next job?
Is it possible to cron do display what it’s trying to run and from what
file
it’s reading.
What I don’t understand is I have no job at 23:04:00.
\