We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
多个不同模块同时采用了本模块来实现定时任务,任务会出冲突/被覆盖掉嘛?
The text was updated successfully, but these errors were encountered:
busybox crontab -c "${cron_d_path}" -r 这个定时执行任务的需求比较大,有好多人是直接while true done循环。就是我希望这个模块进一步的修改,更简洁,更简单,方便内置到其他模块,并且不发生冲突。这就是我希望的,谢谢
Sorry, something went wrong.
看定时任务配置的路径 ${cron_d_path} ,-r是删一遍旧文件的, -c 监听完目录后我记得文件有变动好像会自动更新定时任务来着。
其他模块如果是集成在一起的,可以考虑只操作一次 crontab 命令,后续直接对 root 文件进行修改,要不就分不同目录使用。
crond才是那个能后台运行的,我试过通过无限创建crond进程能把手机卡死,第一次运行一个crond进程,一分钟后运行2个,crond进程数指数爆炸。过不了多久就会把手机卡死,然而crontab是单进程的,crontab才是用来刷新配置用的。完全可以运行多次crontab。但是crond只能运行一次,对于不同模块可能就是运行的不同crond进程,我认为这种不必要的开销是不合理的,还有可能有点模块开发者在运行自己的crond进程前会杀死已有的crond进程...
No branches or pull requests
多个不同模块同时采用了本模块来实现定时任务,任务会出冲突/被覆盖掉嘛?
The text was updated successfully, but these errors were encountered: