I don't stand a few thinks, but generally yes...
I just come, read that answer, and i take like a joke... i think that if i question how be sure to don't restart before do right, it was standing that i can't do that without problem...
If my attitude make problems with this post, sorry... but im not be here for make problems or somthing else that someone can thinkg, i trying to stand and when i know more of coding and have some time i will try to help more seriusly.
The think that isn't ispCP related i stand pefectly, sorry i just go to search some and question in another place more correct for my question.

rbtux: Thanks a lot man! ... i just try to create another ssh inteface, or first try hard the restart in a virtual OS

Ok... I probably overreacted. Shame to me.

Just follow what kilburn said and you won't have any problems. it's a minor fix, not a major upgrade.

ispcomm.

@ispcomm:

well when just reading his post and don't take in credit his poor english, make the post look rude... I don't think that it was meant like it reads...

Quote:rbtux: Thanks a lot man! Big Grin ... i just try to create another ssh inteface, or first try hard the restart in a virtual OS Smile

rbtux, I can't see your solution in the posts, did you pm him?

Quote:i think that if i question how be sure to don't restart before do right, it was standing that i can't do that without problem...

What you didn't understand is that your currently stablished ssh connections are not closed when you restart sshd, even if you've changed the key. That's why I said

Kilburn Wrote:... try to open a new ssh session ...

If it doesn't work, you still have the previously opened connection to fix the problem, so no physical access to the server (wich most of us don't have).

Cheers.