cron arghhh!

QNX Newsgroups (Archives) qdn.public.qnxrtp.applications
1

In 6.0, cron didn’t work at all for me!
In 6.1, cron works too much for me!

The following crontab entry:
0 23 * * fri /root/adm/save_reps.sh

is supposed to execute the script every friday at 23:00.
This script creates two tar file; usr_local_$(date “+ %y%m%d”).tgz and
then home_$(date “+ %y%m%d”).tgz

This is what is really done:
home_010810.tgz 10/08/01 03:07
home_010811.tgz 11/08/01 08:20
home_010812.tgz 12/08/01 08:20
home_010813.tgz 13/08/01 08:21
home_010814.tgz 14/08/01 06:45
usr_local_010809.tgz 10/08/01 01:19
usr_local_010810.tgz 11/08/01 06:29
usr_local_010811.tgz 12/08/01 06:29
usr_local_010812.tgz 13/08/01 06:29
usr_local_010813.tgz 14/08/01 06:32


According to cron, everyday is Friday. So, I wonder why I still come to
work the day after!
These files are created on an NT server, I think that the date is the
date when the file has been closed.
For the first execution:
usr_local_010809.tgz may have been created at 23:00 and close at 01:19.
The second file has been created just after (!?), and at 3:00. a little
bit long but we can do better.

usr_local_010810.tgz may have been created at 23:00 and close at 06:29.
7 hours an half to make an archive of 480MB - about 17kb/s! The second
file has been created just after (!?), and closed at 8:20. 2 hours to
make an archive of 121MB!

On Friday at 23:00, in France, we sleep, drink beer, or have a diner, …
but we don’t work so, The 800 Mhz qrtp server can work quietly!

I’m going to try to create these files localy, just to see!

Alain.

2

Alain Bonnefoy wrote:

In 6.0, cron didn’t work at all for me!
In 6.1, cron works too much for me!

The following crontab entry:
0 23 * * fri /root/adm/save_reps.sh

According to the docs I see, day of the week is supposed to
be specified as a number between 0 and 6 with 0 being Sunday.
Hence instead of “fri” you should have “5”.

is supposed to execute the script every friday at 23:00.
This script creates two tar file; usr_local_$(date “+ %y%m%d”).tgz and
then home_$(date “+ %y%m%d”).tgz

This is what is really done:
home_010810.tgz 10/08/01 03:07
home_010811.tgz 11/08/01 08:20
home_010812.tgz 12/08/01 08:20
home_010813.tgz 13/08/01 08:21
home_010814.tgz 14/08/01 06:45
usr_local_010809.tgz 10/08/01 01:19
usr_local_010810.tgz 11/08/01 06:29
usr_local_010811.tgz 12/08/01 06:29
usr_local_010812.tgz 13/08/01 06:29
usr_local_010813.tgz 14/08/01 06:32

According to cron, everyday is Friday. So, I wonder why I still come to
work the day after!
These files are created on an NT server, I think that the date is the
date when the file has been closed.
For the first execution:
usr_local_010809.tgz may have been created at 23:00 and close at 01:19.
The second file has been created just after (!?), and at 3:00. a little
bit long but we can do better.

usr_local_010810.tgz may have been created at 23:00 and close at 06:29.
7 hours an half to make an archive of 480MB - about 17kb/s! The second
file has been created just after (!?), and closed at 8:20. 2 hours to
make an archive of 121MB!

On Friday at 23:00, in France, we sleep, drink beer, or have a diner, …
but we don’t work so, The 800 Mhz qrtp server can work quietly!

I’m going to try to create these files localy, just to see!

Alain.

3

Norton Allen a écrit :

Alain Bonnefoy wrote:

In 6.0, cron didn’t work at all for me!
In 6.1, cron works too much for me!

The following crontab entry:
0 23 * * fri /root/adm/save_reps.sh

According to the docs I see, day of the week is supposed to
be specified as a number between 0 and 6 with 0 being Sunday.
Hence instead of “fri” you should have “5”.

is supposed to execute the script every friday at 23:00.
This script creates two tar file; usr_local_$(date “+ %y%m%d”).tgz and
then home_$(date “+ %y%m%d”).tgz

