Every day now and then, I get an scp command wrong. Scp is designed after commands like rcp and works totally fine for local-to-local file copy. While this can (or could) be useful in some contexts, It's not what I like to do these days; very often, if either hosts
This is another old trick, but I like to tell the world about such amenities. I often find people writing command lines such as: ssh email@example.com or, worse ssh firstname.lastname@example.org or maybe it was ssh email@example.com yes,
UPDATE: modern ssh-copy-id often support a -p parameter for the port. So this trick is unnecessary and won't probably work. ssh-copy-id is a cool script which is usually distributed along openssh client nowadays; it performs an automatic install of your local public SSH key to a remote server. Its syntax
If you develop enough software, most probably you'll have a test/development network at your service. In such networks, which are usually handled through a virtualization infrastructure, machines come and go very quickly. But ssh clients are usually unhappy about that: alan@melquiades:/etc/ssh$ ssh firstname.lastname@example.org.
Bash builtin disown is a not-so-well known [job control command] http://www.gnu.org/software/bash/manual/html_node/Job-Control-Builtins.html), and yet it's an extremely useful one. So what? You've started a remote ssh session, launched some command which is taking very, very long to complete, and you just