Crontab and poweroff

[rospogrigio]

Hi guys, great site and great job with your 2.8 firmware.
I have a question: I have tried and succeeded in setting up a cron job at startup through this command:

Code: Select all

cronjob.sh "mycommand" "*/10" "*/1" "*" "*" "*" "RT_cmd_1" 

The job is set up correctly even after a reboot, but if I switch off and on the router then the job vanishes. Is there a way to make it persistent also after poweroff? Should I program the flash to achieve this? How risky is this procedure? And if I decide to take the risk, where can I find instructions to do this?

Thank you in advance, bye
rospogrigio

Edit: my router is a Roper Flynet ADSL2/2+ wireless, if this info can be of any help...

[hyperair]

How about this:

Code: Select all

setenv RT_cmd_1 'cronjob.sh "mycommand" "*/10" "*/1" "*" "*" "*" "RT_cmd_1" '

[rospogrigio]

How about this:

Code: Select all

setenv RT_cmd_1 'cronjob.sh "mycommand" "*/10" "*/1" "*" "*" "*" "RT_cmd_1" '

Wow, thx for the quick reply. I am at work now so I will try it later when I get back home. So it should be possible without writing the flash? I also found a script called "saveall.sh" which sends some commands to cm_cli : will it do the job? Anyway, I'll try everything later on...

[hyperair]

Actually setenv sets the bootloader environment variables, and this is always persistent. saveall.sh is for stuff like your wireless configuration, DSL configuration, and whatnot.

RT_cmd_1 is basically one of the environment variables that the Routertech firmware checks when starting up, and runs any commands stored in it. Hence, if you stick a command there, it will be run when the firmware loads.

[rospogrigio]

RT_cmd_1 is basically one of the environment variables that the Routertech firmware checks when starting up, and runs any commands stored in it. Hence, if you stick a command there, it will be run when the firmware loads.

I see. Is there any difference between setting the command on autoexec.sh rather than RT_cmd_1 ? Because actually my first try was using autoexec.sh and it was not persistent. I'll see if RT_cmd_1 works...

[rospogrigio]

OK, it seems to be persistent! (don't know the problem with autoexec.sh though) Thanks everybody for the help!

[hyperair]

Hmm I'm not sure really. I thought it was the same. I'd experiment with my router, but it's a few hundred miles away.

[mstombs]

You shouldn't need the leading RT_cmd_1 for this because the router will notice the "sh" in the cronjob.sh entry.

autoexec.sh waits until the WAN is connected before running - useful for things that need an external Internet connection.

RT_cmd_x run straight after the main router initialization code, RT_init_x ones run before.

When multiple commands exist in the environment they will be executed in alphabetical order, not necessarily the order they appear in the env listing.

[thechief]

Hi guys, great site and great job with your 2.8 firmware.
I have a question: I have tried and succeeded in setting up a cron job at startup through this command:

Code: Select all

cronjob.sh "mycommand" "*/10" "*/1" "*" "*" "*" "RT_cmd_1" 

The job is set up correctly even after a reboot, but if I switch off and on the router then the job vanishes. Is there a way to make it persistent also after poweroff? Should I program the flash to achieve this? How risky is this procedure? And if I decide to take the risk, where can I find instructions to do this?

Thank you in advance, bye
rospogrigio

Edit: my router is a Roper Flynet ADSL2/2+ wireless, if this info can be of any help...

The syntax you are using is for is cronjob-env.sh. Change cronjob.sh to cronjob-env.sh in that command, and you will have all you want.