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.
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.
