Actions
Feature #6411
closed
Classification if updates require a reboot
Status:
Closed
Priority:
Very Low
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
05/27/2016
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Description
Dear pfsense-developers,
i like your work to keep everything updated.
But would it be possible to classify if an update requires a reboot?
2.3.0_1 did not require a reboot (just a packet change)
2.3.1_1 does require one. (as the base package is changed)
Using HA this is usually no big deal, but on a standalone system
you may have unwanted downtime.
Updated by Jim Pingle over 5 years ago
- Category set to Upgrade
- Status changed from New to Closed
Upgrades that do not need a reboot are extremely rare, and the release announcement/upgrade notes will state whether or not it's required in that case.
Actions