Search results

No, it doesn't. Reference: https://www.howtogeek.com/449691/what-is-swapiness-on-linux-and-how-to-change-it/ Trying to “disable swap” by setting the Linux swappiness value to zero simply shifts the swap-associated hard drive activity to file-associated hard drive activity.

No no no, it's not that simple. Please, please read here: https://www.howtogeek.com/449691/what-is-swapiness-on-linux-and-how-to-change-it/

Might I suggest more reading, because doing this most definitely isn't doing what you think it is: https://www.howtogeek.com/449691/what-is-swapiness-on-linux-and-how-to-change-it/

Apologies, that's exactly what I meant. My bad. Forgive me, but I don't just get why it doesn't both: Wildcard bind (as it already does as above) Bind in all families After doing a little more reading, it seems the right, or more optimal way, at least with Linux, is to use IPv4-mapped IPv6...

So, digging some more into PVE/Service/pveproxy.pm (and hence PVE/Tools.pm (and haven't delved deeper)), but it would seem to me this line is the issue? sub get_host_address_family { my ($hostname, $socktype) = @_; my @res = getaddrinfo_all($hostname, socktype => $socktype); return...

I would like to know why mine's doing the same thing. My config is similiar (exact same version), only using openvswitch. Adding my IPv6 address to /etc/hosts made it then only bind to the v6 address. Additionally, now that I've populated my DNS with AAAA records, I can't run consoles now, as...