SG3100 needs to reboot every few days after 2.4.4 upgrade
-
That is not unsupported. We pushed it out specifically to address the unbound memory leaks. It's perfectly fine to run it either way, whichever way works better for someone.
In fact if someone were to upgrade to 2.4.4 today, they'd automatically pull in the new version.
tl;dr: If you have problems with unbound eating memory, upgrade, don't suffer until -p1, even if it is coming soon.
-
@jimp said in SG3100 needs to reboot every few days after 2.4.4 upgrade:
That is not unsupported. We pushed it out specifically to address the unbound memory leaks. It's perfectly fine to run it either way, whichever way works better for someone.
In fact if someone were to upgrade to 2.4.4 today, they'd automatically pull in the new version.
tl;dr: If you have problems with unbound eating memory, upgrade, don't suffer until -p1, even if it is coming soon.
Ahhh ok, thank you
I was asking in the IRC channel about how "supported" the pkg update/pkg upgrade commands were. The feedback I got was that it would be an unsupported thing to do. Thank you for clarification! -
I could see how someone might think that, but in this case we put out some updates for a few issues that some had concerns about (unbound, strongSwan, curl, libssh) and if someone needs to, they can update by hand. We don't do that often, but in this case the issues warranted an OOB update of that nature.
