Peter Humphrey wrote: > On Tuesday 5 November 2024 16:27:57 GMT Grant Taylor wrote: >> On 11/5/24 9:38 AM, Peter Humphrey wrote: >>> The Network Manager man page says to 'chattr +i /etc/resolv.conf', >>> so I did, and that one move enabled the wireless network to work as >>> it should. >> What?!?!?! Network Manager can't be made to keep it's hands off of >> /etc/resolv.conf so the workaround is to leverage file system features >> to break Network Manager's hands when it tries to touch the file? >> >> That's a hell of a bad design in my opinion. > Yes, I thought it might raise a laugh... > >> The tar error will be related to the restore / write to disk, not >> reading from ""tape or command error. > I see what you mean: in my case, tar needs an --ignore-failed-write option. > >> You might explore an option to cause tar to exclude /etc/resolv.conf >> from the restore job. I'm not sure what that would look like as I'm >> usually only messing with exclude during backups. > There is an --exclude option; I can use that. > >> You might be able to mess with some even more esoteric (bind) mount >> options, but that will be quite similar to the chattr dance. >> >> I'd go smack Network Manager with a bigger bat. > I'll hold your coat... :) >
With my VPN, I needed certain entries in that file. Thing is, other stuff kept changing it. I used the resolv.conf.head and tail file to force it to do it my way and still work when the VPN is down. This may or may not be a option for you. If it is, then maybe that will help if you don't want to have issues with backups/copying etc. Dale :-) :-)
