-
Notifications
You must be signed in to change notification settings - Fork 29
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
Should all the greenboot-* systemd services be enabled? #91
Comments
No, those are only triggered when a health check fails and handle the reboot/rollback of your system. |
mmm, are you sure? Because if I leave them disabled (I was performing some test on Fedora Silverblue), greenboot doesn't work as described. |
Because IoT enables them in the IoT presets: /usr/lib/systemd/system-preset/80-iot.preset |
So in a system without such presets, they should be manually enabled? |
Not all, just the ones specified in the presets. |
Yes. |
@alcir all the greenboot-* services present in It does looks like |
Enable other services, as per 80-iot.preset #91
https://src.fedoraproject.org/rpms/fedora-release/pull-request/245 Thank you all. |
Enable greenboot-loading-message.service as per fedora-iot/greenboot#91 (comment)
greenboot/README.md
Line 36 in 650ce77
Do
greenboot-rpm-ostree-grub2-check-fallback greenboot-grub2-set-counter redboot-task-runner redboot-auto-reboot
should be enabled as well?The text was updated successfully, but these errors were encountered: