That's really cool...
Every *-ager should get a high school education
Even if they already know everything !
In order to log in on our office machines, we have to log in to a
gateway machine (austin) first, and from there we can log in to the
To this end, I have the following incantation in ~/.ssh/config on my
However, this leads to some zombie sshd processes lying around on
lucy. It appears that some process or other is not properly
terminated when I type "logout" at the shell on lucy, and then I get
root 686 1 0 08:57 ? 00:00:00 /usr/sbin/sshd
root 3889 686 0 12:46 ? 00:00:00 /usr/sbin/sshd
root 4241 686 0 12:56 ? 00:00:00 /usr/sbin/sshd
grossjoh 4243 4241 0 12:56 ? 00:00:00 /usr/sbin/sshd
running on lucy. What do I do?
the shell on lucy, then often I get my normal shell prompt back. But
sometimes, I don't: the shell on lucy appears to exit normally (it
executes ~/.bash_logout), but I don't get a shell prompt back.
This also extends to commands run that way: I use ssh to access a CVS
repository, and sometimes "cvs update" appears to hang after
completing its work.
I have a laptop where this problem always happens, and I have a home
machine where it seldom happens.
A large number of young women don't trust men with beards. (BFBS Radio)