Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I logged into the remote computer via 'ssh root@<remoteIP>' and when typing the root password, I got the '#' prompt. Then I typed in a console 'shutdown -h now', the remote computer was really shutdown, but my local console was frozen (I am using a text console). I had to 'Ctrl+Alt+F2' to switch to another terminal to continue my work. Does anyone know how to fix this problem?
Sometimes this happens to me also... you can avoid the problem by scheduling the shutdown, in order to have enough time to logout before the shutdown begins (see the manpage of the shutdown command).
When the console is frozen, you can always find the associated ssh process and kill it with a -9 signal or another "violent" signal.
Sometimes this happens to me also... you can avoid the problem by scheduling the shutdown, in order to have enough time to logout before the shutdown begins (see the manpage of the shutdown command).
When the console is frozen, you can always find the associated ssh process and kill it with a -9 signal or another "violent" signal.
Thank you for you reply. It could have many solutions,but I want to know the reason. Sometimes it exited with "closed by remote session", sometimes it is frozen.
tred@vaio:~$ ssh server
tred@server:~$ sudo -i
Password:
root@server:~# shutdown -h now
Broadcast message from root@server (pts/1) (Sat Nov 8 19:51:03 2008):
The system is going down for system halt NOW!
root@server:~# Connection to server closed by remote host.
Connection to server closed.
tred@vaio:~$
My version of ssh is 1.4.7. Maybe you need to update yours?
And you should not have root logins by ssh enabled. Do it as I have done, above: First login as yourself, then gain root privileges. root logins should be DENIED to ssh
Last edited by tredegar; 11-08-2008 at 01:59 PM.
Reason: Don't enable root logins
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.