That is probably by design. /run is a temporary filesystem (often in RAM) and since modern network management systems treat /etc/resolv.conf as a temporary config that is constantly overwritten it makes sense to symlink it over.
But it's an interesting thing to rule out since DNS resolution will try to hit a space in memory, rather than a traditional disk IO action. Just be aware that by change the symlink you might confuse whatever network management tool you are using. -Ben On Sunday, November 3rd, 2024 at 2:58 PM, American Citizen <[email protected]> wrote: > Paul > > You might have put your finger on the problem. My resolv.conf file was > linked over to a /run folder > > > lrwxrwxrwx 1 root root 26 Sep 11 2023 resolv.conf -> > > /run/netconfig/resolv.conf > > I fixed this, and will see how my system performs now > > The two entries both to the Google public DNS servers are okay as far as > IP4 addresses are concerned > > Thank you for mentioning this > > Randall > > On 11/3/24 14:37, Paul Heinlein wrote: > > > On Sat, 2 Nov 2024, American Citizen wrote: > > > > > Tomas: > > > > > > I did a fairly good look into the /var folder. > > > > > > I don't see anything much from either the dmesg log or journalctl.log > > > > > > My system is still going into paralysis mode. For example I went to > > > edit the logs in the var/log area and vim was halted for several seconds > > > > An unlikely but possible culprit: DNS. Is the first server entry in > > your /etc/resolv.conf file valid? If so, does it resolve IPv4 and IPv6 > > queries? > > > > DNS resolution delays impact systems in unexpected ways. > > > > Like I said: unlikely, but worth checking.
