Lag when SSHing to machine

Waris · 08-04-2017, 05:15 PM

Quote:

Originally Posted by MensaWater

If your responses ended with "IN A" after the host names it means they did NOT resolve so that may be your problem. Are your AD server and workstation in domain tang.com? If not did you type in the fully qualified domain name (FQDN) for each (i.e. servername.domainname)?

You're use of rpm command is slightly off.

rpm -qa will show ALL RPM packages - you can run "rpm -qa |grep systemd" to see all packages with systemd in the namme.

When you know the name of the package you can just specify that:
rpm -q systemd

You're not looking to see if you have exactly systemd-219-36.el7 but rather at least that version
So if for example you ran "rpm -q systemd" and it responded with systemd-219-19.el7_2.4.x86_64 that is version 219-19 which is earlier than 219-36 so you'd want to run "yum update systemd" to get the latest package.

On my test system doing that just now installed version 219-42. After the update "rpm -q systemd" now shows:
systemd-219-42.el7.x86_64

Since the link is restricted to RedHat subscribed users I can't put its contents here. It doesn't specifically talk about the issue you are having so may not be involved and the only reason I saw it was because I'd never noticed RHEL7 added that last item to hosts: line in nsswitch.conf before.

Thank you for the correction. Still fairly a newbie with Linux. But yes, I just ran rpm -qa systemd like you said it didnt get anything in return. which probably means it not install, im just afrade that it might change something if i install the systemd package. what do you think, rather what does it exactly do?And also, Yes the dig command, it ends with "IN A" after the host. So how could i go on about setting the DNS? Thank you so much for all the input, i really appreciate the help! Thank you!

Waris · 08-04-2017, 05:16 PM

Quote:

Originally Posted by MensaWater

If your responses ended with "IN A" after the host names it means they did NOT resolve so that may be your problem. Are your AD server and workstation in domain tang.com? If not did you type in the fully qualified domain name (FQDN) for each (i.e. servername.domainname)?

You're use of rpm command is slightly off.

rpm -qa will show ALL RPM packages - you can run "rpm -qa |grep systemd" to see all packages with systemd in the namme.

When you know the name of the package you can just specify that:
rpm -q systemd

You're not looking to see if you have exactly systemd-219-36.el7 but rather at least that version
So if for example you ran "rpm -q systemd" and it responded with systemd-219-19.el7_2.4.x86_64 that is version 219-19 which is earlier than 219-36 so you'd want to run "yum update systemd" to get the latest package.

On my test system doing that just now installed version 219-42. After the update "rpm -q systemd" now shows:
systemd-219-42.el7.x86_64

Since the link is restricted to RedHat subscribed users I can't put its contents here. It doesn't specifically talk about the issue you are having so may not be involved and the only reason I saw it was because I'd never noticed RHEL7 added that last item to hosts: line in nsswitch.conf before.

Thank you for the correction. Still fairly a newbie with Linux. But yes, I just ran rpm -qa systemd like you said it didnt get anything in return. which probably means it not install, im just afrade that it might change something if i install the systemd package. what do you think, rather what does it exactly do?And also, Yes the dig command, it ends with "IN A" after the host. So how could i go on about setting the DNS? Thank you so much for all the input, i really appreciate the help! Thank you!
windows_10 Waris is online now

TheEzekielProject · 08-04-2017, 05:27 PM

Quote:

Originally Posted by Waris

But yes, I just ran rpm -qa systemd like you said it didnt get anything in return. Thank you!

Note that

Code:

rpm -qa |grep systemd

is different from

Code:

rpm -qa systemd

.

And being that you are on CentOS. You almost certainly have systemd installed as systemd is the init system and is not trivial to replace on most systems.

MensaWater · 08-05-2017, 11:01 AM

I fear you missed what I was saying. TheEzekialProject caught it.

My post was saying you can use rpm -qa to list all packages but must then pipe (|) into the grep command specifying the one you want (systemd in this case):
rpm -qa | grep systemd
--OR--
You can leave off the -a flag so it is only "rpm -q" at which point you can just give it the name of the package:
rpm -q systemd