fc-remote from fc-remote doesn't work properly anymore

[Herrmann Hofer]

Hello Brian,

I'm connecting to a second computer via ssh pi08 -t fc-remote, from a terminal already running fc-remote on the first machine. This works perfectly well, until you try to execute a command. The first time, the error "Error setting pty master. Operation not permitted" is shown. Every other attempt causes the error "Error opening ptslave. Input/output error", not matter what program you try to run (ls, ps, ...).

This has been working without problems up to the version of Sept. 26, 2023 (vgit-1828)

(Starting ssh without the -t parameter results in a hung connection).

Starting a second local fc-remote (e.g. with sudo fc-remote) works without problems.

And it's only important which version the target (second) machine is running. The version of fc-remote on the first computer doesn't make a difference.

The reason I am running things this way is, that the first machine is the only one exposed to the internet. I know that I could tunnel through ssh in a second terminal, but sometimes is just convenient (e.g. via menu entries) to quickly connect to another machine on the local network.

Regards and Thanks!

[Herrmann Hofer]

Hello Brian,

I'm wondering if you ever found something out about this problem.
I just tried the vgit-1860 version and the problem still persists. It's the reason I'm still using fc-remote from vgit-1828 on all my Linux machines...

Regards and keep up the wonderful work!

[Herrmann Hofer]

Hello Brian,

Actually, I found a workaround that works for most of my servers:

I'm creating fc-remote.mnu entries that look like these:

// ...

1: vps01

    ssh -t vps01 sudo -u $(id -un) fc-remote

2: vps02

    ssh -t vps01 sudo -u $(id -un) fc-remote

// ...

The sudo-wrapper, using my own user name, creates an additional new pty on the target machine, that doesn't seem to have the limitations I mentioned in the o.p.

Unfortunately, this doesn't work on machines that do not have a working sudo, like my LibreELEC media servers. But that's not that important - as long as the vgit-1828-version still runs on them.

Regards again!