popcornmix
commented
5 years ago Does this file have any effect on a default install of raspbian? i.e. does it get automatically displayed somewhere?
Open dachshund-digital opened 5 years ago
popcornmix
commented
5 years ago Does this file have any effect on a default install of raspbian? i.e. does it get automatically displayed somewhere?
J0WI
commented
5 years ago It's used by various monitoring tools
dachshund-digital
commented
5 years ago I understand why it is set when set, the question is... should it be set when rpi-update runs... IMHO it should be set when a firmware update is actually done. Right now it is not set, so other than a text message on screen warning that the firmware requires a reboot, no notification is set. This is rather bad form. Monitoring tools can't tell if firmware is active or not because the standard notification method is not used, it is considered a standard for reboot notification, based on all the documentation I have reviewed thus far. So who or whom maintains rpi-update, please add this to the feature list.
popcornmix
commented
5 years ago It's used by various monitoring tools
More specifics would be useful.
rpi-update is designed for raspbian users. What affect does this file have on the standard preinstalled packages? What packages that are optionally installed does it have an effect on?
Now on Ubuntu, if I ssh in I see the contents of /var/run/reboot-required echoed back.
But on raspbian that doesn't occur.
lurch
commented
5 years ago Closely related to #263 ?
dachshund-digital
commented
5 years ago Close? No. Very different based on how I read 263. To which, 263 is asking for a way to have rpi-update invoke reboot automatically if the option is provided. What I am asking for is notification based, rpi-update provide proper notification a reboot is requried... not that rpi-update actually do the reboot its self.
Moreover, I found more details on what files should be created by rpi-update and what they should contain. The /var/run/reboot-required should be required when reboot is required, and it should just be a non-empty file, typically it has one line of text that reads "This system requires a reboot" or something to that effect. The /var/run/reboot-required.pkgs file should be created and its content I have explained below.
I would say they are similar, but now different given the additional information I found on this subject. The original issue I pointed out was that rpi-update does not follow the standard method for reboot required notification, and it really should. But there are actually two files that should be enerated:
1) /var/run/reboot-required... if the file exists at the given path, a reboot should be done. Many monitoring solutions leverage the existence of this file, as a notification or warning trigger. Node-Red, various monitoring tools, etc. leverage this.
2) /var/run/reboot-required.pkgs... if a file that is created and lists the packages installed, that require a reboot. So when rpi-update runs, and a reboot is required, not only is /var/run/reboot-required file created, but the /var/run/reboot-required.pkgs file is created, if it does not exist, and "rpi-update" should be in the file. If the file does exist already, than "rpi-update" should be appended at the end of file.
Clearly the first file is a trigger notification file. The second file provides detail on why the first exists. Most Linux distributions, including debian variants rely on these files as noted above.
Ruffio
commented
3 years ago It looks like this is a 'standard' feature for both Debian and Ubuntu:
https://www.cyberciti.biz/faq/how-to-find-out-if-my-ubuntudebian-linux-server-needs-a-reboot/
It would be a nice feature to get implemented if an update has sucessfully taken place IMHO.
It would seem like a good idea to set /var/run/reboot-required if a reboot is required, no? This would mirror the logic apt-get establishes.