Let's say you are teaching a class with students in front of terminals all running obarun jwm and you want them to see an application opening up in their X by a multi ssh connection to their machines.

ssh# 66-olexec -d /dev/tty3 sudo -u user leafpad /home/user/.zshrc

tty3 is where X is running, tty2 is unused, if I direct this to tty2 which has no X it produces an exit 255 (can't open display), if I use tty3 nothing happens (visibly). If I do this from tty2 or tty12 on the same machine it works. If I do this from the remote and use a console command "cat /etc/66/init.conf sent to tty2 then it works, if the user hits return there they still get their login: prompt.

Any clues why this is?
Or how can you start X applications remotely (ssh)

PS I know that olexec was made for more serious tasks than this but since I found this discrepancy I can not explain I ask.
PS2 From the same machine using tty12 to send tty2 a task such as " nano /tmp/test | ls -al /home/user/ >>/tmp/test " nano really screws up the tty functionality. tty12 must terminate nano for tty2 to regain functionality.
Or how can you start X applications remotely (ssh)
https://unix.stackexchange.com/questions/12755/how-to-forward-x-over-ssh-to-run-graphics-applications-remotely
https://wiki.archlinux.org/index.php/OpenSSH# X11_forwarding
Any clues why this is?
I don't understand you're trouble here. I mean what do you expect?
PS2 From the same machine using tty12 to send tty2 a task such as " nano /tmp/test | ls -al /home/user/ >>/tmp/test " nano really screws up the tty functionality. tty12 must terminate nano for tty2 to regain functionality.
what happens if you do "nano /tmp/test | ls -al /home/user/ >>/tmp/test" as it (without the use of 66-olexec) on a terminal? The terminal is blocked... and this is normal.
I am not trying to run x on a remote machine, I want an application to run on that remote machine on its local xserver.
Somehow the examples I was giving above were working when I was trying them, they don't seem to work today when I try them again. Maybe it is sensitive to kernel functionality. I was able to send x-apps from one tty to the one that run X, but trying it through ssh it wouldn't work, but now the other way is not working either.

The example on the subject was working though!
are you sure to configure correctly your ssh configuration from server and client part?
Try to configure and run the command without the use of 66-olexec to diagnose the trouble. When you are ok, retry with 66-olexec.
It works, ssh does, both sides, but I may not know what you mean with further configuration. I run it as it comes with default settings.
I mount with sshfs and I access with ssh as terminal to remote. What else?
AFAIK the default settings do not allow ForwardX11 permissions.
Maybe yann can help you more about this. He has a good knowledge about ssh stuff

Powered by Obarun