Hi all together,
I had the same Issue like tristan but I found the following workaround.
First of all, thank you for your research. That saved me some of time.
I’ve got a Personal Cloud with firmware 2.21.126.
I tried to configure some jobs with editing the /usr/local/config/config.xml. That worked fine until I added more than one entry. With two or more custom entries the nas did not startup anymore. So I had to do the 40s-reset. After a while with try and error I found a workaround.
- on the web admin interface - create some dummy entries for internal backup. This will create a new entry <internal_backup> in /usr/local/config/config.xml
my config.xml now looked like this:
…
6 stime wd_crontab app_get_info recycle_bin_clear chk_wfs_download internal_backup random_check fw_available user_expire_chk ... 3 <1>0 <2>0 <3>* <4>* <5>* internal_backup -a test1 -c jobrun & 3 <1>0 <2>1 <3>* <4>* <5>* internal_backup -a test2 -c jobrun &
-
now you can abuse the entry <internal_backup> for your own job. You can delete the dummy backup-jobs via web interface. The tag <internal_backup> will remain in config.xml.
-
just add your own jobs by abusing <internal_backup>. It seems that’s some kind of special tag, that allows to add items without limit
-
restart