Additions to Crontab Reverting

[Cybernut1]

As I said very early on, right in my second post…the ONLY way for you to solve this issue would be to bake-in your cron changes into the firmware’s source code. All these digging will give you clues and maybe even some answers but not the solution. I do think that would be your best solution in this case, since cron is wiping itself off. Having your own job right in the cron’s original list of jobs will keep your job running all the time even when the cron tab file gets reset every half hour or so. It is rather unfortunate that WD has implemented such a stupid solution for whatever they are trying to achieve by wiping cron itself. Gives very little room for our own solutions.