This is a discussion on ssh -l root hangs when i logout within the Gentoo Linux Support forums, part of the Unix Operating Systems category; --> The subject says it all. If I log onto my Gentoo laptop as root, it hangs when I log ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The subject says it all. If I log onto my Gentoo laptop as root, it hangs when I log off. This is the debug output of SSH (-vvv) when I try to log out, if it helps. debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed I can't hit C-c or anything to exit it. I have to kill the shell. Sorry I can't provide more details. --Geoff Mishkin <gmishkin@comcast.net> |
| |||
| Sorry to be replying to myself, but I meant to say also that if I SSH in as a regular user, I don't have this problem: debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug2: channel 0: rcvd close debug2: channel 0: close_read debug2: channel 0: input open -> closed debug3: channel 0: will not send data after close debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1) debug3: channel 0: close_fds r -1 w -1 e 6 Connection to 192.168.1.108 closed. debug1: Transferred: stdin 0, stdout 0, stderr 37 bytes in 1.4 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 27.0 debug1: Exit status 0 --Geoff Mishkin <gmishkin@bu.edu> |
| ||||
| Geoff Mishkin enlightened us with: > I can't hit C-c or anything to exit it. I have to kill the shell. No you don't. Hit [~] and then [?] for help. Make sure you hit ~ after a newline - hit Enter before that if you're not sure. Doesn't matter anyway, because the shell isn't responding ;-) Use [~],[&] to background your ssh session, and [~],[.] to terminate it. Next time, look it up in the SSH manual page ;-) Sybren -- The problem with the world is stupidity. Not saying there should be a capital punishment for stupidity, but why don't we just take the safety labels off of everything and let the problem solve itself? |
| Thread Tools | |
| Display Modes | |
|
|