rsync updated
-
As every other OS out there : pfSense has also it's 'rsync' update.
Not, imho, an urgent update as pfSense is a firewall. It handles our IP traffic, and doesn't do 'file syncing between devices' out of the box.
rsync a pfSense / FreeBSD package and it's part of pfSense, so : console or SSH.
Console Menu Option 13) doesn't upgrade 'rsync'.
Use Console Menu Option 8) and then paste this commandpkg upgrade
like
[24.11-RELEASE][root@pfSense.bhf.tld]/root: pkg upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: rsync: 3.3.0 -> 3.4.0 [pfSense] Number of packages to be upgraded: 1 333 KiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching rsync-3.4.0.pkg: 100% 333 KiB 341.0kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading rsync from 3.3.0 to 3.4.0... [1/1] Extracting rsync-3.4.0: 100%
For info about the update, pick your favorite social media
-
I'm really unsure with package updates with pkg upgrade.
Was this not an issue in the past with pfSense updates...? -
Yes it was, potentially at least. Before 23.09 when a new version became available pfSense would set that as the default branch in order to show it as available to the user. This historically caused many problems when users didn't realise and installed or updated pkgs from the new branch before upgrading. However that no longer happens, users must now opt-in to the new branch before it is set.
But upgrading individual pkgs like rync in this case is generally safe from inside the same branch. -
@stephenw10
I don't know this, thanks.Is this also for 2.7.2 CE?
-
2.7.2 does include that functionality yes. It's the ability to check the current or any available repo for updates:
[2.7.2-RELEASE][admin@t70.stevew.lan]/root: pfSense-upgrade -h Usage: pfSense-upgrade [-46bdfhnRUy] [-l logfile] [-p socket] [-c|-u|[-i|-d] pkg_name] -4 - Force IPv4 -6 - Force IPv6 -b - Platform is booting -d - Turn on debug -f - Force package installation -h - Show this usage help -l logfile - Logfile path (defaults to /cf/conf/upgrade_log.txt) -n - Dry run -p socket - Write pkg progress to socket -R - Do not reboot (this can be dangerous) -U - Do not update repository information -y - Assume yes as the answer to any possible interaction The following parameters are mutually exclusive: -c - Check if update is available in the current repo -C - Check if upgrade is available in any of the available repos -i pkg_name - Install package PKG_NAME -r pkg_name - Remove package PKG_NAME -u - Update repository information
But 2.7.2 is latest version anyway so safe to upgrade rsync there.