Dwayne Litzenberger wrote: > >> It's more to do with the fact that when run through sshpass, the ssh >> process is connected to a different TTY than the one used by sshpass and >> the parent process. If passing SIGWINCH along to ssh is all it will take >> to make things work, I will gladly do it. If it takes starting to figure >> out what goes wrong and why, I somewhat doubt I'll invest the time >> (though, if you write a patch, I'll incorporate the fix into upstream, >> of course). >> > > Oh, it uses a different tty? I think there might be an ioctl that sshpass > needs to handle, then. > > So now you know how the magic is done.
I've tagged this bug "upstream". I also found the docs I should have read before (tty_ioctl(4), in case you were wondering). I'll see what I can do about this bug. Shachar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
