I think that I have a track. Based on similar "su" problems, I decided to explore the possibility that it is the fault of "dbus". Based on results below, I believe it to be the case and I reassign this issue to "dbus". Restarting dbus fixes this issue.
So I did:
1) time how long ssh to localhost takes:
==>time ssh localhost date
Thu Nov 20 22:55:54 CST 2008
real 0m0.248s
user 0m0.000s
sys 0m0.004s
2) Restarted dbus as root:
root:~ ###/etc/init.d/dbus restart
* Stopping System Tools Backends system-tools-backends
...done.
* Stopping bluetooth
...done.
* Stopping Hardware abstraction layer hald
...done.
* Stopping system message bus dbus
...done.
* Starting system message bus dbus
...done.
* Starting Hardware abstraction layer hald
...done.
* Starting bluetooth
...done.
* Starting System Tools Backends system-tools-backends
...done.
(this killed gnome-panel and stuff also, no biggy)
3) tried ssh again:
==>time ssh localhost date
Thu Nov 20 22:56:06 CST 2008
I think that I have a track. Based on similar "su" problems, I decided to explore the possibility that it is the fault of "dbus". Based on results below, I believe it to be the case and I reassign this issue to "dbus". Restarting dbus fixes this issue.
So I did:
1) time how long ssh to localhost takes:
==>time ssh localhost date
Thu Nov 20 22:55:54 CST 2008
real 0m0.248s
user 0m0.000s
sys 0m0.004s
2) Restarted dbus as root:
root:~ ###/etc/init.d/dbus restart tools-backends tools-backends
* Stopping System Tools Backends system-
...done.
* Stopping bluetooth
...done.
* Stopping Hardware abstraction layer hald
...done.
* Stopping system message bus dbus
...done.
* Starting system message bus dbus
...done.
* Starting Hardware abstraction layer hald
...done.
* Starting bluetooth
...done.
* Starting System Tools Backends system-
...done.
(this killed gnome-panel and stuff also, no biggy)
3) tried ssh again:
==>time ssh localhost date
Thu Nov 20 22:56:06 CST 2008
real 0m0.268s
user 0m0.000s
sys 0m0.008s
So restarting dbus fixed this issue.