Handling FreeRADIUS software upgrades

[Geoffrey D. Bennett]

On Thu, Nov 28, 2024 at 08:27:28AM -0500, Alan DeKok wrote:
> On Nov 28, 2024, at 4:09 AM, George Benjin <george.benjin at gmail.com> wrote:
> > The update re-added the default & inner tunnel site symlinks, as well
> > as the default eap module symlink which resulted in the service not
> > functioning as intended.
> > 
> > We resolved this quickly by deleting the symlinks again but this will
> > probably happen again with a future update.
> > 
> > What changes should we make to our config to avoid this happening
> > again? Delete the default files in the 'available' dirs? Replace them
> > with dummy content? Copy dummy files into the sites-enabled and
> > mods-enabled dirs?
> 
>   After a quick look at the capabilities of RPM, it doesn't look like it's easy to fix this.  i.e. there's no trivial way to say "install these files, but only if the parent directory doesn't already exist".
> 
>   The simplest way to fix this with minimal changes is to just create the problem files, but with zero content.  They won't be over-written on any new install.

+1. That's what we do:

rm -f default inner-tunnel
touch default inner-tunnel

rm -f eap
touch eap