there has been some discussions about cron on qnx6.
is cron still broken on qnx 6.2? I can “crontab -e” to add
59 20 * * * /tmp/test.sh
and save it.
now, date command shows:
Wed Nov 13 20:57:58 MST 2002
so I wait until it passed 20:59, but my “test.sh” never gets
executed. Am I doing something wrong?
If I change the above to
Frank
if my test, my “test.sh” is in a deep directory.
/very/long/path/to/test.sh
I just found the line
59 20 * * * /very/long/path/to/test.sh
is more than 125 characters, which seems to be a magic number.
when I changed to
you are raising the filename length for the upcoming qnx 6.2.1,
so hopefully you will increase this crontab line length to
something like 255 or 1024. ou might want to check those
open source cron to see what they use.
frank
liug <liug@mama.indstate.edu> wrote:
there has been some discussions about cron on qnx6.
is cron still broken on qnx 6.2? I can “crontab -e” to add
59 20 * * * /tmp/test.sh
and save it.
now, date command shows:
Wed Nov 13 20:57:58 MST 2002so I wait until it passed 20:59, but my “test.sh” never gets
executed. Am I doing something wrong?If I change the above to
- /tmp/test.sh
it works on every minute, as expected.
it seems cron works this time.Frank
Kris,
you there?
maybe you can change this?
cron.h:#define TAB_BUFFER_SIZE 127
I looked at /usr/include/limits.h, there is a
#define PATH_MAX 1024
the crontab line probably should be even bigger than that, given
that there are some extra stuff (* * * * *) before the path.
also, since “cron” is a daemon, you should probably log the error
in a better way than using stderr 
Frank
liug <liug@mama.indstate.edu> wrote:
if my test, my “test.sh” is in a deep directory.
/very/long/path/to/test.sh
I just found the line
59 20 * * * /very/long/path/to/test.sh
is more than 125 characters, which seems to be a magic number.
when I changed to
- /very/long/path/to/test.sh
it made the line shorter as you can see. it happened to bring
the line <= 125, and it worked!you are raising the filename length for the upcoming qnx 6.2.1,
so hopefully you will increase this crontab line length to
something like 255 or 1024. ou might want to check those
open source cron to see what they use.frank
liug <> liug@mama.indstate.edu> > wrote:
there has been some discussions about cron on qnx6.
is cron still broken on qnx 6.2? I can “crontab -e” to add
59 20 * * * /tmp/test.sh
and save it.
now, date command shows:
Wed Nov 13 20:57:58 MST 2002so I wait until it passed 20:59, but my “test.sh” never gets
executed. Am I doing something wrong?If I change the above to
- /tmp/test.sh
it works on every minute, as expected.
it seems cron works this time.Frank
Sorry Frank, didn’t mean to ignore you. Yes you’re right. This is kind of
a dorky limitation and should be fixed. I’ll file a PR for it and see if I
can get it into 6.2.1 (which freezes for beta today so I might not be able
to 
cheers,
Kris
“liug” <liug@mama.indstate.edu> wrote in message
news:ar1vs8$67o$1@inn.qnx.com…
Kris,
you there?
maybe you can change this?
cron.h:#define TAB_BUFFER_SIZE 127I looked at /usr/include/limits.h, there is a
#define PATH_MAX 1024
the crontab line probably should be even bigger than that, given
that there are some extra stuff (* * * * *) before the path.also, since “cron” is a daemon, you should probably log the error
in a better way than using stderr >Frank
liug <> liug@mama.indstate.edu> > wrote:
if my test, my “test.sh” is in a deep directory.
/very/long/path/to/test.sh
I just found the line
59 20 * * * /very/long/path/to/test.sh
is more than 125 characters, which seems to be a magic number.
when I changed to
- /very/long/path/to/test.sh
it made the line shorter as you can see. it happened to bring
the line <= 125, and it worked!you are raising the filename length for the upcoming qnx 6.2.1,
so hopefully you will increase this crontab line length to
something like 255 or 1024. ou might want to check those
open source cron to see what they use.frank
liug <> liug@mama.indstate.edu> > wrote:
there has been some discussions about cron on qnx6.
is cron still broken on qnx 6.2? I can “crontab -e” to add
59 20 * * * /tmp/test.sh
and save it.
now, date command shows:
Wed Nov 13 20:57:58 MST 2002so I wait until it passed 20:59, but my “test.sh” never gets
executed. Am I doing something wrong?If I change the above to
- /tmp/test.sh
it works on every minute, as expected.
it seems cron works this time.Frank
Test reply…did my earlier reply show up?
Kris
“liug” <liug@mama.indstate.edu> wrote in message
news:ar1vs8$67o$1@inn.qnx.com…
Kris,
you there?
maybe you can change this?
cron.h:#define TAB_BUFFER_SIZE 127I looked at /usr/include/limits.h, there is a
#define PATH_MAX 1024
the crontab line probably should be even bigger than that, given
that there are some extra stuff (* * * * *) before the path.also, since “cron” is a daemon, you should probably log the error
in a better way than using stderr >Frank
liug <> liug@mama.indstate.edu> > wrote:
if my test, my “test.sh” is in a deep directory.
/very/long/path/to/test.sh
I just found the line
59 20 * * * /very/long/path/to/test.sh
is more than 125 characters, which seems to be a magic number.
when I changed to
- /very/long/path/to/test.sh
it made the line shorter as you can see. it happened to bring
the line <= 125, and it worked!you are raising the filename length for the upcoming qnx 6.2.1,
so hopefully you will increase this crontab line length to
something like 255 or 1024. ou might want to check those
open source cron to see what they use.frank
liug <> liug@mama.indstate.edu> > wrote:
there has been some discussions about cron on qnx6.
is cron still broken on qnx 6.2? I can “crontab -e” to add
59 20 * * * /tmp/test.sh
and save it.
now, date command shows:
Wed Nov 13 20:57:58 MST 2002so I wait until it passed 20:59, but my “test.sh” never gets
executed. Am I doing something wrong?If I change the above to
- /tmp/test.sh
it works on every minute, as expected.
it seems cron works this time.Frank