Re: [PATCH proposal] FISH: don't let ssh write its ouput tothecontrolling tty
Hi,
patch works fine for logging through username password, but
not for rsa keys. MC successfully logs to the remote host but
does not know about it. I think, that this option is not
taken into account in the patch.
Adding hostkey works fine.
Tested on Linux.
Why are the pty_open_{slave,master} funcs moved from subshell.c
to utilunix.c
bye
/dave
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH proposal] FISH: don't let ssh write its ouput tothecontrolling tty
Hi, patch works fine for logging through username password, but not for rsa keys. MC successfully logs to the remote host but does not know about it. Does not know about what ? If it doesn't know the host a dialog box should appear and ask the user to confirm its identity. Are you saying that this box doesn't pop up ? Hm, I am trying to say, that MC freezes (I should have been more precise, sorry). The remote host is up and running. The spawned ssh proces apears in 'ps' list. Killing the ssh returns MC into normal operation (the shell link is not established). bye /dave ___ Mc-devel mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/mc-devel
Re: [PATCH proposal] FISH: don't let ssh write its ouput tothecontrolling tty
Hello!
Why are the pty_open_{slave,master} funcs moved from subshell.c to
utilunix.c
I use them in fish.c and though that if they are to be shared between
fish.c and subshell.c it makes more sense move them into a common place.
That's right.
Btw which is the corresponding header file for utilunix.c ?
Both util.c and utilunix.c use util.h. This is done so that the Windows
port can use common util.c but provide it's own implementation of
utilunix.c.
The Windows port doesn't use VFS and doesn't need pseudoterminals, so
utilunix.c is the right place for those functions.
--
Regards,
Pavel Roskin
___
Mc-devel mailing list
[EMAIL PROTECTED]
http://mail.gnome.org/mailman/listinfo/mc-devel
