I've tried a few different workarounds. At first, I tried writing a script. The idea was to save a script file, on the remote computer, and then run that file from my local computer via SSH. The script would contain my "lxterminal" command. That didn't work. I get the same error message. Then I tried modifying the script so that it would wait 20 seconds, and then open the terminal. That way, after starting the script, I'd have enough time to log off. If I wasn't logged in, then maybe the remote terminal would open. That doesn't work either. What happens is the prompt disappears during the wait stage. So I'm unable to type "exit". If I close the local terminal window, the remote script stops running and it doesn't get to the next line, which is the one that tells it to open the terminal.
evansste wrote:You asked what I'm trying to accomplish. You're basically right that my goal is to start a terminal on a remote computer, and leave that computer unmanned. Basically, once the terminal is open on the remote computer, it would be running Octave on that remote computer. My Octave program runs idly, waiting for me to send information to it. The program works on the information I send it, and then sends results back to my local computer. It's basically a workaround way to accomplish parallel computing without the need to run any other software like Oscar, or any MPI protocols. It works quite well, actually. However, the way things are setup now, I have to turn on the remote computer, make sure a second monitor is connected to it, open a terminal, and start Octave and my program, before I can run my other Octave program on my local computer. It gets old having to turn on the remote computer, so I was looking for a way to write a program which will allow me to automate the process of starting the computer, opening a terminal, and starting Octave. That way, the program on my local computer, can have complete control over the remote computer without me having to worry about it.
evansste wrote:I like the idea of having the option to start the computer, and run things manually if I wanted. There have been times when I've turned on the remote computer, manually, and didn't want Octave to start. That's why I figured I'd look into a way for my program to start the computer and start octave, on its own, when I start a program. In the end, I ended up going back to setting it up so that xterm starts automatically, but it now runs my script which starts lxterminal, which then starts Octave. So I think this setup should work okay..
Users browsing this forum: No registered users and 1 guest