Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Oct 2020 20:36:10 -0700
From:      David Christensen <>
Subject:   Re: FreeBSD using swap even though there's a lot of free memory
Message-ID:  <>
In-Reply-To: <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail>
References:  <5f8d9d5e14b4c_dad82b12ba6585a44346f@sirportly-app-01.mail> <> <> <> <5f885b772d622_95aa2adab2b9c5b41576495c3@sirportly-app-02.mail> <5f8dad6c5225e_11f782aaeb993e5bc705b@sirportly-app-01.mail>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 2020-10-19 08:14, Twingly Customer Support wrote:

> The following are the updates that was installed last Friday, which seems to have solved the problem:
> New packages to be INSTALLED:
>      bash-completion: 2.11,2
>      glib: 2.66.0_1,1
>      postgresql12-client: 12.4
> Installed packages to be UPGRADED:
>      bash: 5.0.17 -> 5.0.18_3
>      ca_root_nss: 3.56 -> 3.57
>      fio: 3.20 -> 3.23

I'm glad the problem went away.  :-)

Updates and upgrades have broken my systems more times than I care to 
remember.  Now, I take an image of the system drive before upgrading a 
machine.  If an upgrade misbehaves, hopefully I will catch it quickly 
and can simply go back to the previous image.  Otherwise, I need to 
include backup/ restore of system configuration files and/or data when 

Perhaps you should consider setting up a staging/ testing environment, 
update/ upgrade that, and run tests.  If everything looks good, then 
upgrade the production environment.

The length of your 'pkg upgrade' output suggests that you might want to 
upgrade more frequently.  This should give you a smaller haystack to 
search if and when an upgrade causes problems.

All of the above might be facilitated with virtualization and/or automation.


Want to link to this message? Use this URL: <>