/etc/crontabs/cron

**contevlad** · 10.12.2022, 06:26

Zitat von RickX

Yes, was a type, the correct name is /etc/cron/crontabs/root, but in post #1 the path is given as /etc/crontabs/cron

I used the following path, inside the root folder I inserted the strings but it doesn't work. /etc/cron/crontabs/root
Inside the root folder I put these strings:
30 * * * * /usr/bin/ntpdate-sync silent
00 05 * * * /usr/script/Reboot.sh
15 05 * * * /usr/script/Standby.sh
15 09 * * * /usr/script/RestartEmu.sh
45 17 * * * /usr/script/RestartEmu.sh
But it doesn't work.

**olwaldi** · 10.12.2022, 07:39

Hmm, I've just yesterday engaged successfully a new shell script to be run by cron, but I used "crontab -e" to edit root's crontab. Thus the modified crontab is loaded automatically into crond. Without that step maybe your changes are just ignored.

As a strategy my scripts create a datestamp within /tmp to see if my script really run, e.g. I use something like

Code:

#! /bin/bash
log=/tmp/SCRIPTNAME
date > $log

And maybe too simple: Check if your script after installation on your box works from command line.

Regards, Michael

**Pike_Bishop** · 10.12.2022, 18:23

Hi contevlad,

no it's not complicated, all you need to do for a first test is to delete your /etc/cron/crontabs/root, and then (you know telnet or ssh) establish a telnet or ssh connection to your box
and execute in telnet or ssh the following command;

Code:

(crontab -l 2>/dev/null; echo "0 5 * * * sh /usr/script/Reboot.sh") | crontab -

you can cut and paste the command from above into telnet or ssh and then press the enter button.
last, simply restart the box completely.

and if it works you do the same for your other scripts.

you write scripts or ? if yes then this isn't complicated.

regards
Pike

**contevlad** · 11.12.2022, 09:54

Zitat von Pike_Bishop

Hi contevlad,

no it's not complicated, all you need to do for a first test is to delete your /etc/cron/crontabs/root, and then (you know telnet or ssh) establish a telnet or ssh connection to your box
and execute in telnet or ssh the following command;

Code:

(crontab -l 2>/dev/null; echo "0 5 * * * sh /usr/script/Reboot.sh") | crontab -

you can cut and paste the command from above into telnet or ssh and then press the enter button.
last, simply restart the box completely.

and if it works you do the same for your other scripts.

you write scripts or ? if yes then this isn't complicated.

regards
Pike

Hi Pike
I have deleted /etc/cron/crontabs/root
Then via telnet I entered my decoder and gave this command of yours (crontab -l 2>/dev/null; echo "0 5 * * * sh /usr/script/Reboot.sh") | crontab - and I restarted the decoder then I followed your command changing time and Stanbay - restarEmu
I restarted everything, the permissions remained 600 did not change it.
But it doesn't work at the time it won't restart.
Inside the root folder here are the strings.
But they don't work
The root folder has permissions 600 maybe I have to change the permissions and if the set times are fine.
Thank you.
0 5 * * * sh /usr/script/Reboot.sh
15 5 * * * sh /usr/script/Standby.sh
15 9 * * * sh /usr/script/RestartEmu.sh
45 17 * * * sh /usr/script/RestartEmu.sh

**4l3x2k** · 11.12.2022, 10:16

Did you try to add these cron entries via the GUI?

/etc/crontabs/cron-1_0_1f_301_103_2114_eeee0000_0_0_0_20221211111203.jpg

If you do not have any special tasks in your reboot and standby scripts you may use the built-in power timer. Since 7.0 they allow exactly such things.

/etc/crontabs/cron-1_0_1f_301_103_2114_eeee0000_0_0_0_20221211111450.jpg

**contevlad** · 11.12.2022, 10:36

**el_malto** · 11.12.2022, 10:46

I don't know of Inunderstand you correctly or you have write it a little bit confused.

Zitat von contevlad

I have placed the following scripts inside the cron folder as path /etc/crontabs/cron

So your scripts are in the cron folder and not in /usr/script/?
You have to put your scripts in /usr/scripts/ as you have specified it.

I opened it with notepad and entered the following strings:
30 * * * * /usr/bin/ntpdate-sync silent
00 05 * * * /usr/script/Reboot.sh
15 05 * * * /usr/script/Standby.sh
15 09 * * * /usr/script/RestartEmu.sh
45 17 * * * /usr/script/RestartEmu.sh

**RickX** · 11.12.2022, 15:10

I think this is just a problem of language and technical terms...

The correct file name is ./etc/crontabs/root

Please note:

root is not a folder. This is a simple file containing some lines of text.
The file root doesn't need execute permissions. 600 is perfectly ok
The crontab should never be edited directly in the file. Use the crontab command instead.

You should add some diagnostic output to your shell scripts.
You can write date and time of every shcript execution into a log file, e.g. in /var/log.
If oyu execute the shell scripts manually from the command line, you can check, if the log lines are generated correctly.
Once this is done, you can check, if the crontab executes the shell scripts. In this case the log lines will be generated, too.

**contevlad** · 11.12.2022, 15:33

I know that root is not a folder. It is a simple file containing a few lines of text.
But it's strange that I can't execute commands via the command Menu' - Time - Cron Timer - green key add as soon as you compose the command crashes. Yet some other image all this procedure can be done by remote control and works great. because inside the image it has the scripts that you can enable and activate.
I also followed Pike's guide to the letter by inserting the string he sent me via telnet and then restarted the decoder then I go to check on the root I see that the command string was successful or /etc/cron/crontabs/root I get the following string inside the root 0 5 * * * sh /usr/script/Reboot.sh
but it doesn't work it doesn't reboot

**4l3x2k** · 11.12.2022, 19:07

Your scripts may be faulty.

You can check whether cron executed them by typing

Code:

grep -rin CROND /var/log/messages

You may post one of the scripts that is not working and the output of the command given above here.
Please set it in "code" to not flood the topic / post. You can also save it to a text file and attach it to a post.

Thema: /etc/crontabs/cron

Themen-Optionen

Anzeige

Stichworte

Lesezeichen

Lesezeichen

Berechtigungen