At 2:34 PM +0100 12/26/08, Martin Costabel wrote: >Harry Goldschmitt wrote: >[] >>I entered my password and then nothing. > >[] >>debug1: Entering interactive session. > >This shows that your ssh connection worked and that your shell >startup scripts are now run. > >>debug2: callback start >>debug2: x11_get_proto: /usr/X11R6/bin/xauth -f >>/tmp/ssh-CUOndFvO9e/xauthfile generate /tmp/launch-7yz9lD/:0 >>MIT-MAGIC-COOKIE-1 untrusted timeout 1200 2>/dev/null >>debug2: x11_get_proto: /usr/X11R6/bin/xauth -f >>/tmp/ssh-CUOndFvO9e/xauthfile list /tmp/launch-7yz9lD/:0 2>/dev/null >>debug1: Requesting X11 forwarding with authentication spoofing. >>debug2: channel 0: request x11-req confirm 0 >>debug2: client_session2_setup: id 0 >>debug2: channel 0: request pty-req confirm 1 >>debug2: channel 0: request shell confirm 1 >>debug2: fd 3 setting TCP_NODELAY >>debug2: callback done >>debug2: channel 0: open confirm rwindow 0 rmax 32768 > >If I run "ssh -Y -v -v xxx", I get the same (apart from the >x11_get_proto lines, which are different), but there are 5 lines in >addition to yours: > >debug2: channel_input_confirm: type 99 id 0 >debug2: PTY allocation request accepted on channel 0 >debug2: channel 0: rcvd adjust 2097152 >debug2: channel_input_confirm: type 99 id 0 >debug2: shell request accepted on channel 0 > >I don't know how to interpret this, maybe it gives you some idea. > >One observation is that you must have activated automatic >x11-forwarding somewhere in some ssh config file, because when I run >ssh without the -Y flag, I don't get the X11-related lines. Verify >the config file to make sure that there is no bug. > >Since your distant machine runs MacOSX 10.5, you could also try the >following, in order to find out which files are opened on the >distant machine: > >open a second terminal window and run there > > ssh xxx sudo filebyproc.d > >Then run your "ssh xxx" in the first window, stop the output in the >second window with ctrl-C, and look at the (long) file list if you >see something unusual or unexpected there. > >-- >Martin > > > >-- >Martin
Thanks, By some luck, I managed to get in by hitting CTL-C as fast as I could after the password prompt. I then put in echo '.bashrc', etc. in each possible script. (All were removed with my previous ssh xxx rm .bash* command.) I didn't find anything interesting but I can log in now. Any ideas why the Fink install might hang after I sudo rm -rf /sw ? Could it be that the Fink install script was seeing the same hang? Right now given the distance, I'm almost afraid to touch it. Harry ------------------------------------------------------------------------------ _______________________________________________ Fink-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fink-users