This is what is really done:
home_010810.tgz 10/08/01 03:07
home_010811.tgz 11/08/01 08:20
home_010812.tgz 12/08/01 08:20
home_010813.tgz 13/08/01 08:21
home_010814.tgz 14/08/01 06:45
usr_local_010809.tgz 10/08/01 01:19
usr_local_010810.tgz 11/08/01 06:29
usr_local_010811.tgz 12/08/01 06:29
usr_local_010812.tgz 13/08/01 06:29
usr_local_010813.tgz 14/08/01 06:32

According to cron, everyday is Friday. So, I wonder why I still come to
work the day after!
These files are created on an NT server, I think that the date is the
date when the file has been closed.
For the first execution:
usr_local_010809.tgz may have been created at 23:00 and close at 01:19.
The second file has been created just after (!?), and at 3:00. a little
bit long but we can do better.

usr_local_010810.tgz may have been created at 23:00 and close at 06:29.
7 hours an half to make an archive of 480MB - about 17kb/s! The second
file has been created just after (!?), and closed at 8:20. 2 hours to
make an archive of 121MB!

On Friday at 23:00, in France, we sleep, drink beer, or have a diner, …
but we don’t work so, The 800 Mhz qrtp server can work quietly!

I’m going to try to create these files localy, just to see!

Alain.

Yes Norton, in fact it may depend on the cron’s version, but in our case, the
problem remains.

As I said, I tried to make the backups locally, and in this case, the date of
the files saved are 11:09 for usr_local_…tgz, so 9 minutes to write about
500 Mb (900 kb/s), much better! BUT, cron still executes this work every days
instead of every Friday!

Anyway, I don’t understand why it takes 7 hours to write a 500 MB file on a 10
MB/s ethernet lan ??

Thanks,
Alain.

4

Instead of “fri” in your cron configuration file, use “5”

Alain Bonnefoy wrote:

Norton Allen a écrit :

Alain Bonnefoy wrote:

In 6.0, cron didn’t work at all for me!
In 6.1, cron works too much for me!

The following crontab entry:
0 23 * * fri /root/adm/save_reps.sh

According to the docs I see, day of the week is supposed to
be specified as a number between 0 and 6 with 0 being Sunday.
Hence instead of “fri” you should have “5”.

is supposed to execute the script every friday at 23:00.
This script creates two tar file; usr_local_$(date “+ %y%m%d”).tgz and
then home_$(date “+ %y%m%d”).tgz

This is what is really done:
home_010810.tgz 10/08/01 03:07
home_010811.tgz 11/08/01 08:20
home_010812.tgz 12/08/01 08:20
home_010813.tgz 13/08/01 08:21
home_010814.tgz 14/08/01 06:45
usr_local_010809.tgz 10/08/01 01:19
usr_local_010810.tgz 11/08/01 06:29
usr_local_010811.tgz 12/08/01 06:29
usr_local_010812.tgz 13/08/01 06:29
usr_local_010813.tgz 14/08/01 06:32

According to cron, everyday is Friday. So, I wonder why I still come to
work the day after!
These files are created on an NT server, I think that the date is the
date when the file has been closed.
For the first execution:
usr_local_010809.tgz may have been created at 23:00 and close at 01:19.
The second file has been created just after (!?), and at 3:00. a little
bit long but we can do better.

usr_local_010810.tgz may have been created at 23:00 and close at 06:29.
7 hours an half to make an archive of 480MB - about 17kb/s! The second
file has been created just after (!?), and closed at 8:20. 2 hours to
make an archive of 121MB!

On Friday at 23:00, in France, we sleep, drink beer, or have a diner, …
but we don’t work so, The 800 Mhz qrtp server can work quietly!

I’m going to try to create these files localy, just to see!

Alain.

Yes Norton, in fact it may depend on the cron’s version, but in our case, the
problem remains.

As I said, I tried to make the backups locally, and in this case, the date of
the files saved are 11:09 for usr_local_…tgz, so 9 minutes to write about
500 Mb (900 kb/s), much better! BUT, cron still executes this work every days
instead of every Friday!

Anyway, I don’t understand why it takes 7 hours to write a 500 MB file on a 10
MB/s ethernet lan ??

Thanks,
Alain.