freebsd-update fetch does not say that my version 13.2 is soon out of date

Hi, the output of the commands on my server gives me:

Code:
# freebsd-version -kru
13.2-RELEASE-p11
13.2-RELEASE-p11
13.2-RELEASE-p11

# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.2-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssh/sshd_config

No updates needed to update system to 13.2-RELEASE-p11.

Why does freebsd-update fetch not indicate near end of support for version 13.2 ?

Thanks in advance.
 
Hi, the output of the commands on my server gives me:

Code:
# freebsd-version -kru
13.2-RELEASE-p11
13.2-RELEASE-p11
13.2-RELEASE-p11

# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.2-RELEASE from update2.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssh/sshd_config

No updates needed to update system to 13.2-RELEASE-p11.

Why does freebsd-update fetch not indicate near end of support for version 13.2 ?

Thanks in advance.
Strange I was running 13.2 until last week and indeed freebsd-update fetch did informed me that 13.2 will be soon unsupported.
May be freebsd-update warns you before but not once the date is passed, considering the fact that today it is June30, it thinks it's already too late I don't know?
 
A month or two ago, I still had no message telling me that the version was going to expire.
Now that it is 07/01/2024, I have a message telling me that I need to upgrade.
Code:
# freebsd-update fetch
src component not installed, skipped
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 13.2-RELEASE from update1.freebsd.org... done.
Fetching metadata index... done.
Inspecting system... done.
Preparing to download files... done.
The following files are affected by updates. No changes have
been downloaded, however, because the files have been modified
locally:
/etc/ssh/sshd_config

No updates needed to update system to 13.2-RELEASE-p11.

WARNING: FreeBSD 13.2-RELEASE-p11 is approaching its End-of-Life date.
It is strongly recommended that you upgrade to a newer
release within the next 0 days.

Strange that he only warned me at the last moment :)
 
freebsd-update is just a shell script, and it looks like there is logic to not warn you too often:

/usr/sbin/freebsd-update
Code:
2153         # Don't warn if the time remaining is more than 3 times the time
2154         # since the last warning.
2155         if [ ${TIMELEFT} -gt `expr ${SINCEWARN} \* 3` ]; then
2156                 return 0
2157         fi
So maybe you ran update a few times fairly close together and it decided not to warn you again?

lasteolwarn holds the value read into $SINCEWARN, and is a file:

/var/db/freebsd-update/lasteolwarn
 
freebsd-update is just a shell script, and it looks like there is logic to not warn you too often:

/usr/sbin/freebsd-update
Code:
2153         # Don't warn if the time remaining is more than 3 times the time
2154         # since the last warning.
2155         if [ ${TIMELEFT} -gt `expr ${SINCEWARN} \* 3` ]; then
2156                 return 0
2157         fi
So maybe you ran update a few times fairly close together and it decided not to warn you again?

lasteolwarn holds the value read into $SINCEWARN, and is a file:

/var/db/freebsd-update/lasteolwarn

Thank you, I have a personal script executed by cron to notify me by email of a possible update...
Now I understand that it is normal that I did not see the warning message.
 
1719889275943.png
The author of freebsd-update stopped work on the code more than five years ago.


Typo: should be b, not d.

… typically a few weeks ahead of a version going out of support.

Yep, the Wayback Machine includes an April snapshot of a warning when someone updated from patch level 10.
 

Attachments

  • 1719888827724.png
    1719888827724.png
    135.9 KB · Views: 3
Back
Top