On Tue, May 30, 2023 at 07:57:12PM +0100, Aoife Moloney wrote: > https://fedoraproject.org/wiki/Changes/Automatic_Cloud_Reboot_On_Updates > == Summary == > Cloud users can provide cloud-init metadata when creating a Fedora > cloud instance and that metadata can contain instructions to update > all packages on the system and reboot the system if any of those > updated packages need a reboot to go into effect. Fedora cloud > instances should write the `/var/run/reboot-required` file if a reboot > is needed after a dnf update so that cloud-init can reboot the > instance. I'll add the same comment that I made in https://github.com/FrostyX/tracer/pull/196: The correct location is /run, not /var/run. In most cases, this doesn't matter greatly, because a compat symlink is provided, but when /var is a separate partition, /var/run would only be accessible if /var is mounted, i.e. rather late in boot. /run is always available. /var/run is a compat symlink that should not be used (esp. in new code). Stuff that is related to initial machine installation and such should not force /var to be mounted. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
