<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Making re-installing packages optional]]></title><description><![CDATA[<p dir="auto">From time to time I upgrade to a newer version on my pfsense, but each time I upgrade it removes all packages and then installs them again.<br />
This also happens after restoring a configuration file.</p>
<p dir="auto">Because some packages are crucial (siproxd,pfblocker) and some are necessary (zabbix) this significantly contributes to the downtime of this firewall.<br />
Especially ntop enhances this downtime. It takes more than 10 minutes to install.</p>
<p dir="auto">I also noticed that pfblocker turns off after each upgrade. This may be the fault of pfblocker.</p>
<p dir="auto">If this "repackaging" would be optional it would greatly help me and others.</p>
<p dir="auto">There's also a spare pfsense that I can turn on, but after turning this one on I need to load the latest configuration file and I will have another 15 minutes downtime which could have been 3….</p>
]]></description><link>https://forum.netgate.com/topic/49771/making-re-installing-packages-optional</link><generator>RSS for Node</generator><lastBuildDate>Sun, 19 Apr 2026 09:03:17 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/49771.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 26 Oct 2012 09:49:05 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Making re-installing packages optional on Tue, 30 Oct 2012 14:49:39 GMT]]></title><description><![CDATA[<p dir="auto">If downtime is that critical, you should be updating during a low-traffic or overnight maintenance window when it won't matter quite so much.</p>
<p dir="auto">A real hacky way to do this would be to install the shellcmd package and then add an earlyshellcmd to run</p>
<pre><code>/bin/rm /conf/needs_package_sync
</code></pre>
<p dir="auto">Which would remove the file that triggers the pkg reinstall.</p>
<p dir="auto">If something breaks in a package because of the upgrade though, you've only got yourself to blame. We reinstall them for a reason, as cmb mentioned.</p>
]]></description><link>https://forum.netgate.com/post/362157</link><guid isPermaLink="true">https://forum.netgate.com/post/362157</guid><dc:creator><![CDATA[jimp]]></dc:creator><pubDate>Tue, 30 Oct 2012 14:49:39 GMT</pubDate></item><item><title><![CDATA[Reply to Making re-installing packages optional on Fri, 26 Oct 2012 09:57:36 GMT]]></title><description><![CDATA[<p dir="auto">Well you can create a local pkg repository to reduce downtime.</p>
<p dir="auto">There is no way to guarantee that the package will work after the upgrade in general scope.</p>
]]></description><link>https://forum.netgate.com/post/361707</link><guid isPermaLink="true">https://forum.netgate.com/post/361707</guid><dc:creator><![CDATA[eri--]]></dc:creator><pubDate>Fri, 26 Oct 2012 09:57:36 GMT</pubDate></item></channel></rss>