Watch the output before hitting Y on apt dist-upgrade or whatnot, it will tell
you exactly what it will do
What I also found useful handling systems that I didnt set up or set up too
long ago to remember is to use dlocate and dpkg —verify
sudo find /etc/ -type f -o -type l | xargs dlocate
if the file is not there then it’s a custom file, so you can do something like
sudo find /etc/ -type f -o -type l | xargs dlocate | awk '{ print $(NF) }’ >
/tmp/files
sudo find /etc/ -type f -o -type l | fgrep -vf /tmp/files
and then go through the list to find anything unusual
also
sudo dpkg --verify
will give you files that do belong to a package but were changed from their
original values.
> On 8. Feb 2022, at 20:29, Bo Berglund <bo.bergl...@gmail.com> wrote:
>
> On Tue, 8 Feb 2022 18:19:05 +0000 (UTC), Leroy Tennison via Openvpn-users
> <openvpn-users@lists.sourceforge.net> wrote:
>
>> This doesn't directly answer your question but we have done what you are
>> about
>> to do and didn't have any problems. In our situation OpenVPN ran on a VM so
>> we
>> did a backup of the image beforehand.
>
> I cannot do this since I cannot attach a new disk to the system from over here
> to transfer the backup to.
>
>
>> Ubuntu is pretty good about not replacing configuration files with
>> customizations
>> without prompting first.
>> A tar of /etc/openvpn would be a good idea.
>
> I am not really concerned with the configuration files there, I have them
> pretty
> much handled.
> But there are other files in other places that worry me more...
>
> What I do not know is if the upgraded system would be *without* OpenVPN if it
> was not installed via the Ubuntu repositories since it seems like the upgrade
> removes the special repos from apt. Will that also remove openvpn itself from
> the system? That is a no-no!
>
> Or will it use the standard Ubuntu repo version? That is basically OK provided
> the system will run even though the current installation is not adhering to
> the
> new paradigm where there are server and client dirs in /etc/openvpn and
> xxx.conf
> files in each of these will start the corresponding service.
>
> This is OK when I do a new install but not so when I deal with upgrading an
> old
> system that was configured the "old" way.
>
>> If you're concerned about uninterrupted operation I don't know that there's
>> much
>> you can do. Might be time to set up a backup system and plan a time/pay the
>> price for a couple of two-minute outages at an opportune time.
>>
>
> This is not a concern. I can do it from over here during off-times in the USA
> (middle of the night).
> I also have a secondary OpenVPN server running on a RaspberryPi device on the
> LAN, which I use if I have to do work on the main vpn server.
> I plan on using that during the upgrade.
>
>
> --
> Bo Berglund
> Developer in Sweden
>
>
>
> _______________________________________________
> Openvpn-users mailing list
> Openvpn-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-users
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
