-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is Crontab working? #77
Comments
It should work. |
Hi @roleoroleo, |
Sorry. |
0.1.4 released. |
If I'm using the web interface to add a cronjob, only the minute value get saved. I used this example: Is saved in the text field: |
Sorry, I added a new bug in the last commit. |
Updated comment: Thank you! I have used: |
i wanted to add a second cronjob, when I save only the first entry is added.
|
You are right. |
Maybe I fixed it with this commit: |
Here it is: |
Is it maybe possible to update the crontab version? The @reboot function isn't working: This would allow to run scripts/binaries on boot, without changing anything of your code. And after a hack-upgrade these autostarts will still remain. |
This cron is part of the busybox. |
Thanks, your suggestion to the startup.sh helps me a lot :-) |
In yi-hack-5 I see the location of the reboot binary as /home/base/tools/reboot I am able to run it from ssh like that. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I would like to make a reboot every midnight by cron.
To do that I'm trying with:
0 0 * * * /tmp/sd/yi-hack/www/reboot.sh
0 0 * * * /sbin/reboot
But no one of those are working.
Doing that straight from SSH makes my camera reboot properly so i think that cron is not working as expected, is that possible?
Running "ps" i can't find the cron process working.
the "root" file where crons saves, updates properly after changing the config and reboot manually the camera, but cron never get executed.
Help please.
Another way to schedule a reboot?
The text was updated successfully, but these errors were encountered: