Solved Very Slow Sudo
-
@IRJ said in Very Slow Sudo:
@DustinB3403 said in Very Slow Sudo:
Another option would be update to current and see if the issue persists.
No effect.
I already had
127.0.0.1 localhostI tried127.0.0.1 systemnameand it made no difference.Shouldn't it be
127.0.0.1 localhostand127.0.1.1 systemname -
@DustinB3403 said in Very Slow Sudo:
Everything I'm seeing for this is related to the hostname either not being in /etc/hosts or that file simply being misconfigured.
I do have some shit in my host file, so I copied it and then made a new one with just one line
127.0.0.1 hostnamestill no joy -
@black3dynamite said in Very Slow Sudo:
@IRJ said in Very Slow Sudo:
@DustinB3403 said in Very Slow Sudo:
Another option would be update to current and see if the issue persists.
No effect.
I already had
127.0.0.1 localhostI tried127.0.0.1 systemnameand it made no difference.Shouldn't it be
127.0.0.1 localhostand127.0.1.1 systemnameAs far as I know, all 127.* is the same loopback address.
-
I'll would compare
hostnamectl,/etc/hostsand/etc/hostname -
I can't find anything else besides the
/etc/hostsbeing screwy. This guy wrote a blog post on it just last year. -
If you were running the
sudocommand from root, is still slow too? -
Maybe the sudoers file is messed up?
-
Check
/etc/resolve.confIs the DNS server valid and can the machine access it and do hostname lookups?
-
@IRJ said in Very Slow Sudo:
@black3dynamite said in Very Slow Sudo:
@IRJ said in Very Slow Sudo:
@DustinB3403 said in Very Slow Sudo:
Another option would be update to current and see if the issue persists.
No effect.
I already had
127.0.0.1 localhostI tried127.0.0.1 systemnameand it made no difference.Shouldn't it be
127.0.0.1 localhostand127.0.1.1 systemnameAs far as I know, all 127.* is the same loopback address.
Ya it's the whole /8
-
@black3dynamite said in Very Slow Sudo:
I'll would compare
hostnamectl,/etc/hostsand/etc/hostnameAll have the same hostname configured.
-
@IRJ Did you check the sudoers file in
/etc/suoders -
@black3dynamite said in Very Slow Sudo:
@IRJ said in Very Slow Sudo:
@DustinB3403 said in Very Slow Sudo:
Another option would be update to current and see if the issue persists.
No effect.
I already had
127.0.0.1 localhostI tried127.0.0.1 systemnameand it made no difference.Shouldn't it be
127.0.0.1 localhostand127.0.1.1 systemnameSo when originally troubleshooting I removed
localhostand changed it tosystemnameI needed both. -
how long has systemname been a thing?
-
@Dashrender said in Very Slow Sudo:
how long has systemname been a thing?
I changed my system name like 2 months ago and thats around the time I had this issue. So yes it appears to be 100% related.
-
@IRJ said in Very Slow Sudo:
@Dashrender said in Very Slow Sudo:
how long has systemname been a thing?
I changed my system name like 2 months ago and thats around the time I had this issue. So yes it appears to be 100% related.
yeah - sorry,
My question was off topic -
I know about Localhost - I've never seen systemname before...
-
@Dashrender said in Very Slow Sudo:
@IRJ said in Very Slow Sudo:
@Dashrender said in Very Slow Sudo:
how long has systemname been a thing?
I changed my system name like 2 months ago and thats around the time I had this issue. So yes it appears to be 100% related.
yeah - sorry,
My question was off topic -
I know about Localhost - I've never seen systemname before...
I'm sure there's a good reason for both systemname and localhost assignments, or it woudlnt' be like that.
-
This post is deleted! -
suuuuuuuuuuu.......doooooooooooooooooo
-
-
@Dashrender said in Very Slow Sudo:
how long has systemname been a thing?
Seems to only appear in Debian/Ubuntu systems.
https://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution
