Aside from the mechanics of doing this, the question I have would be why? If there is some stability issue, it's best to find the root-cause rather than just rebooting (which masks the problem, but doesn't fix it).
So, what is the reason you need to restart the service?
30 * * * * Every 30 minutes past every hour on every day.
*/30 * * * * Every consecutive 30 minutes past every hour on every day.
0,30 * * * * At the hour and every 30 minutes past every hour on every day.
Yes. When cron starts, this will restart stubby every 30 minutes ie. if cron is enabled/started at 04:10, it will run first at 04:40 then every 30 minutes after.
0,30 * * * * /etc/init.d/service stubby restart would run first at 05:00 then every 30 minutes after.
You can use logread -e cron to see when each cron job runs in syslog.
Put it in /etc/crontabs/root
First time you will need to issue: /etc/init.d/cron enable
Then start cron up: /etc/init.d/cron start OR
In LuCI: System/Scheduled Tasks
Paste it into the text box and Save
Go back to System/Startup - find cron and make sure it’s enabled then restart.
Now when you issue a logread -e cron you’ll see the syslog entries for cron.