The release notes actually says "The NTP service needs to be manually restarted under Status>Services afterwards". To me that implies that the old one keeps running, and you have to restart it for the new version to take effect. What in fact happens is that the old one is stopped, and no NTP service will be running until you start the new one.
Still doesn't address the bug I was experiencing - all package install/uninstalls fail, but actually do everything(?) they should. The only thing not done for me as far as I can tell is to change the version number to 2.3_1 ... but maybe that will change if I reboot the firewall. On Fri, May 6, 2016 at 8:04 AM, Oliver Hansen <[email protected]> wrote: > On May 6, 2016 6:01 AM, "Vick Khera" <[email protected]> wrote: > > > > On Thu, May 5, 2016 at 3:05 PM, Jim Thompson <[email protected]> wrote: > > > > > it’s documented that you need to (re)start NTP manually. > > > > > > > Where would one learn this? The update page doesn't say anything about > > "after applying this update, do XYZ". That would be the ideal place, IMO. > > I don't recall if there's a link from the update page but the release notes > have it which are in the usual place. https://blog.pfsense.org/?cat=53 > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
