I've been using a simple script to update my pi, which I manually start (whenever I remember!!) Would it be safe to add a cron job to run it weekly automatically in the middle of the night, or should the update/upgrade/clean commands always be monitored in the console? #!/bin/bash apt update && ap…

To be honest, I never do upgrades on my pi's if the system is running well. I think this stems from not having used windows for almost 20 years and not feeling the need to upgrade that windows users have instilled in them. [edit] This is not a criticism of anyone who needs to upgrade often due to …

On my Pi3, I run webmin which auto-updates everything, never had an issue. On my older Pi2, I just occasionally log in and manually update, no real reason why I couldn't do a script, just never got round to it. So I'd say that, unless you have something exotic installed, an auto-update would be fi…

I agree with @ghayne that this is probably not a good idea on a 'production' system as you can never be 100% certain that an upgrade will not break things. For example an unexpected power failure in the middle of updates can make the system unbootable. However, if you do want automatic updates the…

I don't actually think that the decision is as clear-cut any more. You have to balance the risk of breaking something against the risk of compromise due to slow patching. Indeed some organisations have started auto-updating even servers, auto-updates on end user devices is certainly getting very com…

[image] Colin: you can never be 100% certain that an upgrade will not break things. For example an unexpected power failure in the middle of updates can make the system unbootable. That is always a worry, but surely that would still occur even if the upgrade was being monitored?

[image] Paul-Reed: surely that would still occur even if the upgrade was being monitored Possible, certainly, but for example if there were a threat of thunderstorms then one would probably not start the updates running, whereas automatic updates would run regardless. Also one might make sur…

@TotallyInformation good points.

Upon balance, I've decided to add the script to a cron job to run it 2.10am every Tuesday, and direct the output to /var/log/syslog so I can log & review it's actions. 10 2 * * 2 root /home/pi/scripts/update_pi.sh 2>&1 | logger -t update_pi_script I think @TotallyInformation put forward a…

Out of interest, why did you reject UnattendedUpgrades which is supposedly designed for the task?

I certainly haven't discounted Unattended Upgrades, but was initially off-put by it's size & complexity . It's much more comprehensive, and handles 'reboot requests', 'files not available', and many more edge cases. I will probably progress from using the bash script to use Unattended Upgrades, but…

Node-RED

Node-RED Forum

Scheduling raspbian OS updates & upgrades

General

Paul-Reed 19 February 2020 20:53 15

I've created a new thread especialy for unattended-upgrades

Topic		Replies	Views
Unattended Upgrades - auto update OS Share Your Projects	3	4602	21 February 2020
To update or not to update General	11	864	21 March 2020
Raspbian install script vs. "add software" for node-red? General	4	657	3 September 2018
Make a backup BEFORE upgrading General	15	644	9 April 2021
Updating from NR v0.20.5 to latest version in a Pi: Anything to worry about? General	17	843	22 January 2022

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Scheduling raspbian OS updates & upgrades

Related topics