On 2005-10-28 14:12:26 +0100, Dave Korn wrote:
> Dunno what's recommended, but I expect you should be able to come
> up with a combination of ps/grep/awk/cut that you could put in a
> backtick as an argument to "kill -9" in your .logout file, perhaps?
I use lsof. With zsh:
for file in /tmp/ssh-
Richard Kenner wrote:
> Note that the open connection has your authentication tokens to the
> remote server. If you leave the machine where you started the master
> SSH session, you should usually kill it. "
>
> I missed that part.
>
> So what's the recommended way to kill it? I adde
Note that the open connection has your authentication tokens to the
remote server. If you leave the machine where you started the master
SSH session, you should usually kill it. "
I missed that part.
So what's the recommended way to kill it? I added the ssh -M command to my
.login.
Richard Kenner wrote:
> When I do it, it looks like after I log out, something is still running.
> Is there something I have to stop?
Yep.
http://gcc.gnu.org/wiki/SSH%20connection%20caching
" To create the socket, you need to open a master connection. Just ssh to
gcc.gnu.org using the Contro
When I do it, it looks like after I log out, something is still running. Is
there something I have to stop?
On Thursday 27 October 2005 21:22, Richard Kenner wrote:
> It says it is *recommended* that $HOME/.ssh/config have permission 600.
> However, I seem to get an error if it doesn't, so I think this should be
> "required", not "recommended".
There's also a reason why it's a wiki.
Paul
It says it is *recommended* that $HOME/.ssh/config have permission 600.
However, I seem to get an error if it doesn't, so I think this should be
"required", not "recommended".
