I've posted the scripts I use to share a tmux session with a remote host
via socat in my wiki now. Hope it is useful and interesting to some:
http://www.torriefamily.org/~torriem/wiki/computer_stuff:shareterm
Lots of room for improvement, of course.
On 05/31/2010 04:14 PM, clemens fischer wrote:
> Cool idea! Maybe the "remote" PTY cannot operate SIGWINCH and the like
> with an ssl transport.
Well there's really no mechanism for passing the sigwinch signal through
a socket anyway, so I'm not surprised. This is the for SSL or straight
tcp/ip
On 05/31/2010 12:53 PM, clemens fischer wrote:
> I wonder why socat or some other proxy cannot transparently send this
> message like any other? Is the operating system supposed to transform
> the fd's sent so they are usable by the receiver like dup'ed ones?
I did solve my problem, and I used so
On 05/24/2010 04:06 PM, Nicholas Marriott wrote:
> tmux uses the SCM_RIGHTS OOB data mechanism to pass a file descriptor,
> socat obviously does not handle this.
>
> I'm not sure it would even be possible for it to do so.
>
> The tmux server needs a duplicate of the tty fd so it can update the
>
I have a situation where I need to use socat to tunnel the unix socket
that tmux uses. However tmux isn't happy at all with socat tunneling
stuff. Tmux server log reports "fatal: server_client_msg_dispatch:
MSG_IDENTIFY missing fd" So obviously socat isn't quite passing the
data as tmux expects.
